XDNA Token Utility.

Digital identity should be useful without exposing more than it needs to. DNA Protocol explores that idea through private claims, verifiable credentials and public evidence on XRPL.

XDNA's proposed role is at the application layer: accessing defined services, supporting integrations and participating in the ecosystem. It is not the mechanism that makes a proof valid or a document authentic.

The identity tools provide a synthetic Testnet evaluation environment. A working proof or ledger receipt demonstrates a technical capability; it does not demonstrate token payments, token-gated access or a production identity service.

Genomic privacy remains a longer-term application of this work. The current synthetic identity demonstrations do not analyse DNA or verify a person's biological identity.

A direct connection between XDNA and a defined service: purchase an allowance, use that service and receive a clear record of consumption.

Before activation

• Define exactly what one credit buys and which services accept it.
• Publish pricing, payment handling, expiry and failed-job or refund rules.
• Implement payment confirmation, usage accounting and customer receipts.

Status: proposed. No credit conversion, charging schedule or redemption entitlement is established by this guide. Purchasing or holding XDNA alone does not activate service credits.

Build privacy-preserving identity workflows into other products, with defined access to developer services rather than an open-ended promise of privileges.

Basic document and proof checking should remain accessible to recipients. Our proposed model focuses on paid operational capacity, not forcing someone to acquire tokens just to inspect evidence.

Status: proposed. The evaluation tools are not a paid developer plan. API subscriptions, token-based entitlements and service-level commitments require implementation and published terms before launch.

Support people who make the ecosystem more useful: developers, integration teams, researchers and contributors delivering reviewable work.

Participation should be tied to a documented contribution, not assumed from a token balance. Any programme would need an approved budget, an accountable review process and a clear record of awards.

Status: proposed. This is not an active rewards programme. Holding XDNA does not by itself create a claim to payments, yield, priority service or future allocations.

Give ecosystem participants a defined way to contribute to decisions about DNA Protocol's applications and services.

Rules before voting

• Publish eligibility, proposal thresholds, voting rules and conflict safeguards.
• Define who can execute an approved decision and how results are recorded.
• Explain whether each vote is advisory or binding and how disputes are handled.

Application governance would not control XRPL validators, override a credential holder's consent or give token holders access to someone else's private information.

Status: proposed. This guide does not establish voting rights, ownership of the protocol or an active token-governance system.

XDNA's proposed application uses and XRP's network role are different. Keeping them separate makes the utility model easier to understand and verify.

Testnet is an evaluation network. Its transactions are not Mainnet activity and do not demonstrate commercial use of XDNA.

Evaluate the tools on their demonstrated behaviour. Evaluate token utility on a working token mechanism and its published terms. Neither should be assumed from the other.

Free healthcare, insurance, credit lines, inherited access and staking returns are not established benefits of this utility proposal. None should be inferred from holding XDNA.

Use synthetic samples in the evaluation tools. Do not submit genomic data, identity documents, wallet seeds or private keys. This guide does not change token supply, allocation, vesting or the Tokenomics page.

Follow the technical workflow before evaluating a proposed token use: hold a sample credential, request a claim, check a proof and inspect the evidence.

These links demonstrate the product context for the proposal. They do not establish that XDNA payments or token-based access are enabled. Follow each tool's access requirements and evaluation limits.