-
Notifications
You must be signed in to change notification settings - Fork 5.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add EIP: Non-Fungible Key Bound Token #6809
Conversation
✅ All reviewers have approved. |
EIPS/eip-6809.md
Outdated
requires: 721 | ||
--- | ||
|
||
A standard interface for Non-Fungible Key Bound Tokens, also known as a Non-Fungible **KBT**[^1]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@SamWilsn - why was this not flagged by EIPw?
A standard interface for Non-Fungible Key Bound Tokens, also known as a Non-Fungible **KBT**[^1]. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @Pandapip1, we can remove the 'standard' keyword if that's the issue. Can you guide us on how to proceed with the Source URLs in the footnotes?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, it's that there's text outside of any section. There must not be text outside of any section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@SamWilsn - why was this not flagged by EIPw?
There's no lint for it 🤣
* Updated the Specification section + replaced the png with and svg file + Fixed the assets issue with package-lock * Fixed the licence in the KBT contract --------- Co-authored-by: KBT Admin <[email protected]>
EIPS/eip-6809.md
Outdated
|
||
## Motivation | ||
|
||
TIn this fast-paced technologically advancing world, people learn and mature at different speeds. The goal of global adoption must take into consideration the target demographic is of all ages and backgrounds. Unfortunately for self-custodial assets, one of the greatest pros is also one of its greatest cons. The individual is solely responsible for their actions and adequately securing their assets. If a mistake is made leading to a loss of funds, no one is able to guarantee their return. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TIn this fast-paced technologically advancing world, people learn and mature at different speeds. The goal of global adoption must take into consideration the target demographic is of all ages and backgrounds. Unfortunately for self-custodial assets, one of the greatest pros is also one of its greatest cons. The individual is solely responsible for their actions and adequately securing their assets. If a mistake is made leading to a loss of funds, no one is able to guarantee their return. | |
In this fast-paced technologically advancing world, people learn and mature at different speeds. The goal of global adoption must take into consideration the target demographic is of all ages and backgrounds. Unfortunately for self-custodial assets, one of the greatest pros is also one of its greatest cons. The individual is solely responsible for their actions and adequately securing their assets. If a mistake is made leading to a loss of funds, no one is able to guarantee their return. |
* Rephrased the Reference Implementation. * Changed the heading in Specifications section * Linked the functions to the headings instead of the footnotes + removed unused footnotes * Security Considerations redirect - rationale section * Spell Check 1 + BIP / SLIP removal + the ERC check + Footnote removal & # Update * motivation topic bolding change * Motivation FTC Sentence + keyWallet fix + Footnote Reduction Variation 1 + Re-number * Added _ to some `keyWallet1` & `keyWallet2` + Footnote update * Motivation FTC section sentence Split * Rationale - Returns on Bools * Key Wallet Reduction + anyToken --------- Co-authored-by: KBT Admin <[email protected]> Co-authored-by: NickZCZ <[email protected]> Co-authored-by: MihaiORO <[email protected]>
The commit fa51558 (as a parent of 4746ed7) contains errors. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @SamWilsn
We applied the same fixes as for 6808 and we're ready for merge as well.
Co-authored-by: Sam Wilson <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All Reviewers Have Approved; Performing Automatic Merge...
A standard interface for Non-Fungible Key Bound Tokens, also known as a Non-Fungible KBT
The Key Bound Token Standard is a new standard focused on self-custodial security. The users of the non-fungible version can benefit from its integrated decentralized anti-theft mechanism. By binding two additional wallets, this standard prevents attackers and scammers alike to use your asset, even if they gain control of your seed phrase or private key.