Skip to main content

Setting controllers

Understand how to set or unset a controller contract.

It’s important to note that when the owner explicitly sets the controller (using the registry's setController), a new controller contract will be used and no longer abide by the default permissions. This is "setting" the controller. To "unset" the controller back to its original value, set it back to the 0x0 address—thus, default permissions will go back into place.

Registry methods​

The TablelandTables registry smart contract has three dedicated controller methods, which are helpful to understand within this context. See the registry docs for more details.

Setting the controller​

The owner of a contract needs to call the Tableland registry’s setController method to register a deployed policy onchain.

function setController(
  address caller,     // The table owner's address.
  uint256 tableId,    // Unique `tableId`, as defined in `prefix_chainId_tableId`
  address controller  // Contract address that implements `ITablelandController`
)

In cases where a table is owned by a smart contract, you can also call the setController method from the smart contract. Here, adding a policy update method that can be called after deploy (where the onlyOwner modifier is from a useful Ownable OpenZeppelin contract):

function updateController(uint256 tableId) public onlyOwner {
   TablelandDeployments.get().setController(
      address(this),
      tableId,
      address(this)
    );
}

If you want to ever check the controller, you could use the getController to, for example, check the current controller and only set a new one if it is different than expected.

function updateController(uint256 tableId) public onlyOwner {
  address currentController = TablelandDeployments.get().getController(tableId);
  if (currentController != address(this)) {
    TablelandDeployments.get().setController(
      address(this),
      tableId,
      address(this)
    );
  }
}

And recall that if you want to undo this, you can set it to zero address (0x0...0).

Locking the controller​

In order to permanently set a controller, the lockController method will make it so that a controller can never be updated. This is an irreversible operation to help trustlessly guarantee a table's mutability rules.

function lockController(uint256 tableId) public onlyOwner {
  TablelandDeployments.get().lockController(
    address(this),
    tableId
  );
}

Getting the controller​

If you want to check what address is the table's controller, the getController method will return the address.

function getController(uint256 tableId) public view returns (address) {
  return TablelandDeployments.get().getController(tableId);
}

Using JavaScript​

If you are using a development framework, like hardhat, or simply using a library like ethers, you can make smart contact calls directly to the Tableland registry smart contract to set the controller. This can occur in some script that connects to the one of the deployed registry contracts and calls one of the controller methods.

The Tableland SDK also offers a Registry API to handle registry smart contract calls, too.

Using a block explorer​

If you are just playing around, you can also call the setController method on something like Etherscan by going to the Tableland registry contract directly (you’ll need to call the method from the address of the table owner).