UCAN & WNFS 🌳 What, Why, and Integration 🦜
A presentation at UCAN for FileCoin in August 2021 in by Brooklyn Zelenka
UCAN & WNFS 🌳 What, Why, and Integration 🦜
Decentralized Digital Identity DIDs 🛂
Decentralized Digital Identity DIDs
Decentralized Digital Identity DIDs • One or more public keys • Truly “universal” user IDs • Agnostic about backing • Self-attesting • Database • Blockchain • For users, devices, and more • Relates to verifiable credentials
Decentralized Digital Identity did:key & UCAN
Decentralized Digital Identity did:key & UCAN • “Just” a public key (e.g. RSA, EdDSA)
Decentralized Digital Identity did:key & UCAN • “Just” a public key (e.g. RSA, EdDSA) • Self-certifying, extremely flexible
Decentralized Digital Identity did:key & UCAN • “Just” a public key (e.g. RSA, EdDSA) • Self-certifying, extremely flexible • Well suited to capabilities/authZ (vs identity/authN)
Decentralized Digital Identity did:key & UCAN • “Just” a public key (e.g. RSA, EdDSA) • Self-certifying, extremely flexible • Well suited to capabilities/authZ (vs identity/authN) • Made practical with UCANs • did:key → authN • UCAN → authZ
Decentralized Digital Identity Variety
Decentralized Digital Identity Variety • Microsoft ION, 3Box’s Ceramic, Sovrin, did:key, and well over 400 others
Decentralized Digital Identity Variety • Microsoft ION, 3Box’s Ceramic, Sovrin, did:key, and well over 400 others • Can federate, but hasn’t been done yet win the wild • Fission working towards interop with ION as first step
User Controlled, Local-First, Universal Auth & ID UCAN 🕊
UCAN Fission Use Case → Highly Flexible & Secure
UCAN Fission Use Case → Highly Flexible & Secure • Work directly in a browser without plugins
UCAN Fission Use Case → Highly Flexible & Secure • Work directly in a browser without plugins • Browser is hostile — compatible with WebCrypto non-exportable keys
UCAN Fission Use Case → Highly Flexible & Secure • Work directly in a browser without plugins • Browser is hostile — compatible with WebCrypto non-exportable keys • User controlled / user owned
UCAN Fission Use Case → Highly Flexible & Secure • Work directly in a browser without plugins • Browser is hostile — compatible with WebCrypto non-exportable keys • User controlled / user owned • Pseudonymous, principle of least authority & least visibility
UCAN Fission Use Case → Highly Flexible & Secure • Work directly in a browser without plugins • Browser is hostile — compatible with WebCrypto non-exportable keys • User controlled / user owned • Pseudonymous, principle of least authority & least visibility • Won’t always have access to the “root” device
UCAN Fission Use Case → Highly Flexible & Secure • Work directly in a browser without plugins • Browser is hostile — compatible with WebCrypto non-exportable keys • User controlled / user owned • Pseudonymous, principle of least authority & least visibility • Won’t always have access to the “root” device ffl • Must work o ine
UCAN Fission Use Case → Highly Flexible & Secure • Work directly in a browser without plugins • Browser is hostile — compatible with WebCrypto non-exportable keys • User controlled / user owned • Pseudonymous, principle of least authority & least visibility • Won’t always have access to the “root” device • Must work o ine ffl • Extensible semantics
UCAN Fission Use Case → Highly Flexible & Secure • Work directly in a browser without plugins • Browser is hostile — compatible with WebCrypto non-exportable keys • User controlled / user owned • Pseudonymous, principle of least authority & least visibility • Won’t always have access to the “root” device • Must work o ine • Extensible semantics ffl • Flexible granularity
UCAN Fission Use Case → Highly Flexible & Secure • Work directly in a browser without plugins • Browser is hostile — compatible with WebCrypto non-exportable keys • User controlled / user owned • Pseudonymous, principle of least authority & least visibility • Won’t always have access to the “root” device • Must work o ine • Extensible semantics • Flexible granularity ffl • Revocable
UCAN Object Capability Model (OCAP)
UCAN Object Capability Model (OCAP) • ACL is “reactive auth”
UCAN Object Capability Model (OCAP) • ACL is “reactive auth” 👩🎤
UCAN Object Capability Model (OCAP) • ACL is “reactive auth” 👩🎤 ⚙
UCAN Object Capability Model (OCAP) • ACL is “reactive auth” 👩🎤 👮 ✋ ⚙
UCAN Object Capability Model (OCAP) • ACL is “reactive auth” 📑 👩🎤 👮 ✋ ⚙
UCAN Object Capability Model (OCAP) • ACL is “reactive auth” 📑 👩🎤 👮 ✋ ⚙
UCAN Object Capability Model (OCAP) ACL • ACL is “reactive auth” 📑 👩🎤 👮 ✋ ⚙
UCAN Object Capability Model (OCAP) ACL • ACL is “reactive auth” 📑 • OCAP is “proactive auth” • Contains all the info about access • Any guarding done up front (e.g. time limiting) • Generally some reference, proof, or key • Anything directly created (parenthood) • Delegate subset of access to another (introduction) • Long history (e.g. X.509, SDSI, SPKI, Macaroons) 👩🎤 👮 ✋ ⚙
UCAN Object Capability Model (OCAP) ACL • ACL is “reactive auth” 📑 • OCAP is “proactive auth” • Contains all the info about access • Any guarding done up front (e.g. time limiting) • Generally some reference, proof, or key 👩🎤 • Anything directly created (parenthood) • Delegate subset of access to another (introduction) • Long history (e.g. X.509, SDSI, SPKI, Macaroons) 👩🎤 👮 ✋ ⚙
UCAN Object Capability Model (OCAP) ACL • ACL is “reactive auth” 📑 • OCAP is “proactive auth” • Contains all the info about access • Any guarding done up front (e.g. time limiting) • Generally some reference, proof, or key 👩🎤 👮 ✋ ⚙ • Anything directly created (parenthood) • Delegate subset of access to another (introduction) • Long history (e.g. X.509, SDSI, SPKI, Macaroons) 👩🎤 ⚙
UCAN Object Capability Model (OCAP) ACL • ACL is “reactive auth” 📑 • OCAP is “proactive auth” • Contains all the info about access • Any guarding done up front (e.g. time limiting) • Generally some reference, proof, or key 👩🎤 ✋ 👮 ⚙ 👩🎤 🎟 ⚙ • Anything directly created (parenthood) • Delegate subset of access to another (introduction) • Long history (e.g. X.509, SDSI, SPKI, Macaroons)
UCAN Object Capability Model (OCAP) ACL • ACL is “reactive auth” 📑 • OCAP is “proactive auth” • Contains all the info about access • Any guarding done up front (e.g. time limiting) • Generally some reference, proof, or key 👩🎤 • Anything directly created (parenthood) • Delegate subset of access to another (introduction) • Long history (e.g. X.509, SDSI, SPKI, Macaroons) 👮 ✋ ⚙ OCAP 👩🎤 🎟 ⚙
UCAN Chained Attenuation
UCAN Chained Attenuation 👩💻
UCAN Chained Attenuation 👩💻 🌈 🐶 🍬 🍾 🧸
UCAN Chained Attenuation 👩💻 🌈 🐶 🍬 🍾 🧸 👨🦳🖥
UCAN Chained Attenuation 👩💻 👨🦳🖥 🌈 🐶 🍬 🍾 🧸 🌈 🐶 🍬 🍾 🧸
UCAN Chained Attenuation 👩💻 👨🦳🖥 👨🦳📱 🌈 🐶 🍬 🍾 🧸 🌈 🐶 🍬 🍾 🧸 🌈 🐶 🧸
UCAN Chained Attenuation 👩💻 👨🦳🖥 👨🦳📱 🌈 🐶 🍬 🍾 🧸 🌈 🐶 🍬 🍾 🧸 🌈 🐶 🧸 👩🚀 🐶
UCAN Chained Attenuation 👩💻 👨🦳🖥 👨🦳📱 🌈 🐶 🍬 🍾 🧸 🌈 🐶 🍬 🍾 🧸 🌈 🐶 🌈 🍾 🧸 👨🎨 🧸 👩🚀 🐶
UCAN Chained Attenuation 👩💻 👨🦳🖥 👨🦳📱 🌈 🐶 🍬 🍾 🧸 🌈 🐶 🍬 🍾 🧸 🌈 🐶 🌈 🌈 🧸 🍾 🧸 👨🎨 ☁⚙ 👩🚀 🐶
UCAN Chained Attenuation 👩💻 👨🦳🖥 👨🦳📱 🌈 🐶 🍬 🍾 🧸 🌈 🐶 🍬 🍾 🧸 🌈 🐶 🌈 🌈 👩🚀 🐶 🧸 🌈 🐶 🍾 🧸 👨🎨 ☁⚙ 💃
UCAN Tradeoffs & Hybridization
UCAN Tradeoffs & Hybridization • Pure ACL, reactive • Centrally view who has access to what • Check on every request, bottleneck • At-will revocation • Access rules grow in complexity • More complex provisioning
UCAN Tradeoffs & Hybridization • Pure ACL, reactive • Pure OCAP, proactive • Centrally view who has access to what • Works o ine & everywhere • Check on every request, bottleneck • User owned or provisioned • At-will revocation • No resource contention, infinite scale • Access rules grow in complexity • Easy interop (as we’ll see) • More complex provisioning • Principle of least authority • Revocation more di cult ff ffi ffl • Tracking possible but has tradeo s
UCAN OAuth Sequence
UCAN UCAN Sequence 🕙 🕙
UCAN Revocation Cascade 👩💻 👨🦳🖥 👨🦳📱 🌈 🐶 🍬 🍾 🧸 🌈 🐶 🍬 🍾 🧸 🌈 🐶 🌈 🌈 👩🚀 🐶 🧸 🌈 🐶 🍾 🧸 👨🎨 ☁⚙ 💃
UCAN Revocation Cascade UCAN CID 👩💻 👨🦳🖥 👨🦳📱 🌈 🐶 🍬 🍾 🧸 🌈 🐶 🍬 🍾 🧸 🌈 🐶 🌈 🌈 👩🚀 🐶 🧸 🌈 🐶 🍾 🧸 👨🎨 ☁⚙ 💃
UCAN JWT
UCAN Auth Chaining • OCAP, provable chains, revocable • Non-exportable 2048-bit RSA (WebCrypto), Ed25519 & BLS everywhere else
UCAN Trustless Interop 🛂 OIDC Server 🤖 👽 Service A Service B UCAN with 💁 ID / email Describes o er for 🤖 OIDC Login OIDC Token O er for 🤖+💁 Secured with signature 👽 and HMAC 💁🛂 💁’s OIDC token? 💁’s OIDC token! Check 💁 HMAC and 👽 signature Update 🤖 subscription for 💁 ff ff 204 Accepted 💁 User
High Level Auth Topologies OCAP FileCoin & Accounts ✍
OCAP FileCoin & Accounts Fully Managed (Similar to Today)
OCAP FileCoin & Accounts Fully Managed (Similar to Today) ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓
OCAP FileCoin & Accounts Fully Managed (Similar to Today) ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ 🧘
OCAP FileCoin & Accounts Fully Managed (Similar to Today) ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ 🧘 🛢🛢DB🛢🛢
OCAP FileCoin & Accounts Fully Managed (Similar to Today) ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ 🧘 👩💻🔑 🛢🛢DB🛢🛢
OCAP FileCoin & Accounts Fully Managed (Similar to Today) ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ 🧘 👩💻🔑 🛢🛢DB🛢🛢 👩💻💻 💰💰 💰 🗝 💾
OCAP FileCoin & Accounts Fully Managed (Similar to Today) ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ” n io s i v o Pr 👩💻🔑 🛢🛢DB🛢🛢 💾 💰1 💰 AN “ 🧘 👩💻💻 💰 UC 💰💰 💰 🗝 💾
OCAP FileCoin & Accounts Fully Managed (Similar to Today) ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ” n io s i v o Pr 👩💻🔑 🛢🛢DB🛢🛢 💾 💰1 💰 AN “ 🧘 👩💻💻 💰 UC 💰💰 💰 🗝 💾 💰💾 UCAN 2 👩💻📱 💰 💾
OCAP FileCoin & Accounts Fully Managed (Similar to Today) ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ” n io s i v o Pr 💾 💰1 💰 AN “ 🧘 👩💻💻 💰 UC 💰💾 👩💻🔑 🛢🛢DB🛢🛢 💰💰 💰 🗝 💾 UCAN 2 💰 💾 UC AN 3 TX 🧾 👩💻📱 💰 💾
OCAP FileCoin & Accounts Fully Managed (Similar to Today) ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ” n io s i v o Pr TX 🧾 💾 💰1 💰 AN “ 🧘 👩💻💻 💰 UC 💰💾 👩💻🔑 🛢🛢DB🛢🛢 💰💰 💰 🗝 💾 UCAN 2 💰 💾 UC AN 3 TX 🧾 👩💻📱 💰 💾
OCAP FileCoin & Accounts BLS Cosigner (Self Sovereign) ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ Registration 🧘 2/3 PK for 🔐? 🗝1+🗝2 = 🔑 PK(🗝2,) 👩💻🗝2 {PK(🔑ID), PK(🗝1) } 🗝 ( K UCAN 1 🧘 TX 🧾 👩💻🗝3 (🔐A, 🗝1) 💰💾 3) P 🗝1+🗝3 = 🔑 👩💻💻 👩💻📱 UCAN 2 TX 💰💾 🗝 🧾1 💰 (🔐B, 🗝1) 💾
OCAP FileCoin & Accounts Delegate-Aware Blockchain 💰 💰💰 🔑 💾 💾💾 ✨✨✨ ✨✨✨ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ ⛓ 👩💻💻 💰💾 UCAN 1 UCAN 2 TX 💰💾 🗝 🧾 UCAN 2 🤹 “Dumb” Relay TX 💰💾 🗝 🧾 👩💻📱 💰 🗝 💾
OCAP FileCoin & Accounts Bonus: Payment Channel Interop
OCAP FileCoin & Accounts Bonus: Payment Channel Interop ✨🧑🎨💻🔑 🧑🎨📱🗝 👩🔧🖥
OCAP FileCoin & Accounts Bonus: Payment Channel Interop ✨🧑🎨💻🔑 🧑🎨📱🗝 UCAN{ max: 200💰, from: 🔑, to: 🗝, sig: ✍ } 👩🔧🖥
OCAP FileCoin & Accounts Bonus: Payment Channel Interop ✨🧑🎨💻🔑 🧑🎨📱🗝 UCAN{ max: 200💰, from: 🔑, to: 🗝, sig: ✍ } sendTx(👩🔧, 100💰, UCAN{ max: 200💰, from: 🔑, to: 🗝 sig: ✍ }) 100💰 👩🔧🖥
OCAP FileCoin & Accounts Bonus: Payment Channel Interop ✨🧑🎨💻🔑 🧑🎨📱🗝 UCAN{ max: 200💰, from: 🔑, to: 🗝, sig: ✍ } sendTx(👩🔧, 100💰, UCAN{ max: 200💰, from: 🔑, to: 🗝 sig: ✍ }) 100💰 Countersigned Tx! Countersigned Tx! 👩🔧🖥
User Controlled, Serverless, Universal Auth & ID Read vs Write 👓🖋
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 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 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 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 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
Securing Data Access Persistent Versioning Photos@r0 Vacation Avatars@r0 beach.png caricature.jpg Revision 0
Securing Data Access Persistent Versioning Photos@r0 Vacation Avatars@r0 beach.png caricature.jpg Revision 0 🕙
Securing Data Access Persistent Versioning Photos@r0 Photos@r1 Vacation Avatars@r0 Avatars@r1 beach.png caricature.jpg headshot.png Revision 0 Revision 1 🕙
Securing Data Access Persistent Versioning Photos@r0 ChildHasEvent Vacation Avatars@r0 beach.png caricature.jpg Photos@r1 InsertNew Revision 0 headshot.png Revision 1 🕙 Avatars@r1
Securing Data Access Persistent Versioning Photos@r0 ChildHasEvent Vacation Avatars@r0 beach.png caricature.jpg Photos@r1 InsertNew Revision 0 headshot.png Revision 1 🕙 Avatars@r1
Securing Data Access Persistent Versioning Photos@r0 Generation 0 ChildHasEvent Vacation Avatars@r0 beach.png caricature.jpg Photos@r1 InsertNew Revision 0 headshot.png Revision 1 🕙 Avatars@r1
Securing Data Access Persistent Versioning Generation 0 Generation 1 Photos@r0 ChildHasEvent 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 Future Light Cone Restriction
Securing Data Access Future Light Cone Restriction • Ratchet keys for backwards secrecy • Spiral ratchet for quick fast forwards
Securing Data Access Future Light Cone Restriction • Ratchet keys for backwards secrecy • Spiral ratchet for quick fast forwards
Securing Data Access Future Light Cone Restriction • Ratchet keys for backwards secrecy • Spiral ratchet for quick fast forwards
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 & Hidden Paths
Securing Data Access Namefilters & Hidden Paths • Bare Filter • parentFilte • AND bloom(SHA(aesKey) • AND bloom(SHA(aesKey ++ revisionRatchet) • 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
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 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 Rev 3 (Complete) 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 Merkle CRDT Single File Version Shadow
Securing Data Access Merkle CRDT • Original paper from PL • Persistent data structure by default • Confluent with automated reconciliation • Innate causal clock via Merkle DAG • Coarse grained (path-level) Single File Version Shadow
Securing Data Access Async Granting Read & Write
Securing Data Access Async Granting Read & Write Shared by Me
Securing Data Access Async Granting Read & Write Shared by Me did:key:zStEksDrxkwYmpzqB did:key:zStEksDrxkwYmpzqB did:key:zStEksDrxkwYmpzqB dAQjjx1PRbHG3fq4ChGeJcYU dAQjjx1PRbHG3fq4ChGeJcYU dAQjjx1PRbHG3fq4ChGeJcYU YU44a4CBUExTTjeCbop6Uur YU44a4CBUExTTjeCbop6Uur YU44a4CBUExTTjeCbop6Uur
Securing Data Access Async Granting Read & Write 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 Async Granting Read & Write 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 Async Granting Read & Write 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 Async Granting Read & Write Shared with Me Shared by Me did:key:zStEksDrxkwYmpzqB did:key:zStEksDrxkwYmpzqB did:key:zStEksDrxkwYmpzqB dAQjjx1PRbHG3fq4ChGeJcYU dAQjjx1PRbHG3fq4ChGeJcYU dAQjjx1PRbHG3fq4ChGeJcYU YU44a4CBUExTTjeCbop6Uur YU44a4CBUExTTjeCbop6Uur YU44a4CBUExTTjeCbop6Uur Human Readable Name 🔑 Symlink
