regen-network / testnets Goto Github PK

View Code? Open in Web Editor NEW

38.0 14.0 272.0 1.03 MB

Regen test network information and scripts

Home Page: https://docs.regen.network

Shell 34.67% Go 64.98% Makefile 0.34%

testnets's People

Contributors

Stargazers

Watchers

Forkers

swidnikk cfl0ws joe-bowman louisw420 karzak willszal vitwit regen-friends node-a-team sahith-narahari simi-dev noiseguild chinezupwnz mnugumanova gwg422 awrelll kwunyeung cachitu gbunea paul121 bhavyabindumetla jhernandezb louptheron clawmvp agx10k wjdfx gavinly mattharrop zillabytes andreyvelde tyrion70 art55555 wf555 maricalucian gin westaking carambon stackzmack valerchegs mihbergen edouardlvdl kerinovabit zeldabrea gunray88 stakethat lkotka animaross waccomte stakezone jim380 brane226 dariopavlic huglester iammelea stakewolf creamjun cryptodedushka chrisabbott tubbz-alt gotjoshua kaustubhkapatral deyure2u dpdanpittman anilcse novy4 raulbernal iurii2002 kristofferjon jjangg96 waitrouz tolon lkkroot33 bbbobbbb kinrokinro forbole aiboleath wangshenfeng gabriel-387 rudolfhe55 tonyxoac sun1534 dee-effes anti83 zeroghpp anas336 silentnoname aliefaisala skkz4555 wint3rh0me1288 shenjinjin1 rewkind78 stefneil tedchun3 dirmansebastian klllhhff ama31337 sekaiamber lvyanchi sideeffect117 m37x

testnets's Issues

Request to Change Mechanism for Community Rewards

Right now in plan.md we can see:

Community reward
Top - 10 teams/individuals will receive 50points each for their contributions for the community. technical docs, helping/resolving community issues, etc.

There are a few drawbacks:

One who answers 10 questions on discord daily gets the same reward as one who answers 1 as long as they both are in Top 10.

Vague measure of help: I dont undertsand how do we measure the extend of help.

A very few points are allocation for this section, only 50 :(

Missing Incentivizes (Like lets say someone creates something which is not mentioned in the doc like discord stickers or memes or raised PRs to improve code or docs)

My Proposal:

Create a range of rewards that can be grabbed by someone. [0 - X points]

In each task we can have a field "whoHelpedYou" where users can mention the discord handle of the person who helped them.

We should allocate some more points to it, like I said have a range. I would suggest [0 to 1000 points] to really incentivize the community to help each other.

In each submission a user can mention "whatIdid" --> where he/she can mention the stuff he worked on. It can solely be decided by team whether it was important or not, or should the team allocate rewards for his/her work or not.

This way we can turn extend of help into a metrics which would help the team to evaluate each person better.
This will have community voice [as they get to say who helped them] and as well as team voice [as they can decide whether the extra effort put by an individual was worth a reward or not].

Hoping my suggestion would be considered :)

cannot add float to u128 yet

added 0.5 to amount getting error: no implementation for u128 + float

Suggestion about GO path check devnet-val-setup.sh

Been playing with dev-net for a while. It will be nice to add /usr/local/go path check for existing installation and if version meet requirements then skip Go install function. Even probably better approach is like --go-path=/path/to/go flag pass in to devnet-val-setup.sh for people who use different versions for whatever reason. Also avoiding mv: cannot move 'go' to '/usr/local/go': Directory not empty error and ./devnet-val-setup.sh: line 27: go: command not found

Thank you !

Store contract command causing regen daemon hangs

regen version v0.6.0
docker version  19.03.6      
cargo version cargo 1.50.0 (f04e7fab7 2021-02-04)

After running "sudo docker run" to build the contracts, I am executing:
regen tx wasm store artifacts/cw20_base.wasm --chain-id aplikigo-1 --from <key_name> -y
and the daemon just hangs, validator stoping to get/sign blocks. I tried to use more gas and fees without any luck.

The solution:

restart the cosmovisor daemon
change the user permissions for contracts built with docker
go in artifacts directory and execute the store command from that directory like:
regen tx wasm store cw20_base.wasm --chain-id aplikigo-1 --from my-key --gas auto --fees 2000000utree -y

Transaction send trough not yet synced node make future transactions impossible to pass.

Way to reproduce:

Start new peer, don't wait until sync, send some transactions trough, wait for peer to fully sync with network.

After sending transaction trough fully synced peer:

account sequence mismatch, expected 285, got 284: incorrect account sequence

How to fix:

Restart node.

Suggestion:

