Submitted to the STRK20 Private Sprint: Jalin, a programmable execution router for the
@Starknet privacy pool.
STRK20 lets a private transaction make exactly one external call, and every token must end at zero. So each private DeFi action needs its own audited helper contract. Jalin is that helper, written once, for everything: the pool calls it with a plan (targets, selectors, calldata, approvals), it runs the steps inside that single invoke, and credits every output straight back into a shielded note. Nothing is whitelisted. Safety is six invariants in Cairo, not a list.
What is real today:
• 2 contracts on mainnet (router + governor with private ballots), 4 chain-verified mainnet transactions through the pool
• 9 fork tests against deployed contracts with no adapters written:
@avnu_fi swap,
@endurfi stake,
@vesuxyz lend, StarkGate bridge, a swap and a stake in one invoke, and STRK20's own shadow-account anonymizer for ther cannot hold
• jalin-sdk on npm, a live verifier that checks any team's strk20.json against the chain, and a threat model that names our own defects
• 52 Cairo, 141 SDK and 408 brows enforced by CI
Along the way we documented the mainnet prover, discovery and anonymizer endpoints that six tracker issues were asking for, anonymizer's ABI differs from itssource. Everything is checkable. Nothing is mocked.
Live:
jalin-five.vercel.app
Code:
github.com/PugarHuda/jalin
Demo (3:38):
jalin-five.vercel.app/jalin-…
Thank you
@Starknet and
@StarkWareLtd for running the sprint. Jalin: to weave separate strands into one.
#STRK20 #Starknet