v0.10.17 - Onyx v3

jiggytom

Member
Nov 14, 2014
104
22
68
That's not a collateral fee. Looks like you sent .1DRK (the exact collateral size), I must not be checking those correctly.
The same thing happened to me, I sent you an email about it. was hit with Large Payment split up fee 2x and collateral..not even using DS at all...
 

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
It's the punishment for gambling (the new automated anti gambling detection feature)!
I've NEVER gambled in my life! Never! Ever! Because its all rigged. Now with crypto's, basic statistics apply. I know basic statistics quite well. Made 250 DRK so far today. Figured out a system.

Rule nº1 - Dont be greedy.
Rule nº2 - keep working at it, so far 100% success ;)
 
  • Like
Reactions: moli

oblox

Well-known Member
Aug 6, 2014
1,032
537
183
I've NEVER gambled in my life! Never! Ever! Because its all rigged. Now with crypto's, basic statistics apply. I know basic statistics quite well. Made 250 DRK so far today. Figured out a system.

Rule nº1 - Dont be greedy.
Rule nº2 - keep working at it, so far 100% success ;)
Heh, I know basic statistics as well, didn't change the fact that I had a run of 8 odds betting evens...

Assuming you're betting straight 50/50, your expected value over long periods is 1 anyway--50% x 0 + 50% x 2 = 1.
 
Last edited by a moderator:
  • Like
Reactions: vertoe

UdjinM6

Official Dash Dev
Dash Core Team
Moderator
May 20, 2014
3,638
3,538
1,183
@ this ver i see that the wallet gets locked after sending funds, this bug has been fixed...excellent!
With the latest update I find that the wallet auto locks after you send coins, so when setting up Masternodes it involves one extra step now of having to unlock the wallet between each 1,000 DRK sent, I preferred it to stay unlocked for the time that I'd set when working or until the wallet was closed, are there any advantages in having it lock after every send coin transaction?
:confused:
 
  • Like
Reactions: Lukas_Jackson

UdjinM6

Official Dash Dev
Dash Core Team
Moderator
May 20, 2014
3,638
3,538
1,183
Yes and walletpassphrase <blah> 99 makes a full walletlock after 99 seconds.
yep
the logic there is smth like that
Code:
Locked ---> Unlocked for mixing ------------------/--[Timeout] ----
       \                        \                /                 \
        \------------------------\----> Unlocked -----[Sending]-----\---> Locked
 

yidakee

Well-known Member
Foundation Member
Apr 16, 2014
1,812
1,168
283
Heh, I know basic statistics as well, didn't change the fact that I had a run of 8 odds betting evens...

Assuming you're betting straight 50/50, your expected value over long periods is 1 anyway--50% x 0 + 50% x 2 = 1.
going off topic. /msg you on IRC
 

oblox

Well-known Member
Aug 6, 2014
1,032
537
183
The .21 version of darkcoind seems to break p2pool node.

Can someone check please ?
I am downgrading to .20 till it's solved.

the message in debug.log is
2014-12-06 17:33:12 partner 127.0.0.1:56198 using obsolete version 70043; disconnecting
2014-12-06 17:33:12 ProcessMessage(version, 107 bytes) FAILED
2014-12-06 17:33:12 disconnecting node 127.0.0.1:56198


Might be that p2pool code needs to be updated ?
Protocol bump:

https://darkcointalk.org/threads/onyx-v3-10-17.3141/page-3#post-32442
 

thefrog

Member
May 25, 2014
57
26
58
Thanks to moocowmoo for this one:

20:08 <@moocowmoo> p2pool/bitcoin/p2p.py:22
20:08 <@moocowmoo> thats it