At full sync clear transactions pool.

add chainflow to algradigon-1

{"type":"auth/StdTx","value":{"msg":[{"type":"cosmos-sdk/MsgCreateValidator","value":{"description":{"moniker":"Chainflow","identity":"","website":"","details":""},"commission":{"rate":"0.100000000000000000","max_rate":"0.200000000000000000","max_change_rate":"0.010000000000000000"},"min_self_delegation":"1","delegator_address":"xrn:1qkht8zq6jpnu34m9xyjcgmf4gspdk6t5pfjtnp","validator_address":"xrn:valoper1qkht8zq6jpnu34m9xyjcgmf4gspdk6t5hzr458","pubkey":"xrn:valconspub1zcjduepqt4330l5ryaak9ptckv3ze44aculg56w9jz7vjt0xx57wwwh00mqsnyaxzz","value":{"denom":"utree","amount":"9000000"}}}],"fee":{"amount":[],"gas":"200000"},"signatures":[{"pub_key":{"type":"tendermint/PubKeySecp256k1","value":"Ag2N8bHUk8YcxKqSbshgD3EtcLujKtoNsRBPa29QPBca"},"signature":"kBNnyKnkSTwmX39T9On+7FgmjbaIXBFwsU/1mfhKZDhxK1eMnitZqRvAka74/Qyzksgmsl5/kcY141bAxvFRMg=="}],"memo":"[email protected]:26656"}}

tendermint-validator-set query error

xrncli q tendermint-validator-set --chain-id=kontraua

ERROR: header has vhash 19A61A4724EE0C117127B655BCCF08A56DA36A7FD73242743A10727FF5B10C76 but valset hash is 9F8456E05C7DA6591F62343CB14AC6493AE34847DC319612DD46DFBFBF73DC20

xrncli version --long
name: wasm
server_name: xrnd
client_name: xrncli
version: 0.7.1
commit: c91f81c25042bfa3ee5890761f818b59914e344b
build_tags: netgo,ledger
go: go version go1.13.8 linux/amd64

should devnet-val-setup.sh use a newer version of cosmos-sdk instead of v0.40.0 for cosmovisor?

Is this correct?
https://github.com/regen-network/testnets/blob/master/scripts/devnet-val-setup.sh#L73
Or should it be a newer version?
https://github.com/cosmos/cosmos-sdk/releases
@anilcse

ischyonte-000 validator stopped synchronizing on v0.7.1

Running on v0.7.1, i noticed that my validator was jailed, checking the logs I found a lot of entries like this:

