• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

v0.10.12.x RC4 Testing

Status
Not open for further replies.
I've noticed that since I started running my transaction spam script yesterday, my Amazon micro instance performance is getting worse and worse. Currently a simple darkcoind getbalance is taking 5 seconds to return anything. Maybe it's just an off-day, but if my instance is being throttled due to, well, actual use, it might be a problem for half the masternodes on main-net.
I don't experience such load (running t1.micro) although my wallet.dat is 17MB in size and growing, since i am requesting a new address from the pool for each block/transaction :-D
 
Hmmm, darkcoind is certainly hogging it up (not even running as a masternode right now):

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
1331 ubuntu 20 0 995356 367548 5236 S 99.9 36.2 46:28.15 darkcoind
 
I am wondering why I am the only node that p2pool doesn't consider active. which also cause the mixup in consensus when I am the current node.
mpuTzSLxMQcSzgdPgs4BHxfCvTSBvWZKF4
 
So automatic denomination is odd to me. I grepped through the debug.logs of my darksend nodes, and this is what i get

Node1

Code:
darksendtest@ip-10-65-166-48:~$ tail -f -n 200000  ~/.darkcoin/testnet3/debug.log | egrep 'DoAutomaticDenominating|height\='
2014-07-23 13:02:03 SetBestChain: new best=000000014a9325207ee67f03b990025c33c7d4ebc7d787246acb13977f28ba57  height=2450  log2_work=42.23481  tx=11299  date=2014-07-23 13:01:53 progress=1.000000
2014-07-23 13:02:03 DoAutomaticDenominating : Running darksend denominate for 526 coins
2014-07-23 13:02:17 SetBestChain: new best=000000008a0f18ae82b56ff1501fffe746eb5b6023ff8752fa15daa0db336b12  height=2451  log2_work=42.235136  tx=11300  date=2014-07-23 13:02:07 progress=1.000000
2014-07-23 13:06:19 SetBestChain: new best=000000022ff7f9efbaab66c5238e8543ffa5047ef13ade84a5ef7d36f6fc6308  height=2452  log2_work=42.235467  tx=11357  date=2014-07-23 13:06:02 progress=0.999999
2014-07-23 13:06:52 SetBestChain: new best=00000000d23657e9da41b77ac1a5150b785ea7c9f7561db6ce0657d9d8cfe1e1  height=2453  log2_work=42.235781  tx=11385  date=2014-07-23 13:06:34 progress=0.999999
2014-07-23 13:07:03 SetBestChain: new best=0000000308b59c022f95cefcda6e34fb647afb00e914b850fc3a94d8171dd349  height=2454  log2_work=42.236099  tx=11386  date=2014-07-23 13:06:52 progress=1.000000
2014-07-23 13:08:56 SetBestChain: new best=00000001455be3b75c6a5acb08b7a0d1212e0f636d6343a3e100cdd383a238f0  height=2455  log2_work=42.236419  tx=11442  date=2014-07-23 13:08:33 progress=0.999999
2014-07-23 13:10:49 SetBestChain: new best=00000001fcf14a8af7894b30a51ddc37e5c31cb885ac7a91a5d06dc914b7136c  height=2456  log2_work=42.236731  tx=11470  date=2014-07-23 13:10:38 progress=1.000000
2014-07-23 13:11:30 SetBestChain: new best=0000000236b9b03f82daf5a9cb4b9ed2fe5ea9a94b0403acd5afded0dd9e772b  height=2457  log2_work=42.237037  tx=11498  date=2014-07-23 13:11:20 progress=1.000000
2014-07-23 13:12:09 SetBestChain: new best=000000028b3806c3baced4aefa5270b5a2b38a02d91d66ba7818c0c389688297  height=2458  log2_work=42.237363  tx=11519  date=2014-07-23 13:12:01 progress=1.000000
2014-07-23 13:15:04 SetBestChain: new best=000000026e9b2e38c2b5134201353112bc66a860bddf20d69680633bc5d202ef  height=2459  log2_work=42.237683  tx=11556  date=2014-07-23 13:14:38 progress=0.999999
2014-07-23 13:24:06 SetBestChain: new best=0000000274c6afb1ce4446660b1f2581a5df161684db14a0dd784fc795403f08  height=2460  log2_work=42.237989  tx=11586  date=2014-07-23 13:23:40 progress=0.999999
2014-07-23 13:24:06 DoAutomaticDenominating : Running darksend denominate for 514 coins
2014-07-23 13:24:15 SetBestChain: new best=00000000f4cda60ae651f094190e367ac9cf827e7d3c5c6154887becebd3632c  height=2461  log2_work=42.238262  tx=11587  date=2014-07-23 13:24:07 progress=1.000000


