SEC's attack on LBRY is a travesty of justice. (Made even more disgusting by how cozy the SEC/CFTC were with the FTX fraudsters at the same time they were attacking LBRY.)
Here's a sketch of what I would do to keep the LBRY network going:
1. Form a decentralized DAO to manage the project (similar to @ShapeShift ). Use @DarkFiSquad anonymous DAO tech to prevent rubber hose attacks on developers, donors, leadership. Issue LBRYDAO tokens to finance the work below. (No corporation to shut down.)
2. Collaborate with @ArweaveEco to pin LBRY media for long-term storage. (No centralized storage servers to attack.)
3. Convert existing LBRY desktop app to PWA. (Can't be censored by app stores).
4. Convert LBRY app to use strictly P2P protocol. (Perhaps something like @Holepunch_to tech used by @keepio .) (Strictly P2P software means no large hosting/bandwidth costs.)
5. Host code repository on decentralized github alternative, such as @radicle. (No centralized repository to attack.)
6. Convert LBRY app to communicate with @arweave network strictly over @nymnetworks. (Anonymous uploading to Arweave would make it difficult to make rubber hose attacks on LBRY contributors.)
7. Finance the work above by issuing LBRYDAO tokens. Perhaps merge mine them in a Monero p2pool miner built into the app, which sends 40% of the mined tokens as a devtax to the DAO for operations. (No sales of tokens, no SEC attack.)
Then the only thing that would need to be hosted is a website with links to download the software from the decentralized radicle repository.
It would still vulnerable to network analysis attack via the Arweave network, since Arweave transactions are not anonymous. (Though data stored on Arweave is encrypted.)
#lbry
#archer_crypto
Here's a sketch of what I would do to keep the LBRY network going:
1. Form a decentralized DAO to manage the project (similar to @ShapeShift ). Use @DarkFiSquad anonymous DAO tech to prevent rubber hose attacks on developers, donors, leadership. Issue LBRYDAO tokens to finance the work below. (No corporation to shut down.)
2. Collaborate with @ArweaveEco to pin LBRY media for long-term storage. (No centralized storage servers to attack.)
3. Convert existing LBRY desktop app to PWA. (Can't be censored by app stores).
4. Convert LBRY app to use strictly P2P protocol. (Perhaps something like @Holepunch_to tech used by @keepio .) (Strictly P2P software means no large hosting/bandwidth costs.)
5. Host code repository on decentralized github alternative, such as @radicle. (No centralized repository to attack.)
6. Convert LBRY app to communicate with @arweave network strictly over @nymnetworks. (Anonymous uploading to Arweave would make it difficult to make rubber hose attacks on LBRY contributors.)
7. Finance the work above by issuing LBRYDAO tokens. Perhaps merge mine them in a Monero p2pool miner built into the app, which sends 40% of the mined tokens as a devtax to the DAO for operations. (No sales of tokens, no SEC attack.)
Then the only thing that would need to be hosted is a website with links to download the software from the decentralized radicle repository.
It would still vulnerable to network analysis attack via the Arweave network, since Arweave transactions are not anonymous. (Though data stored on Arweave is encrypted.)
#lbry
#archer_crypto