01 / Live directory
The official address must be verified before it is copied.
MUTA uses BNB Smart Chain. The official contract, explorer link, token implementation and current operational addresses must be verified directly against deployment records before they are published here.
Until that verification is complete, this page will not display an address copied from an advertisement, message or obsolete page.
02 / Asset identity
A name and logo are not enough.
Anyone can create a token called MUTA. The contract address and network are the technical identifiers that distinguish the official asset from an imitation.
Every high-risk action should allow a user to confirm network, contract, destination and transaction details before signing.
03 / Public contracts
Inspectable does not mean risk-free.
A public contract can still contain bugs, privileged functions or unsafe assumptions. Publication is evidence of inspectability, not a guarantee of security.
The final directory should disclose source verification, admin permissions, upgradeability, pause functions, mint or burn controls and audit status only after code review.
04 / Multisig
Important actions should not depend on one private key.
The current security direction includes a 2-of-3 multisig for selected important operations. Two of three authorised signers must approve an action protected by that wallet.
Multisig reduces single-key risk. It does not eliminate collusion, compromise or operator risk and is not automatically a decentralisation claim.
05 / Named roles
One wallet should not quietly mean everything.
Only roles that actually exist should receive public addresses. Legacy addresses should remain visible as LEGACY / DO NOT USE when old materials may still reference them.
06 / Administration
Users should know which rules can still be changed.
Some contracts are immutable; others contain owner, upgrade, pause or parameter controls. Neither model is automatically correct for every purpose.
The relevant questions are who controls those powers, whether they sit behind multisig and what an emergency function can actually do.
07 / User security
A secure contract cannot protect a user who signs the wrong transaction.
MUTERRA will not ask for a seed phrase. Verify the domain, network, contract address, wallet prompt and destination before signing. Do not assume a Discord direct message is official.
Funds sent to a wrong address or control granted to a malicious contract may be impossible to recover.
08 / Remaining risk
Verification reduces uncertainty. It does not remove risk.
No architecture can guarantee the absence of contract bugs, wallet compromise, phishing, network interruptions, changing fees, exchange availability or regulatory change.
The point of a technical source is not to claim that code removes trust. It is to make the remaining trust visible.