Venues match. Pipeshift settles.
Trading venues are good at matching. They are not good at settling, and every venue that builds its own settlement path builds its own way to break.
Pipeshift is the layer underneath, and it does three things.
Atomic delivery versus payment. The security leg and the cash leg move in one transaction. There is no state in which the shares have moved and the money has not.
Multilateral netting. A desk that buys 400 shares and sells 380 in the same session owes 20. We collapse a trade file into one net position per party, so settlement work scales with participants rather than with trades.
One canonical registry. Every venue settles against the same record of what a token represents, keyed by ticker and ISIN rather than by token address. A reissued token keeps its identity and its settlement history.
We are not a DEX, not a venue, and not a custodian. The engines hold no positions between calls and take no view on price.
| Repo | What it is | Status |
|---|---|---|
| pipeshift | Settlement contracts, TypeScript SDK and offline CLI | v0.3.0 |
| pipeshift-attestations | Proof of reserves and per venue settlement policy | v0.1.0 |
| pipeshift-indexer | Event indexer: positions, volumes, compression | v0.2.0 |
Being explicit about scope is cheaper than being discovered.
- The contracts are unaudited. Do not point real value at them yet.
- Nothing is deployed to Robinhood Chain mainnet. Addresses go in the repo README when it is.
- Proof of reserves is designed and not implemented. Custodian attestation is off chain today.
- Settlement is all or nothing per instruction. Partial fills are planned, not shipped.
No dates anywhere. Follow the commits.