🧵Filecoin Onchain Cloud Launch TL;DR: Filecoin Onchain Cloud adds onchain storage, retrieval, and payments with proofs. It includes warm storage, Filecoin Pay, Synapse SDK, Filecoin Pin, and Filecoin Beam. Over 100 builders tested the system ahead of mainnet in 2026.

Read the full article:

5/ Exit and cost Egress fees create lock-in by design and regulators now flag exit risk under DORA and NIS2. This model removes egress penalties, keeps S3 API parity, and makes migration practical: DNS switch plus data sync, not a long refactor.

4/ Filecoin layer Filecoin plays the storage role. Encrypted shards distribute across a decentralized Filecoin network, with geographic constraints if required. No single operator or jurisdiction holds a complete file. This reduces single-provider concentration risk.

3/ Self-hosted gateway Akave claims no legal exception, a US company still faces the CLOUD Act. The approach relies on architecture. Self-Hosted O3 runs on EU infrastructure you choose. Encryption keys stay with the operator. Akave does not hold readable data.

2/ Custody matters EU providers remove US jurisdiction, but custody still rests with the provider. Courts can compel access. For regulated sectors and sensitive data, sovereignty requires zero provider custody, the operator controls infrastructure, keys, and access paths.

1/ The question The EU cloud debate focuses on where data sits. That misses the core issue. Custody, not geography, defines sovereignty. US hyperscalers stay subject to the CLOUD Act even in EU regions, subsidiaries, and “sovereign” clouds.

🧵How Akave Separates Data Custody from Cloud Jurisdiction TL;DR: EU cloud debates focus on location, legal exposure depends on custody and keys. Akave’s Self-Hosted O3 keeps control with the operator, while Filecoin supplies the decentralized storage layer that reduces lock-in.

Explore:

4/ Open codebase The project publishes its contracts, tools, and storage modules on GitHub. Developers audit the workflow, extend components, or integrate the logic into projects that rely on Filecoin for data persistence.

3/ Encryption flow Encryption occurs on the user’s device before any upload step. The user keeps the key, and only the encrypted file reaches a storage provider. This approach reduces exposure and protects data across each stage of the storage path.

2/ Onchain logic All storage actions route through Eastore contracts that record terms and create @Filecoin deals. These records remain accessible, so data retrieval stays possible even if the Eastore site or interface goes offline.

1/ Overview @EastoreWeb3 gives users a drive-like surface that directs data to Filecoin through open contracts. Files pass through local encryption first, and the resulting encrypted data enters the storage flow. The focus stays on user control and clear deal creation.

🧵Eastore and its role in Filecoin storage TL;DR: Eastore offers a drive-like interface on top of Filecoin and uses open smart contracts for storage operations. The project focuses on data ownership, encrypted uploads, and direct Filecoin deal creation.

Read the announcement:

5/ Takeaway Portrait opens access to everyone and relies on a distributed set of peers for durability. A Portrait can outlive individual hosts, and its availability gets better when more users pin or store the content.

4/ Offline Scenario If all hosts of a Portrait go offline, the PortraitStateRegistry contract still records the CID. Files remain accessible if peers or pinning services keep copies on decentralized storage.

3/ Data Reference Each Portrait carries a CID that points to its stored files. The CID remains intact even if a hosting node disconnects, so the storage path stays verifiable across the network.

2/ Architecture Portrait stores page metadata on-chain and offloads images and files to decentralized networks such as IPFS/@Filecoin. This structure reduces dependence on a single host.

1/ Free Access Portrait removes the ten-dollar fee and opens registration to all users. Anyone can claim a space on the network and create a personal Portrait (@withportrait) without cost.

🧵Portrait removes its registration fee. TL;DR: Portrait is free for everyone. The protocol keeps metadata on-chain and stores files through IPFS/Filecoin. A Portrait stays reachable as long as peers pin or host the data. Availability depends on distributed participation.