Built with durable infrastructure — explained simply.
For the people who want to know what FamilyChain is built on and why those choices matter.
The point of the stack
FamilyChain is not technical for the sake of being technical.
The architecture exists to solve a practical problem: most family data lives inside apps and platforms you do not control. If those platforms change direction, your data, experience, and long-term continuity are at risk.
So the FamilyChain stack is designed around three goals: easy access, durable ownership, and long-term persistence.
The Core Components
Sui
Sui provides the underlying object model and transaction system. It is a strong fit for family-level ownership because shared objects, permissions, and evolving state are first-class concepts.
zkLogin
zkLogin lets people sign in with familiar accounts like Google while still getting a real on-chain identity. That means easier onboarding without forcing normal families through wallet-first friction.
Walrus
Walrus is used for durable decentralized storage. It is the right place for messages, media, and family content that should not depend on a traditional centralized application server.
Move smart contracts
Move modules handle family objects, permissions, reward logic, and the systems that need clear, auditable rules underneath the app experience.
Why this matters to a normal family
Easier access
Sign-in should feel familiar. Families should not need to learn crypto before they can use the product.
Better continuity
Family history, rewards, and shared structures should not vanish because one company changes the rules.
Stronger ownership
The system should be closer to a family-owned asset than a rented social account.
Under the hood, in plain English
Identity
Users authenticate through a familiar sign-in flow, then receive an on-chain identity that the app can work with.
Family object
Each family can be modeled as a durable object with members, permissions, and evolving shared state.
App logic
Tasks, rewards, approvals, and other family mechanics can be enforced through code rather than loose promises in a centralized database.
Stored content
Long-lived family content can sit on decentralized storage rather than only inside a private server stack.
What comes later
This page is intentionally clear and high level. Over time, it can expand with architecture diagrams, flowcharts, module breakdowns, sponsorship design, auth/session design, and storage flows.
That way, non-technical visitors can still understand the choices, while technical readers can go as deep as they want.
Want the product view instead?
See how these technical choices show up in the actual family experience.
Go to Features