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

v0.10.17.x Testing

Status
Not open for further replies.
Anon Transaction:
...
Round 8:
Possible Funding Sources:
...
Round 7:
Possible Funding Sources:
...

Each time you see powers of two, you've found source money:

Round 6:
Possible Funding Sources:
[...]
It gets exponentially larger as you go backwards, I would keep going but that already took 30 minutes to do 3 rounds.

I think once the mixing format is final I'll write a little blockchain-crawler to do this job.

Will be interesting to see how much the probability to find the right sender goes up for reoccurring sender/receiver pairs. Most people only have a handful (or two) partners they ever make business with.

Currently, my pool is the only one mining darksend transactions. Until all of the miners update, it'll be slower (should be really fast on mainnet though).

http://ec2-54-197-169-85.compute-1.amazonaws.com/index.php?page=statistics&action=blocks

Need some hash?
 
Started with new windows wallet ver 18 with fresh 1k from faucet. No problems and darksend is progressing every 2 or 3 blocks. :smile:
 
Is it
mspyEVzLp4XbfngHYVa1DN92boUK1Zbhsh ?

or:
mp9HFLtvc19aE3LoU1wEDnZtZTKTE4Li1e ?

Yup, that one. Is darksend not working or did you use insider knowledge? LOL It will get much harder in main net when we have 3 people mixing at one time ;) Unless you're finding a flaw?

Also, when I got the not enough funds error, it was when I tried to choose which funds to use (I wanted to see if change worked) It would have required over 2 coins in change, so I'm guessing that the wallet won't let me lose so many coins, that I have to use a mix of coins that are closer to the total. Is that correct?
 
are there windows users in here having connection problems ?

my wallet shows :

cmd-reply


{
"version" : 101718,
"protocolversion" : 70051,
"walletversion" : 60001,
"balance" : 0.00000000,
"darksend_balance" : 0.00000000,
"blocks" : 74452,
"timeoffset" : 0,
"connections" : 0,
"proxy" : "",
"difficulty" : 2.19260894,
"testnet" : true,
"keypoololdest" : 1417725045,
"keypoolsize" : 1001,
"paytxfee" : 0.00100000,
"mininput" : 0.00001000,
"errors" : ""
}

debug.log shows :

2014-12-04 20:34:39 send version message: version 70051, blocks=74452, us=0.0.0.0:0, them=108.61.198.220:19999, peer=350
2014-12-04 20:34:39 socket closed
2014-12-04 20:34:39 disconnecting node 108.61.198.220:19999
2014-12-04 20:34:39 trying connection 107.191.48.59:19999 lastseen=5.6days
2014-12-04 20:34:39 connected 107.191.48.59:19999
2014-12-04 20:34:39 send version message: version 70051, blocks=74452, us=0.0.0.0:0, them=107.191.48.59:19999, peer=351
2014-12-04 20:34:39 socket recv error 10054
2014-12-04 20:34:39 disconnecting node 107.191.48.59:19999
2014-12-04 20:34:40 trying connection 211.99.224.174:19999 lastseen=3.1days
2014-12-04 20:34:40 connected 211.99.224.174:19999
2014-12-04 20:34:40 send version message: version 70051, blocks=74452, us=0.0.0.0:0, them=211.99.224.174:19999, peer=352
2014-12-04 20:34:40 socket recv error 10054
2014-12-04 20:34:40 disconnecting node 211.99.224.174:19999
2014-12-04 20:34:41 trying connection 211.99.224.174:19999 lastseen=3.1days
2014-12-04 20:34:41 connected 211.99.224.174:19999
2014-12-04 20:34:41 send version message: version 70051, blocks=74452, us=0.0.0.0:0, them=211.99.224.174:19999, peer=353
2014-12-04 20:34:41 socket recv error 10054
2014-12-04 20:34:41 disconnecting node 211.99.224.174:19999
2014-12-04 20:34:42 trying connection 104.131.45.75:19999 lastseen=5.8days
2014-12-04 20:34:42 connected 104.131.45.75:19999
2014-12-04 20:34:42 send version message: version 70051, blocks=74452, us=0.0.0.0:0, them=104.131.45.75:19999, peer=354
2014-12-04 20:34:42 socket closed
2014-12-04 20:34:42 disconnecting node 104.131.45.75:19999
2014-12-04 20:34:42 trying connection 80.240.135.83:19999 lastseen=6.9days
2014-12-04 20:34:42 connected 80.240.135.83:19999
2014-12-04 20:34:42 send version message: version 70051, blocks=74452, us=0.0.0.0:0, them=80.240.135.83:19999, peer=355
2014-12-04 20:34:42 socket recv error 10054
2014-12-04 20:34:42 disconnecting node 80.240.135.83:19999
2014-12-04 20:34:43 trying connection 80.240.135.83:19999 lastseen=6.9days
2014-12-04 20:34:43 connected 80.240.135.83:19999
2014-12-04 20:34:43 send version message: version 70051, blocks=74452, us=0.0.0.0:0, them=80.240.135.83:19999, peer=356
2014-12-04 20:34:43 socket recv error 10054
2014-12-04 20:34:43 disconnecting node 80.240.135.83:19999



