marchon/master-zapier-plan-draft
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1
master-zapier-plan-draft/packages/verae-tree-node/NATS.md
George Lambert f3dc0e6eee
Some checks are pending
offline / test (push) Waiting to run
Details
Add Zapier interface simulator, tree-node Merkle lookups, and user docs 
In-process trace console validates hops, faults, recoveries, and
suggested changes before zapier-platform push. User guide covers
signup through central-chain and bulk-summary tree-node hash lookup.
2026-09-11 12:58:03 -04:00

992 B
Raw Blame History

NATS — verae-tree-node

Tree nodes are WORM archives that store Merkle leaf proofs. They listen on the same archive subjects so a leaf that was never itemized on the main chain can still be found.

Zapier never connects here. Middleware aggregator broadcasts; a tree node that does not hold the leaf stays silent.

Direction Address From / to Body
IN verae.archive.put batch splitter / merkle builder { sha256, tenantId, kind: "tree", record: { merkleRoot, proof, leafIndex, chainSealJobId }, traceId }
IN verae.archive.query aggregator (broadcast, no queue group) { correlationId, sha256, tenantId, kinds: ["tree", …], traceId }
OUT verae.archive.reply.<correlationId> aggregator { archiveId, sha256, records[], traceId } only if bloom.mightHave(sha256)

record.merkleRoot is the hash sealed on the main Verae chain. proof lets a verifier recompute the root from this leaf.