Simple Summary One of the biggest issues that any blockchain faces is to store and manage its ledger(data). The faster the transaction execution of a chain, the bigger the issue of making its data available and retrievabile to all its clients. This SWIP proposes to solve the data availabilty and retrievability problems by having a generic data chain to manage and store data of other blockchains. This data chain will use Swarm as the storage layer to acheieve this goal. Abstract Blockchain scaling usually means to scale in the following dimensions Transaction Execution Data storage

Big Bang - First Level Details [TOC] Example mermaid diagram - see https://mermaid-js.github.io/mermaid/#/sequenceDiagram References Business requirements: https://hackmd.io/@plur9/Sk34fadmd GetLogin smart contracts: https://github.com/GetLoginEth/login/tree/master/src/smart/contracts User movement: https://lucid.app/lucidchart/invitations/accept/3859fb08-6b79-4015-892f-970868f50826?viewport_loc=-750%2C-27%2C4272%2C2181%2C0_0 Workflows: https://hackmd.io/82OaCq1bSO-gfXBlBICBFw?view

User contract creation create the contracts from and external account Fund it with gETH & gBZZ This fund is used to fund the 1 Million invited accounts First user signup (without invite) A main/root user is created this user creates the first 1 million invites

FairOS Roadmap The generic goal should be to provide application developers to help build applications on swarm a breeze. Think like a developer and see what all things would be needed to build applications like Drive Email Slack Youtube Spotify Twitter Instagram

What happens during upload What is a chunk ? Chunking process Swarm storage limits and Garbage collection What does pinning do storing copy of original chunks locally serving contents from the uploaded node only

# Pinning part 2 Implemenetation Architecture For pinning part 2, There are several documents flying around 1) The pinning part 2 [epic](https://github.com/ethersphere/user-stories/issues/58) 2) This talks about the players involved in the [SWIP](https://hackmd.io/b0mhMEClTrGyo1o-9EJbYw?view#missing-chunk-notification-protocol-or-process-for-network-repair-of-missing-chunk-by-reuploading-chunks) process with some details and their interataction. This SWIP hash improvements by Dani and othe

--- tags: fairdrive, datafund --- # Swarm requirements for Fairdrive ## For Fairdrive MVP - [Pinning part 2](https://github.com/ethersphere/user-stories/issues/58) - Native Swarm incentivisation (atleast Basic $X/GB) ## For Fairdrive Beta - Incentive: Swear beta (basic; for services with trusted nodes) - Support for 1GB files (to test in smoke_test) - Fast download of files ([1876](https://github.com/ethersphere/swarm/pull/1876)) - Native Swarm UI to show - Version - System information

--- tags: archive --- # OBSOLETE - moved to https://hackmd.io/@crtahlin/SkYHpFVtB # Fairdrive Use Cases Actors: - User of Fairdrive (should we differentiate individual users and "corporations"?) - App ## User of Fairdrive: - Create fair drive (should we reserve names; e.g. name@email.com;if possible?) - Identity & Logins - Create unique identity - Delete identity - Recover identity if key lost - Documents - Store documents in fair drive - Exchange documents safely with