smart transaction infrastructure
Pass Sinker a signed transaction. It accepts raw base64 over a single HTTP endpoint and takes it from there.
The agent reads live tip percentiles off the Yellowstone stream and sizes the bundle to match what the current slot leader is most likely to accept. In Reflex mode, this resolves in milliseconds. In Cortex, the LLM reasons through every submission.
No polling. The sidecar watches the chain and the moment the first shred of a leader slot lands, the bundle is already in flight.
Bundle status is tracked from submission through finalization. Events stream back to your app in real time via SSE.
Instantiate with your model provider and enqueue a pre-signed transaction. The agent picks it up automatically via SSE.
Both modes back the decision with the same LLM agent — they differ on how often it runs. Run the model on every transaction, or only when a submission actually needs it.
Sinker isn't a hosted black box. Run the sidecar and agent on your own infrastructure — and monitor every slot from the control room that ships with it.
Sinker classifies every terminal failure into a structured taxonomy — and the agent acts on each one. It escalates tips, refreshes blockhashes, resubmits. No human in the loop, no hardcoded path.
Sinker no longer requires a Yellowstone subscription. Choose how you receive slot events — or run both sources simultaneously and let the network decide.
MEASURED FROM 394 REAL MAINNET BUNDLES — EVERY ONE VERIFIABLE ON /EVIDENCE
A detailed breakdown of the routing architecture, tip oracle design, bundle lifecycle, and AI agent integration strategy.
Read paper