Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Archiving this codebase on Arweave for permanence #34769

Open
t8 opened this issue Jan 12, 2024 · 7 comments
Open

Archiving this codebase on Arweave for permanence #34769

t8 opened this issue Jan 12, 2024 · 7 comments
Labels
community Community contribution

Comments

@t8
Copy link

t8 commented Jan 12, 2024

Problem

Solana's core codebases are currently only stored in web2 environments, which aren't permanent nor immutable.

Proposed Solution

Would like to propose automatically archiving this repo to Protocol.land, a decentralized source control protocol on Arweave.

A large part of the Solana community already leverages Arweave for data storage, so thinking it might make sense to do the same for the underlying codebase 🙂

If so, let me know and I’d be happy to open a PR! Super simple to do with a Github action: https://docs.protocol.land/working-with-repositories/import-a-repository-from-github

@t8 t8 added the community Community contribution label Jan 12, 2024
@Himnasmidur
Copy link

This makes a lot of sense. I support it!

Solana's speed with Arweave's stability would be a formidable combination.

@0legRadchenko
Copy link

yep, good idea to safeguard Solana's codebase with Protocol.land's immutable storage :)

@whyyyseee
Copy link

I like this idea, makes sense for Solana's codebase to be archived on protocol.land instead of a traditional web2 solution.

@angrymouse
Copy link

Hmm, what's wrong with just taking code snapshot every few months and uploading .tar.gz to arweave? @t8

@angrymouse
Copy link

angrymouse commented Jan 14, 2024

Running upload script on every push means uploading a lot of txs to arweave, which may be not very cost effective option. Proposed CI script in docs isn't most secure either, as it runs newest version of @protocol.land/sync passing github auth token and arweave wallet to it.
image
Meaning if someone would compromise access to @protocol.land/sync on NPM, it would allow them to get github access token and arweave wallet from this repo's secrets.

@angrymouse
Copy link

angrymouse commented Jan 14, 2024

From security perspective, I believe just switching to forced version would be fine (for example to @protocol.land/[email protected]). From practical perspective tho, I think solana validators already hold full copies of nodes' code for it to be earthquake-proof, though uploading to arweave might add even more resilience.

@kevinheavey
Copy link
Contributor

Don't worry guys I have a snapshot on my laptop, no need for arweave

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community Community contribution
Projects
None yet
Development

No branches or pull requests

6 participants