v0.10.9.x Help test RC2 forking issues

Status
Not open for further replies.
eduffield said:
Yeah, you're right. This is starting to feel rushed. I'm going to move RC3 to the 27th to ensure everything works properly.
Click to expand...
Cool, but IMO no need for a specific date, end of June, beginning of July is good. Thanks to flare the code will be stronger :) !
 
flare said:
Tough decision but the only right one here. Much appreciated. Better to have the rollout postponed than to have trouble with bugs in production, especially when you think of DRK being a 50mn$+ project at the moment.

I am happy to continue my effort to support you with hunting the bugs out of RC3.
Click to expand...
Thank you so much flare! I wish I knew how to do those kind of things, and that's just what we need!
 
TanteStefana said:
Thank you so much flare! I wish I knew how to do those kind of things, and that's just what we need!
Click to expand...

You are welcome.

I've got some things in the pipeline which i'd like to contribute to Darkcoin project with the aim to improve code quality, bug handling, release management and processes, as long as Evan & Team wants my contribution in this field.

Bitcoin (which is the grandfather of darkcoin) is still far ahead regarding these topics - no wonder since Darkcoin project is much younger and the community & team is still in the process of forming.

But Darkcoin is by far not finished yet. As i laid out some posts ago: The proof of service concept is brillant, and the implementation through masternodes/votes is very good and very versatile. There are much more services a Darkcoin network can provide: TOR nodes, Alternative Distributed DNS, Anonymizer, Email Mixer. I don't know what Evans plans for v2.0, 3.0, 4.0 are, but the future of dark is bright.

So if we come to a more mature testing process - i am talking about documentation of specifications, testplans, testcases - i am quite sure you can be part of a team, who is testing a new release before rollout. I will come back to you if you like.

Cheers,
Holger
 
I'm still getting this when I try to get a remote wallet going:
2014-06-08 18:32:09 dsee - Got NEW masternode entry my_home_ip_address:19999
2014-06-08 18:32:09 dsee - Accepted masternode entry -1 -1

And of course it shows up on the list with my home IP address.
I did exactly as instructed on page 17 of this thread, so I'm wondering:
1. Was I supposed to start the remote masternode in a certain way? I just did ./darkcoind then ./darkcoind masternode debug per instructions?

2. Am I supposed to start the local version like we used to? ./darkcoind -masternodeaddr=xxx.xxx.xxx.xxx.:9999

OK, I did the above and finally got:
Code: 
2014-06-08 19:05:40 trying connection 54.193.192.121:19999 lastseen=2.8hrs
2014-06-08 19:05:43 received block 000000000f5c709079d3339805ffbf5100bcf519f6c7bf7f973678366d629cd5
2014-06-08 19:05:43 Committing 1090 changed transactions to coin database...
2014-06-08 19:05:43 SetBestChain: new best=000000000f5c709079d3339805ffbf5100bcf519f6c7bf7f973678366d629cd5  height=16222  log2_work=44.41436  tx=28750  date=2014-06-08 19:05:16 progress=1.000000
2014-06-08 19:05:43 CDarkSendPool::NewBlock - Is Masternode, resetting
2014-06-08 19:05:43 ProcessBlock: ACCEPTED
Success!
Thanks :) I'll update my guide now :)

Hey flare, I'm all for helping, I might need instruction on what to do, but if you need someone just to run things, I'm always here (er... within 10-24 hours usually, LOL) As I'm sure a lot of us are. This is the most exciting project by far on crypto currency, IMO :grin:
 
Last edited by a moderator:
flare said:
You are welcome.

I've got some things in the pipeline which i'd like to contribute to Darkcoin project with the aim to improve code quality, bug handling, release management and processes, as long as Evan & Team wants my contribution in this field.

Bitcoin (which is the grandfather of darkcoin) is still far ahead regarding these topics - no wonder since Darkcoin project is much younger and the community & team is still in the process of forming.

But Darkcoin is by far not finished yet. As i laid out some posts ago: The proof of service concept is brillant, and the implementation through masternodes/votes is very good and very versatile. There are much more services a Darkcoin network can provide: TOR nodes, Alternative Distributed DNS, Anonymizer, Email Mixer. I don't know what Evans plans for v2.0, 3.0, 4.0 are, but the future of dark is bright.

So if we come to a more mature testing process - i am talking about documentation of specifications, testplans, testcases - i am quite sure you can be part of a team, who is testing a new release before rollout. I will come back to you if you like.

Cheers,
Holger
Click to expand...
You have my vote.
 
I just thought of something??????

Can we switch the masternode key in the config file so that the masternode payments go to either or masternodes? (remote or local?)

It would be more convenient, and not too bad a risk, if it went to the remote/always on masternode where it could be sent to a daily use wallet to be sold/spent if you want. Is this possible?
 
What is needed in testnet now? I don't mine but could set up masternodes if that helps.
 
