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
Create a erc20 wrapper contract that implements bridge pool base logic
deployment: bridge pool factory, non-upgradeable eip 1167 thin proxy
This contract should Implement the following:
Upgradeable ERC20 logic such that variables will be set with a initializer function that only BridgePoolFactory may call once in the life time of the contract.
A withdraw function only callable by BridgeRouter that calls the base bridgePool withdraw function, on successful validation of proofs, this contract should mint a wrapper token to the user.
A deposit function only callable by BridgeRouter that takes in msgSender address, abi enconded data that describes the deposit, decodes the data to extract token amount and burn the balance from owner, encode the event data and return the data to bridgeRouter so deposit event can be emitted
Acceptance criteria
The text was updated successfully, but these errors were encountered:
z-j-lin
changed the title
ERC20 External Bridge Pool Wrapper Token Contract
Draft ERC20 External Bridge Pool Wrapper Token Contract
Nov 11, 2022
Create a erc20 wrapper contract that implements bridge pool base logic
deployment: bridge pool factory, non-upgradeable eip 1167 thin proxy
This contract should Implement the following:
Upgradeable ERC20 logic such that variables will be set with a initializer function that only BridgePoolFactory may call once in the life time of the contract.
A withdraw function only callable by BridgeRouter that calls the base bridgePool withdraw function, on successful validation of proofs, this contract should mint a wrapper token to the user.
A deposit function only callable by BridgeRouter that takes in msgSender address, abi enconded data that describes the deposit, decodes the data to extract token amount and burn the balance from owner, encode the event data and return the data to bridgeRouter so deposit event can be emitted
Acceptance criteria
The text was updated successfully, but these errors were encountered: