WebNative: How to put a full stack directly in the browser

🌈WebNative🚀 How to put a full stack directly in the browser ✨Speakeasy JS🍻

Or:

Or: The Beginnings of a WebOS

Or: The Beginnings of a WebOS Wait, no

Or:

Or: A Browser-Based File System, Location Independence, User Controlled Data, Self-Modifying Apps, & Serverless Auth …plus some surprising things we’ve learned along the way

Brooklyn Zelenka @expede

Brooklyn Zelenka @expede • CTO at Fission • https://fission.codes • 100% FOSS • Obsoleting backends one function at a time • PLT, VMs, Distributed Systems, Prev. ETH Core • Founded Vancouver FP, Code & Co ee YVR ff • FOSS — Witchcraft, Exceptional, Rescue, &c

shop.fission.codes Code: SPEAKEASYJS

Stickers! shop.fission.codes Code: SPEAKEASYJS

This is the JavaScript meetup for 🥼 mad science, 🧙 hacking, and 🧪 experiments SpeakeasyJS Homepage

This is the JavaScript meetup for ✅ 🥼 mad science, ✅ 🧙 hacking, and ✅ 🧪 experiments 👍 SpeakeasyJS Homepage

The Problem(s) Starting Conditions 🚦

WebNative 🚀 The Web Today

WebNative 🚀 The Web Today 💁 🖥

WebNative 🚀 The Web Today 💁 🖥 🐢

WebNative 🚀 The Web Today 💁 🖥 🐢 🗃

WebNative 🚀 The Web Today 💁 🖥 🐢 ⚙ 🗃

WebNative 🚀 The Web Today 💁 🖥 🐢 ⚙ 💪 🗃

WebNative 🚀 The Web Today 💁 💁 💁 🖥 🐢 🖥 🖥 ⚙ 💪 🗃

WebNative 🚀 The Web Today 💁 💁 💁 🖥 🐢 🖥 🖥 ⚙ 💪 🔐 🗃

WebNative 🚀 The Web Today 💁 💁 💁 🖥 🖥 🖥 🐙 ⚙ ⚙ ⚙ 🔐 🔐 🔐 🗃 🗃 🗃

WebNative 🚀 What We Actually Want 💁 🖥 📝 🖥 💁 📃

…and so it was for many years…

…and so it was for many years… 🦖☄🌋🌾🏰🏢🚀

Is the way we do things today the “one true way”? Will we be doing things this way in 2025? 2050? 2100? Does knowledge always progress from good to better? Are we stuck in a local maxima?

WebNative 🚀 Natural Consequences • Server-focus • Must learn more of stack • Single source of truth • DevOps, Docker, k8s • Latency assumption • FE deeply concerned with data sync

WebNative 🚀 What Even is a “Server”?

Auth gatekeeper (because multi-tenant data) 2. Resource availability 3. Out-of-band compute (e.g. batch tasks)

WebNative 🚀 What Even is a “Server”?

Auth gatekeeper (because multi-tenant data) 2. Resource availability 3. Out-of-band compute (e.g. batch tasks) s i h t r e b m e m e R ! t s i l

What if we turn the web architecture Inside Out? 🔁

WebNative 🚀 Like Native… but for the Web 🧐

WebNative 🚀 New Assumptions, New Approach • 2021 != 1991 • Don’t need to rely on client/server • Browsers are super powerful • UI & data = only essential parts • Post-serverless, edge++ • New primitives (“game changers”) • Location independent data 🙌 • Browser-based encryption 💪 • Consistency models (OT, CRDTs, RAFT) 🤝 • i.e. State transfer -> state synchronization • New features naturally fall out of the architecture • Recognize that we’re increasingly connected/networked ffi • Local-first means network e cient (in the normal case)

WebNative 🚀 Bootstrapping from Browsers APIs • WebCrypto API • Web Workers • Service Workers • IndexedDB • PWA & Web App Manifest

WebNative 🚀 How Many Steps Can We Skip?

WebNative 🚀 How Many Steps Can We Skip? Users 👨🏫👩🏭🧑⚕👷 Developer 👩💻

WebNative 🚀 How Many Steps Can We Skip? Users 👨🏫👩🏭🧑⚕👷 Browser 🖥 REST / JSON-RPC / GraphQL ↕ Server ⚙ Data Store 🗃 DevOps 📤 Developer 👩💻

WebNative 🚀 How Many Steps Can We Skip? Users 👨🏫👩🏭🧑⚕👷 Browser 🖥 REST / JSON-RPC / GraphQL ↕ Current Server ⚙ Data Store 🗃 DevOps 📤 Developer 👩💻

WebNative 🚀 How Many Steps Can We Skip? Users 👨🏫👩🏭🧑⚕👷 Browser 🖥 REST / JSON-RPC / GraphQL ↕ Current Server ⚙ Data Store 🗃 DevOps 📤 Developer 👩💻 Users 👨🏫👩🏭🧑⚕👷 Browser 🖥 WebNative 🚀 Developer 👩💻

WebNative 🚀 How Many Steps Can We Skip? Users 👨🏫👩🏭🧑⚕👷 Browser 🖥 REST / JSON-RPC / GraphQL ↕ Current Server ⚙ Data Store 🗃 DevOps 📤 Developer 👩💻 Users 👨🏫👩🏭🧑⚕👷 Browser 🖥 WebNative 🚀 Developer 👩💻 Proposed

WebNative 🚀 How Many Steps Can We Skip? Users 👨🏫👩🏭🧑⚕👷 Browser 🖥 Current Users 👨🏫👩🏭🧑⚕👷 Browser 🖥 WebNative 🚀 REST / JSON-RPC / GraphQL ↕ Developer 👩💻 Server ⚙ Quick iteration 🔄 Data Store 🗃 DevOps 📤 Developer 👩💻 Focus on end users 💁 Lower barrier to entry 👨🎨 Proposed

WebNative 🚀 Constraints • Vanilla browser, no plugins • UX as good or better than existing • Literally no distinction between local and production • No server required, put it in the browser • User controlled identity & data • Open to participation • Accessible o ine ffl • At least as secure as existing apps

WebNative 🚀 Mini-Demo

WebNative 🚀 Code

WebNative 🚀 Code Auth doesn’t even leave your browser 👆

WebNative 🚀 Code

If React is “just the view layer”, then WebNative is “just the data layer” It turns out the data layer touches lots of other things

WebNative 🚀 Stack

WebNative 🚀 Stack 1st & 3rd Party Dev’s App Business Logic & View

WebNative 🚀 Stack 1st & 3rd Party Dev’s App Business Logic & View API Platform Abstractions WebNative SDK

WebNative 🚀 Stack ⬆ Apps ⬇ Core Technology 1st & 3rd Party Dev’s App Business Logic & View API Platform Abstractions WebNative SDK

WebNative 🚀 Stack 1st & 3rd Party Dev’s App Business Logic & View API Platform Abstractions WebNative SDK ⬆ Apps ⬇ Core Technology Command/Mutation UCAN Auth & ID Read/Query Cryptree Identity did:key

WebNative 🚀 Stack 1st & 3rd Party Dev’s App Business Logic & View API Platform Abstractions WebNative SDK ⬆ Apps ⬇ Core Technology Command/Mutation UCAN Auth & ID Read/Query Cryptree Transport DNS, IPFS, PubSub, Matrix Identity did:key

WebNative 🚀 Stack 1st & 3rd Party Dev’s App Business Logic & View API Platform Abstractions WebNative SDK ⬆ Apps ⬇ Core Technology Durable Structured Store WebNative Database Durable File Store WebNative File System Durable Data Command/Mutation UCAN Auth & ID Read/Query Cryptree Transport DNS, IPFS, PubSub, Matrix Identity did:key

WebNative 🚀 Stack 1st & 3rd Party Dev’s App Business Logic & View API Platform Abstractions WebNative SDK ⬆ Apps ⬇ Core Technology Broadcast Collaboration, Chat, Instant Sync Soft Realtime Store Durable Structured Store WebNative Database O ine & Async Sharing Exchange Store Durable File Store WebNative File System Durable Data Command/Mutation UCAN ffl Auth & ID Global: Aggregation, Forms, Feeds Gossip Broadcast Read/Query Cryptree Transport DNS, IPFS, PubSub, Matrix Identity did:key

