Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 6159. (Read 9724097 times)

Hi

did someone successfully build and run the wallet on a i686 (=32 bit) linux ?

i build successfully, but then after start, the sync stops at block "blocks" : 45993,

2014-04-29 20:04:48 received block 00000000000b304562f734cdc04f201f9e0497188a26362f76b4642606ebbc70
2014-04-29 20:04:48 ERROR: AcceptBlock() : incorrect proof of work
2014-04-29 20:04:48 ERROR: ProcessBlock() : AcceptBlock FAILED

I have used the latest git source.

Please help, I would like to set up a p2pool node for DRK.
And no, I can not switch to x86_64, as I have other p2pools up and running at the moment on the same node.

DRK is the only one that does not work (at the moment).

thanks

cheers

:~/.darkcoin>  getconf LONG_BIT
32

darkcoind stop
cd ~/.darkcoin
wget http://drk.poolhash.org/files_for_darkoin_block/blocks.tgz
tar xfvz blocks.tgz
rm -rf blocks chainstate
mv home/user/.darkcoin/* .
darkcoind
darkcoind getinfo


{
    "version" : 90102,
    "protocolversion" : 70002,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 60001,
    "timeoffset" : 0,
    "connections" : 3,
    "proxy" : "",
    "difficulty" : 955.31190257,
    "testnet" : false,
    "keypoololdest" : 1398805858,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "errors" : ""
}

2014-04-29 21:27:42 received block 00000000000cfe64fca7b5c3a8ad1ee39dd3f380aeb56027bc25e97904d2c99e
2014-04-29 21:27:42 Committing 9 changed transactions to coin database...
2014-04-29 21:27:42 SetBestChain: new best=00000000000cfe64fca7b5c3a8ad1ee39dd3f380aeb56027bc25e97904d2c99e  height=60001  log2_work=55.944516  tx=245698  date=2014-04-29 21:27:20 progress=0.999999
2014-04-29 21:27:42 ProcessBlock: ACCEPTED

I'm not sure I understand.

John darksends 2 coins from A to C, gets 8 back as change on address X.
He then contributes 2 additional coins from another address in his wallet, address D?

If that's how it works I'm not sure I get how this helps.  It just exposes the holder of address D as the person who darksent 2 coins to C.

I am probably misunderstanding where X1 S1 and W1 are coming from.

John darksends 2 coins from A to C, gets 8 back as change on address X
Joe darksends 3 coins from E to G, gets 7 back as change on address W
Suzie darksends 3 coins from K to Q, gets 7 back as change on address S

Now, we make a pool with X+X1+W+W1+S+S1.

Pool total output == 30DRK

X+X1 = 10DRK
W+W1 = 10DRK
S+S1 = 10DRK

X will always be less than 10DRK, there for we need another input to bring it to 10DRK total. This way no one can tell who is receiving which inputs, thus cleaning them in the inverse way DarkSend works.

Make sense?

X will always be less than 10DRK, therefore we need another input to bring it to 10DRK total. This way no one can tell who is receiving which inputs, thus cleaning them in the inverse way DarkSend works. Checkout my post above again, I modified it a bit.

Make sense?

My mind just exploded. What are X1, S1, and W1?

X will always be less than 10DRK, therefore we need another input to bring it to 10DRK total. This way no one can tell who is receiving which inputs, thus cleaning them in the inverse way DarkSend works. Checkout my post above again, I modified it a bit.

Make sense?

My mind just exploded. What are X1, S1, and W1?

John darksends 2 coins from A to C, gets 8 back as change on address X
a few days later..
John darksends 8 coins from B to D, gets 2 back as change on address Y

Joe darksends 3 coins from E to G, gets 7 back as change on address W
a few days later..
Joe darksends 1 coins from F to H, gets 9 back as change on address Z

Suzie darksends 3 coins from K to Q, gets 7 back as change on address S
a few days later..
Suzie darksends 1 coins from J to R, gets 9 back as change on address T

Now, we make a pool with X+Y+X1+W+Z+W1+S+T+S1.

Pool total output == 60DRK

X+Y+X1 = 10DRK + 10DRK
W+Z+W1 = 10DRK + 10DRK
S+T+S1 = 10DRK + 10DRK

Make sense?

On second thought, I'm not sure this solves the problem.  My understanding is that you want to accumulate the dirty change in the wallet until it breaches a certain amount (say 10 for example), then it is washed in a "change only" wash with a bunch of "10" transactions.  The problem I see is that even the clean coins could be linked to the original transaction.  Just to explain:

John darksends 2 coins from A to C, gets 8 back as change on address X
a few days later..
John darksends 8 coins from B to D, gets 2 back as change on address Y

Y+X are submitted to the change mixing pool (10 coins), and come out "clean" at address Z.

The problem is that the coins at address Z are not clean really, they are "suspect", they could have possibly participated in any darksends that generated the dirty coins that composed the "change washing" pool.

Now when Johns wants to spend coins from A, B, and Z in the same transaction.

So if John wants to send coins from A+B+Z in one transaction, the fact that Z participated in a pool that contained X and Y is enough to expose A and B as the original participants in the darksend transaction.

Really it leaves us at the same position that we were at previously after the original darksends.

I hope that made sense.

Wow! This is great. About 400+ pages ago I talked about having a different kind of pool for change outputs only. Put in all of your change outputs and you'll get new fresh clean inputs of 10DRK. The client could automatically do this after each darksend, which would also get you new inputs for the next round.

I'm currently embedded in patching stratum and p2pool to support the masternode payments, which is why I haven't been around. It takes a lot of work to make something so different from anything else out there, dare I say, revolutionary?

May be it's full now but it doesn't matter because it did sync up until 46226 (using connect=www.drkpool.com, starting from block 0), the block which most people got stuck with.


This doesn't seem like a coincidence to me!

Thank you for the update Evan.

I'm currently embedded in patching stratum and p2pool to support the masternode payments, which is why I haven't been around. It takes a lot of work to make something so different from anything else out there, dare I say, revolutionary?

Wow! This is great. About 400+ pages ago I talked about having a different kind of pool for change outputs only. Put in all of your change outputs and you'll get new fresh clean inputs of 10DRK. The client could automatically do this after each darksend, which would also get you new inputs for the next round.

I'm currently embedded in patching stratum and p2pool to support the masternode payments, which is why I haven't been around. It takes a lot of work to make something so different from anything else out there, dare I say, revolutionary?

I would like to ask the devs to make it compulsory to include the blockchain as part of the supernodes, and have it as 'read by anyone'.
I think that once we have the supernodes up and running with a readable blockchain that is accessible by anyone, different services might evolve independent of the darkcoin devs on top of this, such as the thin wallet described by TS.

My only concern about having a change-address-only pool is that it will shed a little light on the original darksend mixes (ie now you know which coins were change and which coins were not change when you look at the mixing step).  

This is bullshit. You did NOT send out double payout for blocks. Double payment simply happened because you've had DB issue AGAIN!
You're saying people have had issues with your service, and your reward by RANDOMLY awarding double payout for random blocks?!

Hell yeah, let me go point my miner at you  right now!   Random compensation for random block, for lucky winners? That is not compensation, that is a lottery. What about those who gain without loses, or theses who double loos by sheer bad "random compensation luck"?

Your backend is crap and you've been screwing with everyone's mining. This time, it double payed out. It was not intentional, or you'd have made a nice email or forum "spam" about it.

Nor did I receive an email from a admin expressing whatever feeling that they should double payout as compensation for downtime, locked payouts, stratum failure and constant DDoD's, all of which you've previously promised to have fixed and never happen again.

 I've lost more mining to you guys than to scrypt-algo mining instability with 280x's peaking 85ºC and CGwatcher rebooting.
 BE HONEST; DONT BULLSHIT, and people will understand that the world is not perfect and shit happens.

 I don't like being bullshitted. You completely screwed me over twice, on a coin launch and with DRK.

 I like your fronted GUI, mais je n'aime pas votre fausses promesses