Identity Has No
Settlement Layer.

Every token system in production today derives scarcity from one of three sources: computational work, economic stake, or institutional fiat. All three are abstractions. A proof-of-work hash proves that electricity was consumed, not that a specific person consumed it. A proof-of-stake bond proves that capital was risked, not that the staker is who they claim to be. A bank-issued stablecoin proves that reserves exist in a vault, not that the bearer was ever verified as human.

These abstractions work well for transferring monetary value. They fail completely for identity, because identity is not abstract. Identity is a claim about a physical being in a physical world. The only proof that should be considered authoritative is one that originates from the physical world itself.

PIST tokens derive scarcity from three independent physics channels, sampled simultaneously, and evaluated with strict AND logic. If any single channel fails to confirm human presence, no token is minted. The channels are:

Each channel is strong on its own, but the property that matters is that they are physically distinct: compromising one channel does not, on its own, yield the other two. An attacker who clones a device's ambient-sensor signature still cannot replicate its orbital geometry; an attacker who spoofs a satellite signal still cannot forge a quorum attestation from hardware they do not possess. That independence is strong but not absolute—Channel 1 and Channel 3 can involve hardware the same person carries, so a single physical theft can place more than one channel in an attacker's hands. Minting integrity therefore rests on the parametric freeze and re-attestation path of Section 07 as much as on channel separation (see Section 09).

A PIST token is a signed attestation record, not a coin, a balance, or a unit of currency. It has the following structure:

This structure means every token carries its entire history. A token minted today and transferred four times over the next decade will contain five signed attestation events, each independently verifiable, each bound to the physics conditions of its moment. The provenance chain is the token; there is no external ledger to query for a balance. Which chain extension is canonical—the question a settlement layer exists to answer—is resolved by an authoritative chain-state registry, discussed in Section 09.

Token minting is a physical event rather than an API call, and it follows a strict protocol:

1. Capture. The device initiates a ≤100ms sensor window. Magnetometer, accelerometer, and network-jitter readings are sampled simultaneously and hashed into the physics digest.
2. Locate. The kinematic anchor is computed from available orbital or terrestrial signals. The result is a spatial attestation, not a GPS coordinate.
3. Attest. The quorum protocol broadcasts a challenge to the user's device constellation. Each responding device independently signs its attestation.
4. Evaluate. The system applies strict AND logic across all three channels. If any channel returns a null, ambiguous, or anomalous result, the ceremony halts. There are no partial mints and no override mechanisms.
5. Sign. Upon unanimous channel confirmation, the token is created with dual classical/post-quantum signatures and an atomic-clock timestamp. The genesis event becomes the first link in the provenance chain.

The design targets sub-200ms end to end—fast enough to feel instantaneous to an end user. To an attacker, it presents five independent verification gates, each rooted in a different physical domain, all of which must be compromised simultaneously.

Traditional tokens are fungible. One Bitcoin is identical to every other Bitcoin. Its history is irrelevant to its value. PIST tokens are the opposite. A token's value is inseparable from its provenance.

Consider two tokens. The first was minted during a high-assurance identity verification at a regulated financial institution, then transferred through two additional physics-attested events. The second was minted during a routine device authentication. Both are valid. Both prove human presence. But their provenance chains tell fundamentally different stories about the level of assurance they represent.

This is by design. Identity settlement carries proof rather than counting units. A relying party that receives a PIST token can inspect every link in its chain, verify every signature (both classical and post-quantum), and make a trust decision based on the full history of the attestation, not just the current holder's claim.

In conventional cryptographic systems, transferring a token requires a private key signature. Whoever holds the key can authorize the transfer, regardless of who they are or where they are. This is why key theft is catastrophic: possession of the key is indistinguishable from ownership.

Under the PIST protocol, a transfer requires dual proof-of-presence. Both the sender and the recipient must independently complete a physics attestation ceremony before the transfer can execute. The protocol operates in four stages:

The transfer channel itself is a BLAST tunnel: an ephemeral, forward-secret session whose key agreement runs X25519 ECDH today, with a hybrid X25519 + ML-KEM-768 exchange as the intended post-quantum upgrade. Payloads are protected with AES-256-GCM authenticated encryption. The tunnel exists only for the duration of the transfer and is cryptographically destroyed upon completion. No session keys persist. No relay server can inspect the payload.

The result is a transfer mechanism where both parties must be physically present, the channel is ephemeral and forward-secret, and the event is permanently recorded in the token's self-contained provenance chain. Stolen keys, compromised servers, and intercepted network traffic are all insufficient to execute an unauthorized transfer.

Any settlement system that cannot survive hardware failure, key compromise, or algorithmic obsolescence is a liability, not infrastructure. PIST addresses each failure mode with a dedicated recovery mechanism:

A settlement primitive earns trust by being explicit about what it does not yet solve. Three limitations shape the current design, and naming them is part of the design.

Attested capture. A physics digest is a hash of sensor measurements that are then discarded. A hash proves commitment to a set of bytes; it does not, on its own, prove those bytes came from a real sensor rather than a synthesized input. Closing that gap requires a hardware root of trust—an attested capture path, such as a TEE or secure-element-signed sensor read, that binds the measurement to the device before it is hashed. Until that path is universal across enrolled hardware, what a relying party ultimately verifies is that PasskeyBridge's key signed the record. That is a centrally-attested, physics-informed verification record—a strong primitive—but its scarcity is anchored by physics inputs and enforced by signing policy, not by the laws of physics alone.

Finality and forks. A self-contained provenance chain, taken by itself, can be copied at any link and extended two different ways for two different recipients. Detecting that divergence is precisely the problem a settlement layer exists to solve, and a chain with no external reference cannot solve it alone. In PIST, finality comes from an authoritative chain-state registry maintained by PasskeyBridge: the settlement layer is a trusted operator anchored by physics inputs, not a decentralized consensus network. We state this plainly because the honest framing is also the accurate one—PIST is a centralized settlement primitive with physically-grounded minting, not a trustless ledger.

Channel independence. As noted in Section 02, the three minting channels are physically distinct but not perfectly independent: some involve hardware a single person carries, so one physical theft can compromise more than one channel at once. Minting integrity therefore leans on the parametric freeze and re-attestation path of Section 07, not on channel separation as an absolute.