Add Arweawe Name System (ArNS) hosting to Scaffold ETH #1169
kempsterrrr
started this conversation in
Ideas
Replies: 2 comments
-
|
edited to update error on Nethermind gateway example link :) |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
+1 on this - would love to see Arweave supported on scaffold eth and yes I will be teaming up with Kemp to help out with this! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey folks 🙌
Lots of love for Scaffold ETH and the impact it has had onboarding devs into Ethereum. Many friends at Developer DAO got their first start building in Ethereum via Scaffold ETH and BuidlGuidl ❤️
I’d like to propose adding support for hosting sites on Arweave Name System (ArNS). ArNS allows you to associate any data stored on Arweave with a human-readable name, which you can then access as a subdomain for any of the (currently) > 600 gateways in the AR.IO Network.
For example, the ArNS app itself is hosted in this way:
This is the same permanent and immutable static site deployment available on different gateways. You can do the same for all the gateways in the AR.IO network here - gateways.ar.io.
Think of this like IPFS and eth.limo, but your data is permanently pinned and there’s a decentralized network of hundreds of eth.limo’s to serve these sites, which introduces a high level of decentralization and resilience for hosting.
We really resonate with this statement from the contributing guide:The goal of Scaffold-ETH 2 is to provide the primary building blocks for a decentralized application.
I would be very happy to open the PR for this. The constraints for deployment are the same as IPFS so adding support should be relatively easy.
Having reviewed the codebase, it would require:
I went ahead and tested via permaweb-deploy’s CLI command and setting NEXT_PUBLIC_IPFS_BUILD === "true" - this worked out of the box with no changes. Here is the app deployed and available on multiple gateways:
One area that is new to me is using Hardhat and Foundry to securely manage encrypted keys, so I would need to look into how we’d support the deployment workflow with this setup. I am confident it’s achievable and Dhaiwat has offered to collaborate with me on this PR.
Love to get any feedback on the idea 🙏
Beta Was this translation helpful? Give feedback.
All reactions