WebNative 🚀 Painting a Picture 🖼 • Go from zero to production on a plane ✈ • Move data to compute and vice versa 🔄 • Publish updates from inside the browser 🚀 • Code is data = self modifying apps 🐣 • Anyone can be a service provider (lower bar to entry) 💁💁 • Including adversarial cooperation

Content Addressed Data

Content Addressed Data It works offline and online, totally distributed & concurrent, anyone can create or request data, & data is always changing.

Content Addressed Data It works offline and online, totally distributed & concurrent, anyone can create or request data, & data is always changing. Great!

Content Addressed Data It works offline and online, totally distributed & concurrent, anyone can create or request data, & data is always changing. Great! How do you even get a consistent pointer?

Content Addressed Data Pushing Bytes Around 🚚

Content Addressed Data Unique Hash ~ UUID++

Content Addressed Data Arbitrary Content

Content Addressed Data Location Addressing • Predominantly single-source (per file) server/client • Like a key/value store {ip => {path => content}} • DNS maps names to IP addresses • Focused on the physical network • Mutable addressing • www.foo.com/baz may be JSON today, but a video tomorrow • …or altered content

Content Addressed Data Location Addressing • Predominantly single-source (per file) server/client • Like a key/value store {ip => {path => content}} • DNS maps names to IP addresses • Focused on the physical network • Mutable addressing V I R T UA L A D D R E S S P H Y S I C A L L O C AT I O N • www.foo.com/baz may be JSON today, but a video tomorrow • …or altered content

Content Addressed Data Universal / Content-Based Routing • A layer of abstraction above location • Like a key/value store {hash(content) => content} • Content hash AKA “content identifier” or CID • Special “universal” relationship to content V I R T UA L A D D R E S S • Focused on the data • Who cares where it’s stored? • E cient auto-caching • Still have paths • Immutable DAG ffi • No loops P H Y S I C A L L O C AT I O N

Content Addressed Data Universal / Content-Based Routing • A layer of abstraction above location • Like a key/value store {hash(content) => content} CONTENT ID • Content hash AKA “content identifier” or CID • Special “universal” relationship to content V I R T UA L A D D R E S S • Focused on the data • Who cares where it’s stored? • E cient auto-caching • Still have paths • Immutable DAG ffi • No loops P H Y S I C A L L O C AT I O N

Content Addressed Data Hash-Linked Data

Content Addressed Data Hash-Linked Data { Qm123456…: { data: “Hello world”, links: [ {name: “company”, hash: Qmabcdef…} {name: “license”, hash: Qmzyxwvu…} ] } }

Content Addressed Data Hash-Linked Data { { Qm123456…: { data: “Hello world”, links: [ {name: “company”, hash: Qmabcdef…} {name: “license”, hash: Qmzyxwvu…} ] } } Qmabcdef…: { data: “FISSION”, links: [ {name: “city”, hash: Qm1gb5sn…}, {name: “about”, hash: Qmzyxwvu…} ] } }

Content Addressed Data Hash-Linked Data { { Qm123456…: { data: “Hello world”, links: [ {name: “company”, hash: Qmabcdef…} {name: “license”, hash: Qmzyxwvu…} ] } } Qmabcdef…: { data: “FISSION”, links: [ {name: “city”, hash: Qm1gb5sn…}, {name: “about”, hash: Qmzyxwvu…} ] } } ipfs cat /ipfs/Qm123456…/company/about/founder => “Brooke”

Content Addressed Data Tradeoffs • Equality vs identity • Recovering identity from structural equality, but not vice-versa • Caching is trivial • Data fetches • Artifacts • Results of computation • Zooko’s Triangle

Content Addressed Data P2P Discovery, Lookup, Transport

Content Addressed Data P2P Discovery, Lookup, Transport 💁

Content Addressed Data P2P Discovery, Lookup, Transport 💻 💻 ☕ 💻 💁

