You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, is there an explanation on how the governance contracts are pieced together?
I managed to get it working only by replacing the delegatecall method inside DelegateTo function in the Delegator contract into a 'simple' call method. Initialization of delegate-contract kept failing because it seemed the function was using the storage of the delegator instead of that of delegate. The delegatecall method brings along the storage of the caller, i read then, so i replaced it with call and got the initialisation to work. In my current setup delegator is the admin of delegate and delegate is the admin of timelock.
I managed to write proposald, castvotes, queue the proposal. Now i am trying to write a proposal that executes. This gets reverted in the timelock:
Hi, is there an explanation on how the governance contracts are pieced together?
I managed to get it working only by replacing the delegatecall method inside DelegateTo function in the Delegator contract into a 'simple' call method. Initialization of delegate-contract kept failing because it seemed the function was using the storage of the delegator instead of that of delegate. The delegatecall method brings along the storage of the caller, i read then, so i replaced it with call and got the initialisation to work. In my current setup delegator is the admin of delegate and delegate is the admin of timelock.
I managed to write proposald, castvotes, queue the proposal. Now i am trying to write a proposal that executes. This gets reverted in the timelock:
propose(
[],
[0],
["_setProposalThreshold(uint256)"],
[web3.eth.abi.encodeParameters(["uint256"],[33])],
"set proposal threshold to 33"
);
Now i am wondering whether i made a wrong assumption before and doing it all wrong. ..
Suggestions a highly appreciated!
Thanks, Joera
The text was updated successfully, but these errors were encountered: