Closed ShookLyngs closed 1 month ago
Faucet 1: https://signetfaucet.com/ (0.00001 at a time)
Faucet 2: https://botanix.5thweb.io/ (0.001 at a time, 1 time in 24 hours)
If we switch to BTC testnet4, do we redeploy RGB++ lock script and BTC time lock script for testnet4?
If yes, we still need to update rgbpp-sdk/ckb
.
Since BTC testnet3 is coming back somehow. So the priority of supporting BTC signet or testnet4 is now lower.
If we switch to BTC testnet4, do we redeploy RGB++ lock script and BTC time lock script for testnet4? If yes, we still need to update
rgbpp-sdk/ckb
.
However, if testnet3 remains unstable or problematic, then rgbpp-sdk and assets-api have to investigate to support a new test environment.
So the answer to your question is Yes
, in a long term.
Background
The BTC testnet3 is currently slow and the peak fee rate is sky high. Therefore, we may have to support switching to other testnets in the rgbpp-sdk/btc.
Questions
Some questions to be answered, some decisions to be made:
NetworkType.TESTNET
, or should we add a newNetworkType
option?Discussion -> Conclusions
BTC testnet4 is not finalized yet, so BTC signet will be supported first. BTC testnet4 may be supported later.
The BTC testnet3 should continue to be maintained as most of the RGB++ testnet dApps are running on this environment. A new
BTC NetworkType
may be required to accommodate this need.TODO
Bitcoin/RGB++ Assets API @ahonn @mfuuzy
BTC signet SPV on CKB testnet @EthanYuan
CKB testnet rgbpp contracts with BTC signet SPV config @EthanYuan @jjyr
rgbpp-sdk/btc @ShookLyngs
Without modification:
If adding NetworkType.SIGNET:
Update thedecodeAddress
function and remove thenetworkType
from the return type, as it's no longer accurateCheck and update where thedecodeAddress
function was referencedrgbpp-sdk/ckb @duanyytop
References