governorOnly()modifier in the Euler Governance module smart contract will be checking that the caller of its functions is the Euler mulisig and not the TimelockController smart contract.
batchDispatch()function) and use this hex data as the input to the target function in the stub smart contract when creating a proposal on Tally.
governorOnly()modifier in the Euler Governance module smart contract will be checking that the caller of its functions is the TimelockController smart contract.
Execmodule via the Euler multisig (on OpenZeppelin Defender).
batchDispatch()function) and use this hex data as the input to the target function in the stub smart contract when creating a proposal on Tally (this is described in Section 2 below).
CREATE PROPOSAL DATA. Once we do this, we should see the markdown table showing the changes we want to make to the asset. We will also see the batch items Hex transaction data which we need for our on-chain governance proposal stub smart contract on Tally.
CREATE PROPOSAL DATA. The list of configuration updates is updated to reflect the change we are making to DAI, while the USDC update information still remains. The transaction hex is also updated.
DEBUG TX HEX DATAand paste the copied hex into the text field.
Create new proposalat the right corner of the window.
Continueto move onto the next step (
Name your proposal).
Add custom action=> enter the stub smart contract address as the target smart contract. Then select the
executeProposalfunction from the dropdown menu under
contract methodas the target function in the target smart contract. Here is the interesting part: enter the required parameters, i.e., proposal description string and the proposalData which is your proposal transaction hex data from Section 1.
Submit on-chainwhich will open a MetaMask pop-up window for you to sign the transaction to create the proposal on-chain, via the Governance smart contract.