Kipio
Kipio is a decentralized vault for permanent, private ownership of personal content, built to give people lasting control over their digital memories.
Videos

Tech Stack
Description
Kipio is a decentralized protocol and consumer application for permanent, private ownership of digital content. It is designed to give users long-term control over their memories and personal data without depending on centralized platforms or recurring subscriptions.
The Problem
Loss of digital ownership: Personal memories are increasingly dependent on centralized platforms, accounts, subscriptions, and proprietary services.
Centralized storage: Users often have little control over how their content is stored, accessed, or preserved over the long term.
Platform dependency: Moving between services can mean losing access, metadata, or continuity of personal data.
The Solution: A Sovereign Content Protocol
Client-side encryption: Content is encrypted before leaving the user's device.
Permanent decentralized storage: Encrypted content is preserved through decentralized permanent storage infrastructure.
On-chain ownership layer: Arbitrum provides the blockchain layer for user-specific state and content metadata without storing the actual files on-chain.
Open protocol: The underlying infrastructure is designed so other applications and services can interact with Kipio rather than being locked into a single consumer application.
Broader content support: Photos and family memories are the initial use case, but the protocol is designed to support personal content more generally.
Verification and Architecture
Kipio is currently being developed on Arbitrum using Rust and Arbitrum Stylus. Core domain logic is being formally specified and verified with Dafny before being translated into Rust and integrated into the on-chain implementation.
Long-Term Vision
Kipio is designed to support both B2C and B2B use cases. Organizations could integrate with the open protocol or subsidize access for their users, while protocol-level usage fees and other economic mechanisms can provide sustainable infrastructure economics.
The long-term goal is not simply decentralized storage, but infrastructure that gives individuals and organizations stronger control over the ownership, preservation, and portability of their digital content.
Progress During Hackathon
Kipio predates this Buildathon and has been under active development for approximately six months, with an MVP already running on testnet. Beyond the MVP, the development branch contains extensive ongoing research, experimentation, and architectural work.
The main branch state submitted to ETHGlobal shows the state of the project used for that hackathon. In parallel, the development branch state immediately before this Buildathon reflects the more advanced work that continued beyond the ETHGlobal submission. The original Arbitrum Sepolia contract also provides an on-chain history of the project.
Goals for this Buildathon
Evolve Kipio toward a truly multichain protocol.
Adapt the formally verified Dafny domain model to Rust and then to Arbitrum Stylus.
Build the foundations for cross-chain interaction through Chainlink.
Publish and document the formalized domain model and verification work.
Continue developing Kipio as an open protocol focused on user sovereignty and ownership rather than simply shipping a faster MVP.
The final submission will document the concrete milestones achieved during the Buildathon through the project's commit history.
Fundraising Status
Bootstrapped
Kipio is currently bootstrapped and not yet funded by external investors. The project is in active development, with a working product running on testnet and the core protocol continuing to evolve toward a mainnet-ready system.
As a solo developer, the main purpose of future funding would be to turn the project from a one-person effort into a capable team. The priority would be hiring people with strong product and frontend design skills, marketing and growth expertise, and additional blockchain and protocol engineering experience.
The goal is not simply to fund development, but to build the team and product layer necessary to bring an already functioning protocol to a much larger number of users.