v0.10.15.x Testing

Status
Not open for further replies.
Been trying for days to get 5000 to 8 rounds... up to 2510 now...

edit: bwahaha, one tortured core just dug a mighty 16.25 tDRK! :grin:
 
Last edited by a moderator:
eduffield said:
Can a couple people setup a stratum server and p2pool to make sure the patches work and you can indeed get blocks? I'd do it, but I'm busy hunting down the last collateral issues.


Stratum Users:
https://github.com/darkcoin/darkcoin-stratum/commit/4abf08bd0d3de7fae2311f54edb8a5f86f9ab39a

P2Pool Users:
https://github.com/darkcoin/p2pool-drk/commit/98a77c90d5dc460695cab71daed8d8aaab955289
Click to expand...

you give up trying to configure ec2-54-211-25-246.compute-1.amazonaws.com ?
I've got 2Mh trying to get work from that pool endpoint.
 
it seems like I'm still having a problem with the IsCompatibleWithSession check. When doing IsCollateralValid, most of the time txCollateral.vout.size is less than 1 so I get "not compatible with existing transactions!" a lot.
<edit>
it looks like in CreateCollateralTransaction, the fee is set to DARKSEND_COLLATERAL, when it looks like it should be DARKSEND_FEE, since SelectCoinsCollateral can select a tx that's only DARKSEND_COLLATERAL*1 + DARKSEND_FEE, which seems to be less than what ends up needing to be DARKSEND_COLLATERAL + DARKSEND_COLLATERAL in the test later on in createcollateraltransaction to make the vout. I'm just guessing though.
 
Last edited by a moderator:
eduffield said:
Can a couple people setup a stratum server and p2pool to make sure the patches work and you can indeed get blocks? I'd do it, but I'm busy hunting down the last collateral issues.


Stratum Users:
https://github.com/darkcoin/darkcoin-stratum/commit/4abf08bd0d3de7fae2311f54edb8a5f86f9ab39a

P2Pool Users:
https://github.com/darkcoin/p2pool-drk/commit/98a77c90d5dc460695cab71daed8d8aaab955289
Click to expand...

P2Pool - http://31.31.217.60:7903

I had to only change p2pool\bitcoin\p2p.py line 22 to
version=70042,
 
****** PLEASE UPDATE TO v10.15.10 *******

Fixed a couple more collateral charge issues, plus an issue causing "incompatible denominations" when it should have worked. Mixing should be faster now.

Let me know if you get any collateral charges after this. We should be solid now.

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

CI-builds for v0.10.15.10

Windows 32bit:
http://bamboo.darkcoin.qa/artifact/DRKW-DEV/JOB1/build-15/gitian-win-darkcoin-bin/32/darkcoin-qt.exe
http://bamboo.darkcoin.qa/artifact/...tian-win-darkcoin-bin/32/daemon/darkcoind.exe
http://bamboo.darkcoin.qa/artifact/...in-bin/32/darkcoin-0.10.15.10-win32-setup.exe

Mac OS X:
http://bamboo.darkcoin.qa/browse/DR...osx-darkcoin-dist/darkcoin-0.10.15.10-osx.dmg

Linux 32bit:
http://bamboo.darkcoin.qa/artifact/.../gitian-linux-darkcoin-bin/bin/32/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-12/gitian-linux-darkcoin-bin/bin/32/darkcoind

Linux 64bit:
http://bamboo.darkcoin.qa/artifact/.../gitian-linux-darkcoin-bin/bin/64/darkcoin-qt
http://bamboo.darkcoin.qa/artifact/DRKL-DEV/JOB1/build-12/gitian-linux-darkcoin-bin/bin/64/darkcoind
 
pinestabe said:
it seems like I'm still having a problem with the IsCompatibleWithSession check. When doing IsCollateralValid, most of the time txCollateral.vout.size is less than 1 so I get "not compatible with existing transactions!" a lot.
<edit>
it looks like in CreateCollateralTransaction, the fee is set to DARKSEND_COLLATERAL, when it looks like it should be DARKSEND_FEE, since SelectCoinsCollateral can select a tx that's only DARKSEND_COLLATERAL*1 + DARKSEND_FEE, which seems to be less than what ends up needing to be DARKSEND_COLLATERAL + DARKSEND_COLLATERAL in the test later on in createcollateraltransaction to make the vout. I'm just guessing though.
Click to expand...

Interesting to have others looking at the code :smile:

Here's the gist of how those inputs work. They're made as (DARKSEND_COLLATERAL*5)+DARKSEND_FEE. Afterwards, say you get charged a collateral fee (which is DARKSEND_COLLATERAL not DARKSEND_FEE, one is way more expensive than the other on purpose), it'll be (DARKSEND_COLLATERAL*4)+DARKSEND_FEE. You could get charged a collateral fee upwards of five times, each time vout will get paid back the rest of that input. The very last time is (DARKSEND_COLLATERAL*0)+DARKSEND_FEE, i.e, that's not enough to pay a collateral anymore -- so it just turns into a regular darksend session fee.

I just changed this yesterday, maybe your client has the old style of fees? I would try to update and move funds to a brand new wallet.
 
qwizzie said:
can someone pls sent me some tdrk .. 5000 if possible.. thanks
n3yqWFEWaMQMkZA1XvqPpmjkafa5MJBAWs