E[2020-03-24|00:51:32.887] Stopping peer for error                      module=p2p peer="Peer{MConn{173.249.40.87:26656} 4efed1cf14c69aee0695837fc7341036fe7dcc52 out}" err="pong timeout"
E[2020-03-24|00:51:44.125] Connection failed @ sendRoutine              module=p2p [email protected]:26656 conn=MConn{172.104.145.220:26656} err="pong timeout"
E[2020-03-24|00:51:44.125] Stopping peer for error                      module=p2p peer="Peer{MConn{172.104.145.220:26656} ad044dbb96cfc65ee97810faa48a853a3906c9c6 out}" err="pong timeout"
E[2020-03-24|00:51:44.440] Connection failed @ sendRoutine              module=p2p [email protected]:26656 conn=MConn{66.232.119.130:26656} err="pong timeout"
E[2020-03-24|00:51:44.440] Stopping peer for error                      module=p2p peer="Peer{MConn{66.232.119.130:26656} 0d354fdae833c3e26d52ed02f9ed967682e79d1f out}" err="pong timeout"
E[2020-03-24|00:52:14.156] Connection failed @ sendRoutine              module=p2p [email protected]:26656 conn=MConn{80.241.217.149:26656} err="pong timeout"
E[2020-03-24|00:52:14.157] Stopping peer for error                      module=p2p peer="Peer{MConn{80.241.217.149:26656} 86e4a20f8c7f3f8bc646f8f35db0e22d45079395 out}" err="pong timeout"
E[2020-03-24|00:52:44.137] Connection failed @ sendRoutine              module=p2p [email protected]:26656 conn=MConn{51.145.151.205:26656} err="pong timeout"
E[2020-03-24|00:52:44.137] Stopping peer for error                      module=p2p peer="Peer{MConn{51.145.151.205:26656} 96e61f52c6d1fd9de811b7e0858d634d6ed86452 out}" err="pong timeout"
E[2020-03-24|00:53:08.103] Connection failed @ sendRoutine              module=p2p [email protected]:26656 conn=MConn{159.89.249.168:26656} err="pong timeout"
E[2020-03-24|00:53:08.103] Stopping peer for error                      module=p2p peer="Peer{MConn{159.89.249.168:26656} 8aea2394d2e9474dbe67cfcbeb67fb01421ca9d8 out}" err="pong timeout"
E[2020-03-24|00:53:14.124] Connection failed @ sendRoutine              module=p2p [email protected]:26656 conn=MConn{172.104.242.5:26656} err="pong timeout"
E[2020-03-24|00:53:14.125] Stopping peer for error                      module=p2p peer="Peer{MConn{172.104.242.5:26656} 4357200765f03645e746b85832f24d7a8502e31d out}" err="pong timeout"
E[2020-03-24|00:53:14.143] Connection failed @ sendRoutine              module=p2p [email protected]:26656 conn=MConn{173.249.53.224:26656} err="pong timeout"
E[2020-03-24|00:53:14.144] Stopping peer for error                      module=p2p peer="Peer{MConn{173.249.53.224:26656} 3f931256cb882756133fa0daebbffc86f6b26cfb out}" err="pong timeout"
E[2020-03-24|00:53:17.939] Connection failed @ sendRoutine              module=p2p [email protected]:26656 conn=MConn{173.249.40.87:26656} err="pong timeout"
E[2020-03-24|00:53:17.940] Stopping peer for error                      module=p2p peer="Peer{MConn{173.249.40.87:26656} 4efed1cf14c69aee0695837fc7341036fe7dcc52 out}" err="pong timeout"
E[2020-03-24|00:53:44.973] Connection failed @ sendRoutine              module=p2p [email protected]:26656 conn=MConn{206.189.94.44:26656} err="pong timeout"
E[2020-03-24|00:53:44.973] Stopping peer for error                      module=p2p peer="Peer{MConn{206.189.94.44:26656} 7dad3011330030094b355e3a9d1667970f255f57 out}" err="pong timeout"
E[2020-03-24|00:53:59.117] dialing failed (attempts: 1): auth failure: conn.ID (ad044dbb96cfc65ee97810faa48a853a3906c9c6) dialed ID (e7c1c61d41abbc66fab0493f7921289751db1f62) mismatch module=pex [email protected]:26656
E[2020-03-24|00:54:14.125] Connection failed @ sendRoutine              module=p2p [email protected]:26656 conn=MConn{172.105.93.229:26656} err="pong timeout"
E[2020-03-24|00:54:14.125] Stopping peer for error                      module=p2p peer="Peer{MConn{172.105.93.229:26656} e39f9473e38713cfcb3ca232ce863713a9345187 out}" err="pong timeout"
E[2020-03-24|00:54:14.154] Connection failed @ sendRoutine              module=p2p [email protected]:26656 conn=MConn{164.68.101.56:26656} err="pong timeout"
E[2020-03-24|00:54:14.154] Stopping peer for error                      module=p2p peer="Peer{MConn{164.68.101.56:26656} d32432f9c5465aa0d1d9314051bf9a4d28e3bc08 out}" err="pong timeout"
E[2020-03-24|00:54:14.154] Connection failed @ sendRoutine              module=p2p [email protected]:26656 conn=MConn{5.189.150.170:26656} err="pong timeout"
E[2020-03-24|00:54:14.154] Stopping peer for error                      module=p2p peer="Peer{MConn{5.189.150.170:26656} b838b89bc821b98d7ca3ce963c2e75fc4810b124 out}" err="pong timeout"
E[2020-03-24|00:54:53.125] Connection failed @ sendRoutine              module=p2p [email protected]:26656 conn=MConn{159.89.249.168:26656} err="pong timeout"
E[2020-03-24|00:54:53.125] Stopping peer for error                      module=p2p peer="Peer{MConn{159.89.249.168:26656} 8aea2394d2e9474dbe67cfcbeb67fb01421ca9d8 out}" err="pong timeout"
E[2020-03-24|00:54:59.113] dialing failed (attempts: 15): dial tcp 164.68.118.125:26656: connect: connection refused module=pex [email protected]:26656

On first restart I got these log:

I[2020-03-24|11:53:16.803] starting ABCI with Tendermint                module=main 
panic: Failed to process committed block (145162:135215864F2F0A6452BC3C4DC2F75F547664FEA79F139204FE3019D56B731B28): wrong Block.Header.AppHash.  Expected 4F0E1A7D3D239D6BA42466E1AC75BF76A12CA185FCC6C48ED9A133AD4BE7521F, got E9DE1CF669FF9A60BA7E41D9A6A0D2BADE467C5F988050CB271B0F3349B9783A

