DyslexicZombei's Darkcoin Community MasterNode Svcs: CLOSED. Nodes 2 4 5 Refunds

[roede94105]

If node 4 is short of the 1,000 DRK, I'm happy at any time to top up to the full amount when DZ needs it to go live, likewise for node 5 etc, so if you put coins in to a shared node you're guaranteed it will be a full functioning one, I'll leave the time frame up to DZ when to ask me to fill partially invested nodes, maybe once a week or when they get up to 500 DRK or something.

That's awesome of you to make that offer Otoh. Thank you!

We might have to take you up on that depending on how the next 13.5 hours works out.

The Node #4 wallet is currently 95% full! Depending on how the deposits work out, one of the later deposits may have to shift to a possible Node #5, due to the way the stake ownerships must fit like a puzzle to equal 1000DRK - hence the mixing/matching of earlier B2 reservations and later B3 reservations.

People in Node #5 can wait to be generously rescued by Otoh to fill the Node OR ask a penalty free refund (since nothing happened).

I have to head to work, but I'll check PMs this evening on Reddit and here, before giving the final community fund raising update for this launch period of this service.

Hey Zombie, R2A from Reddit here,

I was just wondering if I had something to do for the setup of my full node (1k dark) or not,

I'm so eager to have mine setup  

Good luck with your work!

Thank you! We're waiting for RC3 and instructions to go public before the cold storage of DRK wallets for nodes owned by one person can be implemented. Please *don't* send me your 1000DRK if you want a full node or two...or a bunch.

If I had my way, I wouldn't touch anyone's DRK stake funds to set up these partial nodes, but alas...

Full node owners with a Setup Reservation: please be patient and wait for RC3 to release before sending me an encrypted and complex password protected wallet file in which I won't have access to the original stake funds (and there's less anxiety on my part about handling large amounts of other people's funds).

Also, I'll be contacting full node owners in the order in which they contacted me before or when RC3 releases so for prompt set-up when I get to your full node in the Q, please have your encrypted 10000DRK wallet files and other relevant info per developer instructions. Assuming the first few nodes aren't having issues with the hard fork, I'll be starting full node setup on the evening of the 20th when I get back from work. On Friday or this weekend: If you can have this wallet file(s) and other relevant info ready for me, that will help immensely with speeding up setup time.

Since this thread has taken on a life of its own but is starting to branch off into discussion about Full Nodes: I'll likely start a Full Node thread on this subforum tomorrow night to help organize that effort to separate it from the Partial Node aspect of this thread, so also please keep an eye out for that.

Thanks for your answer! Please, if possible, post the thread link in this thread so I see it immediately

Good luck with your work!

[1714822492]

1714822492

[1714822492]

1714822492

[2C-Bee]

 TxID: c574af1636e77891b04ced5e3c32f9ff92cf454abd18f8fb31d022cf2b98e1b6
Sent: 250.00 DRK
Payout address: XrpE7NzLM9sTzQPTpt8G5aFoMqqF12akRx

[DyslexicZombei]

TxID: c574af1636e77891b04ced5e3c32f9ff92cf454abd18f8fb31d022cf2b98e1b6
Sent: 250.00 DRK
Payout address: XrpE7NzLM9sTzQPTpt8G5aFoMqqF12akRx

Thank you. Confirmed.

We are at exactly 4.5 Nodes funded and thanks to Otoh's generous offer, those in the fifth node won't be left out.

==

Also: I don't have much time with two deadlines fast approaching, one fun and the other work, but real quick -

- good idea on the float ddink7: I don't know if Otoh would want to essentially be a community bank for ownership swaps, but if/when I can get to the point of helping to keep nodes afloat, I'd do it without hesitation. Since we were setting up the first node, we were setting a template for the nodes to follow. Otoh and I discussed the structure of this and what would be fair: we decided that 3 days notice was fair in that the original stake owner wouldn't have to wait long (esp. if they planned ahead) to withdraw from a node, and we should hopefully be able to fill that hole in ownership within 72 hours so that the node doesn't have to go down due to a stake fund shortage.

