Comment on page
BEP-20 Compatibility
The BEP20 specification defines a list of API functions (and relevant events) that each token contract is expected to implement (and emit). The failure to meet these requirements means the token contract cannot be considered to be BEP20-compliant. In this section, we examine the list of API functions defined by the BEP20 specification and validate whether there exists any inconsistency or incompatibility in the implementation of the inherent business logic of the audited contract(s)
| Expected Functionality | Description according to the BEP20 Standard | Compatible |
name |
| Returns the name of the token. | ✓ |
symbol |
| Returns the symbol of the token. | ✓ |
decimals |
| Returns the number of decimals used to get its user representation | ✓ |
totalSupply |
| Returns the number of tokens in existence. | ✓ |
balanceOf |
| Returns the number of tokens owned by account . | ✓ |
allowance |
| Returns the remaining number of tokens that spender will be allowed to spend on behalf of owner through transferFrom . | ✓ |
transfer | transfer() is declared as a public function | Moves amount tokens from the caller’s account to recipient .Returns a boolean value indicating whether the operation succeeded. | ✓ |
transferFrom |
| Moves amount tokens from sender to recipient using the allowance mechanism. amount is then deducted from the caller’s allowance.Returns a boolean value indicating whether the operation succeeded. | ✓ |
approve |
| Sets amount as the allowance of spender over the caller’s tokens.Returns a boolean value indicating whether the operation succeeded. | ✓ |
Transfer Event |
| Emitted when value tokens are moved from one account (from ) to another (to ).Note that value may be zero | ✓ |
Approval Event |
| Emitted when the allowance of a spender for an owner is set by a call to approve . value is the new allowance. | ✓ |
Last modified 1yr ago