Node2

Code:
darksendtest@ip-10-123-167-211:~$  tail -f -n 200000  ~/.darkcoin/testnet3/debug.log | egrep 'DoAutomaticDenominating|height\='
2014-07-23 13:02:03 SetBestChain: new best=000000014a9325207ee67f03b990025c33c7d4ebc7d787246acb13977f28ba57  height=2450  log2_work=42.23481  tx=11299  date=2014-07-23 13:01:53 progress=1.000000
2014-07-23 13:02:03 DoAutomaticDenominating : Running darksend denominate for 1931 coins
2014-07-23 13:02:17 SetBestChain: new best=000000008a0f18ae82b56ff1501fffe746eb5b6023ff8752fa15daa0db336b12  height=2451  log2_work=42.235136  tx=11300  date=2014-07-23 13:02:07 progress=1.000000
2014-07-23 13:06:20 SetBestChain: new best=000000022ff7f9efbaab66c5238e8543ffa5047ef13ade84a5ef7d36f6fc6308  height=2452  log2_work=42.235467  tx=11357  date=2014-07-23 13:06:02 progress=0.999999
2014-07-23 13:06:52 SetBestChain: new best=00000000d23657e9da41b77ac1a5150b785ea7c9f7561db6ce0657d9d8cfe1e1  height=2453  log2_work=42.235781  tx=11385  date=2014-07-23 13:06:34 progress=0.999999
2014-07-23 13:07:03 SetBestChain: new best=0000000308b59c022f95cefcda6e34fb647afb00e914b850fc3a94d8171dd349  height=2454  log2_work=42.236099  tx=11386  date=2014-07-23 13:06:52 progress=1.000000
2014-07-23 13:08:57 SetBestChain: new best=00000001455be3b75c6a5acb08b7a0d1212e0f636d6343a3e100cdd383a238f0  height=2455  log2_work=42.236419  tx=11442  date=2014-07-23 13:08:33 progress=0.999999
2014-07-23 13:10:49 SetBestChain: new best=00000001fcf14a8af7894b30a51ddc37e5c31cb885ac7a91a5d06dc914b7136c  height=2456  log2_work=42.236731  tx=11470  date=2014-07-23 13:10:38 progress=1.000000
2014-07-23 13:11:31 SetBestChain: new best=0000000236b9b03f82daf5a9cb4b9ed2fe5ea9a94b0403acd5afded0dd9e772b  height=2457  log2_work=42.237037  tx=11498  date=2014-07-23 13:11:20 progress=1.000000
2014-07-23 13:12:09 SetBestChain: new best=000000028b3806c3baced4aefa5270b5a2b38a02d91d66ba7818c0c389688297  height=2458  log2_work=42.237363  tx=11519  date=2014-07-23 13:12:01 progress=1.000000
2014-07-23 13:15:04 SetBestChain: new best=000000026e9b2e38c2b5134201353112bc66a860bddf20d69680633bc5d202ef  height=2459  log2_work=42.237683  tx=11556  date=2014-07-23 13:14:38 progress=0.999999
2014-07-23 13:24:06 SetBestChain: new best=0000000274c6afb1ce4446660b1f2581a5df161684db14a0dd784fc795403f08  height=2460  log2_work=42.237989  tx=11586  date=2014-07-23 13:23:40 progress=0.999999
2014-07-23 13:24:06 DoAutomaticDenominating : Running darksend denominate for 2020 coins
2014-07-23 13:24:15 SetBestChain: new best=00000000f4cda60ae651f094190e367ac9cf827e7d3c5c6154887becebd3632c  height=2461  log2_work=42.238262  tx=11587  date=2014-07-23 13:24:07 progress=1.000000

