Help to encode data to use the Timelock

rafaelhernandez · July 21, 2021, 5:44pm

Hello!
I am currently trying to use a timelock to queue / execute transactions in a "masterchef" contract.
The thing is, using functions through a timelock is very different. I am asked for these parameters:

target = the address of the contract where the function is located
value = MATIC used on the transaction (currently 0)
signature = the function I want to execute
data = here is the issue. I dont know how to format the parameters of the function to byte32
eta = current block + delay

Example:

Trying to add a pool in (0x67acAa79F5F33496ac0e9C2D1876F8C3AdC28FeD)
with this timelock (0xfa6eA85eb982C9988653835C3CabB5C14ef6Cf75)

target = 0x67acAa79F5F33496ac0e9C2D1876F8C3AdC28FeD
value = 0
signature = add(uint256,address,uint16)
data = ??
eta = (Current block + 43200 + small number to have some spare time)

Can someone explain me how to get the parameters

_allocPoint = 35
_lpToken = 0x35a991d3D522dc5eE89Be334798CA2788DDf0fB9
_depositFeeBP = 400

in byte32 to make the transaction? Thanks!

Already tried https://abi.hashex.org , but the timelock just tells me the data is wrong

spalladino · July 22, 2021, 12:46pm

Hey Rafael! I'd suggest you check out the tests for the Timelock contract in the repository, they should help in understanding how to craft txs to be sent via the timelock:

github.com

OpenZeppelin/openzeppelin-contracts/blob/master/test/governance/TimelockController.test.js

const { BN, constants, expectEvent, expectRevert, time } = require('@openzeppelin/test-helpers');
const { ZERO_ADDRESS, ZERO_BYTES32 } = constants;
const { proposalStatesToBitMap } = require('../helpers/governance');

const { expect } = require('chai');

const { shouldSupportInterfaces } = require('../utils/introspection/SupportsInterface.behavior');
const { expectRevertCustomError } = require('../helpers/customError');
const { OperationState } = require('../helpers/enums');

const TimelockController = artifacts.require('TimelockController');
const CallReceiverMock = artifacts.require('CallReceiverMock');
const Implementation2 = artifacts.require('Implementation2');
const ERC721 = artifacts.require('$ERC721');
const ERC1155 = artifacts.require('$ERC1155');
const TimelockReentrant = artifacts.require('$TimelockReentrant');

const MINDELAY = time.duration.days(1);

const salt = '0x025e7b0be353a74631ad648c667493c0e1cd31caa4cc2d3520fdc171ea0cc726'; // a random value

This file has been truncated. show original

This guide may also help:

A simpler alternative could be using Defender. We recently added support for Timelocks on Defender Admin. You can get a free individual account that works fine on Matic to run txs through a Timelock. Let us know if that works for you!

Topic		Replies	Views
Interact with MasterChef, through Timelock Support	7	1174	April 21, 2021
How to interact with mastercheft through TimeLock Contracts	17	1799	January 27, 2022
Timelock: queueTransaction, queuedTransactions and executeTransaction Support	6	895	July 8, 2021
How to interact with a smart contract MasterChef when the Owner is TimeLock? Support	16	3769	July 1, 2021
Error in Timelock using TimelockCrontroller Contracts	4	483	May 5, 2023

Help to encode data to use the Timelock

Example:

Related topics