Verification Policy
Official verification policy for Capsule-linked email, phone, Anti-Phishing Code, Email OTP, QR login and approval authorization workflows.
Effective version Mainnet readiness version — verification operating policy
Verification confirms that an approval device, login request or action is connected to the expected Capsule Identity.
Verification does not make nΩn.ID the identity. The Capsule remains the identity and the Genesis Contract remains the source of truth.
nΩn.ID provides authorization and approval confirmation connected to Capsule Identity.
Email and phone may be used to discover or verify a Capsule during registration and connection flows.
Email OTP may be required before Capsule creation or device registration proceeds.
Users are responsible for maintaining secure access to their registered email and phone channels.
The Anti-Phishing Code is used as a protection reference for Capsule-linked flows.
Users must verify Anti-Phishing information before approving sensitive actions.
If the Anti-Phishing information does not match the user's expected value, the request should be denied and reported.
Each approval request should be reviewed before approval.
Users should check the service, reason, request ID, Capsule ID and any security indicators displayed by the app.
Approving a request constitutes user authorization for that action.
QR login connects a browser or external session to the nΩn.ID approval process.
Users should approve QR login only if they initiated the login and recognize the destination.
Unknown QR requests must be denied.
Verification reduces risk but does not eliminate all risk.
Users remain responsible for device security, credential protection and review of approval requests.
SkodriNΩN may update verification requirements as the ecosystem evolves.
Use only official SkodriNΩN communication channels for support, verification, recovery, legal, security or incident-related matters.
