Skip to content

Commit

Permalink
Fix section order for EIP-4353 (ethereum#5179)
Browse files Browse the repository at this point in the history
  • Loading branch information
SamWilsn authored Jun 30, 2022
1 parent 0cf9afe commit f84aadf
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions EIPS/eip-4353.md
Original file line number Diff line number Diff line change
Expand Up @@ -133,14 +133,14 @@ contract ERC721Staked is ERC721URIStorage, Ownable {
}
```

## Backward Compatibility
TBD

## Rationale
This standard is completely agnostic to how tokens are deposited or handled by the NFT. It is, therefore, the choice and responsibility of the author to encode and communicate the encoding of their tokenomics to purchasees of their token and/or to make their contracts viewable by purchasees.

Although the intention of this standard is for tokens staked at mint and withdrawable only upon burn, the interface may be modified for dynamic withdrawing and depositing of tokens especially under DeFi application settings. In its current form, the contract logic may be the determining factor whether a deviation from the standard exists.

## Backward Compatibility
TBD

## Test Cases
```js
const { expect } = require("chai");
Expand Down Expand Up @@ -227,4 +227,4 @@ Staked claims will be unreliable without a locking mechanism enforced, for examp
A dedicated service may exist to verify the claims of a token by analyzing transactions on the explorer. In this manner, verification may be automated to ensure a token's claims are valid. The logical extension of this method may be to extend the interface and support flagging erroneous claims, all the while maintaining a simple goal of validating and verifying a staked amount exists to benefit the operator experience.

## Copyright
Copyright and related rights waived via [CC0](../LICENSE.md).
Copyright and related rights waived via [CC0](../LICENSE.md).

0 comments on commit f84aadf

Please sign in to comment.