Fill gaps from assistant conversations: clarify USDT0 collateral is bridged - #84
Open
mintlify[bot] wants to merge 1 commit into
Open
Fill gaps from assistant conversations: clarify USDT0 collateral is bridged#84mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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.
Summary
Readers repeatedly asked what USDT0 is and, if they moved it onto Berachain, which network to use to move it back. The HONEY collateral list named USDT0 but did not explain that it is a bridged asset.
Changes
$USDT0is the LayerZero OFT (Omnichain Fungible Token) representation of Tether and is not native to Berachain.Context
Assistant conversations in the review window showed users confusing USDT with USDT0 on Bepolia, and asking how to send USDT0 back after receiving it. Vesting-claim-URL and support-only buckets (fund recovery, roadmap, checker tool) were intentionally not addressed because no verifiable claim interface or recovery flow is documented in the repo.