https://drkipn.com/test/faucet/ doesnt seem to be working at the moment.
Click to expand...
The faucet has a huge delay. I requested for 1000 tdrk about 13 hours ago and just now they arrived in my wallet. I've talked with teamer, the owner of the faucet and he said it's updated, just not sure what the problem is.

Edit: I just tried this faucet: http://test.faucet.masternode.io/ and it works. Got 1000 tdrk from there just now
 
moli said:
The faucet has a huge delay. I requested for 1000 tdrk about 13 hours ago and just now they arrived in my wallet. I've talked with teamer, the owner of the faucet and he said it's updated, just not sure what the problem is.

Edit: I just tried this faucet: http://test.faucet.masternode.io/ and it works. Got 1000 tdrk from there just now
Click to expand...

okay.. will try that link .. thanks
 
Evan : i sent you an email with debug.log .. only 1 of my 5 wallets came across 0.1 fees.. the other 4 wallets seem to be running fine (need more time monitoring them)
 
I've confirmed these payments are completely equal based on the active time per masternode.

Payments Address
10 mkFnwmgWU5MEVybrphXF4oBpZZ5nTyZAEL
10 mpV2d8vgC7LQNNzXzS3E84TMdykQQvHvkX
10 mvxbSnZWL2jk3xxpPbLosXhSQ5jUKTUz14
10 mwBSmtHcH8jvUK6gr7F1w43HYttAGe9BFY
10 mwTXxpQW32AKtQUYhNKmTpgW3TmDDS8RBF
10 my9VPHXbbYiV84CXYfj1FzmNoMrmjv1duv
10 n4Ly2sMUYJ9sq7dmrESv9gftYb4udweubP
11 miq9MsJvrdypV1ovpGSYvShBpMX7A5FaqU
11 mkkc3ac6PFKax1AzK7SeqHJUMUhwnHT5sj
11 moTGqJBcDTtUpr2a7fSRYLUVNnMtcCME6Z
11 moufT7XNgdCjWnYyJUyuLZjK64zkfatfwM
11 mvK4V9LsPZvjgCaEPGq5d9b8xfKf3LiETt
11 mybEwGJB98ZHEJkNs5Xa2Pps4DxUNMT2Yf
11 myKtKKwAnQWXR78QndMu5sjGoovPbu4jkC
11 n3477ZfbKrovCAZ8WgBHHk1f9YwzWgjJ3o
11 n43UCKkMybVQ7bFBfyZ2wJciHTetheyuc1
12 mhDE2DkKDK1Q3TVv3Gdg3GKMzNH7bxzF7M
12 mpCjmn7rKUs6TcXeXxTKoBK1wtkC1Qsune
12 mtohxUb85JwGutcg7y3UoAXhEDKQYkPop9
12 my55Qww9sToastiaQPrs5cvwm2M8MbDEuf
13 mpYsqsaz4Dcq3PSXSAS6QAVB6rPMMEcGY6
2 n15eS391XV1KMooJSX6GcWAwMDP43ojXtL
3 mxb92XRQH95udALrjmU3EuToPqRs2Kfs7D
5 mtfFVhkB4dsn7xRNxzWjJGEEHPSeQhon8X
5 myZ9uTjQeEH1N3Mf4iAtw8pRV2DFUYHzeu
5 n31XM9Bucj1HHCiXzC5YtLKnqfKcwWgJ7n
8 mjhQ5PXZ6TftozhvMffmZczQU5cTAJbo35
8 mtBF5aK8sUP8NADWmnq7gC775TePFx42ro
8 mzyWRFPLH8q5F1B8isJ7E2uSJGhJSuDRKY
9 mg7j7YAhqUbLrN1btxZcnhW18ydCk7wACh
9 moQgMKbaQAZKCCwAqCZvHt6ijouXCNGpYy
9 mpMVevHGJCuBpqxFqbah1dgkSDnyi58nTb
9 mrtY9qopFHzyqcXju13xFSE2Py6gVUWL6S
9 msYvxx52hVZjwDrgi1AHgmNUpxrTg1ctxT
9 mvcEegL5wRP5kQ4A445zRhJjCjbZz9C2vF
Click to expand...
 
If i am seeing these in the debug.log and darksend is not progressing, what can i do?

2014-10-14 16:46:25 Darksend request incomplete: collateral not valid. Will retry...

I am using the wallet from 10.13.13 - is that a factor?
 
kryptofoo said:
If i am seeing these in the debug.log and darksend is not progressing, what can i do?

2014-10-14 16:46:25 Darksend request incomplete: collateral not valid. Will retry...

I am using the wallet from 10.13.13 - is that a factor?
Click to expand...

Send all of the money to a new wallet, and start over again. Also, you need 10.15.10
 
Weird after updating p2pool it's now stuck just like the other mainnet p2pool. I really wish I could figure otu what is causing p2pool to just crash like this and get stuck at this stage...

2014-10-14 17:04:02.668429 Testing bitcoind P2P connection to '127.0.0.1:19999'...
2014-10-14 17:04:07.668725 ...taking a while. Common reasons for this include all of bitcoind's connection slots being used...

This is my second server it's happened to and I know others have reported this as well. A fresh git clone doesn't help. So confused.
 
eduffield said:
Send all of the money to a new wallet, and start over again. Also, you need 10.15.10
Click to expand...
already running 10.15.10 - just created new wallet transferred funds darksend is working again. I guess new wallet is pretty much a prerequisite to using new darksend release.

Edit: thank you sir!
 
Last edited by a moderator:
Status
Not open for further replies.
Back
Top