Running masternodes helps, running a wallet helps too, and if you know how to modify code and want to try to manipulate stuff, such as the payouts, etc... hack it and cause trouble, then go for that too! flare just did that, but I'm sure there are other sections of the code that need to be hardened, if you can think of something :D
 
eduffield said:
  • In the debug log of the hot daemon you should see "CDarkSendPool::EnableHotColdMasterNode() - Enabled! You may shut down the cold daemon."
  • You may now turn off the cold node, but DO NOT move the funds. This will immediately disable your masternode.
Click to expand...
I still never got this message and I haven't been paid yet, so I have no idea if this is working. Can anyone tell me if they got this message when setting up a remote wallet?

I'm also not on the MN list. Can't anyone pop in and say how they did their remote wallet please?
 
I have restated darkcoind of nomp at block 16232 ~ 16233.
nomp found a block at 16235, 16237, 16238, 16239.

16238 has no masternode payment.
 
I'm showing up with :0 flag, but when I open the wallet in darkcoin-qt (built from forkfix branch), I'm getting MN payments (30.20 DRK latest one has 3 confirms)

Code: 
masternode list
{
    "98.165.130.67:19999" : 1,
    "184.73.179.148:19999" : 1,
    "184.73.179.187:19999" : 1,
    "184.73.179.196:19999" : 1,
    "188.226.133.22:19999" : 1,
    "188.226.248.36:19999" : 1,
    "188.226.243.116:19999" : 1,
    "37.187.47.129:19999" : 1,
    "23.242.106.27:19999" : 0,
    "68.32.185.63:19999" : 1,
    "104.33.210.231:19999" : 1,
    "54.203.217.224:19999" : 1
}
The IP address is not showing up on the masterlist http://tdrk.poolhash.org/blocks/masterlist.txt

Should I stop and restart? I'm using remote/local method per the original guide. Thanks.
 
archLinuxUser said:
I'm showing up with :0 flag, but when I open the wallet in darkcoin-qt (built from forkfix branch), I'm getting MN payments (30.20 DRK latest one has 3 confirms)

Code: 
masternode list
{
    "98.165.130.67:19999" : 1,
    "184.73.179.148:19999" : 1,
    "184.73.179.187:19999" : 1,
    "184.73.179.196:19999" : 1,
    "188.226.133.22:19999" : 1,
    "188.226.248.36:19999" : 1,
    "188.226.243.116:19999" : 1,
    "37.187.47.129:19999" : 1,
    "23.242.106.27:19999" : 0,
    "68.32.185.63:19999" : 1,
    "104.33.210.231:19999" : 1,
    "54.203.217.224:19999" : 1
}
The IP address is not showing up on the masterlist http://tdrk.poolhash.org/blocks/masterlist.txt

Should I stop and restart? I'm using remote/local method per the original guide. Thanks.
Click to expand...
I think stop at least 10 min, and restart.
As removed from masternode list, NM will not be paid.

First do update.
 
chaeplin said:
I think stop at least 10 min, and restart.
As removed from masternode list, NM will not be paid.

First do update.
Click to expand...

ok, I'll do that. I'm getting paid, though, which is the weird thing.
wallet address: mnKjtxAsabarv2y2kb3sGyHz7rFEnm7Uu4
Is this the latest version of MN binary: v0.10.9.6-7-ga18bf5f-beta ?
Thanks.

Code: 
{
"account" : "0",
"address" : "mnKjtxAsabarv2y2kb3sGyHz7rFEnm7Uu4",
"category" : "immature",
"amount" : 30.20000000,
"confirmations" : 21,
"generated" : true,
"blockhash" : "00000000f405d94ced10cdfd1841e72da700656f20e4ab83858f610bfdd450ad",
"blockindex" : 0,
"blocktime" : 1402257499,
"txid" : "da3d3b16408f64112fcc9668c7609d9790d0a578e0ef506f832912bba84d4717",
"time" : 1402257499,
"timereceived" : 1402260197
},
{
"account" : "0",
"address" : "mnKjtxAsabarv2y2kb3sGyHz7rFEnm7Uu4",
"category" : "immature",
"amount" : 30.20000000,
"confirmations" : 11,
"generated" : true,
"blockhash" : "000000016ccfede9769ead15a5c395866d27bc1aef5a2513cb075042c0715f2b",
"blockindex" : 0,
"blocktime" : 1402259654,
"txid" : "30b68b0acf7955d1816783594b940e0698c8560a04e94eaff9e5378bb819c69a",
"time" : 1402259654,
"timereceived" : 1402260197
}
]
 
archLinuxUser said:
ok, I'll do that. I'm getting paid, though, which is the weird thing.
wallet address: mnKjtxAsabarv2y2kb3sGyHz7rFEnm7Uu4
Is this the latest version of MN binary: v0.10.9.6-7-ga18bf5f-beta ?
Thanks.

