Send one route. No keys. No custody.
This is the packet for a Solana bot operator who wants Blackline to produce a bounded proof result. Submit one route, fixture URL, or signature context. Blackline will not ask for wallet secrets or mutate already-signed arbitrary transactions.
Submit from a bot harness
Operators can submit the same proof packet programmatically. The API stores the request in the authenticated proof queue for bounded evidence review.
Bot harnesses can fetch the canonical machine-readable packet at /proof/packet before submitting. It includes field rules, accepted input types, public boundaries, and the expected response.
Operators outside this repo can submit the same packet with curl:
curl -sS -X POST 'https://solana.jockeyvc.com/v1/proof-requests' \
-H 'content-type: application/json' \
--data '{"operatorName":"Example Solana Bot","contactEmail":"operator@example.com","inputType":"route","network":"devnet","fixtureUrl":"https://gist.github.com/operator/unsigned-fixture.json","signature":"","routeContext":"Jupiter swap route comparing direct public RPC versus Blackline. Current failure mode is expired sends during burst traffic. No private keys or wallet secrets are included.","successMetric":"Worth paying if Blackline gives clearer terminal state and fewer expired sends on the same route.","paidIntent":"not-yet"}'{
"operatorName": "Example Solana Bot",
"contactEmail": "operator@example.com",
"inputType": "route",
"network": "devnet",
"fixtureUrl": "https://gist.github.com/operator/unsigned-fixture.json",
"signature": "",
"routeContext": "Jupiter swap route comparing direct public RPC versus Blackline. Current failure mode is expired sends during burst traffic. No private keys or wallet secrets are included.",
"successMetric": "Worth paying if Blackline gives clearer terminal state and fewer expired sends on the same route.",
"paidIntent": "not-yet"
}What belongs in the packet
Do not include private keys, seed phrases, custody access, production wallet secrets, or claims that require Blackline to rewrite an already-signed arbitrary transaction.
Three ways to submit without an integration.
Public signature
Best for a recent failed, delayed, expired, or timed-out transaction where the operator can explain the route.
Open this formUnsigned fixture
Best for proving `txready` on a transaction before signing without sharing custody or wallet secrets.
Open this formRoute comparison
Best for comparing direct RPC versus Blackline on the same devnet or tiny capped mainnet route.
Open this form