Edit that line to read:
Code:
def connectionMade(self):
        self.send_version(
            version=70051,
            services=1,
Instead of:
Code:
def connectionMade(self):
        self.send_version(
            version=70049,
            services=1,

Thank you !!
 

djcrypto

Member
May 27, 2014
180
94
88
It says 10.17.23 in the OP but the link is only for 10.17.21? Which one am I aiming for?
 

deusstultus

New Member
Dec 5, 2014
29
33
13
It says 10.17.23 in the OP but the link is only for 10.17.21? Which one am I aiming for?
Use the binaries in OP if that 's your preferred method at 10.17.21 or build from source at 10.17.23. Effective differences aren't incredible in most case, protocol difference was effective 10.17.19, the following were cleanup.
 

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183

eduffield

Core Developer
Mar 9, 2014
1,084
5,319
183
10.17.23 Onyx V3 - All Users

Please update to 17.23 at your earliest convenience, everything is working and looks OK with this version.

10.17.22
- Allow new dsee broadcasts to overwrite existing addresses of masternodes
- Fixed broken unit tests
- Fixed P2Pool connectivity issues (minprotocol = 70043 now)

10.17.23
- Fixed a minor DSEEP vulnerability

Source: https://github.com/darkcoin/darkcoin
Windows .exe: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.17.23-win.zip
Mac OSX: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.17.23-osx.dmg
Linux: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.10.17.23-linux.tar.gz
 

moli

Grizzled Member
Aug 5, 2014
3,255
1,830
1,183
I've been trying to mix some DRK on Mainnet and just got this in the debug.log:
2014-12-09 18:20:01 Submitted to masternode, waiting in queue .
2014-12-09 18:20:13 accepted connection 104.156.230.164:39773
2014-12-09 18:20:13 partner 104.156.230.164:39773 using obsolete version 70038; disconnecting
2014-12-09 18:20:13 ProcessMessage(version, 108 bytes) FAILED
2014-12-09 18:20:13 disconnecting node 104.156.230.164:39773
Does it mean someone is still on protocol 70038 and trying to mix DS and this can cause a lot of holdups for everyone else? How many people are still on the older protocol versions and trying to mix DS, can we know?

EDIT: And if the older protocol versions cause the delay in mixing, can we make them to be kicked off the network when they try to do the mixing?

UPDATE: Evan's answer to this question in IRC:
[15:27:36] <evan82> no that's an inbound connection to an older version
 
Last edited by a moderator:
  • Like
Reactions: splawik21

splawik21

Grizzled Member
Dash Core Team
Moderator
Foundation Member
Dash Support Group
Apr 8, 2014
1,917
1,274
1,283
I've been trying to mix some DRK on Mainnet and just got this in the debug.log:
... And if the older protocol versions cause the delay in mixing, can we make them to be kicked off the network when they try to do the mixing?
Can they simply have their wallet syncing blocked untill they update to newest stable client?
 

Light

Well-known Member
Foundation Member
Jun 4, 2014
346
256
233
One of my masternodes suddenly dropped from drk.mn list and also does not show when I type "masternode list" from local wallet.

When i unlock wallet and then type "masternode debug" it says: 'inbound port is not open. Please open it and try it again. (19999 for testnet and 9999 for mainnet)

I checked darkcoin.conf file and it does have this command line about port thou:
  1. masternodeaddr=[my IP]:9999
Any idea what is going on? Help is appreciated.
 
  • Like
Reactions: splawik21

GilAlexander

Member
Jun 26, 2014
84
23
48
One of my masternodes suddenly dropped from drk.mn list and also does not show when I type "masternode list" from local wallet.

When i unlock wallet and then type "masternode debug" it says: 'inbound port is not open. Please open it and try it again. (19999 for testnet and 9999 for mainnet)

I checked darkcoin.conf file and it does have this command line about port thou:
  1. masternodeaddr=[my IP]:9999
Any idea what is going on? Help is appreciated.
Go "http://ping.eu/port-chk/", type your vps' ip and 9999, click 'go' and check your port status.
If it's closed - on your vps:
Restart demon, type "netstat -anltp | grep "LISTEN"" (without outer quotes). "0.0.0.0:9999 LISTEN /darkcoind" in 1-2 lines is normal. Make sure all is as it was before. Check again on ping.eu.
 
  • Like
Reactions: Light

Light

Well-known Member
Foundation Member
Jun 4, 2014
346
256
233
Go "http://ping.eu/port-chk/", type your vps' ip and 9999, click 'go' and check your port status.
If it's closed - on your vps:
Restart demon, type "netstat -anltp | grep "LISTEN"" (without outer quotes). "0.0.0.0:9999 LISTEN /darkcoind" in 1-2 lines is normal. Make sure all is as it was before. Check again on ping.eu.
Thanks. It says port is closed but I don't have access to remote wallet. Waiting for flare :)

EDIT: The issue resolved, thanks to flare.
 
Last edited by a moderator:

Populandum

Well-known Member
Foundation Member
Apr 9, 2014
103
76
178
I think I found a bug in the windows wallet <.< When receiving funds they move from "unconfirmed: " to "Total balance: " after only 1 confirmation. If you point at the transaction in recent transactions it says unconfirmed (1 of 6 confirmations) though.
 

vertoe

Three of Nine
Mar 28, 2014
2,573
1,652
1,283
Unimatrix Zero One
I think I found a bug in the windows wallet <.< When receiving funds they move from "unconfirmed: " to "Total balance: " after only 1 confirmation. If you point at the transaction in recent transactions it says unconfirmed (1 of 6 confirmations) though.
That's no real bug, rather a design issue.

1 "confirmation" already means the transaction is confirmed and thus it is listed in total balance.
6 confirmations used to be the minimum number of confirmations where you can be 110% certain that this transaction is unrevertable by the network.
 

Populandum

Well-known Member
Foundation Member
Apr 9, 2014
103
76
178
That's no real bug, rather a design issue.

1 "confirmation" already means the transaction is confirmed and thus it is listed in total balance.
6 confirmations used to be the minimum number of confirmations where you can be 110% certain that this transaction is unrevertable by the network.
While I agree it is not a real bug, it is a design issue as it can confuse some users. I should have written "issue" and not "bug" I guess :p
 
  • Like
Reactions: splawik21

poiuty

Active Member
Nov 26, 2014
408
226
113
p2pool fail
Code:
2014-12-26 23:27:42 Masternode payment to XkN1qML7m5V8w8PGsaAcCwW9E1QmfQfzY1
2014-12-26 23:27:42 CreateNewBlock(): total size 1417
2014-12-26 23:27:42 CheckBlock() : Couldn't find masternode payment(1|175000000) or payee(1|1Wh4bh) nHeight 192813.
2014-12-26 23:27:42 ERROR: CheckBlock() : Couldn't find masternode payment or payee
2014-12-26 23:27:42 dseep - Asking source node for missing entry CTxIn(COutPoint(a29ee59096367a843194c888c61c934379fcf7ddd8850db536561c2880b1a1fb, 1), scriptSig=)
2014-12-26 23:27:42 dseep - Asking source node for missing entry CTxIn(COutPoint(a055eef25e114f49a3bf2729e181a6a88904285b8cf8ab5b688bde62a8107f6e, 1), scriptSig=)
2014-12-26 23:27:45 Masternode payment to XkN1qML7m5V8w8PGsaAcCwW9E1QmfQfzY1
2014-12-26 23:27:45 CreateNewBlock(): total size 1417
2014-12-26 23:27:45 CheckBlock() : Couldn't find masternode payment(1|175000000) or payee(1|1Wh4bh) nHeight 192813.
2014-12-26 23:27:45 ERROR: CheckBlock() : Couldn't find masternode payment or payee
2014-12-26 23:27:46 dseep - Asking source node for missing entry CTxIn(COutPoint(cd2a09c27b2974d9954412b96c4fd18ce1641c97d8da97a4591ddcd11e073514, 0), scriptSig=)
2014-12-26 23:27:46 dseep - Asking source node for missing entry CTxIn(COutPoint(f51e02ffa8367bd64d03d63471c3ff183bb6778ce198ef5d09983e257d8c6715, 1), scriptSig=)
2014-12-26 23:27:46 dseep - Asking source node for missing entry CTxIn(COutPoint(4c183649bcf95fe3d6754dd270fe49fee78c44d63a81db910c6ea4c75b924093, 0), scriptSig=)
2014-12-26 23:27:47 dseep - Asking source node for missing entry CTxIn(COutPoint(ff9d28f1bef66c6d2d54bc7b3b33c4b5e75b0d7abc225508db7fd4a52bd9bccf, 1), scriptSig=)
2014-12-26 23:27:47 dseep - Asking source node for missing entry CTxIn(COutPoint(06a829372d6fc171899563bc3820447d0d214eafc92e35703b9114121ce8abc8, 0), scriptSig=)
2014-12-26 23:27:47 dseep - Asking source node for missing entry CTxIn(COutPoint(762e62a4148da57275d905845ccad4fcc0c2fa0b6954679f11ea36c1cad1b3a4, 1), scriptSig=)
2014-12-26 23:27:48 Masternode payment to XkN1qML7m5V8w8PGsaAcCwW9E1QmfQfzY1
2014-12-26 23:27:48 CreateNewBlock(): total size 1417
2014-12-26 23:27:48 CheckBlock() : Couldn't find masternode payment(1|175000000) or payee(1|1Wh4bh) nHeight 192813.
2014-12-26 23:27:48 ERROR: CheckBlock() : Couldn't find masternode payment or payee
2014-12-26 23:27:49 dseep - Asking source node for missing entry CTxIn(COutPoint(bfbec1b00dfcb825082105501d4d0d698c0f6c1498ab7656cd4eeeee9379d720, 0), scriptSig=)
2014-12-26 23:27:50 dseep - Asking source node for missing entry CTxIn(COutPoint(93a920edb15496cc43bc8e2b1b084cb8c3713e20cd3e593fa4b4d7e8dc224617, 0), scriptSig=)
2014-12-26 23:27:50 dseep - Asking source node for missing entry CTxIn(COutPoint(c3ce42a3daee1182189e8610d7a38eaae7480cc40e2864259546a4c5203fc8d4, 1), scriptSig=)
2014-12-26 23:27:51 Masternode payment to XkN1qML7m5V8w8PGsaAcCwW9E1QmfQfzY1
2014-12-26 23:27:51 CreateNewBlock(): total size 1417
2014-12-26 23:27:51 CheckBlock() : Couldn't find masternode payment(1|175000000) or payee(1|1Wh4bh) nHeight 192813.
2014-12-26 23:27:51 ERROR: CheckBlock() : Couldn't find masternode payment or payee