| docker run -d --restart always --publish 8301:8301 --publish 8302:8302 \ | |
| --volume ~/keys:/keys:z --volume ~/.coda-config:/root/.coda-config:Z \ | |
| --nsme codainstance coda:1.0 coda daemon -peer `SEED1` -peer `SEED2` \ | |
| -block-producer-key "/keys/validator-keys" -run-snark-worker `PUBLICKEY` \ | |
| -snark-worker-fee 1 -block-producer-password `PASSWD` |
| echo "deb [trusted=yes] http://packages.o1test.net/ unstable main" | sudo tee /etc/apt/sources.list.d/coda.list | |
| apt-get update | |
| apt-get install -t unstable coda-testnet-postake-medium-curves=0.0.12-beta+406048-feature-bump-genesis-timestamp-3e9b174-PV48525e92 |
| const Web3 = require('web3'); | |
| const BigNumber = require('bignumber.js'); | |
| const fs = require('fs') | |
| const { promisify } = require('util') | |
| const readFileAsync = promisify(fs.readFile) | |
| const options = { | |
| transactionConfirmationBlocks: 2, | |
| transactionBlockTimeout: 50, | |
| } | |
| if (typeof web3 !== 'undefined') { |
This is based on @bertux written systemd script and it can any k instance of the witnet. Docker is not required, and only thing you need to do is run script.
Before running the script you have to make the script executable by:
chmod +x witnet.sh
Usage:
./witnet.sh create -s 1 -e 5
For running this script which uses REST endpoints of ava. I am using the default network id , which I took as 12.
go run main/* --public-ip=127.0.0.1 --snow-sample-size=1 --snow-quorum-size=1 --staking-tls-enabled=false --network-id=12 --api-admin-enabled=true
And then ./ava.sh.
This script is using default network id so the funds are there in ewoqjP7PxY4yr3iLTpLisriqt94hdyDFNgchSxGGztUrTXtNN
Install jq for running the below script.
NOTE: create chconfig path with chain-config.json in it.
./chain.sh setan setanchain-2 "http://localhost:26657" "chconfig/" "1" 26657 test
./chain.sh doubloons gameofzoneshub-2 "http://localhost:26557" "chconfig/" "2" 26557 test
./chain.sh sample sample-2 "http://localhost:26457" "chconfig/" "3" 26457 test
If no other details other than rpc-addr and chain-id is present that is because either the zone has restricted the access to only some IPs or the zone is down. You can use the detail for connecting and establishing channels with chains.
Note: I used the details from the constent_info to create this json. In future, this gist will be autoupdated.
Other weird issue that , I found is below packet has two txs and the second tx in array has two is itself a combination of two tx
How can be a tx combination of 2 txs. Because of this, i can not relay all the packets in my channel from pylonchain to setanchain(my chain). While relay the packets i got error at this line. https://github.com/iqlusioninc/relayer/blob/master/relayer/naive-strategy.go#L242
For getting that packet.
rly q txs pylonchain "send_packet.packet_src_channel=heyjusbiqh&send_packet.packet_sequence=11"
Trying to transfer funds between melea-11 and pylonchain is failing with packet commitment failed.
$ rly tx xfer pylonchain melea-11 10pylon true $(rly ch addr melea-11) --debug
I[2020-04-29|12:52:38.393] ✔ [pylonchain]@{80008} - msg(0:transfer) hash(BA9A99164183355C9D6D3293FAEAF290729E1C38A8B0D8B820EABD49DBE1EDD1)
I[2020-04-29|12:52:47.344] - [melea-11] -> sending transaction:
I[2020-04-29|12:52:47.345] ✘ [melea-11]@{0} - msg(0:update_client,1:ics04/opaque) err(client: packet commitment verification failed)
{"height":"0","txhash":"13D864A31A9D72132F08F5FDE51C84B6469C3DEE0FE946D309E54D16E148A6DC","codespace":"client","code":16,"raw_log":"couldn't verify counterparty packet commitment: key mismatch on operation #0: expected commitments/ports/transfer/channels/abixkfasxc/packets/144 but got commitments/ports/transfer/channels/abixkfasxc/packets/1404: packet commitment verification failed","gas_wanted":"200000","gas_used":"110315"}