v14.0 Testing

[forro]

v14 rc4:
I set privatesend to keep 10 tdash anonymized, 4 rounds. When I look in inputs, it created ~122 worth of tdash in denoms:
11 of 10 tdash
11 of 1 tdash
10 of .1 tdash
9 of .001 tdash

It also noticed It did not create any .01 tdash.

 

[ivan.ivx]

May I get a tDash? yRghXktehNTt2ttFr951xaDToYKVKpXBeJ, Thank you

 

[AjM]

May I get a tDash? yRghXktehNTt2ttFr951xaDToYKVKpXBeJ, Thank you

Yes you can, use faucets https://www.dash.org/forum/threads/testnet-tools-resources.1768/

 

[ivan.ivx]

Yes you can, use faucets <url>

None of those faucets are working.

 

[AjM]

None of those faucets are working.

Ok, lets call some help, @flare @elbereth

 

[flare]

Ok, lets call some help, @flare @elbereth

Thanks, will work on that tomorrow.

 

[Shaggy]

Hi guys,

we are currently working as a startup on a webplattform. Plan is to adapt Dash aswell. To assure 100% quality we would like to test different use cases over the dash testnet. i tried to get since last week some tDash. Unfortunatly the Faucet links do not work. Would it be possible to send me around 10k of tDash? would be enough for various testcases incl. loadtests.

tDash - Wallet:
ygtAvgykxLnmshUdfqt1QHAYfUJ5z1soav

thank u in advance and best regards,

Cagdas

 

[strophy]

Hi guys,

we are currently working as a startup on a webplattform. Plan is to adapt Dash aswell. To assure 100% quality we would like to test different use cases over the dash testnet. i tried to get since last week some tDash. Unfortunatly the Faucet links do not work. Would it be possible to send me around 10k of tDash? would be enough for various testcases incl. loadtests.

tDash - Wallet:
ygtAvgykxLnmshUdfqt1QHAYfUJ5z1soav

thank u in advance and best regards,

Cagdas

Faucet has been refilled: http://faucet.test.dash.crowdnode.io/

 

[Shaggy]

True, thank you. Is there a reason i dont receive any tdash? One and the first transaction worked. the second one (after 5 min of course) worked on the faucet platform but didnt arrive on my wallet.

Firewall off;
Version: v0.14.0.0-rc4
Checked the chain, should be also ok.

Any ideas? is the faucet maybe broken?

Edit: sending works, receiving still dont

Thanks in advance

 

[gtabmx]

Given the 0.14 testnet faucets are dry or not currently online, can someone please send yNmbhgXgmhpmUxf5fE3rwAGqZ4ofL8UvRi about 100 tDASH ?

Thanks!

 

[strophy]

http://faucet.test.dash.crowdnode.io/ has been resynced + refilled and is working normally.

 

[wangzf]

如何使用测试网络？我在官方网络上安装了最新的钱包0.13.3。测试网络不能同步到最新的块，而只能到块高度78808.如何升级到0.14？

 

[wangzf]

How to use the test network? I installed the latest wallet 0.13.3 on the official network. The test network can not be synchronized to the latest block, but only to the block height 78808. How to upgrade to 0.14?

 

[codablock]

v0.14.0.0-rc5 has just been released: https://github.com/dashpay/dash/releases/tag/v0.14.0.0-rc5

Please upgrade when you find time. This RC is very close to what's going to be the final version.
This RC mostly contains bug fixes and performance improvements for LLMQ based ChainLocks and InstantSend.

An additional change is the introduction of simulated DKG errors and simulated misbehavior. I've configured all my masternodes to simulate a few errors in upcoming DKGs, so we should see regular complaints and justification messages on testnet now.

 

[strophy]

@wangzf you should use these binaries for testnet: https://github.com/dashpay/dash/releases/tag/v0.14.0.0-rc5

It is easiest to use a clean datadir and sync from scratch. If you are stuck at block 78808 using 0.14.0.0-rc5, you can use the `getchaintips 5` command to find the block marked invalid and then `invalidateblock <blockhash>` to try and get to the right chain height again.

Faucet here: http://faucet.test.dash.crowdnode.io/

 

[pwjjrn]

如何使用测试网络？我在官方网络上安装了最新的钱包0.13.3。测试网络不能同步到最新的块，而只能到块高度78808.如何升级到0.14？

建议新环境 ,下载安装 v0.14.
https://github.com/dashpay/dash/releases/tag/v0.14.0.0-rc5

 

[qwizzie]

