Timelock contract

Contracts addresses

Delay is set to 24 hours : The Koala's dev team can't make any change on Masterchef contract (in charge of farms and pools of Koala DeFi) without queuing them at least 24h before execution. With this delay, the community has the time to look at any modification on farms, pool and emission rate before execution.
Timelock contract is the owner of Masterchef contract : You can check into read function of Masterchef contract (7-owner) that our Timelock contract is indeed this one : 0x4fdBd2982BDb512B293C7cd14a6B580Eb80Cb552
You can find and read the code here :
Contract Address 0x4fdbd2982bdb512b293c7cd14a6b580eb80cb552 | BscScan
Binance (BNB) Blockchain Explorer

Timelock contract source and last commit on Github

Here is the last update of the contract when put in production with 24 hours delay
Update Timelock contract with 24 hours delay · koaladefi/[email protected]
GitHub
Here is the contract creation transaction from the Koala Deployer adresse :
Binance Transaction Hash (Txhash) Details | BscScan
Binance (BNB) Blockchain Explorer

Understanding a Timelock transaction

This information is to help our community to understand a Timelock transaction when the transaction is queued into the Timelock for a future execution. Koala DeFi will post each transaction queued on Twitter but this will help people to double check that the changes on Masterchef contract is ok.
Here is a transaction example (this transaction have been queued for example and will not be executed) :
Binance Transaction Hash (Txhash) Details | BscScan
Binance (BNB) Blockchain Explorer
To have a look to the transaction :
1 click to view details :
2 click to decode input data :
3 read and understand transaction datas :
    target : is the Masterchef contract address
    value : 0 (is not used)
    signature : updateEmissionRate(unint256) : This one is important : It is the Masterchef contract's function that can be executed after the delay (24h on Koala DeFi Timelock contract). In this example, the transaction will change the number of Lyptus created per block (no change in this example case because the value is equal to 1)
    data : This one is important also : It's the value (or series of value) that will be passed into the function parameters. The value is encoded in hexadecimal and on 64bits. In this example, the value is 0000000000000000000000000000000000000000000000000de0b6b3a7640000 (in Hexa) and equal to 1000000000000000000 (in decimal) (your can use this tool to make the conversion). Then the decimal value need to be divided by 10e18 : 1000000000000000000/10e18 = 1 --> This result means that the Lyptus per block value will be equal to 1 if the transaction is executed.
Last modified 6mo ago