Publishable Network Contracts in Scrapscript
summary
A new language, Scrapscript, implements content-addressable scraps that are cryptographically signed and publishable to a “scrapyard” and an address type that embeds a protocol, encoders/decoders, and an unsafe-at timestamp to enforce SLA windows. The compiler checks protocol types and runtime decoders verify payloads, a CLI publishes addresses, and a prototype demonstrates practical publishing and verification though the timestamp model admits correctness limits; session, dependent, and refinement type experiments guide tradeoffs.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:24Publishable network contracts
- 2:37Pain of distributed systems
- 8:01Formalizing blame in contracts
- 10:52Scrapscript language
- 15:50Monkey tools vs contracts
- 16:37Soundless vs unsound systems
- 18:02Responsible server properties
- 21:38Evaluating contract systems
- 24:52Refinement types and evolution
- 27:19Session types and ordering
- 28:24Q&A on session types
- 34:06Closing remarks
related talks
47mDeep Programmability: A New Lens on Networking
29mMoving from Sidechains to Parachains
01h 01mStructured Networking
31mLibp2p: A Modular, P2P Networking Stack
32mGetting started with p2p
01h 04mHashpools One Year Development Update
57mStructured Networking in C++
28mSafe, Modular Packet Pipeline Programming