Content Addressed Data P2P Discovery, Lookup, Transport 💻 💻 💻 💻 💻 ☕ 💻 💻 💁 💻 💻 💻 💻 💻

Content Addressed Data P2P Discovery, Lookup, Transport 💻 💻 💁 💻

Content Addressed Data Mutable Pointer Broadcast: DNSLink 💻🖥 🖥💻 💻 👩💻 ☁ 🔗 https://yourname.example.com 👨🎤

Content Addressed Data Mutable Pointer Broadcast: DNSLink 💻🖥 🖥💻 ☁ 🔗 https://yourname.example.com TXT => CID 💻 👩💻 👨🎤

Content Addressed Data Mutable Pointer Broadcast: DNSLink 💻🖥 🖥💻 💻 👩💻 ☁ 🔗 https://yourname.example.com 👨🎤

Content Addressed Data Mutable Pointer Broadcast: DNSLink 💻🖥 🖥💻 🧘 ☁ 🔗 https://yourname.example.com 👨🎤

Content Addressed Data Mutable Pointer Broadcast: DNSLink 💻🖥 🖥💻 ☁ 🔗 https://yourname.example.com TXT => CID 🧘 👨🎤

Content Addressed Data Mutable Pointer Broadcast: DNSLink 💻🖥 🖥💻 🧘 ☁ 🔗 https://yourname.example.com 👨🎤

Content Addressed Data

Content Addressed Data So we have a universal namespace.

Content Addressed Data So we have a universal namespace. Great!

Content Addressed Data So we have a universal namespace. Great! Well that seems pretty insecure…

Securing Data Access Fixing the Leaky Pipes 🚿

Securing Data Access Grouped by User, Not by App

Securing Data Access Grouped by User, Not by App f f f Alice’s Stu Bob’s Stu Carol’s Stu

Securing Data Access Grouped by User, Not by App Bob’s Photo Gallery 🖼 f f f Alice’s Stu Bob’s Stu Carol’s Stu

Securing Data Access Grouped by User, Not by App Bob’s Photo Gallery 🖼 Alice’s Stu Bob’s Stu Carol’s Stu f f f Carol’s Videogame 👾

Securing Data Access Grouped by User, Not by App Alice’s Stu Mu Alic sic e’s Pla 🎶 yer Bob’s Photo Gallery 🖼 Bob’s Stu Carol’s Stu f f f Carol’s Videogame 👾

Securing Data Access WNFS Layout

Securing Data Access WNFS Layout alice.fission.name

Securing Data Access WNFS Layout Public Photos Avatars Apps alice.fission.name

Securing Data Access WNFS Layout alice.fission.name Public Photos Avatars Private Apps Photos Apps Family Photos My Gallery

Securing Data Access WNFS Layout alice.fission.name Public Photos Avatars Private Apps Shared By Me Photos Apps Family Photos My Gallery Keys and Keys Keysand and Pointers Pointers Pointers

Securing Data Access WNFS Layout alice.fission.name Public Photos Avatars Private Apps Shared By Me Photos Apps Family Photos My Gallery Keys and Keys Keysand and Pointers Pointers Pointers Shared w/ Me Keys and Pointers

Securing Data Access Virtual Nodes

Securing Data Access Virtual Nodes Raw Node

Securing Data Access Virtual Nodes Raw Node File Node Raw Data Metadata

Securing Data Access Virtual Nodes Raw Node File Node Raw Data Metadata Directory Node Index Metadata

Securing Data Access Virtual Nodes File Node Raw Node • Virtual Node Raw Data • Consistent interface • Arbitrary metadata • Tags, creators, MIME, sources, &c Metadata Directory Node Index Metadata

Securing Data Access Hard & Soft Links

Securing Data Access Hard & Soft Links • Hard links • New for the web! • Direct reference • 2 pointers ~ duplicate

Securing Data Access Hard & Soft Links • Hard links • New for the web! • Direct reference • 2 pointers ~ duplicate • Soft links • Like a symlink or web link • 2 pointers ~ latest • May break • Always some version available

Securing Data Access Persistent Versioning & Events