Code: 
{
"account" : "0",
"address" : "mnKjtxAsabarv2y2kb3sGyHz7rFEnm7Uu4",
"category" : "immature",
"amount" : 30.20000000,
"confirmations" : 21,
"generated" : true,
"blockhash" : "00000000f405d94ced10cdfd1841e72da700656f20e4ab83858f610bfdd450ad",
"blockindex" : 0,
"blocktime" : 1402257499,
"txid" : "da3d3b16408f64112fcc9668c7609d9790d0a578e0ef506f832912bba84d4717",
"time" : 1402257499,
"timereceived" : 1402260197
},
{
"account" : "0",
"address" : "mnKjtxAsabarv2y2kb3sGyHz7rFEnm7Uu4",
"category" : "immature",
"amount" : 30.20000000,
"confirmations" : 11,
"generated" : true,
"blockhash" : "000000016ccfede9769ead15a5c395866d27bc1aef5a2513cb075042c0715f2b",
"blockindex" : 0,
"blocktime" : 1402259654,
"txid" : "30b68b0acf7955d1816783594b940e0698c8560a04e94eaff9e5378bb819c69a",
"time" : 1402259654,
"timereceived" : 1402260197
}
]
Click to expand...

You paid 56 mins ago.
1 hour ago06/09 05:34:162162470.367151mposmnKjtxAsabarv2y2kb3sGyHz7rFEnm7Uu430.200

****** Please update to 9.5.9 or 10.9.9 *******

I'm still getting spam messages and can't tell if I fixed it earlier or users haven't updated so I incremented the protocol version to bump all of the older versions off the network again.

Binaries (stable)
http://www.darkcoin.io/downloads/forkfix/darkcoin-qt
http://www.darkcoin.io/downloads/forkfix/darkcoind

RC3 Binaries ( masternodes )
http://www.darkcoin.io/downloads/rc3/darkcoin-qt
http://www.darkcoin.io/downloads/rc3/darkcoind
Click to expand...
 
chaeplin said:
You paid 56 mins ago.
1 hour ago06/09 05:34:162162470.367151mposmnKjtxAsabarv2y2kb3sGyHz7rFEnm7Uu430.200
Click to expand...
Even with the flag of :0; I still received another payment. 2 Confirms so far.

"23.242.106.27:19999" : 0,
I guess this could be an issue on the mainnet if MN's are getting paid and not showing up on the masterlist?

Code: 
{
"account" : "0",
"address" : "mnKjtxAsabarv2y2kb3sGyHz7rFEnm7Uu4",
"category" : "immature",
"amount" : 30.20000000,
"confirmations" : 2,
"generated" : true,
"blockhash" : "00000001d9b179908862339ce52de646dcd24470ec26e426481b7dee9382d2ef",
"blockindex" : 0,
"blocktime" : 1402265543,
"txid" : "be6b85014069f82fe2c26e36485a3d69992ba5c50f51c4d5cf9b08d9fdf57aeb",
"time" : 1402265543,
"timereceived" : 1402265667
}
]
 
archLinuxUser said:
Even with the flag of :0; I still received another payment. 2 Confirms so far.
"23.242.106.27:19999" : 0,
I guess this could be an issue on the mainnet if MN's are getting paid and not showing up on the masterlist?

Code: 
{
"account" : "0",
"address" : "mnKjtxAsabarv2y2kb3sGyHz7rFEnm7Uu4",
"category" : "immature",
"amount" : 30.20000000,
"confirmations" : 2,
"generated" : true,
"blockhash" : "00000001d9b179908862339ce52de646dcd24470ec26e426481b7dee9382d2ef",
"blockindex" : 0,
"blocktime" : 1402265543,
"txid" : "be6b85014069f82fe2c26e36485a3d69992ba5c50f51c4d5cf9b08d9fdf57aeb",
"time" : 1402265543,
"timereceived" : 1402265667
}
]
Click to expand...

Yes. I have checked.
I think mpos and nomp has different masternode list.
 
Updated!

getting a lot of these in debug:
2014-06-08 22:40:31 trying connection 107.22.42.148:19999 lastseen=22.3hrs
2014-06-08 22:40:36 connection timeout
2014-06-08 22:40:37 trying connection 54.81.90.244:19999 lastseen=155.1hrs
2014-06-08 22:40:42 connection timeout
2014-06-08 22:40:43 trying connection 54.83.186.105:19999 lastseen=147.9hrs
2014-06-08 22:40:43 connect() failed after select(): Connection refused
2014-06-08 22:40:44 trying connection 194.65.106.45:19999 lastseen=63.9hrs
2014-06-08 22:40:44 connect() failed after select(): Connection refused
2014-06-08 22:40:44 trying connection 50.17.52.166:19999 lastseen=145.2hrs


is my daemon trying to connect to all masternodes it has in DB, and now slowly removes them from last masternode list cache?
 
Status
Not open for further replies.
Back
Top