V12 Testing Thread

TanteStefana · Aug 3, 2015

My two on 11.2.23 are still on the chain it seems??

TanteStefana · Aug 3, 2015

Sub-Ether said:
I got another testnet wallet that started on V11 and went to V12, that I used for testing (but didn't roll back)
I deleted everything apart from the wallet and now it refuses to sync even from block =1 at the start,
have tried all the repair options, nothing works and it sees no peers,

2015-08-03 17:12:00 ERROR: ContextualCheckBlockHeader : forked chain older than last checkpoint (height 1)
2015-08-03 17:12:00 ERROR: ProcessNewBlock : AcceptBlock FAILED
2015-08-03 17:12:00 Misbehaving: 37.157.253.66:19999 (0 -> 100) BAN THRESHOLD EXCEEDED
2015-08-03 17:14:34 socket recv error An existing connection was forcibly closed by the remote host. (10054)
2015-08-03 17:15:38 socket recv error An existing connection was forcibly closed by the remote host. (10054)

I had this problem a while ago, and I think putting txindex=1 into the config file is what helped but that is for the 11.2.23 wallet, I believe, so I'm not being any help

moli · Aug 3, 2015

Alright... according to the plan stated on the OP of this thread...

"The block reward will be lowered by 10% a week or two after the release of v12, in preparation for budget proposals however, the budget doesn’t have to use all of this funds if there are not proposals with community support the coins are just not minted."

Here's the rewards coming to my masternodes, they are reduced by ~10% (vs the rewards before at 13.xxxxxx tDASH):

Btw, flare, this is the question i was asking on page 94...

it was good time in the middle of the night...lol
So this is going to happen on Mainnet... I guess we can check this off now...
Let's go over the list to make sure everything is checked off before this baby goes on Mainnet, shall we!!!

:grin::grin::grin:

TanteStefana · Aug 3, 2015

RE: Sub-Ether's issue, has this ever been resolved?

https://dashtalk.org/threads/v12-testing-thread.5484/page-106#post-61620

flare · Aug 3, 2015

moli said:
Alright... according to the plan stated on the OP of this thread...

"The block reward will be lowered by 10% a week or two after the release of v12, in preparation for budget proposals however, the budget doesn’t have to use all of this funds if there are not proposals with community support the coins are just not minted."

Here's the rewards coming to my masternodes, they are reduced by ~10% (vs the rewards before at 13.xxxxxx tDASH):

View attachment 1683

Btw, flare, this is the question i was asking on page 94... it was good time in the middle of the night...lol
So this is going to happen on Mainnet... I guess we can check this off now...
Let's go over the list to make sure everything is checked off before this baby goes on Mainnet, shall we!!!

:grin::grin::grin:

Yep, i've asked Evan to add a 10% reduction to testnet as well, which he did

https://github.com/dashpay/dash/commit/ef1dc8434e0b95f4aa6567bfb2fe1974e2fe57b4

moli · Aug 3, 2015

flare said:
Yep, i've asked Evan to add a 10% reduction to testnet as well, which he did

https://github.com/dashpay/dash/commit/ef1dc8434e0b95f4aa6567bfb2fe1974e2fe57b4

I'm glad you did... I was wondering about it myself... lol .. Thank you!

moli · Aug 3, 2015

Sub-Ether said:
Not for one of my wallets, it will not start syncing or lock onto the peers!!!
(Tante, I tried the txindex=1)

2015-08-03 17:45:12 ERROR: ContextualCheckBlockHeader : forked chain older than last checkpoint (height 1)

Have you got the latest version?
https://dashpay.atlassian.net/builds/allPlans.action

It was solved for me with build 249 windows.

Sub-Ether · Aug 3, 2015

moli said:
Have you got the latest version?
https://dashpay.atlassian.net/builds/allPlans.action

It was solved for me with build 249 windows.

Yer sorry, I was just about to delete the comment, its syncing from 25 weeks ago now.
(strange how 1 older version worked ok on the same machine, I suppose it was the last checkpoint)

scratchy · Aug 3, 2015

errors: EXCEPTION: St13runtime_error tinyformat: Not enough conversion specifiers in format string dash in ProcessMessages()

AjM · Aug 3, 2015

New wallet, new downloaded blockchain, latest build, both synced and same block height.

Sent (without ds and ix) from testwallet2 500 tDASH to testwallet1 and from faucet about 360 tDASH,
cant see any tDASH in testwallet1, should be about 860 tDASH, but nothing, nada, zero, nothing.
I am worried...

EDIT, never mind, my mistake, wrong address, doh

Sub-Ether · Aug 3, 2015

EDIT, never mind, my mistake, wrong address, doh

[/QUOTE]
Are you sure it's a test wallet ? :wink:

AjM · Aug 3, 2015

Sub-Ether said:
EDIT, never mind, my mistake, wrong address, doh
Are you sure it's a test wallet ? :wink:

Thank god, yes...

moli · Aug 3, 2015

scratchy said:
errors: EXCEPTION: St13runtime_error tinyformat: Not enough conversion specifiers in format string dash in ProcessMessages()

UdjinM6 got the fix: https://github.com/dashpay/dash/commit/18635f09794f21b5f7e58ffd5d867ed83018d9d8

AjM · Aug 3, 2015

AjM said:
UdjinM6
Tried send some coins back to the faucet, with instantx.
All funds had 7 confirmations and still got this error:
"InstantX requires inputs with at least 6 confirmations, you might need to wait a few minutes and try again."
Why?

Clean new test, fresh wallet and blockchain.
Result: worked ok, so my v12-v11-v12 test wallet was messed up some how.

eduffield · Aug 3, 2015

If you're running a masternode can you search the debug.log for "CFinalizedBudget::AutoCheck" and post what it has said. Just the last 10-20 lines will do. Thanks!

thelazier · Aug 3, 2015

eduffield said:
If you're running a masternode can you search the debug.log for "CFinalizedBudget::AutoCheck" and post what it has said. Just the last 10-20 lines will do. Thanks!

2015-08-03 19:38:39 CFinalizedBudget::AutoCheck - Finalized Budget Matches! Submitting Vote.
Found only one from dashd-v0.12.0.35-18635f0

moli · Aug 3, 2015

eduffield said:
If you're running a masternode can you search the debug.log for "CFinalizedBudget::AutoCheck" and post what it has said. Just the last 10-20 lines will do. Thanks!

I'm running two MN wallets, CFinalizedBudget::AutoCheck is not found in the debug logs.

AlexMomo · Aug 3, 2015

eduffield said:
If you're running a masternode can you search the debug.log for "CFinalizedBudget::AutoCheck" and post what it has said. Just the last 10-20 lines will do. Thanks!

Code:

2015-08-03 19:18:43 CFinalizedBudget::AutoCheck - Finalized Budget Matches! Submitting Vote.
2015-08-03 19:18:43 CBudgetProposalBroadcast::IsBudgetCollateralValid - Can't find collateral tx CTransaction(hash=0000000000, ver=1, vin.size=0, vout.size=0, nLockTime=0)

2015-08-03 19:18:43 CBudgetProposalBroadcast::IsBudgetCollateralValid - Can't find collateral tx CTransaction(hash=0000000000, ver=1, vin.size=0, vout.size=0, nLockTime=0)

2015-08-03 19:18:43 CBudgetProposalBroadcast::IsBudgetCollateralValid - Can't find collateral tx CTransaction(hash=0000000000, ver=1, vin.size=0, vout.size=0, nLockTime=0)

2015-08-03 19:18:43 CBudgetVote::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(7df7922444303f096fd15dd86c137d0e20649471a08248c08131a6609ddb9e1e, 17), scriptSig=)
2015-08-03 19:18:43 CBudgetVote::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(6c4544305174642cae9169f7a0fe4c5988a40c38a21cd089e9434406077e3816, 2), scriptSig=)
2015-08-03 19:18:43 CBudgetVote::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(8b219fe9ce4b69de57cbdfda7b732902e49072f9d97b25a5dc77be04c3dea760, 18), scriptSig=)
2015-08-03 19:18:43 CBudgetVote::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(7df7922444303f096fd15dd86c137d0e20649471a08248c08131a6609ddb9e1e, 15), scriptSig=)
2015-08-03 19:18:43 CBudgetVote::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(7df7922444303f096fd15dd86c137d0e20649471a08248c08131a6609ddb9e1e, 18), scriptSig=)
2015-08-03 19:18:43 CBudgetVote::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(0a686fddc9b532b563d9003d49dab6dcf907b0cd8ff76e3b83c17e2b678698f9, 7), scriptSig=)
2015-08-03 19:18:43 CBudgetVote::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(6c4544305174642cae9169f7a0fe4c5988a40c38a21cd089e9434406077e3816, 8), scriptSig=)
2015-08-03 19:18:43 CBudgetVote::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(7df7922444303f096fd15dd86c137d0e20649471a08248c08131a6609ddb9e1e, 2), scriptSig=)
2015-08-03 19:18:43 CBudgetVote::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(7df7922444303f096fd15dd86c137d0e20649471a08248c08131a6609ddb9e1e, 4), scriptSig=)
2015-08-03 19:18:43 CBudgetVote::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(7df7922444303f096fd15dd86c137d0e20649471a08248c08131a6609ddb9e1e, 19), scriptSig=)
2015-08-03 19:18:43 CBudgetVote::SignatureValid() - Unknown Masternode - CTxIn(COutPoint(7df7922444303f096fd15dd86c137d0e20649471a08248c08131a6609ddb9e1e, 11), scriptSig=)
//snip...

moli · Aug 3, 2015

eduffield -- When submitting without having available money from the wallet, we still get this:

Code:

16:44:07


mnbudget prepare Test1 https://www.test.com 10 78600 y5uoxqr4Dwx9BsWRK636d5JrERCpPh49Kh 5 true


16:44:07

0000000000000000000000000000000000000000000000000000000000000000

Could we have a response from the system something like :
"Sorry, your proposal submission requires a fee of 1 DASH. Please make sure money is available from your wallet."

eduffield · Aug 3, 2015

moli said:
eduffield -- When submitting without having available money from the wallet, we still get this:

Code:

16:44:07 mnbudget prepare Test1 https://www.test.com 10 78600 y5uoxqr4Dwx9BsWRK636d5JrERCpPh49Kh 5 true 16:44:07 0000000000000000000000000000000000000000000000000000000000000000

Could we have a response from the system something like :
"Sorry, your proposal submission requires a fee of 1 DASH. Please make sure money is available from your wallet."

Ah, I'll explicitly check for that.

V12 Testing Thread

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Active member

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Core Developer

Active member

Well-known member

Member

Well-known member

Core Developer