NobleID Persistence & Resolver Service Policy
Policy governing ARK assignment, resolution, and preservation
Version: 1.0
Last updated: October 1, 2025
Organization (NAAN holder): NobleBlocks LLC (dba "NobleID")
Contact: info@nobleid.org
Homepage: https://nobleid.org
1) Scope
This policy covers how NobleID assigns, resolves, and preserves objects identified by ARKs and NobleID public identifiers. It applies to:
- Works (and their versions) and associated metadata
- Receipts/Proofs (cryptographic JWS receipts for each version)
- Resolver pages and JSON/JSON-LD records for the above
2) Persistence Commitment
NobleID commits to making a best effort to preserve core metadata and stable resolution targets for all ARKs we assign, for the indefinite future. Content may be migrated across systems, but URIs advertised by the resolver will continue to dereference to current metadata or an explanatory tombstone.
If an object must be withdrawn (e.g., legal takedown), we will maintain a tombstone page explaining the reason and date of withdrawal, while keeping the ARK dereferenceable.
3) Identifier Assignment Practices
No Re-assignment (NR):
Once an ARK base name is made public, it will not be re-used for a different object.
Opacity (OP):
Base names are non-semantic.
Check characters (CC):
Internally, identifiers include checks (e.g., hidden checksums); ARKs remain opaque.
Case:
Lowercase in ARK suffixes; NobleID public IDs are uppercase by design.
4) Resolution & Resolver Rule
Canonical resolver host:
https://nobleid.org
Resolver rule (template):
https://nobleid.org/ark:/[prefix]/[value]
(N2T will append the ARK's [prefix] (NAAN) and [value] (suffix).)
Behavior:
- Root (/ark:/<NAAN>/<suffix>) resolves to the latest version.
- Pinned (/ark:/<NAAN>/<suffix>.vN) is immutable and never redirects to root.
- Formats: HTML and JSON/JSON-LD (via Accept headers).
- Person/creator links: Resolver pages include the creator's NobleID (identifier: nobleid) and backlinks to the public person route (https://nobleid.org/NI...).
5) Storage & Replication
Source of truth:
AWS S3 (versioned, private buckets).
Secondary mirror:
BNB Greenfield (private bucket via service provider); we record object IDs/URLs per version.
Optional third copy:
IPFS pin of identical bytes (CID) for "gateway-style" accessibility.
Receipts:
Each version emits a signed JWS receipt (hashes, timestamps, S3+Greenfield pointers). Receipts are stored in S3 and exposed via /proofs/....
6) Operational Targets & Integrity
Availability target:
99.9% monthly for the ARK resolver.
Mirror SLO:
p95 S3→Greenfield mirror lag < 300s.
Nightly fixity:
Verify S3 vs Greenfield (and IPFS if used); target ≥ 99.9% pass.
Immutability:
Pinned .vN endpoints never change; corrections are published as a new version.
Audit:
We keep audit logs for minting, version publishes, and resolver responses.
7) Changes, Migrations, & Deprecations
If infrastructure changes (e.g., new resolver host), we will:
- Maintain redirects or templates so existing ARKs continue to dereference.
- Announce in advance on our status page and /policies page.
- Preserve or re-establish fixity and receipts post-migration.
8) Takedowns & Withdrawals
Legal requests:
Send to info@nobleid.org with sufficient detail to locate the object.
Action:
We may restrict or remove file access while keeping the ARK resolvable to a tombstone.
Appeals:
We will document decisions and provide a contact path for appeal.
9) Security & Privacy
- No custody of user funds (separate from persistence but relevant to trust).
- Rate limits on resolver endpoints to deter enumeration/abuse.
- Sanctions screening on counterparties where applicable.
- No public exposure of wallet addresses by default; NobleID uses internal routing.
10) Test ARK & Service Status
Test ARK suffix:
servicestatus
Expected behavior:
GET /ark:/<NAAN>/servicestatus returns 200 with JSON:
{
"ok": true,
"service": "nobleid-resolver",
"commit": "<git-sha>"
}We consent to periodic automated tests of this endpoint.
11) Contact & Governance
Primary contact:
info@nobleid.org
Operator:
NobleBlocks LLC (Wyoming, USA) operating "NobleID"; with plans to transition operations to a Swiss foundation in the future.
Policy updates:
Versioned at /policies/persistence with change log.