Someone asked us a short, fair question under a recent r/web3 post:
How is it different from Lens?
You can read the question in its original context here: Building a modular Web3 social app with user-owned community nodes.
Our first instinct was to answer with gas fees. That difference matters, but it is not the most useful answer and can misrepresent what Lens has already built.
The more important question is this:
Which parts of a social network genuinely need shared blockchain consensus, and which parts should remain under the user's direct control?
Lens and Foldinglink draw that boundary in different places. Lens begins with a shared onchain social graph. Foldinglink begins with personally controlled hardware and asks which selected states should be made jointly verifiable. This article explains that difference without pretending either approach is free of trade-offs.
What does Lens actually do today?
Lens is not putting every like or comment directly on Ethereum Layer 1 and making the user wait for an L1 confirmation.
The current Lens stack combines Lens Chain, its Social Protocol, and Grove storage. Lens describes Lens Chain as an Ethereum Layer 2 that uses ZKsync, Avail, and Ethereum. Its Accounts, Graphs, Feeds, Groups, Rules, and Actions provide onchain building blocks that developers can combine into different social applications. Lens Chain documentation
Lens also supports account abstraction and a signless or gasless user experience. An application can sponsor a transaction so the user does not need to hold gas or approve every interaction manually. Gasless for the user does not mean no transaction occurred; another party may be absorbing a system-level cost. Lens overview
Lens has also moved beyond the simple description that every attachment is permanently placed on IPFS. Grove supports immutable resources, but it also supports mutable resources protected by access-control rules. The official Grove client exposes authorized edit and delete operations. Grove client
The accurate comparison is therefore not "Lens charges for every click and cannot delete anything." Its strength is a shared, portable, composable social layer that multiple applications can use.
What architecture is Foldinglink testing?
Foldinglink starts from a different physical and product assumption: a person may already own useful hardware that can participate in a community network.
NAS devices are our current practical entry point because they are designed to remain online and serve data. Foldinglink is not primarily a NAS seller, and the idea is not limited to one appliance category.
The working architecture separates four responsibilities.
Status key: CURRENT BUILD = visible App flows; IN TESTING = encrypted NAS storage, RPC/full nodes, custom L2, and deletion; DESIGN TARGET = share and deletion controls; OPEN QUESTION = offline copies, costs, security, data availability, sequencing, and final node roles.
1. The application layer
The Foldinglink App is where familiar actions happen: publishing a post, asking or answering a question, sending a direct message, joining a group, sharing a selected resource, or starting an order.
A blockchain should not force people to think about settlement or node synchronization every time they participate in a conversation.
2. The encrypted NAS storage layer
Content is designed to be encrypted on the client before it is written to participating NAS storage. The intended model can distribute encrypted copies to user-authorized nodes for availability and recovery while the user retains control over the keys and sharing boundary.
This is not a public pool of donated disk space. The intended path is:
PRIVATE ENCRYPTED STORAGE -> EXPLICIT SHARE GATE -> COMMUNITY APP
A participant chooses what to share and with whom. Joining the network should not expose an entire private volume.
3. The NAS-hosted L2 node layer
The current architecture under testing also allows NAS hardware to run RPC or full-node responsibilities for Foldinglink's custom OP Stack environment. The same physical machine may therefore contribute storage and synchronize L2 state, but those remain different jobs.
We are not claiming that every participating NAS acts as a sequencer, validator, or consensus node. Those roles require a more explicit operating design than running an RPC endpoint or following chain state.
4. The shared-state and settlement layer
The chain layer is being explored for selected information that multiple participants may need to verify, such as authorization, transaction state, contribution records, points-related state, or a community decision.
The team has completed an onchain transaction test in a custom L2 environment. That proves a test path, not a public production network. Ethereum is part of the wider settlement and security context. OP Stack systems involve execution, data availability, sequencing, batching, and settlement choices that still need measurement in Foldinglink's configuration. OP Stack documentation
Gasless is not the same as offchain
This is where the comparison becomes more interesting than a fee table.
Lens makes onchain social primitives composable while hiding chain mechanics from the user. Foldinglink is asking an earlier question: does this social action need to become a blockchain transaction at all?
A reaction, a draft message, or an ordinary conversation may not need the same settlement properties as an escrowed exchange or a disputed community decision. Foldinglink is testing whether routine activity can remain in the application and node network while selected shared state is recorded through the L2.
That could reduce chain execution, but it does not justify a numerical cost claim. We do not have a like-for-like benchmark covering sponsorship, L2 operation, L1 settlement, storage, bandwidth, and infrastructure overhead.
What does "active deletion" mean in a distributed system?
Deletion deserves more precision than a yes-or-no comparison.
Foldinglink's design gives the owner a way to erase content from their local node, revoke the permission or key that made the content readable, and broadcast a deletion or invalidation instruction to the authorized encrypted replicas participating in that data relationship.
That is meaningfully different from treating every uploaded object as permanently available. But it is not a magic eraser.
Active deletion does not mean Foldinglink can guarantee the removal of:
- an offline backup that is not reachable when the instruction is sent;
- a copy someone exported or independently saved while they had legitimate access;
- the historical existence of a blockchain transaction or audit record;
- an original file that belongs to another user on that user's own hardware.
An owner deleting their content is also different from a platform trying to remove prohibited content from someone else's device. Decentralized storage does not remove moderation, abuse-response, or operator-responsibility problems.
Deletion propagation, key revocation, cache cleanup, offline-node behavior, and evidence that replicas actually became unavailable are all still in testing or design validation.
Lens and Foldinglink optimize for different things
The fairest comparison is not a winner-and-loser scorecard.
| Question | Lens today | Foldinglink working model |
|---|---|---|
| Where does the design begin? | A shared onchain social protocol and graph | Personally controlled hardware and defined communities |
| How are social actions handled? | Through composable onchain social primitives on Lens Chain | Routine actions are being separated from states that require shared verification |
| What does gasless mean? | Transactions may be sponsored or hidden behind account abstraction | The design aims to avoid creating a chain transaction when consensus is unnecessary |
| Where does content live? | Grove provides onchain-controlled storage with mutable and immutable options | Client-encrypted content is intended to live across user-controlled, authorized NAS nodes |
| What does deletion mean? | Authorized mutable resources can be deleted, while onchain history may remain | Local erasure, replica invalidation, and access revocation are design targets with explicit limits |
| What is already proven? | A live protocol, chain, developer stack, and application ecosystem | Current App flows and an internal L2 transaction path; the multi-NAS architecture remains in testing |
Lens's advantages are substantial. It offers developers an existing social graph, portable accounts, composable rules, indexing, tooling, and a functioning ecosystem. Foldinglink should not pretend that operating personal nodes automatically replaces those benefits.
Foldinglink's hypothesis is narrower and more physical: defined communities may value an application in which the infrastructure, private data boundary, and selected resource sharing remain closer to the people operating the network.
What does Foldinglink still have to prove?
An understandable diagram is not implementation evidence.
We need to test:
- how encrypted replicas synchronize across multiple NAS nodes;
- what happens when a node is offline during an update or deletion request;
- how key revocation, caches, retries, and stale copies are handled;
- the CPU, memory, disk, bandwidth, and uptime cost of storage plus RPC or full-node operation;
- which nodes sequence transactions, where data availability lives, and how failures are recovered;
- whether application state and L2 state remain consistent during real error conditions;
- how reporting, prohibited content, operator controls, and legal obligations work in practice;
- which parts of the system can be independently inspected and reviewed.
These are release criteria, not details to hide behind the word "decentralized."
So, how is Foldinglink different from Lens?
The short answer is not "Lens, but cheaper."
Lens is building a broadly composable onchain social stack. Foldinglink is testing a personal-node-first architecture in which private encrypted data, ordinary community activity, and selected shared state do not automatically live in the same place.
The bet is that a social product can use blockchain where common verification matters without making every human interaction a blockchain event, and that personally controlled hardware can provide a meaningful data boundary rather than becoming an open public drive.
That bet is still being tested.
Which social actions, if any, do you think genuinely need to be onchain?