v0.10.12.x RC4 Testing

qwizzie · Aug 8, 2014

flare said:
No, not yet - it's 8am here and i got some sleep

Will compile the latest iteration as soon as i get the latest source.

thanks mate..

stonehedge · Aug 8, 2014

Thank you everybody for putting in the effort.

Stealth923 · Aug 8, 2014

When theres "darkSend Status => ERROR : not compatible with existing transactions" in the debug.log file....does this mean it cannot find any compatible mixing partners in the masternode and you will need to wait until someone can mix with you?

moli · Aug 8, 2014

Stealth923 said:
When theres "darkSend Status => ERROR : not compatible with existing transactions" in the debug.log file....does this mean it cannot find any compatible mixing partners in the masternode and you will need to wait until someone can mix with you?

Last night Evan explained this: ""not compatible" means the automated process got rejected by a masternode. It's not a problem, it will just keep trying"
https://darkcointalk.org/threads/rc4-testing.1830/page-65

moli · Aug 8, 2014

Windows wallet v.17 does not denominate for me. I've tried two fresh wallets but it still would not denominate. And sometimes it sends coins using non-anonymous, sometimes it would not, saying "there's not enough fund in the balance" when there is enough.

ozziecoin · Aug 8, 2014

Flare has not updated Win v.17 to fix locking issue.

flare · Aug 8, 2014

eduffield said:
****** Please Update To 10.12.17 or 9.12.17 *******

Fixed coin locking issues

Stable Binaries
http://www.darkcoin.io/downloads/master-rc4/darkcoin-qt
http://www.darkcoin.io/downloads/master-rc4/darkcoind

RC4 Binaries ( masternodes / auto-denom )
http://www.darkcoin.io/downloads/rc4/darkcoin-qt
http://www.darkcoin.io/downloads/rc4/darkcoind

yidakee · Aug 8, 2014

moli said:
Windows wallet v.17 does not denominate for me. I've tried two fresh wallets but it still would not denominate. And sometimes it sends coins using non-anonymous, sometimes it would not, saying "there's not enough fund in the balance" when there is enough.
View attachment 322

I do se demonimation there. Last tx is "payment to self" ... right click on it and select "show transaction details"

daaarkcoins · Aug 8, 2014

yidakee said:
Bug alert!
Updated, and the QT opens with the wallet un

Come again?

yidakee · Aug 8, 2014

daaarkcoins said:
Come again?

False alarm. I had type that yesterday but found it was my mistake so didnt post, but the forum engine / safari remembers even if I close the window. When I quoted moli it picked up what I had written yesterday.

Ignore that, sorry for the mess

JGCMiner · Aug 8, 2014

illodin said:
Would it be possible to explain the >5,000 coin problem, maybe someone with a fresh vision could get a crazy idea on how to solve it?

More technical details on this issue would be nice. :smile:

AlexZZZ · Aug 8, 2014

Hi! I today finished denomination process in win 32-bit qt v0.10.12.16
http://imgur.com/wM8jGMF
http://imgur.com/pcXosbn
http://imgur.com/BfiCc4o

elbereth · Aug 8, 2014

Sorry for the delay (had irl problems).
tdrkmn01-08 updated to 0.10.12.17.
tp2pool compiled from master-rc4 to 0.9.12.17.
Portchecker updated to protocol version 70029 and version 0.9.12.17.

flare · Aug 8, 2014

JGCMiner said:
illodin said:

Would it be possible to explain the >5,000 coin problem, maybe someone with a fresh vision could get a crazy idea on how to solve it?

Click to expand...

More technical details on this issue would be nice. :smile:

The technical background of the 5000 DRK limitation is, that with current denomination scheme (0.1 ; 1 ; 10 ; 100 ; 500) the tx scripts for sending amounts > 5000 DRK get to large (20k+) and will not be relayed/mined by miners.

Possible solutions are to

a) extend the scheme by additional denomination units (e.g. 1000 & 5000)
b) switch to different scheme:
- either binary scheme as proposed by Kristov Atlas ( 1 + 2 + 4 + 8 + 16 + 32 + 64 + 128 + ...)
- or a optimized scheme as proposed by babygiraffe in https://darkcointalk.org/threads/development-updates-july-7th.1735/#post-11434

darkwing · Aug 8, 2014

Could the wallet not denominate balances above 5000 into sets of 5000?

JGCMiner · Aug 8, 2014

flare said:
The technical background of the 5000 DRK limitation is, that with current denomination scheme (0.1 ; 1 ; 10 ; 100 ; 500) the tx scripts for sending amounts > 5000 DRK get to large (20k+) and will not be relayed/mined by miners.

Possible solutions are to

a) extend the scheme by additional denomination units (e.g. 1000 & 5000)
b) switch to different scheme:
- either binary scheme as proposed by Kristov Atlas ( 1 + 2 + 4 + 8 + 16 + 32 + 64 + 128 + ...)
- or a optimized scheme as proposed by babygiraffe in https://darkcointalk.org/threads/development-updates-july-7th.1735/#post-11434

It might be worth considering one of those solutions.

While this will not effect 90%+ of the users, it will effect early adopters who likely have the most coin. Furthermore, these same people are going to be DRK's most ardent supporters, the same people who will most likely to set up services for DRK, and so on.

If adding a 1000 or 5000 level for cases where you have more than 5000DRK will make the whole system provably less anonymous then I understand the hesitation, but if it would just delay RC4 (because more testing would be needed) then I say the code should be modified.

superplus · Aug 8, 2014

darkwing said:
Could the wallet not denominate balances above 5000 into sets of 5000?

also thought of that, would be nice to have no limit

daaarkcoins · Aug 8, 2014

flare said:
The technical background of the 5000 DRK limitation is, that with current denomination scheme (0.1 ; 1 ; 10 ; 100 ; 500) the tx scripts for sending amounts > 5000 DRK get to large (20k+) and will not be relayed/mined by miners.

What's the big deal? The client can just split transactions > 5000 DRK into multiple transactions < 5000 DRK. Wouldn't even require any further interaction with the user.

flare · Aug 8, 2014

daaarkcoins said:
What's the big deal? The client can just split transactions > 5000 DRK into multiple transactions < 5000 DRK. Wouldn't even require any further interaction with the user.

Yep, that's another possible solution. Has to be implemented though

daaarkcoins · Aug 8, 2014

flare said:
Has to be implemented though

done :grin: can't we just lift the 20kB tx size limit? It doesn't seem to matter if too large transactions are split up into smaller transactions or just raise the size limit.

Code:

while(amountToSend > 0){
  txAmount = 0;

  while((txSize < MAX_SIZE) && (txAmount < amountToSend)){
    addInput();
  }

  sendTx();
  amountToSend -= txAmount;
}

Imho the size limit could also be replaced with a "size per amount limit" or a "size per coin days destroyed limit"

v0.10.12.x RC4 Testing

Well-known member

Well-known member

Well-known member

Well-known member

Well-known member

Member

Well-known member

Well-known member

Member

Well-known member

Active member

New member

Well-known member

Well-known member

Active member

Active member

New member

Member

Well-known member

Member