Node3

Code:
darksendtest@ip-10-156-144-57:~$  tail -f -n 200000  ~/.darkcoin/testnet3/debug.log | egrep 'DoAutomaticDenominating|height\='
2014-07-23 13:02:03 SetBestChain: new best=000000014a9325207ee67f03b990025c33c7d4ebc7d787246acb13977f28ba57  height=2450  log2_work=42.23481  tx=11299  date=2014-07-23 13:01:53 progress=1.000000
2014-07-23 13:02:03 DoAutomaticDenominating : Running darksend denominate for 503 coins
2014-07-23 13:02:17 SetBestChain: new best=000000008a0f18ae82b56ff1501fffe746eb5b6023ff8752fa15daa0db336b12  height=2451  log2_work=42.235136  tx=11300  date=2014-07-23 13:02:07 progress=1.000000
2014-07-23 13:06:19 SetBestChain: new best=000000022ff7f9efbaab66c5238e8543ffa5047ef13ade84a5ef7d36f6fc6308  height=2452  log2_work=42.235467  tx=11357  date=2014-07-23 13:06:02 progress=0.999999
2014-07-23 13:06:52 SetBestChain: new best=00000000d23657e9da41b77ac1a5150b785ea7c9f7561db6ce0657d9d8cfe1e1  height=2453  log2_work=42.235781  tx=11385  date=2014-07-23 13:06:34 progress=0.999999
2014-07-23 13:07:03 SetBestChain: new best=0000000308b59c022f95cefcda6e34fb647afb00e914b850fc3a94d8171dd349  height=2454  log2_work=42.236099  tx=11386  date=2014-07-23 13:06:52 progress=1.000000
2014-07-23 13:08:56 SetBestChain: new best=00000001455be3b75c6a5acb08b7a0d1212e0f636d6343a3e100cdd383a238f0  height=2455  log2_work=42.236419  tx=11442  date=2014-07-23 13:08:33 progress=0.999999
2014-07-23 13:10:53 SetBestChain: new best=00000001fcf14a8af7894b30a51ddc37e5c31cb885ac7a91a5d06dc914b7136c  height=2456  log2_work=42.236731  tx=11470  date=2014-07-23 13:10:38 progress=0.999999
2014-07-23 13:11:44 SetBestChain: new best=0000000236b9b03f82daf5a9cb4b9ed2fe5ea9a94b0403acd5afded0dd9e772b  height=2457  log2_work=42.237037  tx=11498  date=2014-07-23 13:11:20 progress=0.999999
2014-07-23 13:12:28 SetBestChain: new best=000000028b3806c3baced4aefa5270b5a2b38a02d91d66ba7818c0c389688297  height=2458  log2_work=42.237363  tx=11519  date=2014-07-23 13:12:01 progress=0.999999
2014-07-23 13:15:04 SetBestChain: new best=000000026e9b2e38c2b5134201353112bc66a860bddf20d69680633bc5d202ef  height=2459  log2_work=42.237683  tx=11556  date=2014-07-23 13:14:38 progress=0.999999
2014-07-23 13:24:06 SetBestChain: new best=0000000274c6afb1ce4446660b1f2581a5df161684db14a0dd784fc795403f08  height=2460  log2_work=42.237989  tx=11586  date=2014-07-23 13:23:40 progress=0.999999
2014-07-23 13:24:06 DoAutomaticDenominating : Running darksend denominate for 506 coins
2014-07-23 13:24:15 SetBestChain: new best=00000000f4cda60ae651f094190e367ac9cf827e7d3c5c6154887becebd3632c  height=2461  log2_work=42.238262  tx=11587  date=2014-07-23


Obviously all nodes are in sync regarding the denomination, and its taking place all 10 blocks - so far so good.
Problem there is: There is NO sign in the blockchain at the given time/blockheight that these coins have been denominated. Evan, what am i doing wrong :rolleyes:? Or is the wallet denominating internally? If so, why do i always get

