BIT-0007: The (un)official wTAO Contract#17
Open
quintessenial wants to merge 2 commits intoopentensor:mainfrom
Open
BIT-0007: The (un)official wTAO Contract#17quintessenial wants to merge 2 commits intoopentensor:mainfrom
quintessenial wants to merge 2 commits intoopentensor:mainfrom
Conversation
|
For Taofu we have deployed a wrapped Tao contract that we will start using for our launchpad soon. We have been asking for a standardised WTAO contract since the launch of Bittensor EVM. This contract is now live on mainnet and we have verified it on Taostats: https://evm.taostats.io/address/0x9Dc08C6e2BF0F1eeD1E00670f80Df39145529F81?tab=contract We could take this contract as the endorsed contract as it is public and verified. |
Author
We will happily use this contract when we launch taonado. |
quintessenial
changed the title
Author
|
Is this happening? 👀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bittensor needs an (un)official and (un)endorsed ERC-20 compatible wTAO contract for use across all applications built within the Bittensor EVM.
By design, the EVM does not allow an EOA (Externally Owned Account) to grant another address direct access to their native token balance. This is often handled on other networks by creating an ERC-20 compatible wrapper contract for the native token.
This proposal outlines why an (un)official address is ideal over a system of fragmented custom wTAO implementations and provides a reference wTAO implementation based on the WETH implementation.