Should latest pull request for 14.0 (#2923) not be labeled as a bug fix, in what should be
a code freeze by now this close to 14.0 release ? If its not a bug fix, should it not be reserved for 14.1 ?

It worries me that this new code (bug fix or not) will effectively get less testing time then it would receive with a 14.1 update release. Also i feel like the code freeze process now comes across as a process that is being handled somewhat loosely and not strictly enforced.

Edit : the already approved 0.14 release notes draft pull request #2896 needs to be updated, reviewed and acknowledged again to include #2923

 

[wangzf]

I used v0.14 to run the test network, but when I started synchronizing to the latest block, I ran out of memory, executed commands like dash-cli with no response, and started synchronizing from the first block after restarting.

 

[wangzf]

I would like to ask the relevant node testing technical consultation, I can only get the answer here?

 

[wangzf]

@wangzf you should use these binaries for testnet: https://github.com/dashpay/dash/releases/tag/v0.14.0.0-rc5

It is easiest to use a clean datadir and sync from scratch. If you are stuck at block 78808 using 0.14.0.0-rc5, you can use the `getchaintips 5` command to find the block marked invalid and then `invalidateblock <blockhash>` to try and get to the right chain height again.

Faucet here: http://faucet.test.dash.crowdnode.io/

2019-05-17 09:06:33 ERROR: AcceptBlockHeader: block 00000000154499187efd42d9d63d874d0699f230748a7575ac0be154eafc1022 is marked invalid
2019-05-17 09:06:33 ERROR: invalid header received

 

[wangzf]

Submit the signed message ：This step of operation has been misreported. The error is as follows.

./dash-cli protx register_submit "03000100012b49b2e31f6097188676c0074d060cdeb2acf1fa929c779cf24f5cbcb83e1b670000000000feffffff0121c89a3b000000001976a914290cad49d053a230caae20873bfe2882aa08684088ac00000000d1010000000000a38321ed944a58cbfd45502e30d1f02ed729f18082f3cf703d8b61c4f7dbe9aa0100000000000000000000000000ffff7f00000127140a46247cb37a14429f93bb3382101069c96f9fea808c4a25d8051876f94805c555acaea9c9eb3c0bc252e99e0c44d64ffdb72244ae1e67236c1c882a25ecaa1947ffa758063e603c53107e8ba78fa858628113f2a35a499800001976a914298655b3f03b1b940146016dbbb97a82982ff56a88acd3d8a865c5d5c184259f1f82ed201b1ac3dd10f3549348c273d66bd93377d7af00" "IJKBhxsWogxWfN4K6L5k\/1h7XgQaFJqiN4Lk49pjrAz4BWppEI5q1AIy9+eXxQ2J9lOJfANB8sl1IGj04dul2nU="
error code: -1
error message:
bad-protx-collateral (code 16)

 

[strophy]

Hi @wangzf I'm not sure why you're getting this message, your collateral looks like it is defined properly in the protx:

"proRegTx": {
"version": 1,
"collateralHash": "aae9dbf7c4618b3d70cff38280f129d72ef0d1302e5045fdcb584a94ed2183a3",
"collateralIndex": 1,
"service": "127.0.0.1:10004",
"ownerAddress": "yMFmdi7TBqvoXN2MEcpbTb43g1eKCceNMT",
"votingAddress": "yLtTdJse23PForWwaJ8FwRTWK7gDtMVM1k",
"payoutAddress": "yQ71Up3wADdNv2oyEhBVFCj7cagxyAxd56",
"pubKeyOperator": "808c4a25d8051876f94805c555acaea9c9eb3c0bc252e99e0c44d64ffdb72244ae1e67236c1c882a25ecaa1947ffa758",
"operatorReward": 0,
"inputsHash": "afd77733d96bd673c2489354f310ddc31a1b20ed821f9f2584c1d5c565a8d8d3"
}

I tried to build your probable transaction that you should have signed with the collateral key for yQ4Vjsi2jY5HkxVxRQpjL2wXpQhYiKyKKn as follows:

"signMessage": "yQ71Up3wADdNv2oyEhBVFCj7cagxyAxd56|0|yLtTdJse23PForWwaJ8FwRTWK7gDtMVM1k|yMFmdi7TBqvoXN2MEcpbTb43g1eKCceNMT|afd77733d96bd673c2489354f310ddc31a1b20ed821f9f2584c1d5c565a8d8d3"

And it did not verify. Can you post your input and output of protx register_prepare please?

It might be easier to discuss this on Discord in realtime. You can find me there as user @strophy#2696

 

[binlaniua]

no Faucet is work.. please send tdash "yVfEEQkqBuT2G5REpPWqTc8SLEV6epQGwt"

 

[xkcd]

100 tDASH
88e8cf2796319844046e94a1483be7d8a4202a1572a2933cc6fff5580d5c9a53

 

[codablock]

There is still http://test.faucet.masternode.io/ which should have enough funds.