ERC-3643 sandbox

Orbyn supports sandbox experimentation with compliance-aware token patterns. These experiments do not make a token a security, make an issuer regulated, or make the network legally compliant in any jurisdiction.

Identity scope

Identity verification applies to holders and recipients of a specific ERC-3643 token according to that token’s policy. It is not account permissioning for the entire Orbyn Network and does not automatically apply to every wallet.

Roles and lifecycle

• A Trusted Claim Issuer signs claims accepted by the token’s Identity Registry.
• Claims must define an issuer, issue date, expiry rules, and revocation procedure.
• The owner, agent, and compliance officer roles must be separated in the token’s operational policy.
• Freeze, pause, recovery, forced transfer, mint, and burn actions require explicit authorization and audit records.
• Expired or revoked claims can make an address ineligible for a token-specific transfer.

Raw PII must never be stored on-chain. Identity documents, addresses, biometrics, and KYC files belong in an appropriate off-chain system; on-chain data should be limited to the minimum references, attestations, statuses, and events required by the token.

Out of scope

Dividend distribution, record-date snapshots, voting, rounding, unclaimed funds, and reconciliation are corporate-action modules outside the ERC-3643 core and outside the Beta launch scope.