Devops: Spin up custom public Ethereum testnet, identify all needed configurations, fully document
Budget: $30 – $250 USD
Your task is to spin up a NEW custom public Ethereum testnet, that anyone can connect to with metamask, probably using a package that automates 99% of this, e.g.:
https://github.com/kurtosis-tech/ethereum-package
This task includes:
(1) Figuring out how to do the needed customizations so that it appears as a new separate network, including:
+ Custom genesis block - this testnet is launching from scratch, NOT forking the existing state of any existing ethereum network.
+ Custom "Chain ID", so that other ethereum nodes and wallets like metamask see it as a different ethereum-based network
+ Should use the SAME wallet derivation path as Ethereum, instead of using a different derivation path based on Chain ID - so that if your wallet has a certain address on Ethereum, then it has the same address on this new network.
+ Configure the initial PoS miner(s) / initial airdrop to first miner(s)
+ Making sure that anyone else can easily run a full node and connect to our testnet too, as long as they have the proper configuration settings - NOTE: we're launching a public, permissionless testnet, not a private permissioned network.
(2) Doing a test deploy of the properly-configured software, via our AWS account, and confirm that the network is working and live
(3) Test connecting to this new network in metamask and send coins between accounts
(4) Provide us the full launching script, to deploy a new full node on this network from scratch, just by launching one script with the pre-made configuration file you created and and nothing else. I.e. enter one command and it launches everything. If any e.g. IP addresses or address should be passed each time it is run, then those should be passed as command line arguments, or settings at the top of the script, and all private keys should be put in some kind of `.env` file.
(5) Provide a document explaining all the configuration steps you did, what each modified configuration setting does, and an explanation of why the configuration steps you did are good and sufficient for our needs.
(6) Self-check before asking us to do anything: Provide proof to us that everything is working before asking us to check anything. Never ask us to "check it". Instead provide to us definitive proof that each requirement is fulfilled.
Future work: Setting up bridging software, for bridging tokens between the real Ethereum chain and our Testnet chain, and much more. Lots of additional work like this available if you're good at this.
Basically, a custom Ethereum public testnet, that anyone can connect
Thanks!
https://github.com/kurtosis-tech/ethereum-package
This task includes:
(1) Figuring out how to do the needed customizations so that it appears as a new separate network, including:
+ Custom genesis block - this testnet is launching from scratch, NOT forking the existing state of any existing ethereum network.
+ Custom "Chain ID", so that other ethereum nodes and wallets like metamask see it as a different ethereum-based network
+ Should use the SAME wallet derivation path as Ethereum, instead of using a different derivation path based on Chain ID - so that if your wallet has a certain address on Ethereum, then it has the same address on this new network.
+ Configure the initial PoS miner(s) / initial airdrop to first miner(s)
+ Making sure that anyone else can easily run a full node and connect to our testnet too, as long as they have the proper configuration settings - NOTE: we're launching a public, permissionless testnet, not a private permissioned network.
(2) Doing a test deploy of the properly-configured software, via our AWS account, and confirm that the network is working and live
(3) Test connecting to this new network in metamask and send coins between accounts
(4) Provide us the full launching script, to deploy a new full node on this network from scratch, just by launching one script with the pre-made configuration file you created and and nothing else. I.e. enter one command and it launches everything. If any e.g. IP addresses or address should be passed each time it is run, then those should be passed as command line arguments, or settings at the top of the script, and all private keys should be put in some kind of `.env` file.
(5) Provide a document explaining all the configuration steps you did, what each modified configuration setting does, and an explanation of why the configuration steps you did are good and sufficient for our needs.
(6) Self-check before asking us to do anything: Provide proof to us that everything is working before asking us to check anything. Never ask us to "check it". Instead provide to us definitive proof that each requirement is fulfilled.
Future work: Setting up bridging software, for bridging tokens between the real Ethereum chain and our Testnet chain, and much more. Lots of additional work like this available if you're good at this.
Basically, a custom Ethereum public testnet, that anyone can connect
Thanks!