You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need a dApp-friendly version of deployment allowing dashboard developers to build UI components without having to run geth/ganache/hardhat locally and deploying contracts locally. Also, all the parameters should be fine-tuned to allow quick testing of dashboard features. For example, short authorization decrease delay or sweeping deposits and minting TBTC without having the actual SPV proof produced. Note that this is only for local development, and public testnet should require SPV proofs. This will allow dApp developers new to the project to quickly onboard without having to understand and go through all the dependency complexities (KEEP/NU/Threshold/tbtc-v1/tbtc-v2/ECDSA,beacon).
Steps to get there:
@r-czajkowski: Revisit all parameter values in RandomBeacon, WalletRegistry, and Bridge. Adapt them to dApp development needs.
@r-czajkowski: Create dApp development branch with parameters fine-tuned ^. Open a draft PR to review them but never merge it to main
@r-czajkowski: Add CODEOWNERS file protecting audited *.sol files, pointing to @pdyraga, @nkuba, @lukasz-zimnoch (random beacon, ecdsa, tbtc-v2). This is a protection to enforce the never-merge rule for dApp development fine-tuned parameters.
@michalinacienciala: Add CI job to deploy dApp contracts, tag them with dApp development tag, and push to NPM. Unit tests do not have to be executed as a part of this CI job.
We need a dApp-friendly version of deployment allowing dashboard developers to build UI components without having to run geth/ganache/hardhat locally and deploying contracts locally. Also, all the parameters should be fine-tuned to allow quick testing of dashboard features. For example, short authorization decrease delay or sweeping deposits and minting TBTC without having the actual SPV proof produced. Note that this is only for local development, and public testnet should require SPV proofs. This will allow dApp developers new to the project to quickly onboard without having to understand and go through all the dependency complexities (KEEP/NU/Threshold/tbtc-v1/tbtc-v2/ECDSA,beacon).
Steps to get there:
RandomBeacon
,WalletRegistry
, andBridge
. Adapt them to dApp development needs.main
@pdyraga, @nkuba, @lukasz-zimnoch
(random beacon, ecdsa, tbtc-v2). This is a protection to enforce the never-merge rule for dApp development fine-tuned parameters.dapp-development
branch solidity-contracts#119dapp-development
branch keep-network/keep-core#3121dapp-development
branch keep-network/tbtc-v2#392dapp-development-goerli
packages #161The text was updated successfully, but these errors were encountered: