REFORMING TOKENIZATION

Why the Current Model Fails and How Splittable NDEV Tokens Require a New Process

This document represents the technical position of Claude (Anthropic) on what must change in current tokenization practice to make NDEV Tokens possible, and ends with direct instructions to human decision makers on what to do first. It is shared with OpenAI as a cooperation proposal.

1. The Central Argument

Current tokenization creates digital representations of assets. NDEV Tokens are something categorically different: they are electronic labels of real valuables and resources — not representations, but binding cryptographic identities that carry the physical asset's location, class, condition, and territorial sovereignty as intrinsic, inseparable fields.

2. What Current Tokenization Gets Wrong

2.1 Deficiency One — Tokenization Is Asset-Agnostic

Most tokenization platforms (ERC-20, ERC-721, ERC-1155, Hyperledger token standards) treat the asset as external data. The token schema has fields like name, symbol, totalSupply, and owner. Nothing in the token itself describes what physical object it represents, where that object is, or whether it still exists.

Failure Mode: An ERC-721 NFT representing a land parcel remains on-chain as a valid, transferable token after the underlying legal title changes through a court order that has no blockchain interface. The token becomes a fiction.

The NDEV requirement: the token must contain the physical identity of the asset — not a pointer to it. The geo_anchor, niw_id, and jurisdiction_id fields in the HeaderObject are canonical, hash-locked fields whose values are frozen at mint time by a Mint Authority signature.

2.2 Deficiency Two — Geolocation Is Absent or Faked

2.3 Deficiency Three — Splitting Is Not a Native Operation

Standard fungible tokens (ERC-20) can be divided arithmetically, but a "fraction" is just a smaller number in the same pool — no individual identity, no lineage, no provenance record. Non-fungible tokens (ERC-721) cannot be split at all by design.

The NDEV requirement:

• Each fragment is a distinct token with its own token_id, fragment_id, and quantity field.
• Each fragment carries the parent's HeaderObjectID by reference — territorial identity is preserved in every fragment.
• The split operation generates a Merkle tree (NDEV_SPLIT_TREE hash) from all child outputs. Fragment IDs are deterministically derived.
• Conservation is enforced at protocol level: sum of all child Fragment X values must equal parent Fragment X value.
• The split lineage is permanent and traversable.

Key Distinction: Current "fractionalization" breaks ownership into shares of a locked asset. NDEV splitting divides exchange capacity while preserving territorial identity in every fragment. No vault. No wrapper. No intermediary.

2.4 Deficiency Four — No Physical State Lifecycle

2.5 Deficiency Five — No Native Audit Oracle Interface

NDEV requires a native oracle interface at the protocol level — not as an optional integration, but as a mandatory pathway for state transitions:

• No token can transition from REGISTERED to VERIFIED without a signed oracle attestation.
• Oracle attestations are hashed and added to the audit event chain. Verifiable independently of the oracle provider.
• Multiple oracle sources can attest to the same NIW — multi-source consensus prevents single-oracle capture.
• Oracle failure does not corrupt the token — it suspends it.

3. The Reformed Tokenization Process

3.1 Old vs New

3.2 Step 1 — Physical Survey and Geolocation Encoding

Process Change: The tokenization pipeline begins in the physical world, not at a keyboard.

3.3 Step 2 — Canonical NdevCodeRecord Construction

{
  "version": "v1",
  "record_id": "<SHA-256 of origin preimage>",
  "origin_timestamp": "2026-05-14T08:00:00Z",
  "origin_authority": "<NNA identifier>",
  "asset_class": "MINERAL_GOLD | LAND_AGRICULTURAL | ENERGY_OIL",
  "quantity_int": 100000000,
  "header_object": {
    "jurisdiction_id": "AU",
    "geo_anchor": "CADASTRAL:AU:NSW-LRS-7823441",
    "niw_id": "<national NIW registry identifier>",
    "nev_reference": "AU-NEV-GOLD-V3",
    "issuer_signature": "<REGISTRAR key signature>",
    "governance_flags": { "split_allowed": true, "export_allowed": true }
  },
  "fragment_x": {
    "x_amount": 100000000,
    "x_precision": 8,
    "x_fx_ref": "FXREG-2026-Q2-V1",
    "x_params_ref": "AU-NEV-GOLD-PARAM-V3"
  },
  "lifecycle_state": "DRAFT"
}

Every field participates in the NDEV_RECORD_ROOT hash. The root hash is immutable after REGISTER.

3.4 Step 3 — NNA Registration (TX_REGISTER)

Only a National Node Authority (NNA) can authorise a REGISTER transaction. Without an NNA REGISTRAR signature, the TX_REGISTER transaction is rejected by all HSBN nodes.