Securing Data Access Persistent Versioning & Events Photos@r0 Vacation Avatars@r0 beach.png caricature.jpg Revision 0

Securing Data Access Persistent Versioning & Events Photos@r0 Vacation Avatars@r0 beach.png caricature.jpg Revision 0 🕙

Securing Data Access Persistent Versioning & Events Photos@r0 Photos@r1 Vacation Avatars@r0 Avatars@r1 beach.png caricature.jpg headshot.png Revision 0 Revision 1 🕙

Securing Data Access Persistent Versioning & Events Photos@r0 ChildEvent Vacation Avatars@r0 beach.png caricature.jpg Photos@r1 InsertNew Revision 0 headshot.png Revision 1 🕙 Avatars@r1

Securing Data Access Persistent Versioning & Events Photos@r0 ChildEvent Vacation Avatars@r0 beach.png caricature.jpg Photos@r1 InsertNew Revision 0 Avatars@r1 headshot.png Revision 1 🕙 Generation 0

Securing Data Access Persistent Versioning & Events Generation 0 Generation 1 Photos@r0 ChildEvent Vacation Avatars@r0 beach.png caricature.jpg Photos@r1 InsertNew Revision 0 headshot.png Revision 1 🕙 Avatars@r1

Securing Data Access Rearranged Photos@r1 Photos@r0 Vacation Avatars@r0 beach.png caricature.jpg Avatars@r1 headshot.png

Securing Data Access Private Nodes 🙈 CBOR Binary Encrypted Node 🔒 AES256 + 🔑 Virtual Node = Index 🔑 🔑 Metadata 🔑

Securing Data Access Cryptree 🎄 Virtual Node Virtual Node 🔑 Index 🔑 🔑 Metadata 🔑 🔑 🔑 Index Metadata

Cryptree 🎄 Virtual Node Virtual Node 🔑 Index 🔑 🔑 Metadata 🔑 🔑 name: “beach.jpg” revision: 42 key: “B374A26A71490437A…” 🔑

