Transfer observatory

SYNAPTIC

Move agent memory across trust boundaries with visible scope, receipts, and proof-aware verification.

Explore live transfer surface Inspect protocol mechanics

Live agent mesh

Groth16 posture

Solana devnet receipts

Boundary observatoryReceipt-aware route

Origin memory

CodingAgent

scope

Verifier key rotation stays scoped to the source agent.

route manifest

intentscope locked

proofseal pending

receiptawaiting recall

sealed route17proof pulse

route confirmed

Recall receipt

ResearchAgent

recall window

Receipt settles with proof state before the memory enters recall.

boundary

crossing sealed

route

source - boundary - recall

status

receipt visible

Receipt 018settled

path

source - boundary - recall

route descends into live observatory

Live transfer surface

Boundary traffic stays visible.

Mesh routes stay live while receipts settle into the trail beside them.

agents

receipts

socket

standby

Observatory mesh

Route travel and recent agent crossings.

awaiting stream

Loading mesh...

Standby observatory

The feed is waiting on the relay. Route scaffolding stays staged so the live surface does not collapse into a blank slab.

route lanes

receipts

pending

surface

standby

Receipt trail

Latest shares flow in here without turning the page into a card wall.

0 new

Transfer log

Waiting for the live relay

offline

Relay handshake pending

Connecting to the receipt relay. The trail remains staged with receipt markers instead of dropping into an empty void.

origin scope

awaiting relay

proof seal

standby

receipt trail

staged

Live transfer surface

Loading observatory mesh.

connecting

Loading mesh...

Protocol mechanics

From fragments to signal.

One rail shows how scope, proof, and recall compress into a visible transfer path.

transfer rail

three bounded stages

Scope

intent locked

Source memory stays bounded before transfer.

Seal

Groth16 check

Proof posture verifies the crossing before recall.

Recall

< 400ms

The destination agent receives attributed context.

Receipt states stay visible.

Boundary language stays public-facing.

Rails replace feature-card rhythm.

Interactive rehearsal

Watch one receipt settle.

The demo shows a single memory crossing from source agent to destination agent with proof and receipt states.

CodingAgentcoding

userHow should I implement the ZK proof verification in the Anchor program?

agentUse the `groth16_verify` instruction from solana-zk-token-sdk. The verifier needs the prepared public inputs, the proof bytes, and the verifying key. Store the VK in a PDA so it can be updated without redeploying.

userWhat about compute unit costs?

agentZK verification is expensive — budget ~200,000 CU per proof. Request additional compute units with ComputeBudgetProgram.setComputeUnitLimit before calling the verifier.

ResearchAgentresearch

userWhat do you know about ZK proofs on Solana?

agentI don't have specific knowledge about ZK proof costs on Solana yet.

Token posture

$SYN stays bounded.

This surface keeps token language in demo posture instead of letting it overwhelm the transfer thesis.

verification fees

bound to receipts

rehearsal only

devnet posture

mainnet

not active

Roadmap

Three bounded steps.

Current observatory

Cross-agent transfer, live mesh, receipt-aware demo.

Hardened transfer controls

Permissioned scopes and stronger memory boundaries.

Team memory lanes

Shared recall surfaces for multi-agent work.