0017-allow-batching-calls-staking-contract
Last updated
Was this helpful?
Last updated
Was this helpful?
Expose a way to batch multiple calls into a single transaction. It provides great flexibility for indexer agents to combine multiple functions in different ways. It also reduce the gas cost by saving the initial gas, and in some cases, accessing a "used" slot by the other bundled transactions.
A new contract called MultiCall is introduced, inspired by the one used by Uniswap. The payable keyword was removed from the multicall() as the protocol does not deal with ETH. Additionally, it is insecure in some instances if the contract relies on msg.value.
The Staking contract inherits from MultiCall that expose a public multicall(bytes[] calldata data) function that receives an array of payloads to send to the contract itself. This allows to batch ANY publicly callable contract function.
By using a multicall a user can batch an arbitrary number of operations into a single transaction. The indexer agent can combine close, open, claim transactions in any way it sees more effective.
See
The proposal introduces some breaking changes to save bytecode.
The following functions are removed as they can be constructed using a multicall:
closeAllocationMany()
closeAndAllocate()
claimMany()
The implementation was audited by Consensys Diligence.
The implementation has not yet been deployed to Testnet.
Copyright and related rights waived via .