Closed humbitious closed 2 years ago
Before a workflow can be instantiated on the public chain, it needs to be closed out and disabled on the private chain
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
This issue now has a funding of 3.4023 ETH (2000.01 USD @ $587.84/ETH) attached to it.
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
Work for 3.4023 ETH (1910.98 USD @ $566.42/ETH) has been submitted by:
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
Work for 2000.0 USDC (2000.00 USD @ $1.0/USDC) has been submitted by:
@sekmet do you have an ETA for when the video will be added to your README here? We'd love to have a look tomorrow if possible. Thanks!
Hello Mr. Tim, Readme and App updated --> https://github.com/sekmet/Baseline-Chain-Dashboard Thank you!
Thanks @sekmet, this is great!
Issue Status: 1. Open 2. Started 3. Submitted 4. Done
The funding of 2000.0 USDC (2000.00 USD @ $1.0/USDC) attached to this issue has been approved & issued to @sekmet.
Good work
Baseline Chain Switcher Demo and Components
Bounty
$2,000 in Eth.
Description of the Challenge
There is a folder in the Baseline Protocol Repo that contains the code for a service called "Commitment Manager". It allows you to set the type of ethereum blockchain client and the specific blockchain instance on which you will manage commitments (merkle-trie, proofs) by configuring the service's environment variables.
Use the Commitment Manager to start a baselined workflow on a private Besu blockchain instance, run the workflow several times to successfully deposit commitments into the shield contract on that blockchain. Then, write a switch function and user interface that allows an admin to switch from that private Besu blockchain to the public blockchain via Infura. Minimally, new baseline worksteps/workflows will now go to a public testnet/mainnet.
Submission Requirements
Required:
commit-mgr
should be configurable via env vars such that it can use Infura as its web3 providerBonus features:
commit-mgr
serviceJudging Criteria
In order to win the bounty, a submission MUST meet every item in the the "Required" list. If multiple submissions meet all of the "Required" items, tie-breakers will be judged in the following order:
Winner Announcement Date
January 27, 2021