Auth wallets in BEX

Version V0.0.1

Auth wallets are public wallet signals that can help users understand who may be able to manage a token or a BEX profile.

They are informational only. An auth wallet entry is not a token ownership badge, not a BEX verification proof, not a trust score, and not an endorsement.

Possible auth wallet types:

• BEX management wallet: wallet authorized to manage an owner profile inside BEX.
• Project owner wallet: wallet configured by the project for TokenOps administration.
• Burn wallet: wallet configured for burn and verification flows.
• Metadata update authority: Solana authority that can update token metadata when still present.
• Mint authority: Solana authority that can mint additional supply when still present.
• Freeze authority: Solana authority that can freeze token accounts when still present.

Why some fields are empty:

• Many fixed-supply tokens revoke mint authority.
• Some tokens revoke or never configure freeze authority.
• External search candidates only show on-chain authority data after BEX can inspect the mint.
• A community or prepared profile may not have an owner-managed BEX wallet yet.

Why no auth wallets may be shown:

• The mint authority and freeze authority can both be unset or revoked. This is common for fixed-supply tokens and is often a positive supply-control signal.
• Metadata update authority can be missing, immutable, unsupported by the inspected metadata standard, or not resolvable from the current RPC lookup.
• A mint can exist without a BEX owner profile, project owner wallet, burn wallet, or management wallet.
• BEX does not show historical deployer wallets as auth wallets unless they are still present as a current authority signal.
• Temporary RPC or metadata lookup failures can also leave all authority fields empty until the mint is inspected again.

No auth wallets shown does not automatically mean the project is unsafe. It means BEX currently has no wallet authority signal it can display for that mint. Users should treat this as a research note, compare official project sources, and avoid assuming ownership from absence or presence alone.

Chain facts:

BEX may also show technical chain facts beside auth wallets. These facts can include the token standard, whether the mint account was found, whether a metadata account was found, which authority fields were checked, when the lookup was last refreshed, and when the next refresh is expected.

These facts are not a trust score. They are a transparent record of what BEX could read from the chain and what it could not classify as an auth wallet. For example, Token-2022 extensions may be shown as technical signals when BEX does not yet interpret them as owner or authority wallets.

BEX refreshes cached mint authority data on a timer configured by the admin panel. The default refresh interval is 24 hours.

How to use this information:

• Treat auth wallets as useful context for research.
• Compare them with official project communication before trusting them.
• Do not assume a wallet listed here owns the project unless BEX explicitly shows an owner-managed profile or a verification proof.