gcharang
commented
5 years ago Hi! you can add the doc here: https://github.com/KomodoPlatform/Documentation/blob/dev/docs/source/komodo/regtest-assetchain.rst
This is in dev branch, once you add it here, I will create an entry in index file and merge to master.
Notes from commentary with dukeleto:
dukeletoToday at 4:38 PM @siddhartha-crypto that printout is a debug printout, that i think i added. it only prints to stdout of the daemon. You happen to be running curl in the same terminal that has the STDOUT of your daemon. that printout should probably be commented out, too @siddhartha-crypto you need to specify -regtest on the CLI command-line, so what you did was try to import a mainnet private into regtest, which won't work @siddhartha-crypto for additional complexity, regtest starts as sprout, and changes to sapling at block 61. Sprout and sapling private keys are different and incompatible, so watch out for that siddhartha-cryptoToday at 5:03 PM ok, that's interesting...
so, for every komodo-cli command, I need to add -regtest, and sapling addresses are not valid until after block 61...
Seems like I ought to document that somewhere... but where... hmmm..... dukeletoToday at 5:12 PM not sure it's documented anywhere, it's just what happens in James's sapling change-over code, it selects a "reasonable" block, and it regtest, it always seems to choose 61
=== Running testscript dpowconfs.py === Initializing DPoWconfs test directory /var/folders/k0/s6fw3wld56j9bx2h_kfvp_x80bj2wq/T/testx8B5Jd Writing to /var/folders/k0/s6fw3wld56j9bx2h_kfvp_x80bj2wq/T/testx8B5Jd/node0/komodo.conf Setting up network... cmd=/Users/jonathanleto/git/komodo/qa/pull-tester/run-bitcoin-cli Running /Users/jonathanleto/git/komodo/qa/pull-tester/run-bitcoin-cli -ac_name=REGTEST -conf=/var/folders/k0/s6fw3wld56j9bx2h_kfvp_x80bj2wq/T/testx8B5Jd/node0/REGTEST.conf -port=64367 -rpcport=64368 -regtest -addressindex=1 -spentindex=1 -ac_supply=5555555 -ac_reward=10000000000000 -ac_cc=2 -whitelist=127.0.0.1 -debug --daemon -rpcuser=rt -rpcpassword=rt -rpcwait getblockcount perc 0.0000% ac_pub=[000000...] acsize.0 ERA0: end.0 reward.10000000000000 halving.0 decay.0 000000000000000000000000000000000000000000000000000000000000000000000000000000000000a0724e18090000000000000000000000000000000000000000000000020000 extralen.73 crc0.10646e3b set p2pport.64367 call komodo_args.(/Users/jonathanleto/git/komodo/src/komodod) NOTARY_PUBKEY.()
sorry for the huge paste, but that shows a regtest chain starting up @siddhartha-crypto siddhartha-cryptoToday at 5:17 PM Ok.
I'm thinking that I don't want newcomers to Komodo to use a regtest chain just yet, then, so I don't know that I want this on developers.komodoplatform.com (which is only for newcomers, for now).
If we put this anywhere, it would go on docs.komodoplatform.com ...
I don't deal with that repo much -- I'm not sure how the sidebar is structured.
@SHossain
If you want to get me just a section on docs.komodoplatform.com with a title "Using a regtest asset chain for testing" and then just point me to it, I can write a quick description of how all this works and make these notes before we lose them. I can add this as an issue to the repo, if you're busy right now. dukeletoToday at 5:43 PM @siddhartha-crypto i understand that regtest is not newcomer friendly, it's mostly for KMD core devs, and also devs of asset chains and devs of external coins that use dpow we probably need some docs of how to run some of our tests, which use regtest mode to run my dpowconfs tests, you run ./qa/pull-tester/rpc-tests.sh dpowconfs from the root of the komodo git repo that takes care of all the details, and if somebody wants to know more, they can read the source of a test file :smiley: we also have cryptoconditions tests and all the tests we inherited from zec, some pass, some don't