i have 1 connection now but it keeps spamming ''socket recv error 10054''

Edit : finally getting some more stable connections (3-4), its still weird, normally i'm getting 8 connections very very fast but since latest update it seems to take a very long time to get to 8 connections.
 
Last edited by a moderator:
are there windows users in here having connection problems ?

...

i have 1 connection now but it keeps spamming ''socket recv error 10054''

Edit : finally getting some more stable connections (3-4), its still weird, normally i'm getting 8 connections very very fast but since latest update it seems to take a very long time to get to 8 connections.
I'm getting 8 connections straight away
 
My wallet is at 100% with the majority of 100 denominations in round 5. No further darksend denominations for over an hour.

EDIT: Started back up again.
 
Last edited by a moderator:
are there windows users in here having connection problems ?
[...]
Edit : finally getting some more stable connections (3-4), its still weird, normally i'm getting 8 connections very very fast but since latest update it seems to take a very long time to get to 8 connections.

I sometimes have that (also with the older wallets) after deleting peers.dat.

A workaround that worked for me so far is closing the wallet (so that a new peers.dat gets written) and starting it again.

For reasons only the Gods of program-initialization know starting with an existing peers.dat establishes the connections faster.
 
I sometimes have that (also with the older wallets) after deleting peers.dat.

A workaround that worked for me so far is closing the wallet (so that a new peers.dat gets written) and starting it again.

For reasons only the Gods of program-initialization know starting with an existing peers.dat establishes the connections faster.

yeah, i noticed that too after awhile and i made sure the peers.dat that i deleted earlier got newly written .. only this time it just takes such long time to reach
8 connections. But right now i have two 7's and the rest are 6 connections so i'm getting there.... slowly :)
 
Last edited by a moderator:
i have a very difficult time getting connected with my windows wallets, anyone else experiencing this ? Can someone provide me with
some addnodes ? ( i deleted the peer.dat already several times .. all my wallets just seems to have problems getting to even 1 connection)

edit : my wallets seem to stop syncing after 74426, i will delete blockchains and try again
edit : same problem, difficulty connecting
edit : okay starting to get connected with some wallets to a few connections now
addnode test.dnsseed.masternode.io
 
addnode test.dnsseed.masternode.io

thanks, added in my darkcoin.conf

Mixing went well last night, 1 wallet done (Darksend Balance 922 with amount 990 / 8 rounds set, more then fair) and the other 5 only have 1 round to go. With my 6 running wallets got only hit with 3 collateral fees so far so that looks good too.

1 suggestion : once the wallet has reached its targetted rounds and is finished maybe it could show something different then status msg ''Darksend is idle'',
maybe it could show ''Darksend mixing finished'' ?
 
Last edited by a moderator:
Has anyone been able to send transactions on Testnet? I haven't been able to send my coins or do any anonymization on Testnet, the transactions do not move for some reason. They can be unstuck by using -zapwallettxes but then they get stuck again and again...
 
Has anyone been able to send transactions on Testnet? I haven't been able to send my coins or do any anonymization on Testnet, the transactions do not move for some reason. They can be unstuck by using -zapwallettxes but then they get stuck again and again...
Just tested, its dead.
 
My wallet sees 29 Masternodes and there're a few miners on Testnet that I know of but for some reason I can't even send the tdrk back to the faucet.

I can see 29 MNs.
I can send tDRKs to faucet but transactions stays unconfirmed.
Maybe protocol problem...

Edit: i talk for v17.21
 
hehe... 10.17.23 also has a bug. Not mixing at all. Just sending out 0.5 DRK (adding tx fee) results in this.

DTv0HiO.png


And while we're at it, a slight GUI cosmetic quirk in OSX.

sCX1iZl.png


Would someone explain Jira to me? I find it a bit confusing...

I tried creating a bug report, it said it was successful, but I dont see it. I posted it in 17.xx
 
Last edited by a moderator:
Status
Not open for further replies.
Back
Top