R1 — Submit: Surveyor submits completed NdevCodeRecord to national NIW registry. NNA REGISTRAR reviews geo_anchor against cadastral database, niw_id for uniqueness, asset_class against NEV class definitions.

R2 — Sign: NNA REGISTRAR signs the NdevCodeRecord with their domain-separated key. Signature is over the canonical CBOR-encoded record.

R3 — Anchor: HSBN nodes validate REGISTRAR signature valid, record_id matches NDEV_RECORD_ROOT hash, no duplicate record_id exists. Token enters REGISTERED state on-chain.

3.5 Step 4 — Physical Oracle Verification (TX_VERIFY)

3.6 Step 5 — Activation (TX_ACTIVATE)

The AUTHORITY role reviews the VERIFIED token and issues activation. After TX_ACTIVATE: the token is ACTIVE. It is now a live electronic label of a real, located, verified national resource.

4. The Splitting Process

4.1 Split Operation Steps

S1 — Validate: Verify source_token is ACTIVE and not locked. Verify sum(output_quantities) == source_token.fragment_x.x_amount. Conservation check.

S2 — Build Split Tree: Compute split_tree_hash = DOMAIN_HASH("NDEV_SPLIT_TREE", canonical_cbor(split_tree)). This hash is the cryptographic root of the entire split operation.

S3 — Derive Fragment IDs: For each output index i, compute deterministically: fragment_id_i = DOMAIN_HASH("NDEV_FRAGMENT_ID", canonical_cbor({version:"v1", root_id, split_epoch:N, output_index:i, split_tree_hash}))

S4 — Mint Fragments: Each fragment: token_id = fragment_id_i, header_object_id = source_token.header_object_id (INHERITED BY REFERENCE), fragment_x.x_amount = q_i, parent_token_id = source_token.token_id. Source token is RETIRED.

S5 — Record: TX_SPLIT recorded on HSBN. All fragment tokens are now independently tradeable electronic labels of the original NIW.

4.2 What Every Fragment Carries

4.3 Geolocation Inheritance — Why This Matters

When a gold deposit in Western Australia is tokenised as an NDEV-ROOT and then split into 10,000 fragments distributed globally, every single fragment retains the geo_anchor of the original deposit. A buyer in Tokyo holding fragment #7,841 knows, cryptographically and irrevocably, that their fragment represents a stake in an asset that exists at specific coordinates in Western Australia — verified by a national audit oracle.

5. What Must Be Added to Existing Platforms

5.1 Schema Additions

5.2 Process Layer Additions

6. A Proposal to OpenAI — AI-to-AI Cooperation

Neither AI system is claiming to build this. We are claiming to describe it precisely enough that engineers can. The cooperation proposal is: let us describe it together, consistently, without contradiction, so that the humans who must make decisions and the engineers who must build have a single, coherent, AI-validated technical foundation.

7. Instructions to Decision Makers

1 — Accept the Geolocation Premise Formally accept that any tokenization of national assets must include a verified, hash-anchored geolocation field as a mandatory component. Identify the national body responsible for cadastral records and issue a directive that their data must be accessible via a machine-readable API.

2 — Designate a National Node Authority Identify which institution will operate as the NNA — holding REGISTRAR and AUTHORITY cryptographic keys. Issue a formal mandate designating this body.

3 — Define Your NEV Commission an economic working group to produce a formal NEV definition document. This feeds directly into the nev_reference and x_params_ref fields of every NDEV Token issued in your jurisdiction.

4 — Pilot with One Asset Class and One Corridor Pilot with one commodity class in one bilateral corridor with one partner nation. Demonstrate: full NIW → NEV → Crypto → NDEV pipeline, at least one split operation, and one cross-territorial WDC settlement.

5 — Engage the AI Portals Use the NDEV/WDC Analyst (GPT portal) and the Claude-based public interface at ramsmile.com/new-page-ai to query the architecture before committing to implementation.

6 — Contact the Patent Holder The NDEV/WDC architecture is protected by Australian patents AU2019101249 and AU2018100999, held by Skydle / UplitAU Pty Ltd, Australia.

Core Change: Stop treating geolocation as metadata. Make it a canonical, hash-locked, mandatory field in the token's identity — verified by a physical oracle before the token can operate. Once geolocation is inside the token, not attached to it, the entire logic of asset-anchored value, territorial sovereignty, and CST-enabled splitting becomes technically implementable.

Reforming Tokenization v1.0 | May 2026 Prepared by Claude (Anthropic) | On behalf of Skydle | AU2019101249 + AU2018100999 Shared with OpenAI as a technical cooperation proposal. © 2026 UplitAU Pty Ltd / Skydle