It did get stuck on 5 confrmation for about a minute. It was my first instantX and i saw the green circle right after i sent it but then i saw it said confirming 5 of 6. About a minute later it turned to a confirmed green check mark.
I still say instantX is too expensive for small amounts. For a $3 transaction it cost 30 cents. Is there some reason that transactions under 100DRK (or even 50DRK) can't be exempt and just pay a regular 0.01 or 0.001 transaction fee?
Somebody tried to explain it to me already but i still don't understand.
Yes because masternodes confirms 5 out of 6, the last one is a POW block confirmation. I do think that sending 1-10drk a fee 0,1drk for IX is too HIGH. There should be some "if then" code fee implemented. Ok cool, so it did get confirmed instantly like it's supposed to, right? Edit: Minotaur26 just answered my question, thanks If possible i would like to see the fee lowered to 0.01 (3 cents) for anything under 100DRK. Only reason i can see for not doing it would be that it could cause some kind of spam attack. The IX Fee is 0.01, which is 3 cents. Darksend has a 0.01-0.1 DRK fee depending on the amount you're sending (because it doesn't support change). So if you use IX+DS it appears much more expensive, but it's really just DS that's more expensive. |
|
|
|
Q: why is this MN getting regular payment as it shows old version?
23.21.204.34:9999
It's running the new version according to the reference node ./darkcoind masternode list protocol | grep '23.21.204.34:9999'
"23.21.204.34:9999" : 70066, |
|
|
|
omg i just lost about 75 drk
instantx sucks when sending to shapeshift
i feel horrible
fml
i sent at the start of the 10 minutes using instantx
and then they didnt recieve it and i didnt see it on the block explorer
still waiting and now when they recieve them i dont kno what will happen
what do i do now please tell me. did i lose 75 drk? that is alot of money
In theory if an IX fails it should still proceed as a normal tx. If that hasn't happened maybe try restarting your wallet with -zapwallettxes and see if that magically restores them. Not in theory, that's how they work. It's impossible to lose money using IX, either it succeeds and the source of the money is locked or it fails and it's a normal tx. I don't see the transaction on the block explorer. What can i do? My wallet says 9 confirmations though Send me the transaction ID, I'll check it out |
|
|
|
omg i just lost about 75 drk
instantx sucks when sending to shapeshift
i feel horrible
fml
i sent at the start of the 10 minutes using instantx
and then they didnt recieve it and i didnt see it on the block explorer
still waiting and now when they recieve them i dont kno what will happen
what do i do now please tell me. did i lose 75 drk? that is alot of money
In theory if an IX fails it should still proceed as a normal tx. If that hasn't happened maybe try restarting your wallet with -zapwallettxes and see if that magically restores them. Not in theory, that's how they work. It's impossible to lose money using IX, either it succeeds and the source of the money is locked or it fails and it's a normal tx. |
|
|
|
Let's say you roll out an update and enforcement is off. The next day, god forbid, you get hit by a bus before you turn enforcement on. What then?
We saw what bad actor pools do when enforcement is not on. It's not variance as stonehedge alludes; it is theft.
The beauty of bitcoin is it doesn't need a single person to flip a switch for it to work properly. At present, Darkcoin does.
That's a risk to the entire masternode system and as such, a risk to the entire Darkcoin network. And a potentially catastrophic one at that.
There's a reference node key in the software. If I get hit by a bus, someone just needs to change the key and have everyone update. What would that take, like six hours? Certainly, but then someone has to maintain the actual reference node. I'm sure as heck not going to trust anyone to the degree I trust you. And the point is, I shouldn't have to trust anyone when it comes to cryptocurrency. It's supposed to be trustless. Because let's be honest, humans can't be trusted. We're all fallible. I agree, I'm not arguing we should keep it. It's temporary  |
|
|
|
Let's say you roll out an update and enforcement is off. The next day, god forbid, you get hit by a bus before you turn enforcement on. What then?
We saw what bad actor pools do when enforcement is not on. It's not variance as stonehedge alludes; it is theft.
The beauty of bitcoin is it doesn't need a single person to flip a switch for it to work properly. At present, Darkcoin does.
That's a risk to the entire masternode system and as such, a risk to the entire Darkcoin network. And a potentially catastrophic one at that.
There's a reference node key in the software. If I get hit by a bus, someone just needs to change the key and have everyone update. What would that take, like six hours? |
|
|
|
I just added 20btc worth of DRK to my position. This is the first Darkcoin purchase I have made in a LONG time. I am still very bothered by the centralized reference node Darkcoin employs and hope that removing it becomes a priority. In my opinion, Darkcoin is vulnerable in its dominant position as the king of anonymity until that happens. All it will take is one top tier dev who sees the chink in Darkcoin's armor and doesn't fucking disappear  Once the reference node issue is finally resolved, I suspect we'll be seeing ATH's for Darkcoin. I agree that the ref node has to go and I believe that it is seen as a high priority for the dev team. However, why does everybody get so freaked out by it? Its a temporary and elegant solution to a problem. Without it, we'd just go back to variance in masternode payments. I stand to be corrected but it is not an attack vector for the network. I agree, it literally poses no risk to any part of the system. |
|
|
|
I just added 20btc worth of DRK to my position. This is the first Darkcoin purchase I have made in a LONG time. I am still very bothered by the centralized reference node Darkcoin employs and hope that removing it becomes a priority. In my opinion, Darkcoin is vulnerable in its dominant position as the king of anonymity until that happens. All it will take is one top tier dev who sees the chink in Darkcoin's armor and doesn't fucking disappear Once the reference node issue is finally resolved, I suspect we'll be seeing ATH's for Darkcoin. Removal of the reference node is absolutely a priority. Instead of a blockchain based solution, I was thinking it could use the same exact logic as InstantX, just collect 20 of 30 signatures. If you get 20+ for one address, then it wins and is enforced. So the masternode network as a whole becomes the reference node. |
|
|
|
Someone can tell me how can I be sure my MN works properly? I see my MN online and it is 100% ok according to dark.mn. But i did not get any payment since 06 march. I check my debug.log and did not see any ERROR message. MN is updated to latest *.25 version. Any suggestions?
I'm assuming you mean Feb. Anyway, if you are seeing it on DRK.MN and you are grepping 1 on the masternode list for your IP, it's being seen by the network. Yes, i mean February. And yes i get 1 on grep command. So i am super unlucky? It appears so. I have three masternodes that haven't been paid yet. Enforcement is on and working perfectly, as a result the fair payment cycle has begun. The full cycle should be about 4 days long, if you don't receive payment by Saturday feel free to shoot me an email and I'll look into your specific node. |
|
|
|
i found this on my logs... yee 2015-02-16 00:48:18 ERROR: ProcessBlock() : CheckBlock FAILED 2015-02-16 01:09:11 ERROR: CheckBlock() : Couldn't find masternode payment or pa yee 2015-02-16 01:09:11 ERROR: ProcessBlock() : CheckBlock FAILED 2015-02-16 01:33:06 ERROR: CheckBlock() : Couldn't find masternode payment or pa yee 2015-02-16 01:33:06 ERROR: ProcessBlock() : CheckBlock FAILED 2015-02-16 01:33:06 ERROR: CheckBlock() : Couldn't find masternode payment or pa yee 2015-02-16 01:33:06 ERROR: ProcessBlock() : CheckBlock FAILED 2015-02-16 01:58:15 ERROR: CheckBlock() : Couldn't find masternode payment or pa yee 2015-02-16 01:58:15 ERROR: ConnectTip() : ConnectBlock 00000000001373b3b2b886221 45e9800b93da3d667cc6ec5e223f6e36a643683 failed 2015-02-16 01:58:15 ERROR: CheckBlock() : Couldn't find masternode payment or pa yee 2015-02-16 01:58:15 ERROR: ConnectTip() : ConnectBlock 00000000001373b3b2b886221 45e9800b93da3d667cc6ec5e223f6e36a643683 failed 2015-02-16 02:17:43 ERROR: CheckBlock() : Couldn't find masternode payment or pa yee 2015-02-16 02:17:43 ERROR: ProcessBlock() : CheckBlock FAILED 2015-02-16 03:02:06 ERROR: CheckBlock() : Couldn't find masternode payment or pa yee 2015-02-16 03:02:06 ERROR: ProcessBlock() : CheckBlock FAILED 2015-02-16 03:30:50 ERROR: CheckBlock() : Couldn't find masternode payment or pa yee 2015-02-16 03:30:50 ERROR: ProcessBlock() : CheckBlock FAILED not good? i will delete everything and start from scratch That's super strange. Can you send me your logs? |
|
|
|
With enforcement on does it mean masternode with old version do not get payments?
Define "old version" but yes it should be restricted to Core releases (most recent protocol iirc). 0.11.0.13 or 0.11.0.14 - these are 1.1% ? The general rule is a masternode requires updating within 7 days after a release or they'll stop getting paid. |
|
|
|
From what we can tell there's a uncommon condition on the network (seems to be about 1 in 10 clients), where some databases have became corrupt. Please check your logs for these messages:
--
2015-02-15 17:34:26 ERROR: ReadBlockFromDisk : Deserialize or I/O error - ReadCompactSize() : size too large
OR
2015-02-15 17:34:26 ERROR: ReadBlockFromDisk : Errors in block header
---
If you find entries like that delete ~/.darkcoin/blocks and chainstate, then resync from the bootstrap:
https://github.com/UdjinM6/darkcoin-bootstrap
Thanks
|
|
|
|
Evan : i found a lot of them in my normal wallet (not a MN wallet) when i started it up just now.
2015-02-15 16:06:13 ProcessBlock: ACCEPTED
2015-02-15 16:06:13 CheckBlock() : fork detected, skipping transaction locking checks
2015-02-15 16:06:13 CheckBlock() : skipping masternode payment checks
2015-02-15 16:06:13 CheckBlock() : fork detected, skipping transaction locking checks
2015-02-15 16:06:13 CheckBlock() : skipping masternode payment checks
2015-02-15 16:06:13 UpdateTip: new best=000000000002129735ab9c6a64ac95d3d5483a261943f83f75f153ae458bc53f height=220605 log2_work=60.99049 tx=866830 date=2015-02-15 15:08:26 progress=0.999325
2015-02-15 16:06:13 ProcessBlock: ACCEPTED
Later on they disappear and turn into ''CheckBlock() : Found masternode payment 220624'' for example.
2015-02-15 16:16:51 ProcessBlock: ACCEPTED
2015-02-15 16:16:53 mnw - winning vote CTxIn(COutPoint(e3ae3784bf5b18997895f278f174870a77333c5bd5dcb18695b2e912f2eab78c, 1), scriptSig=) Height 220633 bestHeight 220623
2015-02-15 16:17:00 spork - new 0cd8b35cf3d8e12fb749a8bdd9d5e533d42ea84306aa2d3e0c93d6171c0c1114 ID 10000 Time 1420126342 bestHeight 220623
2015-02-15 16:17:01 CheckBlock() : fork detected, skipping transaction locking checks
2015-02-15 16:17:01 CheckBlock() : Found masternode payment 220624
2015-02-15 16:17:01 CheckBlock() : fork detected, skipping transaction locking checks
2015-02-15 16:17:01 CheckBlock() : Found masternode payment 220624
2015-02-15 16:17:01 UpdateTip: new best=0000000000002b06f0b8bfe973d77031f999c2a4087ec31e631db2a45c4c901d height=220624 log2_work=60.990674 tx=866914 date=2015-02-15 16:16:51 progress=0.999998
2015-02-15 16:17:01 ProcessBlock: ACCEPTED
so i assume my wallet received your spork settings and there is no need to sent you the debug.log ?
I was very vague, These are OK: 2015-02-15 15:56:43 CheckBlock() : skipping transaction locking checks 2015-02-15 15:56:43 CheckBlock() : Found masternode payment 220620 2015-02-15 15:56:43 CheckBlock() : skipping transaction locking checks 2015-02-15 15:56:43 CheckBlock() : Found masternode payment 220620 2015-02-15 15:56:43 UpdateTip: new The ones I'm looking for look like this, and they must be after block 220625: 2015-02-15 04:58:45 ProcessBlock: ACCEPTED 2015-02-15 04:58:45 CheckBlock() : skipping transaction locking checks 2015-02-15 04:58:45 CheckBlock() : skipping masternode payment checks 2015-02-15 04:58:45 CheckBlock() : skipping transaction locking checks 2015-02-15 04:58:45 CheckBlock() : skipping masternode payment checks 2015-02-15 04:58:45 UpdateTip: new best=000000000007397b7b443996254c0ae2bec814edb474fa9658ac3bf4a68e7d5d height=220310 log2_work=60.987778 tx=865814 date=2015-02-15 02:27:51 progress=0.998236 |
|
|
|
A short update about enforcement
As it turns out the enforcement code and strategy worked fine, but it just appears some clients lost the spork settings and other clients were coming and going and never received them. This is pretty easy to resolve, simply by having the reference node frequently send out spork settings to the network.
We've turned back on enforcement and everything looks fine so far. If you want to help out just look for "CheckBlock() : skipping masternode payment checks" in your logs. If you see that, shoot me an email to evan@darkcoin.io with your debug.log.
|
|
|
|
rpc error with daemon instance 0 when submitting block with submitblock {"code":-2,"message":"Safe mode: Warning: The network does not appear to fully agree! Some miners appear to be experiencing issues."}
Evan, please turn off enforcement.
No blocks found for 41 minutes in whole darkcoin network. MiningPoolHub is also suffering submitting new block.
If the main issue is the missing RPC (I guess so, you're running a pool ) you can add "disablesafemode=1" to your darkcoin.conf. It doesn't change the fact that your daemon sees some issues in the blockchain, but at least it answers to RPC calls again. Edit: seems drk.mn is stuck, current block is 220342 Network is definitely forked with explorers on blocks 220334, 220331, 220350 Enforcement is off, looking into the issue. |
|
|
|
|
Enforcement is on and everything looks good! Thanks for updating everyone
|
|
|
|
I didn't get paid for days because of these freaks, profiting on our back ...
We should be extremely careful with every major overhaul of the network ..
Our development cycles are going to start slowing down now that we have IX & DS out there and working properly. |
|
|
|
Evan, does this mean the noncomplying pools also have to update? Yes. Everyone must update or be forked. |
|
|
|
v0.11.1.25 - MANDATORY UPDATE
Due to some pools taking advantage of paying the incorrect masternodes (on purpose), enabling enforcement failed earlier today. Please update to the latest version of the software, 11.1.25, which includes a much stronger policy for enforcing masternode payments. This will also cause bans on any clients mining on the wrong chain. After the entire network updates (Pools, Exchanges, Masternodes, etc), we'll activate enforcement again.
https://www.darkcoin.io/downloads/
|
|
|
|
|
Show Posts
