Route manifest
Serviceproofnet.attestobind.v1
Methodverify_binding
TransportPQTLS
Node adapterproofnet_native
Node bindingsha3-512:e5e1...e4d4
Route digestsha3-512:14ac...9bb2
Consumer view
Resolvednode/proofnet-pq1-demo-node
TrustPQ identity verified
Freshness180s
Replaymemory_block:1284309
SignerML-DSA-87
Anchornot_requested
Route packet
A route is a claim, and the claim cites an identity.
BTCore route records pair service metadata with the advertising node's identity binding. A consumer can verify both the route and the identity that issued it from the same packet.
{
"type": "proofnet_service_route_packet_v0",
"attesto_type": "service_route",
"service": "proofnet.attestobind.v1",
"method": "verify_binding",
"node_identity": {
"adapter": "proofnet_native",
"subject": "proofnet-native-demo-node",
"binding_digest": "sha3-512:e5e1...e4d4"
},
"route_digest": "sha3-512:14ac...9bb2",
"transport": "PQTLS",
"proofnet_pq_algorithm": "ML-DSA-87",
"canonical_digest": "SHA3-512",
"record_home": "proofnet_memory_block",
"public_safe": true
}
Why route under identity
A bare endpoint is not trust. A bound route is.
01
Route issued
A node advertises a service route tied to its own identity binding.
02
Consumer resolves
The consumer verifies the identity before attempting to call the route.
03
PQ handshake
The transport handshake runs under PQTLS bound to the same identity.
04
Recorded
The accepted route claim is written to the memory-block ledger for later replay.