Code:
darksendtest@ip-10-65-166-48:~/bin$ darkcoind darksend mpDr5WPHAwg22PRriCaGLQegpUv33GU3t9 10
error: {"code":-4,"message":"Insufficient funds"}

if there are 1000+ coins denominated?

I've been running denominations and getting errors that the transactions created are invalid. So the clients AutoDenominate is working, just some bug is breaking the transactions when they're merged. More info soon.
 
I've been running denominations and getting errors that the transactions created are invalid. So the clients AutoDenominate is working, just some bug is breaking the transactions when they're merged. More info soon.
is it possible that I am the current MN when there are invalid created transactions? I have a node that is not active with all the players, namely p2pool.
https://test.drk.mn/masternodes.html node:
mpuTzSLxMQcSzgdPgs4BHxfCvTSBvWZKF4

if I understand correctly, 2 or more nodes are doing the work, but if p2pool thinks I am invalid, and him and I are doing the work???

edit: somebody stop me if I start mumbling jibberish
 
I've been running denominations and getting errors that the transactions created are invalid. So the clients AutoDenominate is working, just some bug is breaking the transactions when they're merged. More info soon.

Anyone else seeing this message? That'll cause some issues :)

2014-07-23 18:19:25 CDarkSendPool::Sign - My entries are not correct! Refusing to sign. 0 entries 67 target.
 
Who wants to play "Darksend testnet Ping-Pong Noise game" ?

I tried setting um a hot local tMN, and after HOURS trying to figure out why ALL my ports are closed (including 19999), despite all port forwarding efforts and dozen calls to my ISP tech line.... seems my router is faulty and will be swapped within 72h. Makes no sense at all, but whatever...

So, in the meantime...

All I can do for now is create tx noise. For all the non technical testers, this is a great chance to pitch in with some "work". I created a separate thread so as not to clutter the big-boy talk. Please join, it should be quite some fun if you've got some imagination

https://darkcointalk.org/threads/rc4-testnet-ping-pong-noise-game.1863/
Please be sure to use darksend, or not... but do use it!
 
Last edited by a moderator:
is it possible that I am the current MN when there are invalid created transactions? I have a node that is not active with all the players, namely p2pool.
https://test.drk.mn/masternodes.html node:
mpuTzSLxMQcSzgdPgs4BHxfCvTSBvWZKF4

if I understand correctly, 2 or more nodes are doing the work, but if p2pool thinks I am invalid, and him and I are doing the work???

edit: somebody stop me if I start mumbling jibberish

I have found that my node sv02 select mpuTzSLxMQcSzgdPgs4BHxfCvTSBvWZKF4.

Updated : [07/24 03:13:31]

Code:
Type sv01 sv02 nomp
Checked 07/24 03:13:01 07/24 03:13:01 07/24 03:13:02
Current 211.99.224.173:19999:1 54.202.29.136:1 9999:1 211.99.224.173:19999:1  <--- inconsistency
blockcount 2575 2575 2575
version 91202 101203 91202
connections 14 21 11

mpuTzSLxMQcSzgdPgs4BHxfCvTSBvWZKF4 Amazon_OregonUnited States
us.png
_._.29.136-
off.gif
+
on.gif
-
off.gif
<--- inconsistency
 
Last edited by a moderator:
Anyone else seeing this message? That'll cause some issues :)

2014-07-23 18:19:25 CDarkSendPool::Sign - My entries are not correct! Refusing to sign. 0 entries 67 target.
the string: "My entries are not correct!" is NOT in my debug.log
 
As of RC3 the masternode selector was set to mod 10, i.e., it changed every 25 minutes. Because we were waiting on 3 individuals to come together to merge transactions, that often took longer than 2.5 minutes. As of RC4, we can set this to mod 1 again, so it will change every block.
tbh i didn't even notice that RC3 is running on mod 10 in mainnet :-D

So that means that each 10 blocks current node == payee, as the selection code is the same?
 
Last edited by a moderator:
Anyone else seeing this message? That'll cause some issues :)

2014-07-23 18:19:25 CDarkSendPool::Sign - My entries are not correct! Refusing to sign. 0 entries 67 target.
Here we go


