420 Registry security

Verify chain/network identity, service ID and active version before trusting a destination. Do not substitute a UI URL, cached address or search ranking for canonical Registry resolution.

Registration does not mean audited, harmless or authorized to spend. For sensitive actions, verify implementation/code commitments and the called protocol's own authorization rules.

Support should never request signing secrets, recovery material or private credentials.