First thing, the
ADMIN role has the same permission as the
FOUNDER role, so it might not be necessary to assign the account that created the colony (the
FOUNDER) as an
ADMIN unless you plan to transfer the
FOUNDER role to another account. See Permissions for Colony Client methods.
That being said, you should still be able to set the account assigned the
FOUNDER role as an
ADMIN. This is currently possible in the colony-starter-react (soon to be renamed
colony-example-react package). You can test it by running the following:
yarn global upgrade @colony/colony-starter
colony build colony-starter-react
This might be related to a mismatch in versions but the only reason I can think of for a revert error would be assigning the
ADMIN role when calling the method from an instance of
colonyClient where the account is not assigned the
FOUNDER role (the account that created the colony).
The colony-starter-react package is currently using the following versions of colonyJS packages:
And the following version of colonyNetwork (the commit hash):
This commit hash includes the current version of the colonyNetwork smart contracts deployed to rinkeby and we will continue using this as the latest recommended version for the remainder of the month, then we will be upgrading to a new version of the colonyNetwork smart contracts once we deploy a new version to rinkeby (the version that will be the
glider release - the first release on mainnet deployed the following month).