Satsuma Research
Deep comparisons, measured.
Longer-form technical work: head-to-head chain comparisons, performance studies, and the reasoning behind Satsuma's design — cited, and backed by numbers.
The Same Bridge, the Parity Way — and the Bill
We rebuilt our trustless bridge with the stack that runs Polkadot↔Kusama: pallet-bridge-grandpa plus ordered message lanes. Same trust model, different machinery — and this time every proof lands as a signed transaction with a fee on the record. The head-to-head, measured.
ISMP Bridging with Satsuma
We ran two independent satsuma chains — different genesis, different validators — and moved value between them with no multisig, no custodian, no middleman. Each chain verifies the other's GRANDPA finality on-chain, then verifies a state proof. 4 seconds end to end.
A Trustless zk Re-Genesis
The trust-minimized restart still leaned on an honest two-thirds of validators to sign. This time we replace the signatures with a zero-knowledge validity proof — anyone verifies it in milliseconds, and no coalition of validators can forge it.
The Limit of Sub-Second Blocks Is Geography, Not Speed
We built a testbed to push Satsuma's block time below one second and find where it breaks. Compute wasn't the wall. The speed of light was.
A Trust-Minimized Re-Genesis
Changing a chain's block time means halting it and relaunching from the old ledger. We built that migration on a live testbed — and made it so nobody has to trust that the balances carried over honestly.
TON vs Satsuma: Sharding, Sub-Second Blocks and Finality
TON just shipped sub-second blocks and unbounded sharding. We measured Satsuma against it — and most of what makes TON fast, Satsuma is built not to need. Here's the reasoning, and the one idea worth borrowing.