goroutine 969 [running]:
github.com/tendermint/tendermint/blockchain/v0.(*BlockchainReactor).poolRoutine(0xc000cd76c0)
 github.com/tendermint/[email protected]/blockchain/v0/reactor.go:344 +0x12ff
created by github.com/tendermint/tendermint/blockchain/v0.(*BlockchainReactor).OnStart
 github.com/tendermint/[email protected]/blockchain/v0/reactor.go:118 +0x84

And on each subsequent restart:

I[2020-03-24|11:56:24.846] starting ABCI with Tendermint                module=main 
ERROR: error during handshake: error on replay: wrong Block.Header.AppHash.  Expected 4F0E1A7D3D239D6BA42466E1AC75BF76A12CA185FCC6C48ED9A133AD4BE7521F, got E9DE1CF669FF9A60BA7E41D9A6A0D2BADE467C5F988050CB271B0F3349B9783A

In order to recover the validator i needed to issue an unsafe-reset-all and synchronize from scratch.

request to add gentx to the genesis

Seems you announced that 62 gentx were accoutned to genesis, but you've not added my submission, which is 62th

Pull request - add Breader gentx #181

--gas auto = Error: unknown query path: unknown request

When create-validator with --gas auto

Error: unknown query path: unknown request

set to

--gas 250000 or --gas-prices 0.03utree

works fine

Create script to calculate uptime for a range of blocks

Context

In the regen-test-1001 testnet we offered the following points: https://github.com/regen-network/testnets/tree/master/regen-test-1001

This issue refers specifically to the uptime reward.

Acceptance Criteria

Given a blockchain full-node
When the uptime calculation script is run with a start and end block
Then a table of validator keys and the number of blocks where they voted is printed

Note: we are interested in validators that voted, not whether or not they were jailed or did not have enough stake. Ideally, we should count any detectable uptime, not just validators that happened to be bonded/unjailed.

--offline flag doesn't work as expected

--offline flag not been noticed by client.

Processed transaction with

regen tx bank send "$from_key" "$destination" "$AMOUNT" \
        --node "$rpc_address" \
        --chain-id "$chain_name" -y \
        --memo "$memo" \
        --offline \
        --fees 5000utree

Broadcast transaction to network

https://aplikigo.regen.aneka.io/txs/B3B274BE24B7951FF3549418044C1F4F5E6F911460B2CFF7AA31690819B00542

Expected

Doesn't broadcast

node or validator hangs when uploading contract with gas auto

Can reproduce this by building the contracts in phase-3, and storing using gas=auto
This causes the validator to miss blocks

regen cli has duplicate update-group-admin


regen tx group -h
Group transaction subcommands

Usage:
  regen tx group [flags]
  regen tx group [command]

Available Commands:
  create-group                  Create a group which is an aggregation of member accounts with associated weights and an administrator account. Note, the '--from' flag is ignored as it is implied from [admin].
  create-group-account          Create a group account which is an account associated with a group and a decision policy. Note, the '--from' flag is ignored as it is implied from [admin].
  create-proposal               Submit a new proposal
  exec                          Execute a proposal
  update-group-account-admin    Update a group account admin
  update-group-account-metadata Update a group account metadata
  update-group-account-policy   Update a group account decision policy
  update-group-admin            Update a group's admin
  update-group-admin            Update a group's admin
  update-group-members          Update a group's members. Set a member's weight to "0" to delete it.
  vote                          Vote on a proposal

congo-1 community testnet - call for launch validators

We're planning to launch the congo-1 community testnet on -

Thursday November 7th at 1700 UTC (08/11 at 0200KST, 1200EST and 0900PST).

To ensure a successful launch, @joe-bowman and I are making a call for genesis validators who can commit to being online at genesis time. We'll likely allocate enough TREE to this confirmed set of validators to bring the network online at the chosen time.

If you're interested in participating at genesis time AND can commit to being online at that time, please indicate your interest in the comments below 👇

Please link to your genesis transaction PR in your comment. You can submit your PR here.

Attemt to deploy contract hang validator.

Messing around contract deployment

After running this ( not sure if this even have any sense, just experiment )

NODE="http://127.0.0.1:26657"

regen tx wasm store cw20_base.wasm \
  --chain-id "aplikigo-1" \
  --gas auto \
  --from posfreak -y \
  --memo "PoSFreak" \
  --node "$NODE"

validator hang and RPC doesn't respond anymore.
Nothing in a log, it just stop producing any output.

systemctl restart cosmovisor solved the issue.

Can be related to --gas auto , just an idea.