Show Theme Tokens and BitPlan documents correctly in the wallet - #108
Merged
Merged
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
What changed
application/x-bitplanassets as BitPlan Documents instead of unknown contentWhy
The wallet should explain the assets it holds without guessing that opaque application data is an image. The supplied Nightrider token is an OrdFS package whose identity lives in indexed MAP metadata; BitPlan is an encrypted document MIME type.
Verification
/,/wallet, and/wallet/ordinalsat 320x820 and 1440x1000Scope boundary
The remaining Refresh required badge is separate: legacy outputs without the wallet-owned
id:tracking tag remain non-actionable. Display metadata must not silently become spend authority.Linear: OPL-4042