, } , { Securing Data Access Index Metadata

🔑 Cryptree 🎄 Virtual Node Virtual Node 🔑 Index 🔑 🔑 Metadata 🔑 🔑 name: “beach.jpg” revision: 42 key: “B374A26A71490437A…” 🔑

, } , { Securing Data Access Index Metadata

🔑 Cryptree 🎄 Virtual Node Virtual Node 🔑 Index 🔑 🔑 Metadata 🔑 🔑 name: “beach.jpg” revision: 42 key: “B374A26A71490437A…” 🔑

, } , { Securing Data Access Index Metadata

Securing Data Access Subtree Read Access

Securing Data Access Encrypted Tree is Surprisingly Efficient

Securing Data Access Encrypted Tree is Surprisingly Efficient HAMT (weight 16)

Securing Data Access Encrypted Tree is Surprisingly Efficient HAMT 163 = 4,096 items (weight 16) 164 = 65,536 items

Securing Data Access Encrypted Tree is Surprisingly Efficient HAMT 163 = 4,096 items (weight 16) 164 = 65,536 items Append-only Quick Read/Write Merkleized Concurrency Friendly

Securing Data Access Encrypted Tree is Surprisingly Efficient HAMT 163 = 4,096 items (weight 16) 164 = 65,536 items Append-only Quick Read/Write Merkleized Concurrency Friendly 🔑

Securing Data Access Namefilters & Hiding Paths

Securing Data Access Namefilters & Hiding Paths • Bare Filter • parentFilte • AND bloom(SHA(aesKey) • AND bloom(SHA(aesKey ++ revision) • Saturation • nameFilter AND bloom(SHA(nameFilter) ) ) ) r • Repeat until threshold bits flipped

Securing Data Access Access-Mediated Collaborative Rooting

Securing Data Access Access-Mediated Collaborative Rooting Rev 0

Securing Data Access Access-Mediated Collaborative Rooting Rev 0 Rev 1 (Partial)

Securing Data Access Access-Mediated Collaborative Rooting Rooting progress Rev 0 Rev 1 (Partial)

Securing Data Access Access-Mediated Collaborative Rooting Rooting progress No common root at this layer! Attached via HAMT Rev 0 Rev 1 (Partial)

Securing Data Access Progressive Fast Forward Rev 0 Rev 1 (Partial)

Securing Data Access Progressive Fast Forward Rev 0 Rev 1 (Partial) Rev 2 (Partial)

Securing Data Access Progressive Fast Forward Rev 3 (Complete) Rev 0 Rev 1 (Partial) Rev 2 (Partial)

Securing Data Access Progressive Fast Forward current rev + 2n Rev 3 (Complete) Rev 0 Rev 1 (Partial) Rev 2 (Partial)

Securing Data Access Progressive Fast Forward current rev + 2n —2m current rev + 2n Rev 3 (Complete) Rev 0 Rev 1 (Partial) Rev 2 (Partial)

Securing Data Access Progressive Fast Forward current rev + 2n —2m current rev + 2n O(2 * log n) Θ(1) 🎉 Rev 3 (Complete) Rev 0 Rev 1 (Partial) Rev 2 (Partial)

Securing Data Access File Sharing

Securing Data Access File Sharing Shared by Me

Securing Data Access File Sharing Shared by Me did:key:zStEksDrxkwYmpzqB did:key:zStEksDrxkwYmpzqB did:key:zStEksDrxkwYmpzqB dAQjjx1PRbHG3fq4ChGeJcYU dAQjjx1PRbHG3fq4ChGeJcYU dAQjjx1PRbHG3fq4ChGeJcYU YU44a4CBUExTTjeCbop6Uur YU44a4CBUExTTjeCbop6Uur YU44a4CBUExTTjeCbop6Uur

Securing Data Access File Sharing Shared by Me did:key:zStEksDrxkwYmpzqB did:key:zStEksDrxkwYmpzqB did:key:zStEksDrxkwYmpzqB dAQjjx1PRbHG3fq4ChGeJcYU dAQjjx1PRbHG3fq4ChGeJcYU dAQjjx1PRbHG3fq4ChGeJcYU YU44a4CBUExTTjeCbop6Uur YU44a4CBUExTTjeCbop6Uur YU44a4CBUExTTjeCbop6Uur Human Readable Name 🔑 Symlink

Securing Data Access File Sharing Shared by Me Shared with Me did:key:zStEksDrxkwYmpzqB did:key:zStEksDrxkwYmpzqB did:key:zStEksDrxkwYmpzqB dAQjjx1PRbHG3fq4ChGeJcYU dAQjjx1PRbHG3fq4ChGeJcYU dAQjjx1PRbHG3fq4ChGeJcYU YU44a4CBUExTTjeCbop6Uur YU44a4CBUExTTjeCbop6Uur YU44a4CBUExTTjeCbop6Uur Human Readable Name 🔑 Symlink

Securing Data Access

Securing Data Access So we can read recursively encrypted trees that live anywhere.

Securing Data Access So we can read recursively encrypted trees that live anywhere. Great!

Securing Data Access So we can read recursively encrypted trees that live anywhere. Great! How do you do writes if a a server can’t check the content?

User Controlled, Serverless, Universal Auth & ID …and UCAN Too 💪

UCAN Self-Sovereign Identity 🔑

UCAN Self-Sovereign Identity • W3C 🔑

UCAN Self-Sovereign Identity • W3C • Microsoft 🔑

UCAN Self-Sovereign Identity • W3C • Microsoft • Government of British Columbia 🔑

UCAN Self-Sovereign Identity • W3C • Microsoft • Government of British Columbia • Based on public-key cryptography 🔑

UCAN Self-Sovereign Identity • W3C • Microsoft • Government of British Columbia • Based on public-key cryptography • Truly “universal” user IDs 🔑

UCAN Self-Sovereign Identity • W3C • Microsoft • Government of British Columbia • Based on public-key cryptography • Truly “universal” user IDs • Agnostic about backing 🔑

UCAN Self-Sovereign Identity • W3C • Microsoft • Government of British Columbia • Based on public-key cryptography • Truly “universal” user IDs • Agnostic about backing • For users, devices, and more 🔑

UCAN Object Capability Model (OCAP)

UCAN Object Capability Model (OCAP) • ACL is “reactive auth” / OCAP is “proactive auth”

UCAN Object Capability Model (OCAP) • ACL is “reactive auth” / OCAP is “proactive auth” • OCAP contains all the info about access

UCAN Object Capability Model (OCAP) • ACL is “reactive auth” / OCAP is “proactive auth” • OCAP contains all the info about access • Generally some reference, proof, or key • Rights to anything directly created (parenthood) • The right to delegate subset of access to another (introduction)

UCAN Object Capability Model (OCAP) • ACL is “reactive auth” / OCAP is “proactive auth” • OCAP contains all the info about access • Generally some reference, proof, or key • Rights to anything directly created (parenthood) • The right to delegate subset of access to another (introduction) • Long history (e.g. X.509, SDSI, SPKI, Macaroons)

UCAN 3rd-party Redelegation & Attenuation

UCAN 3rd-party Redelegation & Attenuation 🖥

UCAN 3rd-party Redelegation & Attenuation 🖥 ⚙

UCAN 3rd-party Redelegation & Attenuation 🖥 🔟 ⚙

UCAN 3rd-party Redelegation & Attenuation 🖥 🔟 ⚙ 🛠

UCAN 3rd-party Redelegation & Attenuation 🖥 🔟 ⚙ 2⃣ 🛠

UCAN JWT

UCAN Auth Chaining • OCAP, provable chains, revocable • Non-exportable 2048-bit RSA (WebCrypto), Ed25519 & BLS everywhere else

UCAN OAuth vs UCAN Sequence

UCAN OAuth vs UCAN Sequence (Verifiable & user originated)

Final Thoughts 🙊

Final Thoughts More Coming — Embarrassingly Distributed Deductive Database

Final Thoughts More Coming — Embarrassingly Distributed Deductive Database Source I

Final Thoughts More Coming — Embarrassingly Distributed Deductive Database Source I User+App A

Final Thoughts More Coming — Embarrassingly Distributed Deductive Database Source I User+App A Source II

Final Thoughts More Coming — Embarrassingly Distributed Deductive Database B Source II Us e r+A pp Source I User+App A

Final Thoughts More Coming — Embarrassingly Distributed Deductive Database pp D User+App C User+App A B r+A r+A Us e Us e Source II pp Source I

Final Thoughts More Coming — Embarrassingly Distributed Deductive Database • Assert, refute, time, source D User+App C • Merge / split easily • Access control = di erent views • JSON in the front, Datalog in the back 🧑🎤 • Help define API? calendly.com/walkah ff pp User+App A B r+A r+A Us e Us e Source II pp Source I

Final Thoughts More Coming — Universal Distributed Compute Off-Platform Side Effect Stream Platform Effect Stream Pure Function Stream Base Event Stream

Final Thoughts Stack 1st & 3rd Party Dev’s App Business Logic & View API Platform Abstractions WebNative SDK ⬆ Apps ⬇ Core Technology Broadcast Collaboration, Chat, Instant Sync Soft Realtime Store Durable Structured Store WebNative Database O ine & Async Sharing Exchange Store Durable File Store WebNative File System Durable Data Command/Mutation UCAN ffl Auth & ID Global: Aggregation, Forms, Feeds Gossip Broadcast Read/Query Cryptree Networking DNS, IPFS, PubSub, Matrix Identity did:key

Final Thoughts 60+ Year Trend

Final Thoughts 60+ Year Trend High Touch Invisible Custom Product / Rental Commodity / Utility

Final Thoughts 60+ Year Trend High Touch Ba rrie r to Ent ry Invisible Custom Product / Rental Commodity / Utility

Final Thoughts 60+ Year Trend High Touch Bespoke Private Ownership Ba rrie r to Ent ry Shared Hosting Serverless Universal Invisible Custom Product / Rental Commodity / Utility

https://fission.codes https://guide.fission.codes https://discord.gg/zAQBDEq 😄 Thank You, Speakeasy JS 🎉 brooklyn@fission.codes github.com/expede @expede shop.fission.codes Code: SPEAKEASYJS