Code:
2014-07-23 18:21:26 got RelayDarkSendFinalTransaction
2014-07-23 18:21:26 CDarkSendPool::SignFinalTransaction CTransaction(hash=c907128cbd1795cec6743461cccb112fb94743c3cb0d9ec2236f12fb3e981101, ver=1, vin.size=48, vout.size=105, nLockTime=0)
    CTxIn(COutPoint(005e559278d59fb7c002d2cd7a64b18ad12fa9a57cfe312fa06e62bf5d2ba8ff, 0), scriptSig=)
    CTxIn(COutPoint(e975b530e1301142fcc4baeb3bae718ebc9c3541a6d9ed784d7f9872277409fc, 22), scriptSig=)
    CTxIn(COutPoint(571f01fd04470f3df11e227d8035c7160e7876c84f039aef8a51c03bc715e74f, 107), scriptSig=)
    CTxIn(COutPoint(06b83be5ef77910e00f3d7660d1ad15509492b17674a2e85c4f535b04d5ba98f, 1), scriptSig=)
    CTxIn(COutPoint(240f65eec0ae1e7690a184f74197c961bd5f41b662b32b5d6236df1975e650a3, 3), scriptSig=)
    CTxIn(COutPoint(33bcc2c583e13a4994205729030f4f1bad5387b2061f9bd6a669ddd524b1c585, 1), scriptSig=)
    CTxIn(COutPoint(35b1a35c22ec520a4b7a5a0ec60193ced1b38269e55535fd6afb4f3abec4f619, 1), scriptSig=)
    CTxIn(COutPoint(394cc4cbf716ff27806811dc8fe897ac8852b036d43a25ca08a993789d0aa824, 3), scriptSig=)
    CTxIn(COutPoint(3c7d5a1b7eb4ba4b601655a5fdda86e05d81160d7fab642a724dabfed4ea190c, 0), scriptSig=)
    CTxIn(COutPoint(3e7602fbb024ca054d59254b8626d083a37ef23c180adef0432ba7c5511dc284, 0), scriptSig=)
    CTxIn(COutPoint(4013545ca161d31c414134350146dcad01aeb006f8dbcddba3f01da2d82e7e54, 3), scriptSig=)
    CTxIn(COutPoint(4219976eeb3004ae02e4ada8b2729de59289ee0365b9ba27dbb40214a08cb2e6, 0), scriptSig=)
    CTxIn(COutPoint(453a10a0280da378368a5198669f8ad246eca67a41118007da6f76c1dc2f708c, 1), scriptSig=)
    CTxIn(COutPoint(45e61d1724ae4200e562a5a0007c9de7581a40dea036db8976bb548d05227c59, 1), scriptSig=)
    CTxIn(COutPoint(4a392a3bc0c177106fc8525dc4ca03640cc07dd59b8a3f85f8344337ceca9e65, 0), scriptSig=)
    CTxIn(COutPoint(4d41ccfe8d3ecb3c6041d59f6b641ace6fc48f443f7e36dee7c9491ac36a85bc, 0), scriptSig=)
    CTxIn(COutPoint(4e6db341230302f9f2ac7a1d440ed7cfb23aeacde3f70b78a91fb1b10c26bd45, 1), scriptSig=)
    CTxIn(COutPoint(53da7ce7d2d586acb9603703e08c169c3cd3787b95c2db9f22c4edff06b90f6a, 0), scriptSig=)
    CTxIn(COutPoint(571f01fd04470f3df11e227d8035c7160e7876c84f039aef8a51c03bc715e74f, 22), scriptSig=)
    CTxIn(COutPoint(571f01fd04470f3df11e227d8035c7160e7876c84f039aef8a51c03bc715e74f, 23), scriptSig=)
    CTxIn(COutPoint(571f01fd04470f3df11e227d8035c7160e7876c84f039aef8a51c03bc715e74f, 24), scriptSig=)
