Decentralized Access Control with Medusa
summary
Medusa runs a threshold re-encryption network that lets a smart contract register a 32‑byte encrypted key (not the whole file) on-chain, then re-encrypt that key for a buyer after on‑chain payment. Demo uses Filecoin/IPFS for storage, Arbitrum and Hyperspace testnets for contracts, and a simple OnlyFiles dApp; demo completes payment→event→gossip→on‑chain response cycle with minor live glitches. SDK exposes register ciphertext, request re‑encrypt, and an OracleResult callback for front ends.
AI-written summary · about
chapters (7)
- 0:00Medusa introduction
- 2:23What is Medusa
- 8:21Only Files demo
- 16:21Live demo Only Files
- 20:56Documentation and SDK walkthrough
- 25:29Medusa integration code
- 30:44Medusa future Q&A
related talks
34mPrivacy All the Way Down: Tackling MEV at Different Layers via. Cryptography
01h 00mPrivacy Preserving Data Manipulation in Decentralized Systems
28mManage dApp Secrets: Create Private Data Sharing
01h 00mPrivacy Preserving Smart Contracts
15mEncrypt or Die
12mWeb 3.0 Realized With Traceless Privacy and Seamless Compatibility
16mDecentralized Secrets for Identities Networks & Platforms
31m🛠 Building Applications with Filecoin & FEVM