Someone earlier mentioned you have to "lock" the 1000 coins in a masternode if you pay out the "earnings" in order to keep the node running and that it is not spending the reserved coins.
How do i lock them @ Linux?
Enable coin control in settings.. Then go to send tab... You should see how then. Linux commandline? In general listunspent ( minconf maxconf ["address",...] )
Returns array of unspent transaction outputs with between minconf and maxconf (inclusive) confirmations. Optionally filter to only include txouts paid to specified addresses. Results are an array of Objects, each of which has: {txid, vout, scriptPubKey, amount, confirmations}
Arguments: 1. minconf (numeric, optional, default=1) The minimum confirmationsi to filter 2. maxconf (numeric, optional, default=9999999) The maximum confirmations to filter 3. "addresses" (string) A json array of darkcoin addresses to filter [ "address" (string) darkcoin address ,... ]
Result [ (array of json object) { "txid" : "txid", (string) the transaction id "vout" : n, (numeric) the vout value "address" : "address", (string) the darkcoin address "account" : "account", (string) The associated account, or "" for the default account "scriptPubKey" : "key", (string) the script key "amount" : x.xxx, (numeric) the transaction amount in btc "confirmations" : n (numeric) The number of confirmations } ,... ]
Examples > darkcoin-cli listunspent > darkcoin-cli listunspent 6 9999999 "[\"1PGFqEzfmQch1gKD3ra4k18PNj3tTUUSqg\",\"1LtvqCaApEdUGFkpKMM4MstjcaL4dKg8SP\"]" > curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "listunspent", "params": [6, 9999999 "[\"1PGFqEzfmQch1gKD3ra4k18PNj3tTUUSqg\",\"1LtvqCaApEdUGFkpKMM4MstjcaL4dKg8SP\"]"] }' -H 'content-type: text/plain;' http://127.0.0.1:9998/
But for local wallet masternode outputs it's easier: darkcoind masternode outputs And then lockunspent unlock [{"txid":"txid","vout":n},...]
Updates list of temporarily unspendable outputs. Temporarily lock (unlock=false) or unlock (unlock=true) specified transaction outputs. A locked transaction output will not be chosen by automatic coin selection, when spending darkcoins. Locks are stored in memory only. Nodes start with zero locked outputs, and the locked output list is always cleared (by virtue of process exit) when a node stops or fails. Also see the listunspent call
Arguments: 1. unlock (boolean, required) Whether to unlock (true) or lock (false) the specified transactions 2. "transactions" (string, required) A json array of objects. Each object the txid (string) vout (numeric) [ (json array of json objects) { "txid":"id", (string) The transaction id "vout": n (numeric) The output number } ,... ]
Result: true|false (boolean) Whether the command was successful or not
Examples:
List the unspent transactions > darkcoin-cli listunspent
Lock an unspent transaction > darkcoin-cli lockunspent false "[{\"txid\":\"a08e6907dbbd3d809776dbfc5d82e371b764ed838b5655e72f463568df1aadf0\",\"vout\":1}]"
List the locked transactions > darkcoin-cli listlockunspent
Unlock the transaction again > darkcoin-cli lockunspent true "[{\"txid\":\"a08e6907dbbd3d809776dbfc5d82e371b764ed838b5655e72f463568df1aadf0\",\"vout\":1}]"
As a json rpc call > curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "lockunspent", "params": [false, "[{\"txid\":\"a08e6907dbbd3d809776dbfc5d82e371b764ed838b5655e72f463568df1aadf0\",\"vout\":1}]"] }' -H 'content-type: text/plain;' http://127.0.0.1:9998/
|
|
|
220429 , 220485 , 220505, 220620 (orphaned), 220967 (orphaned), 221,438 (orphaned)
Anything in debug.log / your pool logs at these blocks? I suppose there is a bug in you software somewhere. Mind sharing some more details on what you are running in pm or email? udjinm6@darkcoin.ioEmailing you now. https://github.com/simplecrypto/powerpool/pull/124 thanks, will let you know how it goes. Curious why all of a sudden it's an issue though... enforcement But the blocks before the recent updates were already correct reward amounts. Enforcement only made them orphans... Well, maybe there is smth more... but at least you will not "burn" coins generating less then you should. Check you logs with these changes applied and drop me an email if you see your block orphaned again.
|
|
|
220429 , 220485 , 220505, 220620 (orphaned), 220967 (orphaned), 221,438 (orphaned)
Anything in debug.log / your pool logs at these blocks? I suppose there is a bug in you software somewhere. Mind sharing some more details on what you are running in pm or email? udjinm6@darkcoin.ioEmailing you now. https://github.com/simplecrypto/powerpool/pull/124 thanks, will let you know how it goes. Curious why all of a sudden it's an issue though... enforcement
|
|
|
220429 , 220485 , 220505, 220620 (orphaned), 220967 (orphaned), 221,438 (orphaned)
Anything in debug.log / your pool logs at these blocks? I suppose there is a bug in you software somewhere. Mind sharing some more details on what you are running in pm or email? udjinm6@darkcoin.ioEmailing you now. https://github.com/simplecrypto/powerpool/pull/124
|
|
|
... and got 2 payments in 24 h !
...and that is "like clockwork"?? FOR ME it is... what do you want, to be angry for getting 2 payments in 24h ? No man, nice for you but shouldn't it be 1 payment every3.5 days? Enforcement on? There is a tiny chance that some MN could be payed twice now. Treat it as a lucky ticket v0.11.2.x will have improved version of payee selection https://github.com/darkcoin/darkcoin/pull/185/files (this code still need to pass testing though)
|
|
|
Yes I follow. I ment those coins are still there. Now looks like it is nobody's MN? Has it anything to do with that MN is on 11.0.14 same as drkmn01 at https://drk.mn/?mnregexp=and why that drkmn01 is on that version? There is still a bunch of 0.11.0.14 https://drk.mn/?mnregexp=0.11.0.14 No idea why drkmn01 is on it though, I guess elbereth might give a better answer
|
|
|
wtf has my pool paid MN 60% last 2 blocks, while some jerkoff is back to paying none?
that 60% is weird though, shouldnt even be possible. I suggest you provide Evan with your debug.log edit : i checked both MN addresses that got paid those 60% according website drk.mn and both just received 1.74 DRK on the 15th of feb, so it looks like they were actually paid according 37.5 % https://drk.mn/blocks.htmlfound blocks : 220484 & 220429 XyLz1jG5mUy93hK1QDcPZ6DqDqLvWdEF4A paid to random MN: XjkuayokN6t7V2FxaM81t9gP6aBgHzJNAo Xe98kvZ7MNNsVBbVF7MpgYv1oiKAm67sRy And another at 60% http://explorer.darkcoin.io/block/00000000000b96c470468ba586538be558528a58237ec5d507ee1f5ca953e883What a piss off. also 1.74 drk MN payment (in accordance with 37.5%) , i think drk.mn is showing incorrect info well my wallet isn't getting paid the correct amount. It's being skimmed somewhere... "address" : "XyLz1jG5mUy93hK1QDcPZ6DqDqLvWdEF4A", "category" : "immature", "amount" : 1.16131435, "confirmations" : 2, "generated" : true, "blockhash" : "00000000000b96c470468ba586538be558528a58237ec5d507ee1f5ca953e883", The problem seems to be with the amount generated. According to the explorer only 2.9 coins are being created when it should be 4.65. Very strange block. In block 220504 generation amount is correct. This is still happening! ANd now since enforcement, I'm not even getting those blocks, even thought the MN get their share. Evan this started happening only since 19+ and continues What block exactly? 220429 , 220485 , 220505, 220620 (orphaned), 220967 (orphaned), 221,438 (orphaned) Anything in debug.log / your pool logs at these blocks? I suppose there is a bug in you software somewhere. Mind sharing some more details on what you are running in pm or email? udjinm6@darkcoin.io
|
|
|
wtf has my pool paid MN 60% last 2 blocks, while some jerkoff is back to paying none?
that 60% is weird though, shouldnt even be possible. I suggest you provide Evan with your debug.log edit : i checked both MN addresses that got paid those 60% according website drk.mn and both just received 1.74 DRK on the 15th of feb, so it looks like they were actually paid according 37.5 % https://drk.mn/blocks.htmlfound blocks : 220484 & 220429 XyLz1jG5mUy93hK1QDcPZ6DqDqLvWdEF4A paid to random MN: XjkuayokN6t7V2FxaM81t9gP6aBgHzJNAo Xe98kvZ7MNNsVBbVF7MpgYv1oiKAm67sRy And another at 60% http://explorer.darkcoin.io/block/00000000000b96c470468ba586538be558528a58237ec5d507ee1f5ca953e883What a piss off. also 1.74 drk MN payment (in accordance with 37.5%) , i think drk.mn is showing incorrect info well my wallet isn't getting paid the correct amount. It's being skimmed somewhere... "address" : "XyLz1jG5mUy93hK1QDcPZ6DqDqLvWdEF4A", "category" : "immature", "amount" : 1.16131435, "confirmations" : 2, "generated" : true, "blockhash" : "00000000000b96c470468ba586538be558528a58237ec5d507ee1f5ca953e883", The problem seems to be with the amount generated. According to the explorer only 2.9 coins are being created when it should be 4.65. Very strange block. In block 220504 generation amount is correct. This is still happening! ANd now since enforcement, I'm not even getting those blocks, even thought the MN get their share. Evan this started happening only since 19+ and continues What block exactly?
|
|
|
Well, first of all it says "active" not "full". Now look at that: Not too bad hah? Glorious to see, UdjinM6, am thinking how the network topology is described, as there are 2 types of network so this is a hybrid system, are the masternode's a fully connected mesh topology hybridized with a peer to peer partly connected mesh networking system of the standard blockchain type. A hybrid system supersedes a single networking layer,best of both worlds I would have thought. Am I seeing the networking layers correctly? Masternode (MN) network is not fully connected if you mean by that that each MN should be connected to each another one. It's not like that and there is no reason for that actually as it wouldn't let MN network to scale. MN network is a huge group of the most stable peers on the network and that serves well for the purposes they were made for.
|
|
|
i was debating a ltc holder who said something about drk checkpointing. anybody know what he is talking about or is he misinformed? i remember peercoin had to do something like that.
"Chekpointing, do you still use that to "secure" the network ? Cause if yes, there's no decentralisation, someone have the keys, the network rely on one man... ouch. But I guess you have to, to avoid 51%."
Oh, yeah, right... https://github.com/litecoin-project/litecoin/commits/master-0.8/src/checkpoints.cpp
|
|
|
Well, first of all it says "active" not "full". Now look at that: Not too bad hah?
|
|
|
lol bootstrap, qwizzie, not boobs_trap
|
|
|
When will be ready "hide mn ip" ?
When it's ready... I would expect 4 to 6 months but it may take longer depending on many variables. Based on what exactly? Not trying to diminish you opinion, but why do think it'll take so long? Based on the fact that the dev team have a lot to do including the development of 2fa first as well as mobile apps and not to mention fixing bugs in DS and IX as and when they are found. Don't get me wrong, it would be great to have ip obfuscation and everything else sooner and 4 to 6 months is a guesstimating based on the development rate so far... DS has taken 12 months to get it to this stage IX took 5 months from white paper I'm guessing 2FA will take 5 months and then they will look at ip obfuscation. Yep, this will not happen overnight for sure
|
|
|
- would like to see the windows wallets sync and download as fast and as problemless as on Linux (which is impressively fast).
crowning : I'm not sure if this is a Darkcoin problem...ALL my wallets sync way faster on Linux.
Maybe the windows GUI during sync is just starting to many processes at once, i wonder if it would be more efficient / faster if we decouple longterm syncing with the loading of the GUI wallet. With long syncs (longer than a day perhaps? ) make it sync first and only show some simple loading / syncing screen and once synced start all other processes of the GUI, including further syncing ofc. edit : just my thoughts, i dont have much techn knowledge / code knowledge so i have no idea if what i describe above is even remotely possible or even necessary. GUI performance issues should be fixed in 0.11.2.x spoiler: Performance Pack is already there https://github.com/darkcoin/darkcoin/pull/177
|
|
|
Darkcoin Mining Pool Hubhttp://darkcoin.miningpoolhub.comJust updated darkcoin wallet to 0.11.01.25 I was curious that why only our pool was affected and I found that several other pools also stuck within 24 hours. xhash.net darkcoinoboxru ghashio check their pool from http://drk.mn and you will find that there payee was stuck too. We are innocent. We want to resolve misunderstanding. Please don't leave and come back. Thank you for updating! I can confirm that at least your 3 latest blocks are correct now: masternode winners .... "219770" : "XtrWP6SYsZxvVFBxe9s5gascAi3jwypfps" .... "219773" : "XvXiUUj6ae6QJpuNQyjFUZv4qEM1guw56i", .... "219775" : "XwsCeVUM7fE9rFob1zr5p7TtEfcSXmMrg5", .... As for the others, that shouldn't really happen for that many peers for so long time, we'll investigate further then... Anyway network should look way healthier with you back on track. Our aim to safely enforce with 80% mining power on latest protocol is still here. EDIT: Once again to all pool owners who is still running on one of pre .25 versions: We still have this guy XxDotRpSDzgyAkx3jHkLZD8YYZRwbcjmmA to fork off and he has 10%+ so we need everyone. Even if you are 1% or smaller.
|
|
|
^ If you add that up with Udjin's comment it makes sense It was stuck paying same payee and he was sleppin However the address you mentioned do not use this feature. It got its payments when coinmine.pl hit a bug we already fixed now. That bug caused pool to pay exact same random lucky MN first few blocks on every restart. However I'd like to thank coinmine.pl for following our updates very quickly and completely complying network rules (while I can't say the same about one another large pool that was already mentioned here...) EDIT: and every other pool who updated too of course, thank you guys! Oh my god. I'm compiling new wallet. I don't think its the same bug...one talks about upon restart, not every damn MN. Dunno who to believe anymore. That should stuck for few blocks until next mnw message propagates but he could be connected to wrong (old) peers that refused to propagate mnw too. This really could happen. EDIT: there is not a great probability though but it's Friday 13
|
|
|
About MiningPoolHub darkcoin masternode payment problem.I didn't know what happened last night. (Yeah, it's night in my time zone) and surprised with bunch of scam shouting me. I personally own my masternode, Xe8YGfjzTYpvfsCXgL6uqvokL8mvV4dCNz Here is my masternode's payment. https://chainz.cryptoid.info/drk/address.dws?Xe8YGfjzTYpvfsCXgL6uqvokL8mvV4dCNz.htmI have no idea about Xit9gEJiUphYGggS2NCu5UaqoR4YWxmFaZ I promise I don't lie. darkcoind getinfo { "version" : 110122, "protocolversion" : 70066, "walletversion" : 60000, "balance" : xxxx, "darksend_balance" : 0.00000000, "blocks" : xxxx, "timeoffset" : 144, "connections" : 22, "proxy" : "", "difficulty" : 3183.25971769, "testnet" : false, "keypoololdest" : 1394007947, "keypoolsize" : 1001, "paytxfee" : 0.00000000, "relayfee" : 0.00001000, "errors" : "" } ....snip... I'm really innocent, don't know what things gone. Maybe I'm wrong, I remember there was masternode payee hijacking few weeks ago? Sorry if I'm wrong but maybe it's related to that. I have debug.log from recent wallet ran. Hope the dev to find out the problem. I restarted darkcoin wallet and it seems running fine currently. That makes sense for me. However you are still on .22 and that means you will stuck again on another address (I believe you already did - XgHuL7STpcmLeP3YHv4ooPAK24Bf5CGLko). Can you update to .25 please? EDIT: ^ If you add that up with Udjin's comment it makes sense It was stuck paying same payee and he was sleppin However the address you mentioned do not use this feature. It got its payments when coinmine.pl hit a bug we already fixed now. That bug caused pool to pay exact same random lucky MN first few blocks on every restart. However I'd like to thank coinmine.pl for following our updates very quickly and completely complying network rules (while I can't say the same about one another large pool that was already mentioned here...) EDIT: and every other pool who updated too of course, thank you guys! Oh my god. I'm compiling new wallet. Nice!
|
|
|
|