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
We have already exposed some native functionalities to EVM smart contracts through events with special signatures.
This proposal adds a new one to the family: __BankModuleTransfer(bytes from, bytes to, uint256 amount), it gives full control of a denom named after the contract address in bank module to the evm contract, the denom is named as crc20{contract_address}.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
We have already exposed some native functionalities to EVM smart contracts through events with special signatures.
This proposal adds a new one to the family:
__BankModuleTransfer(bytes from, bytes to, uint256 amount)
, it gives full control of a denom named after the contract address in bank module to the evm contract, the denom is named ascrc20{contract_address}
.Implementation
The event handler in native module:
How it's used in solidity:
Security
DDos Attack
The cost of the bank module is not reflected in the gas consumption calculated by the EVM, could be vulnerable to abusive usage.
Beta Was this translation helpful? Give feedback.
All reactions