[...] 

    CTxOut(nValue=0.00100000, scriptPubKey=OP_DUP OP_HASH160 15df6867acf7)
    CTxOut(nValue=0.00100000, scriptPubKey=OP_DUP OP_HASH160 15df6867acf7)
    CTxOut(nValue=0.00100000, scriptPubKey=OP_DUP OP_HASH160 15df6867acf7)
    CTxOut(nValue=831.83020003, scriptPubKey=OP_DUP OP_HASH160 15df6867acf7)

2014-07-23 18:21:26 CDarkSendPool::Sign - My entries are not correct! Refusing to sign. 0 entries 34 target.
2014-07-23 18:21:26 CDarkSendPool::UpdateState() == 3 | 4
2014-07-23 18:21:26 DarkSendStatusUpdate - state: 4 entriesCount: 3 accepted: -1 error:
2014-07-23 18:21:27 CDarkSendPool::UpdateState() == 4 | 4
2014-07-23 18:21:27 DarkSendStatusUpdate - state: 4 entriesCount: 3 accepted: -1 error:
2014-07-23 18:21:37 CDarkSendPool::UpdateState() == 2 | 6
 
Anyone else seeing this message? That'll cause some issues :)

2014-07-23 18:19:25 CDarkSendPool::Sign - My entries are not correct! Refusing to sign. 0 entries 67 target.
No such message in my 8x (tdrkmn01 to tdrkmn08) 0.10.12.3 nodes (only 1 is an active masternode tho).
Nothing in my tp2pool (0.9.12.2) but that's expected. :p
 
Some progress from a conversation between me and Kristov. I thought it might be useful to understand what's going on behind the scenes:

---------------------------------------------------

I've been doing some more work on this and I'm thinking the client is going to strive to keep X number of each denomination in powers of two in the wallet. After each transaction occurs, it will need to possibly create new ones to replace the ones that are missing. But if you have every power of 2 in denomination form, you can make any amount once.

Something like this:


Denomination-----Pubkey----p2-----p3
0.001---------------1------2-----3
0.002---------------4------5-----6
0.004---------------7------8-----9
0.008---------------10-----11----12
0.016---------------13-----14----15
0.032---------------16-----17----18
0.064---------------19-----20----21
0.128---------------22-----23----24
0.256---------------25-----26----27
0.512---------------28-----29----30
1.024---------------31-----32----33
2.048---------------34-----35----36
4.096---------------37-----38----39

So your client will make 3x of each kind, then construct payments from these:

Payment1 for 1.024+0.004+0.001 = 1.029DRK (32+7+1)

After that your wallet has (it will refill denominations by darksend'ing):

Denomination-------Pubkey------p2------p3
0.001---------------2----------3------40
0.002---------------4----------5------6
0.004---------------8----------9------41
0.008---------------10---------11-----12
0.016---------------13---------14-----15
0.032---------------16---------17-----18
0.064---------------19---------20-----21
0.128---------------22---------23-----24
0.256---------------25---------26-----27
0.512---------------28---------29-----30
1.024---------------31---------33-----42
2.048---------------34---------35-----36
4.096---------------37---------38-----39

Next payment for 4.096+4.096+0.256 = 8.448DRK (39+37+25)

After that your wallet has:

Denomination------Pubkey p2-----p3
0.001---------------2-----3-----40
0.002---------------4-----5-----6
0.004---------------8-----9-----41
0.008---------------10----11----12
0.016---------------13----14----15
0.032---------------16----17----18
0.064---------------19----20----21
0.128---------------22----23----24
0.256---------------26----27
0.512---------------28----29----30
1.024---------------31----33----42
2.048---------------34----35----36
4.096---------------39

Here's the full list of denominations with this strategy:

1----0.001
2----0.002
3----0.004
4----0.008
5----0.016
6----0.032
7----0.064
8----0.128
9----0.256
10----0.512
11----1.024
12----2.048
13----4.096
14----8.192
15----16.384
16----32.768
17----65.536
18----131.072
19----262.144
20----524.288
21----1048.576

Also, for the bloat that will come with this I think I can pull off
summary blocks. So every 10,000 blocks the masternodes would create a
summary block, it would be a giant block with every populated output
that still has funds more than dust. That should be pretty robust and
we don't have to worry about the blockchain size.
 
Status
Not open for further replies.
Back
Top