Repository navigation
Add exact-token transfer preparation and refresh current product copy - #111
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Token pages currently explain receiving requirements but do not carry their exact asset selection into a transfer checklist. The homepage and Features page also retain a few claims from older app versions.
This release adds a shared transfer-preparation tool with the token identifier, network, receiving instructions, fee asset and user checklist. Every catalog detail page opens its exact token/network combination; the homepage links to the USDT/USDC starting view. Selections remain useful without JavaScript, and changing a selection resets the checklist and updates its shareable URL. Query variants are excluded from indexing and point to the existing canonical guide.
Current homepage, Features and discovery metadata now agree with the documented App Store release, Oath 5.0.2 (104). Historical guides and screenshot version labels retain their provenance. Rendering uses the accepted catalog snapshot without a live provider, wallet connection or address/credential input. Catalog presence is explicitly distinguished from issuer approval or individually tested sending.
Validation:
The existing deployment workflow now verifies the published transfer tool and a selected asset from each token-capable network, in addition to the existing three-host, crawler, sitemap and document checks.