Add AIP-2: Address Standardization Proposal for Asset Identification (atom32) #2
Conversation
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
Signed-off-by: Wizz Wallet <[email protected]>
|
A fantastic idea and helps differentiate addresses with Atomicals assets +1 |
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.
This proposal introduces a standardized address format based on bech32 encoding to resolve asset identification challenges within the Bitcoin system, particularly concerning the Atomicals Protocol.
The new address format aims to differentiate Atomicals Protocol assets from Bitcoin assets,
enabling node services to accurately identify and handle distinct asset types, thus preventing unintended asset burning during transactions.