If you think about it: as long as ownership/management is kosher (or you're doing it yourself), partial node ownerships are great places to store DRK you weren't going to spend anyway and then you get to earn interest on them. At this point the two main minting/reward systems for cryptocoins are PoW and PoS. Darkcoin essentially combines the best of both worlds and becomes both a Proof of Work and a Proof of Stake coin tomorrow: Work is represented by mining, like in the BTC realm. Earning from Stake are offered via Masternodes, like forging in the NXT realm.

- re: BTC Talk forum security being used to either force a fake withdrawal or change a payout address falsely. The forum's been hacked before as we all know and it relies on SMF which has been pooh poohed by some as being woefully out of date and insecure. As far as compromised accounts: If it's a problem, then it's a problem every vendor and operator has to deal with (esp. the ones doing payouts). To my knowledge the forum system has never been compromised in this manner (forcing fake trades/deals) but it's also not out of the realm of possibility.

I honestly don't know how we as a community could deal with this at the moment, with the tools we currently have available. It's certainly a risk for us, as I've used this centralized forum to bring together the disparate cryptocommunity in one place for this new service which you all have been helping me to improve and evolve.

I'm open to suggestions from those that have ideas about how to reduce or prevent a fake trade or false payout redirection.

[ddink7]

TxID: c574af1636e77891b04ced5e3c32f9ff92cf454abd18f8fb31d022cf2b98e1b6
Sent: 250.00 DRK
Payout address: XrpE7NzLM9sTzQPTpt8G5aFoMqqF12akRx

Thank you. Confirmed.

We are at exactly 4.5 Nodes funded and thanks to Otoh's generous offer, those in the fifth node won't be left out.

==

Also: I don't have much time with two deadlines fast approaching, one fun and the other work, but real quick -

- good idea on the float ddink7: I don't know if Otoh would want to essentially be a community bank for ownership swaps, but if/when I can get to the point of helping to keep nodes afloat, I'd do it without hesitation. Since we were setting up the first node, we were setting a template for the nodes to follow. Otoh and I discussed the structure of this and what would be fair: we decided that 3 days notice was fair in that the original stake owner wouldn't have to wait long (esp. if they planned ahead) to withdraw from a node, and we should hopefully be able to fill that hole in ownership within 72 hours so that the node doesn't have to go down due to a stake fund shortage.

If you think about it: as long as ownership/management is kosher (or you're doing it yourself), partial node ownerships are great places to store DRK you weren't going to spend anyway and then you get to earn interest on them. At this point the two main minting/reward systems for cryptocoins are PoW and PoS. Darkcoin essentially combines the best of both worlds and becomes both a Proof of Work and a Proof of Stake coin tomorrow: Work is represented by mining, like in the BTC realm. Earning from Stake are offered via Masternodes, like forging in the NXT realm.

- re: BTC Talk forum security being used to either force a fake withdrawal or change a payout address falsely. The forum's been hacked before as we all know and it relies on SMF which has been pooh poohed by some as being woefully out of date and insecure. As far as compromised accounts: If it's a problem, then it's a problem every vendor and operator has to deal with (esp. the ones doing payouts). To my knowledge the forum system has never been compromised in this manner (forcing fake trades/deals) but it's also not out of the realm of possibility.

I honestly don't know how we as a community could deal with this at the moment, with the tools we currently have available. It's certainly a risk for us, as I've used this centralized forum to bring together the disparate cryptocommunity in one place for this new service which you all have been helping me to improve and evolve.

I'm open to suggestions from those that have ideas about how to reduce or prevent a fake trade or false payout redirection.

Why don't you get a list of emails and/or phone numbers from all your stakeholders. If somebody wants to withdraw to the payout address you have on file, no problem. ***If somebody wants to change their payout address, you require email and/or voice confirmation.*** What do you think?

[bregge]

250drk send some hours ago,check PM
Transaktions-ID: 9ab5810fcec1e54338c2f355ce025e08841dfccb92db3d1740269bf33813fb7e
payout: XuRE3QHnmT6oUM1ctqmd4zxYzWhhuEg7e8

If needed i can deposit 150drk more for fillup the node.

[DyslexicZombei]

250drk send some hours ago,check PM
Transaktions-ID: 9ab5810fcec1e54338c2f355ce025e08841dfccb92db3d1740269bf33813fb7e
payout: XuRE3QHnmT6oUM1ctqmd4zxYzWhhuEg7e8

If needed i can deposit 150drk more for fillup the node.

Thanks bregge. Noted, Mahalo and Welcome Aboard! We should be fine, as there's a few more that might straggle in (late PMs on other sites) and Otoh has offered to fill up any partial nodes left hanging.

Also: I posted the FULL NODE thread but there's not much info yet because we know little at this point: https://bitcointalk.org/index.php?topic=658285.0

As you hear about the cold storage setup for full nodes, please feel free to share anything new you learn with the rest of us. 

[DyslexicZombei]

New batch Three Reservations are Closed. Only those that contacted me offsite for the first time yesterday will get a 24 hour extension to 9PM HST tonight.

After that: partial node set ups will be completely closed until the backlog of first Batch of Full Nodes clears from the daughter thread for Full nodes that this thread spawned.

[ddink7]

DZ: I know you have been busy with work, but was just wondering if you had any updates on the ETA for having MNs set up? Thanks a bunch!

[DyslexicZombei]

DZ: I know you have been busy with work, but was just wondering if you had any updates on the ETA for having MNs set up? Thanks a bunch!

If all goes well, they'll go live sometime tonight after I harden the 2nd template (turns out there's two at the moment based on two different Linux OS systems ). First template's almost finished and I'm working on node prep/hardening this evening without too much distraction (family's at the movies).

I plan on heading to work a little later tomorrow morning but I leave before payments go live at I believe 11am my time. Cross your fingers for us that there's no major stumbling blocks that keeps us from being live with at least 4 community nodes by tomorrow morning.

==

Last update of the night: Template #1 survived a pretty intensive scan of...well, everything, audit and check of logs. I don't want to say it's bulletproof because we all know how that goes but this system as is, would be near DoD CAT I STIG standards if submitted for Accreditation; I deviate because I disagree with certain vendor choices.

Node #1 is good to go except I need to take it down to implement cold storage for RC3 for even better security, and it will be the first to be up with cold storage.

BTW, we ended up at 4.75 Nodes filled.

Ok, back to work.

[DyslexicZombei]

Node #2 is now up utilizing cold storage and RC3. It's all ready for tomorrow.

sumguy@XX-XX-XX-21:~/.darkcoin$ ./darkcoind getinfo
{
    "version" : 100811,
    "protocolversion" : 70015,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 86914,
    "timeoffset" : 0,
    "connections" : 1,
    "proxy" : "",
    "difficulty" : 3601.02705821,
    "testnet" : false,
    "keypoololdest" : 1402136780,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "errors" : "Hard Fork Alert: Masternode Payments begin on Friday, June 20th. Please update! http://goo.gl/ucp4m7"

This was the movement of funds into cold storage for Node #2:
Status: 64 confirmations
Date: 6/19/2014 21:18
Debit: -1000.00 DRK
Credit: 1000.00 DRK
Net amount: 0.00 DRK
Transaction ID: 12cb0d02f4f3aee8ca1b55f1ce7883e32d20822ff322c9a73eee85337b4f1994

==

Node #1 is also running but with the orig. hot wallet at the moment:

SumbunnythatIusedtoknow@xx-xx-xx-147:~$ darkcoind getinfo
{
    "version" : 100811,
    "protocolversion" : 70015,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 88632,
    "timeoffset" : 0,
    "connections" : 1,
    "proxy" : "",
    "difficulty" : 3117.28726659,
    "testnet" : false,
    "keypoololdest" : 1402136780,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "errors" : "Hard Fork Alert: Masternode Payments begin on Friday, June 20th. Please update! http://goo.gl/ucp4m7"


Still trying to figure out how to send the coins back from Node #1 to the orig. wallet so I can put stake funds from #1 into cold storage. Interestingly, when you implement this it tells you you're paying a payment to yourself and your balance stays the same.

[DyslexicZombei]

Node #3 Cold storage transaction and current status:

Status: 6 confirmations, broadcast through 11 nodes
Date: 6/19/2014 23:53
Debit: -1000.00 DRK
Credit: 1000.00 DRK
Net amount: 0.00 DRK
Transaction ID: 26e347b1f6119915e59b561d5145a03ad65f31e55528a72ea0fd46305af47b14

unkofester@ip-xxx-xx-xx-22:~$ darkcoind getinfo
{
    "version" : 100811,
    "protocolversion" : 70015,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 87547,
    "timeoffset" : 0,
    "connections" : 2,
    "proxy" : "",
    "difficulty" : 3270.72867714,
    "testnet" : false,
    "keypoololdest" : 1402136780,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "errors" : "Hard Fork Alert: Masternode Payments begin on Friday, June 20th. Please update! http://goo.gl/ucp4m7"

[DyslexicZombei]

Node #4 wallet transaction to cold storage:

Status: 0/unconfirmed
Date: 6/20/2014 00:09
Debit: -1000.00 DRK
Credit: 1000.00 DRK
Net amount: 0.00 DRK
Transaction ID: 30762d9e5644cb8f486a7e27c4db4cc7f07ae64e0ad8cfc00b01d800f17bcaeb

sumofallpears@xxx-xx-xx-19:~$ darkcoind getinfo
{
    "version" : 100811,
    "protocolversion" : 70015,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 86402,
    "timeoffset" : 0,
    "connections" : 2,
    "proxy" : "",
    "difficulty" : 3198.16472526,
    "testnet" : false,
    "keypoololdest" : 1402136780,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00001000,
    "errors" : "Hard Fork Alert: Masternode Payments begin on Friday, June 20th. Please update! http://goo.gl/ucp4m7"

Whew! Ok that does it. I have a little more to do to finish up but that's it for the night.
Otoh if you can send 250 DRK for the last node, we'd have a complete 5th node I can launch pretty quickly.

[Otoh]

...

Whew! Ok that does it. I have a little more to do to finish up but that's it for the night.
Otoh if you can send 250 DRK for the last node, we'd have a complete 5th node I can launch pretty quickly.

Sent!

Status: 0/unconfirmed, broadcast through 8 nodes
Date: 20/06/2014 15:23
To: DZ MN deposits XuFmZmR5x66gbyR4rKMNBj3wPXzdoybFZJ
Debit: -250.00 DRK
Transaction fee: -0.001 DRK
Net amount: -250.001 DRK
Transaction ID: ee4833c9978fa7bf4afeb08cf1b7799e20be65aa95f2752aa6b2479cd6c289db

It's best to email me or PM as I don't have time to check the thread often, I will be traveling in a few days and so may be afk from time to time as well, especially around the 26th, but all new node top up requests will be filled as soon as I get back online.

Also I'm happy to leave a permanent float to cover anyone wishing to withdraw from an existing node, I'd then be taking their position either temporally until new funds come in or permanently, which ever is easiest to administer and keep track of. Nodes once set up would then be guaranteed to stay working even if some of the join investors withdrew funds from them.

[DyslexicZombei]

Thanks Otoh. I'll shoot you a PM later. We"re not quite out of the woods yet: I keep running into this console error on my local wallet when I try to startup the MasterNode via cold storage & local wallet: says to set MasterNode=1 in conf file, and it *is* set in both conf files to 1.

I've gone thru the instructions & config with a fine toothed comb and the conf file settings match exactly on both ends. Worked till 1am on it. Slept a few hours and got back to it at 630: looked at config again. config was good but I keep getting the error without documentation around about what to do if you see this error.

I think I'm seeing weirdness from the Darkcoin network itself too. Otoh's deposit still hasn't shown up although its been a while and I upgraded qt last night to the latest ver. Hmm, we're up but we're literally at the final step of implementing node activation from cold wallet and stymied at that very last step! It's a bit frustrating to have had to troubleshoot this final step for hours without seeing anything wrong with the config.

I may have to just re-visit this when I get home this afternoon. I left a comment up explaining what I was seeing on the RC3 setup thread at Darkcoin Talk. There's steps you can do with troublesome nodes which involve moving funds around and regenerating keys but to do it properly I'll need more time and I want to see network stability. If there's forking problems we may have to wait for the network to settle down. Feeling a tad nervous moving several K of DRK around - even self-payments - if the network is acting funky.

Let's hope this fork goes smoother than last time.

[DyslexicZombei]

Darnit. Just as I suspected there *is* network instability. You get a feel for it when you've been working with networks for so long (and other times it just slaps you in the face).

Evan confirms there's some forking issues: https://bitcointalk.org/index.php?topic=421615.msg7421501#msg7421501

Sigh. Sorry gents, I worked hard to get us ready for RC3 but we better wait for the situation to settle down before I start troubleshooting this again.

With network stability being low, Doesn't seem like much point of doing all this work just to possibly end up on the wrong fork and have to redo the config again. Looks like node payments are still disabled anyway until this is solved, so at least we're not losing out on rewards. I'll check the network status when I get home from work and continue troubleshooting that last step if the forking issues are solved by then.

[ddink7]

Darnit. Just as I suspected there *is* network instability. You get a feel for it when you've been working with networks for so long (and other times it just slaps you in the face).

Evan confirms there's some forking issues: https://bitcointalk.org/index.php?topic=421615.msg7421501#msg7421501

Sigh. Sorry gents, I worked hard to get us ready for RC3 but we better wait for the situation to settle down before I start troubleshooting this again.

With network stability being low, Doesn't seem like much point of doing all this work just to possibly end up on the wrong fork and have to redo the config again. Looks like node payments are still disabled anyway until this is solved, so at least we're not losing out on rewards. I'll check the network status when I get home from work and continue troubleshooting that last step if the forking issues are solved by then.

DZ: As a network engineer, what's your read on the forking situation today? Do you think this is something Evan can resolve fairly easily?

[DyslexicZombei]

TBH: I don't know enough to have an informed opinion since I don't have time to be a testnet operator which would've likely informed me more. I don't know where and how the code is failing and that's out of my area of expertise.

This is more in the realm of program debugging with an assist from network admins/engineers involved behind the scenes.

[Otoh]

Also I forgot, I need to update the wallet that I'd sent the 250 DRK from, if that makes any difference to the transfer, it's still on v0.9.4.11-unk-beta, I can update it tomorrow and resend if that was the problem.

[DyslexicZombei]

Also I forgot, I need to update the wallet that I'd sent the 250 DRK from, if that makes any difference to the transfer, it's still on v0.9.4.11-unk-beta, I can update it tomorrow and resend if that was the problem.

Strange. Nothing yet.

I would've thought that it would be fine to send DRK between the two client versions before the planned fork but it's possible that your transaction went out on some orphaned block in an unplanned side fork.

Oh, I may a solution for the RC2 to 3 upgrade to cold storage for our node #1: https://bitcointalk.org/index.php?topic=421615.msg7424706#msg7424706

I'll explore this tonight to see if its both applicable and possibly helpful. Turns out that occasionally there's good info in there amidst the trolling and mudslinging.

[Otoh]

I've updated that wallet to v0.9.10.2-unk-beta now, which is showing about double the confirmations that the old wallet had I think, let me know if it needs to be resent please, many thanks, hopefully it's working now.

Status: 369 confirmations
Date: 20/06/2014 15:23
To: DZ MN deposits XuFmZmR5x66gbyR4rKMNBj3wPXzdoybFZJ
Debit: -250.00 DRK
Transaction fee: -0.001 DRK
Net amount: -250.001 DRK
Transaction ID: ee4833c9978fa7bf4afeb08cf1b7799e20be65aa95f2752aa6b2479cd6c289db