Walrus
A decentralised storage and data-availability network built by Mysten Labs on Sui, using RedStuff erasure coding across a 1000-shard proof-of-stake committee. Its Walrus Memory product pitches wallet-owned, portable memory for AI agents, but the default configuration routes plaintext through a Foundation-run relayer and OpenAI, so the ownership record is on-chain while the live query path is not.
The strongest team in the Sui ecosystem built a genuinely decentralised storage network, and Walrus Memory is the most on-thesis product name in DeAI. But the default memory path trusts a Foundation relayer that sees your plaintext and ships it to OpenAI, with the searchable index in a centralised database. The ownership record is on-chain. The live query path, by default, is not.
- + Decentralised base storage done well: 1000-shard PoS committee, on-chain shard assignment and slashing, permissionless node registration
- + Elite doxxed team (Mysten Labs / Sui), Apache-2.0 across walrus, seal and MemWal, OtterSec audit, arXiv whitepaper
- + Mandatory token utility plus institutional access via the Grayscale Walrus Trust, and a healthier ~49% float
- − Default Walrus Memory relayer sees plaintext and exports to OpenAI; the live query index sits in a centralised database
- − Singular dependency on Sui, which halted for ~6h44m in May 2026 and paused Walrus
- − Soft value accrual (USD-denominated storage, no burn) and revenue not independently reconciled; not on DeFiLlama
Walrus scores 62/100 (Grade C -- partially decentralised with significant centralisation vectors). The base storage network is one of the stronger decentralised-storage designs in the space: a 1000-shard delegated-proof-of-stake committee, on-chain shard assignment and slashing, permissionless node registration, 4.5x erasure-coded redundancy, and fully open-source Apache-2.0 code with a published whitepaper and audit. Open-source transparency (13/15) and infrastructure (13/20) are the strongest dimensions.
The drag is at the edges: governance (8/20) still sits with Mysten Labs and the Foundation, and the DeAI product -- Walrus Memory -- weakens data sovereignty (10/15) and censorship resistance (9/15) because its default mode trusts a Foundation-run relayer that sees plaintext and ships it to OpenAI, with the searchable index in a centralised Postgres database. Walrus is also singularly dependent on Sui, which halted for nearly seven hours in May 2026. The ownership record is genuinely on-chain; the live query path, by default, is not.
Overall returns potential is moderate at 55/100. Strongest dimension: token utility (14/20). Weakest: revenue sustainability (10/25).
Not financial advice. Scores are opinions, not recommendations. Crypto is high-risk – you could lose everything you invest. Full disclaimer.
Embed this rating
The badge updates automatically when the score changes.
On this page
Storage paid in WAL, erasure-coded across shards, fees routed to nodes and stakers
A user or app stores a blob and pays the fee in WAL; the protocol registers it on Sui and takes the fee upfront. RedStuff 2D erasure coding splits the blob into slivers spread across a fixed 1000 shards at about 4.5x redundancy, so data survives even when two-thirds of fragments are lost. Storage nodes hold and serve their slivers, kept honest by on-chain slashing. The fee is paid out to nodes and delegated stakers per epoch, and staked WAL secures the committee. Seal adds client-side threshold encryption, and Walrus Memory layers wallet-owned agent memory on top.
What it does
Walrus is a decentralised storage and data-availabilityData AvailabilityThe guarantee that data a system depends on can actually be retrieved by anyone who needs it, when they need it. A data-availability layer stores data and proves it is retrievable, so applications do not have to trust a single host.Like a public library that not only holds a book but guarantees any member can walk in and borrow it. It is not enough that the book exists somewhere; the promise is that you can get it on demand, without asking the author's permission.Read more → network built by Mysten Labs, the team behind the Sui blockchain. You upload a file, Walrus splits it into fragments, spreads those fragments across a network of independent storage nodes, and lets anyone retrieve or verify the file without trusting a single host. It went live on mainnet on 25 March 2025.
The core technique is erasure codingErasure CodingA technique that splits data into fragments and adds redundant fragments, so the original can be rebuilt even if many fragments are lost. Decentralised storage networks use it to survive node failures without storing full copies everywhere.Like a jigsaw puzzle designed so that any two-thirds of the pieces are enough to see the whole picture. You can lose a third of the box and still reconstruct the image, without having printed three complete copies of it.Read more →. Walrus uses a two-dimensional scheme called RedStuff that encodes each blob into primary and secondary slivers spread across a fixed set of 1000 shards. The security model tolerates up to a third of shards being faulty or malicious, and a blob can be rebuilt from a third of its slivers, so data survives even when two-thirds of the fragments are gone. Redundancy runs at about 4.5 times the raw file size, against roughly 25 times for full replication. That efficiency is the whole pitch: resilient, verifiable storage that doesn’t cost a fortune.
Sui does the coordination. Each blob is a Sui object, and registration, payments, shard assignment, staking and slashingSlashingA penalty in Proof of Stake networks that destroys or confiscates part of a validator's staked tokens when it misbehaves, such as going offline or double-signing. It makes honest operation the rational choice.Like a security deposit on a rental. Behave, and you get it back. Damage the property, and the landlord keeps a slice to cover the harm. The deposit exists so that bad behaviour costs the person who could cause it, not everyone else.Read more → all run as on-chain transactions. The sliver data itself never touches the chain. Data is public by default; privacy comes from a separate threshold encryptionThreshold EncryptionAn encryption scheme where the power to decrypt is split across several parties, and only a defined quorum acting together can recover the data. No single party can decrypt alone, and the loss of a few parties does not lock the data away.Like a bank vault that needs several managers to turn their keys at once. One manager cannot open it, and if one is on holiday the others can still get in, provided enough of them show up together.Read more → layer called Seal, which encrypts blobs client-side before they are stored.
The doxxed founding team is the Sui founding team: Evan Cheng, Sam Blackshear (creator of the Move language), Adeniyi Abiodun, George Danezis (a UCL security professor) and Kostas Chalkias. All five came out of Meta’s Novi and Diem work. The whitepaper sits on arXiv, and the Move contracts carry an OtterSec audit.
The reason Walrus matters to Own Your Mind is a product launched on 3 June 2026: Walrus Memory. It targets the AI-agent memory problem, and the way it handles ownership is close to the literal idea of owning your mind.
Value proposition
1000-shard PoS storage
RedStuff erasure coding at ~4.5x redundancy across a delegated-proof-of-stake committee, with on-chain shard assignment and slashing.
Wallet-owned agent memory
Walrus Memory ties each memory to a Sui signing key with verifiable provenance, so agents keep memory the user controls.
Centralised default path
Out of the box a relayer sees plaintext and exports it to OpenAI; full sovereignty needs the manual or self-hosted flow.
AI agents forget. Between sessions, most lose the context they built up, and what memory they do keep is locked inside a platform database the user doesn’t control. Walrus Memory pitches the fix: portable memory, tied to a wallet, that an agent can carry across sessions, apps and model providers, with cryptographic proof it wasn’t tampered with.
The ownership design is the strong part. Every memory is bound to a Sui signing key that only you hold, permissions are enforced by Move contracts, and each blob has a content-addressed identifier with on-chain metadata, so provenance is independently verifiable. The MCPMCP (Model Context Protocol)An open standard that lets AI applications connect to external tools, data sources, and services through a common interface, so any compliant agent can use any compliant tool without custom integration work.Like a USB port for AI agents. Before a universal port, every device needed its own cable and driver. A shared standard means any tool that speaks the protocol plugs into any agent that speaks it, no bespoke wiring required.Read more → server means agents in tools like Claude Code or Cursor can read and write that memory through a standard interface. On paper, this is user-owned memory in a way no centralised competitor offers.
The catch is the default configuration, and it’s a big catch. In the managed mode that most developers will use first, a relayer run by the Walrus Foundation receives your memory in plaintext, sends it to OpenAI to generate embeddingsEmbeddingA numerical representation of a word, sentence, or image as a list of numbers (a vector) that captures its meaning. Similar things have similar embeddings, which makes them useful for search, clustering, and recommendation.Like a map where every word has GPS coordinates. Words with similar meanings end up close together on the map. "Cat" and "kitten" are nearby. "Cat" and "thunderstorm" are far apart. The map is the embedding space.Read more →, and holds the searchable index in an ordinary PostgreSQL database. Walrus itself only stores the encrypted cold copy for restore. So the live memory an agent actually queries sits in a centralised database, and your plaintext passes through both the Foundation and OpenAI on the way in.
You can close that gap, but you have to opt in. A manual client flow keeps encryption and embedding on your machine so the relayer sees only ciphertext, and a self-hosted deployment runs the whole stack yourself. Both work. Neither is the default. The honest reading is that Walrus Memory gives you a decentralised ownership record and a decentralised restore backup wrapped around a centralised, plaintext-exposed query layer, and the sovereignty it advertises only arrives when you leave the easy path.
On function alone, it’s behind. The retrieval stack is conventional, and dedicated agent-memory incumbents like Zep, Mem0 and Letta recall better and are simpler to adopt. The one thing Walrus Memory has that they do not is verifiable, wallet-owned ownership. That matters only if you actually need it.
Tokenomics
WAL is the native token of the Walrus network on Sui. The supply is a fixed 5 billion, released on a roughly nine-year schedule rather than through perpetual inflation. Circulating supply is about 49%, a healthier float than most launches of the past two years.
Distribution breaks down as:
- Community: 53% (43% reserve, 6% future user drop, 4% initial airdrop; reserve vesting to around 2033)
- Core contributors: 30% (20% early contributors, 10% Mysten Labs, vesting to around 2030)
- Storage subsidies: 10% (a bootstrapping pool that tops up node and staker rewards)
- Investors: 7% (12-month cliffCliffA waiting period at the start of a token vesting schedule during which no tokens unlock at all. After the cliff ends, tokens begin releasing according to the vesting schedule.Like a probationary period at a new job. You don't get your stock options on day one. You wait 12 months to prove you'll stick around, then everything starts unlocking normally.Read more → then one-month linear, first release passed on 27 March 2026)
Community is the largest single bucket, which reads well. The counterweight is that insiders and investors together hold about 37%, and the initial airdrop was distributed as NFTs that drew a wave of low-retention farming activity. Contributor and reserve tranches keep vesting for years, and there is no burn to offset them.
The token has three uses: storage is paid in WAL, WAL is staked to storage nodes under delegated proof-of-stakeProof of StakeA consensus mechanism where validators earn the right to create new blocks by staking tokens as collateral. If they misbehave, the network slashes their stake. Proof of Stake replaced energy-intensive mining on most modern chains.Like being a licensed auctioneer. You post a bond to get the license, you earn fees for every auction you run, and you lose the bond if you rig an auction. The bigger the bond, the more auctions you get to run.Read more →, and stake carries governance weight. The important nuance sits in how payments work. Storage is priced in dollar terms at $0.023 per gigabyte per month, and the protocol converts that to WAL, takes the fee upfront, and pays it out to nodes and stakers over the storage lifetime, one epochEpochA fixed-length period in a Proof of Stake blockchain during which the validator set is stable and rewards are calculated. Epochs are the natural unit for staking rewards and network state changes.Like a payroll period at a job. Within the period, your role is fixed and your pay is calculated based on hours worked. At the end, the period closes, paychecks are issued, and a new period begins with potentially different conditions.Read more → at a time. Staking yield is a share of those fees, temporarily augmented by the subsidy pool, not a fixed inflationary emission.
That design keeps storage prices stable, which is good for users. It also means WAL captures storage demand as transactional flow rather than as a compounding value sink. Because storage is priced in dollars, a rising WAL price does not lift fee revenue per byte, and there is no burn. So the link between network growth and token value is real but soft.
Walrus raised $140 million in a March 2025 token sale led by Standard Crypto, with a16z crypto, Electric Capital and Franklin Templeton participating, at a reported $2 billion valuation. In August 2025 Grayscale launched a single-asset Walrus Trust, sold as a private placement to accredited investors. WAL hit its high in May 2025 and now trades about 95.6% below it, with market cap a little under half of fully diluted value.
How to participate
Store data or give an agent memory. The lowest barrier. Pay in WAL to store a blob, or wire Walrus Memory into an agent through the MemWal SDKSDKSoftware Development Kit. A collection of code libraries, documentation, and tools that lets developers integrate a service into their applications without writing everything from scratch. SDKs are how projects become easy to build with.Like a plug-and-play kit for building furniture. You don't have to mill your own wood, forge your own screws, or design the joinery from scratch. The kit gives you pre-cut parts and instructions so you can assemble the thing in an afternoon.Read more → or the MCP server. Two things to know before you rely on it. The default relayer sees your plaintext unless you use the manual client flow, and on mainnet a blob defaults to just two storage epochs unless you pay to extend it, so “permanent” is a setting, not a given.
Stake WAL. Delegate WAL to a storage node operator under delegated proof-of-stake and earn a share of storage fees net of commission. No hardware needed. Two caveats: the default operator commission is a steep 60%, and there is no published headline yield, because the team frames rewards as starting low and scaling with network usage.
Run a storage node. Registration is permissionlessPermissionlessA system anyone can use or build on without asking a gatekeeper. No application, no allowlist, no approval step. If you meet the protocol's on-chain rules, you are in. The opposite of permissioned.Like a public road versus a members' club. Anyone with a car can drive on the road; the club checks your name at the door. Permissionless protocols are the road.Read more →: provision a Linux server with a large disk, a public DNS name and TLS, register a candidate node with a Sui wallet, and you are eligible. Whether you actually join the active committee and receive shards depends on attracting enough delegated stake, so it’s open to enter but competitive to be seated.
Build on it. Beyond raw storage, you can build on Walrus Sites, use Seal for encrypted access control, or self-host the full Walrus Memory stack (a Rust relayer, a TypeScript sidecar, and a Postgres index) to own the entire trust boundary. Documentation is good, though the docs site blocks automated fetching.
Honest assessment
What works
The base storage network is a strong piece of engineering. RedStuff gets Byzantine fault tolerance at 4.5 times redundancy where full replication needs around 25 times, the shard set is a fixed 1000 with on-chain assignment reassigned every epoch, and misbehaving nodes are slashed by an on-chain committee vote rather than by an admin. Node registration is permissionless. For decentralised storage, this is near the front of the field.
The team and the openness are top-tier. The founders are the Sui founders, fully doxxed, out of Meta’s Novi and Diem programmes, and the whitepaper is a proper peer-review-style document on arXiv. The code is Apache-2.0 across the storage network, the Seal encryption layer and the MemWal SDK, with daily commit activity and an OtterSec audit on the Move contracts.
The ownership primitive in Walrus Memory is the real thing. A memory bound to a wallet key, enforced by on-chain contracts, with verifiable provenance, is something the centralised memory tools cannot match. For an application where you need to prove who owns a piece of an agent’s memory and that it wasn’t altered, this is a real edge.
What doesn’t work
The default Walrus Memory experience isn’t decentralised where it counts. The managed relayer sees plaintext, exports it to OpenAI for embeddings, and keeps the queryable index in a centralised database. Walrus is the restore backup, not the live memory. Calling the out-of-the-box product “user-owned, decentralised memory” oversells it, because the sovereignty only holds once a developer moves to the manual or self-hosted flow.
The traction figures circulating in third-party write-ups don’t hold up. One widely repeated claim puts Walrus Memory at around 2,300 terabytes weeks after launch, which is more than five times Walrus’s own stated whole-network total of roughly 467 terabytes. Numbers that fail their own internal sanity check shouldn’t be cited, and the product dashboard publishes no metrics to check against.
Value accrual is weaker than the utility story suggests. Storage is priced in dollars and paid out over time, there is no burn, and present staking yield leans on a subsidy pool. WAL is a medium of exchange for storage and a staking asset, not a mechanism that compounds network growth into token value.
The risk
Walrus is singularly dependent on Sui. Every ownership record, payment and access-control check lives on Sui, so when Sui halted for nearly seven hours in May 2026 on a gas-charging bug, Walrus paused with it. Storage rivals that are chain-agnostic don’t carry that single point of failure.
Revenue is real as a mechanism but can’t be independently checked. Walrus is not tracked on DeFiLlama, the storage-usage figures are self-reported, and a rough estimate of fee income is negligible against fully diluted value. Regulatory status is unsettled too: WAL has no classification ruling, and the Grayscale trust used a private placement, which manages that risk without resolving it.
The operator set is young. Mysten Labs ran every node at developer-preview stage, and the current committee of about 100 operators is stake-selected and recent, so its real independence hasn’t been demonstrated on-chain over time.
My position
I don’t hold WAL. Walrus is a serious network from the best team in the field, and Walrus Memory is the most on-thesis product name I have reviewed: wallet-owned, portable, verifiable agent memory is close to the whole point of this site. The gap is between the ownership record, which is on-chain and yours, and the live query path, which by default runs through a Foundation relayer, OpenAI and a centralised database. I would move on this if Walrus Memory produced on-chain-verifiable traction, if the mainnet Seal key-server committee decentralised as promised, and if storage-fee revenue ever reconciled against an independent source.
Freedom Score: 62/100
Walrus scores 62/100 (C grade). Full methodology at Freedom Score Methodology.
Infrastructure decentralisation (13/20): The base storage network is strong for its class: a fixed 1000-shard delegated-proof-of-stake committee of about 100 operators, permissionless node registration, on-chain shard assignment reassigned every epoch, and on-chain slashing by a two-thirds shard quorum. That is materially more decentralised than permissioned-validator data protocols. Three things hold it back. Walrus is tightly coupled to Sui as its only coordination chain, the operator set is young after Mysten ran all nodes at preview, and Walrus Memory routes live traffic through a Foundation relayer.
Governance decentralisation (8/20): On-chain node governance is real at the protocol layer, with stake-weighted votes on parameters and slashing executed by a shard supermajority. But the project is built by Mysten Labs and stewarded by the Walrus Foundation, which holds the large community-reserve and contributor allocations and retains practical control of direction. Token-holder governance is early, with no participation metrics found during research.
Token distribution fairness (9/15): Community is the largest bucket at 53%, with storage subsidies a further 10%. Insiders take 30% and investors 7%, so insiders plus investors hold about 37%. Circulating supply near 49% is a healthier float than most recent launches and sits above the 30% concern threshold. Offsetting that, the NFT airdrop drew low-retention farming, and the 30% contributor allocation is a meaningful overhang vesting to 2030.
Censorship resistance (9/15): At rest the storage layer resists censorship well: blobs are erasure-coded across 1000 shards with a one-third fault tolerance and self-healing recovery, so no single operator can suppress a blob. Two deductions. Blobs are public by default, with privacy depending on the separate Seal layer whose mainnet key servers are not yet the decentralised committee. And the Sui dependency, plus the Walrus Memory relayer, are practical chokepoints that can gate access even when the stored data is resilient.
Data sovereignty (10/15): Ownership is user-held at the record layer. Every memory or blob is tied to a wallet signing key and enforced by Sui Move contracts, with content-addressed, independently verifiable provenance. But the default Walrus Memory path undercuts it operationally: the managed relayer receives plaintext and exports it to OpenAI, and the live index sits in a conventional database, so out of the box you trust the relayer and OpenAI. Full sovereignty needs the manual flow or self-hosting. A strong design compromised by a centralised, plaintext-exposed default.
Open source and transparency (13/15): Broad and active. The storage network is Rust and Move under Apache-2.0 with hundreds of commits a year and dozens of contributors, and the Seal and MemWal repositories are also Apache-2.0. There is a peer-review-style whitepaper on arXiv, an OtterSec audit of the Move contracts, and a live HackenProof bug bounty. Deductions: no published audit found for RedStuff itself or a Seal-specific report, and the Walrus Memory dashboard exposes no public traction metrics.
Path to improvement
Three changes would materially raise the score:
- Decentralise the Walrus Memory serving path. Making the manual, no-plaintext client flow the default, or shipping the promised decentralised Seal key-server committee on mainnet, would close the gap between the ownership record and the live query layer that costs the product its sovereignty points.
- Prove operator independence on-chain. Publishing verifiable committee composition over time, showing real geographic and organisational spread beyond the preview-era Mysten operators, would turn the “over 100 operators” claim into a demonstrated fact.
- Reduce the Sui single point of failure. A concrete story for degraded-mode operation during a Sui halt, or credible progress toward the whitepaper’s chain-agnostic design, would address the dependency the May 2026 outage exposed.
Returns Score: 55/100
WAL scores 55/100 (C grade). Full methodology at Returns Score Methodology.
Token utility (14/20): WAL has genuine, mandatory utility. Storage on Walrus must be paid in WAL, delegated staking secures the network and earns a share of fees, and stake carries governance weight. Storage demand therefore requires WAL, which is more than many tokens can say. The ceiling is that storage is priced in dollar terms, with the WAL amount floating to price, so WAL behaves as a medium of exchange and staking asset rather than a hard value sink.
Value accrual (9/20): There is a real usage-to-holder link, since storage fees paid in WAL are distributed to nodes and stakers each epoch. It is soft, though. Fees are dollar-denominated, so a higher WAL price does not raise revenue per byte, there is no burn, and a subsidy pool currently tops up yield, which means present staking returns are partly bootstrapped rather than fully fee-driven.
Supply dynamics (12/20): A fixed 5 billion cap with no perpetual inflation, and about 49% circulating, is a healthier setup than most 2025 and 2026 launches and sits above the 30% concern threshold. The investor cliff passed in March 2026. Working against it, contributor tranches vest to around 2030 and the community reserve to around 2033, insiders and investors hold roughly 37% between them, and there is no burn to offset emission.
Revenue sustainability (10/25): Storage fees come from paying customers, so the revenue mechanism is sound, and Walrus describes itself as the second-largest decentralised storage network by self-reported capacity. But there is no independent reconciliation. Walrus is not tracked on DeFiLlama, the capacity figure is self-reported, much of it is subsidised, and a rough estimate of fee income is negligible against fully diluted value. Following the honesty rules, unverified revenue is discounted rather than taken at face value.
Liquidity and access (10/15): WAL trades on Gate.io and other major venues, and the Grayscale Walrus Trust adds a regulated institutional wrapper for accredited investors. Two things temper it: daily volume is modest, and the token sits about 95.6% below its May 2025 high, so the exchange access is solid while market interest has thinned.
Path to improvement
Three changes would materially raise the returns score:
- Reconcile revenue independently. Getting Walrus onto DeFiLlama or an on-chain fee index, so storage-fee revenue can be verified against a source other than the project, would let the revenue dimension rest on evidence rather than a discounted self-report.
- Tighten value accrual. A mechanism that links storage growth to token value more directly, whether a fee burn or a staking sink that grows with usage, would convert transactional WAL flow into something that compounds for holders.
- Grow verifiable demand. On-chain-verifiable Walrus Memory adoption, or published paying-customer storage revenue, would turn the utility narrative into a demand signal a holder can actually measure.
Score change log
| Date | Score | Change | Reason |
|---|---|---|---|
| 2026-07-03 | Both | N/A | Initial publish. Freedom 62/100 (C), Returns 55/100 (C). Triaged from a khala.io article (Tier-3 promo); Full Review approved. Base storage network scored as the subject, Walrus Memory as the DeAI wedge. Every metric re-verified across primary and Tier-2 sources; third-party traction figures (including a 2,300TB claim exceeding the ~467TB network total) excluded as unverifiable. Revenue integrity verdict: unverifiable (not on DeFiLlama); revenue_annual_usd null. Live market data from CoinGecko (walrus-2), 2026-07-02. |
Team overview
Former engineering director at Apple and Meta (Novi/Diem). Long LLVM/compiler background.
Creator of the Move smart-contract language (at Meta/Novi).
Former blockchain lead at Meta (Novi); previously Oracle and VMware.
Professor of Security and Privacy Engineering at UCL; ex-Meta/Novi researcher. Walrus whitepaper co-author.
Ex-Meta (Novi) and ex-R3 chief cryptographer; author of zkLogin and Winterfell work.
https://www.theblock.co/profile/326034/kostas-kryptos-chalkias| Round | Amount | Date | Lead |
|---|---|---|---|
| Token sale (WAL) | $140.0M | 2025-03-20 | Standard Crypto |
Source: OYM Research · Last updated 2026-07-20
Technical snapshot
Walrus stores data as immutable blobs. Each blob is erasure-encoded with RedStuff -- a 2D erasure-coding scheme adapted from the Twin-code framework, operating on an (f+1) x (2f+1) matrix of symbols -- into primary and secondary slivers distributed across a fixed set of 1000 shards. Storage nodes hold one or more shards per epoch and store all slivers for their shards. The security model is n = 3f+1 nodes tolerating f Byzantine faults; a blob reconstructs from f+1 of the 3f+1 slivers, so it survives even when up to roughly two-thirds of slivers are lost, while the stated safety assumption is that more than two-thirds of shards stay honest. Redundancy is about 4.5x the raw blob size, versus ~3x for classic Reed-Solomon and ~25x for full replication. Sui is used as a black-box coordination layer: blobs are Sui Move objects, and registration, availability certification, payments, shard-to-node assignment, staking and slashing all execute as on-chain transactions. The actual sliver data never touches Sui. Seal, a separate threshold-encryption and access-control layer, encrypts data client-side before storage (Walrus blobs are public by default). Quilt batches small blobs to amortise per-blob overhead. Walrus Memory (SDK name MemWal) is an application layer that adds embeddings, semantic search and an agent-memory API on top.
Commit Activity
Audits
Scope: Walrus Move smart contracts (storage, payments, governance/metadata)
Security assessment completed. Referenced from the official Sui security page.
View reportSource: OYM Research · Last updated 2026-07-20
Tokenomics deep dive
Token utility
- Storage payments: storage is paid in WAL; the protocol takes the fee upfront and distributes it to nodes and stakers over the storage lifetime, per epoch, keeping the storage price stable in USD terms regardless of WAL price
- Staking (network security): delegate WAL to storage nodes under delegated proof-of-stake; stakers earn a share of storage fees net of node commission
- Governance: on-chain voting on system parameters and node penalties, weighted by stake
Supply
| Max supply | Total supply | Circulating | Circ. % |
|---|---|---|---|
| 5,000,000,000 | 5,000,000,000 | 2,456,666,667 | 49.1% |
Allocation
Method: WAL token sale ($140M, March 2025) for the investor allocation; community airdrop (NFT-form) and future user drop; contributor and Mysten allocations on vesting schedules. Emission of the 5B cap runs on a fixed ~9-year schedule (roughly 32% in Year 1).
| Category | % | Vesting | Cliff |
|---|---|---|---|
| Community | 53% | Community Reserve 43% (approx 690M at launch, remainder linear to ~March 2033) + Future User Drop 6% + Initial Airdrop 4% | None |
| Core contributors (incl. Mysten Labs) | 30% | Early Contributors 20% + Mysten Labs 10% (50M at launch, remaining 450M linear to ~March 2030) | Varies |
| Storage subsidies | 10% | Released over time to top up storage-node and staker rewards as the fee base grows | None |
| Investors | 7% | 12-month cliff then 1-month linear; first major unlock at the 27 March 2026 cliff expiry (now passed) | 12 months |
Emissions
Vesting timeline
Investors cliff
None -- fixed 5B cap released on a fixed schedule over ~9 years
Staking
TGE and mainnet 25-27 March 2025. ATH $0.759 (14 May 2025); currently ~95.6% below ATH. MC/FDV ~0.49. Investor cliff (27 March 2026) has passed. A stale third-party snapshot cited ~1.534B circulating; the live CoinGecko figure (~2.457B, ~49%) is authoritative.
Source: OYM Research · Last updated 2026-07-20
Participation at a glance
Store data on Walrus (pay in WAL, priced at a fixed USD $0.023/GB/month, billed on the ~4.5x encoded size plus ~64MB per-blob metadata), or use Walrus Memory to give AI agents portable, wallet-owned memory via the MemWal SDK (Remember/Recall/Restore/Analyze/Ask) or an MCP server.
Delegate WAL to storage node operators under delegated proof-of-stake to earn a share of storage fees net of commission.
Run a storage node: provision Linux (Ubuntu 24.04, x86_64 with AVX2/SSSE3), a large disk, a public DNS name + TLS, open ports, and register a candidate node with a Sui wallet (~1 SUI). Joining the active committee depends on attracting enough delegated stake.
Build on Walrus storage, Walrus Sites, Seal-encrypted access control, or the Walrus Memory SDK. Self-host the Memory relayer (Rust relayer + TypeScript sidecar + PostgreSQL/pgvector) for full control of the trust boundary.
Developer resources
Source: OYM Research · Last updated 2026-07-20
Usage and traction
Data from: Walrus whitepaper (arXiv 2505.05370), Walrus one-year review, CoinGecko API (2026-07-02)
Walrus Memory launched 3 June 2026 (earlier preview as MemWal ~March 2026). Post-launch traction figures circulating in third-party coverage (~3,500 agent owners, ~73,000 blobs, ~2,300TB, P95 recall 1.5-3s) are unverifiable and, in the case of 2,300TB, implausible against the ~467TB network total; excluded.
Source: OYM Research · Last updated 2026-07-20
Community
Governance
Developed by Mysten Labs, governed by the Walrus Foundation. On-chain governance lets storage nodes vote on system parameters and penalties, weighted by stake. At developer-preview stage Mysten Labs operated all storage nodes; mainnet now runs a stake-selected committee of ~100 operators. Token-holder governance is early; practical direction sits with Mysten Labs and the Foundation.
Sentiment
Strong developer credibility from the Mysten Labs / Sui lineage and an elite doxxed team. Institutional signal via the Grayscale Walrus Trust. Skeptical commentary focuses on airdrop-farming quality (NFT airdrop drove large low-retention wallet activity), doubt that large datasets will actually migrate on-chain, and validator-incentive concentration risk.
Source: OYM Research · Last updated 2026-07-20