Anyone had stuck bitcoin transaction? I sent 5.5 btc about 6 hours ago, and still unconfirmed. I used blockchain.info wallet. I realized I included 0 fee. Anyone know what happens? I wanna make sure eventually it confirms? I sent it to cryptsy to get some DRK, but it is taking too long. Hope I catch it before next spike.
Transaction ID# 85708e444bfc505bc1320b73d9bc978427dc67ca7b7075691ae4d69a40b080bd
Try this, open the bitcoin client with --zapwallettxes. You'll notice your money is suddenly back, then change the fees so you pay something and try sending the money again. This will double spend your money, but the second transaction will have the fees to make it into a block. There's a very limited about of space per block that's allocated on the bitcoin network to free transactions, otherwise it'll take forever. |
|
|
|
I'm having an issue with v0.11.0.13-g90ad641-beta (64-bit). (Win zip file version).
Earlier versions were crashing for me today but this one synced up fine after using a December wallet backup and clearing out peers etc.
The issue is that most of my wallet balance has disappeared - yikes!
Specifically, I see three transactions, dated Jan 21 and 22 that seem to account for the missing amount. They are labelled "Darksend Denominate" and I'm guessing they were legitimately part of a recent Darksend Mixing episode that had looked normal before today, but it appears that the post-mixing return of the balance has disappeared.
Any thoughts on this?
Try running with -zapwallettxes Edit: More likely, -reindex Thanks for the suggestion, g4q34g4qg47ww but -reindex did not help. More detailed answer here: https://bitcointalk.org/index.php?topic=421615.msg10243367#msg10243367It looks for the moment that I have lost (almost) all my DRK. The underlying issue seems to be that my wallet got corrupted at about the time of a mixing session and/or the hassles with early versions of 11.0. My various backups either are before the mixing - and therefore useless, or after the corruption occurred - and therefore useless. I'm not sure what the underlying lesson is yet! We have excellent tools for recovering DRK from corrupt wallets . Try this: https://github.com/darkcoinproject/key_finder |
|
|
|
The issue was patched in Bitcoin Core 0.9.4 (released just a few days ago), we forked from 0.9.3. So they beat us to fixing it. It's funny though how r/Bitcoin reacts to stuff like this though... crazy. According to nullc (maxwell I think? Coinjoin inventor / darkcoin hater) the fix in darkcoin is incorrect? Yeah, I missed the later reference which still causes the client to crash, will be fixed in 11.0.13. |
|
|
|
v0.11.0.11This is the last protocol bump and we're moving back to testnet, sorry about all the updates I just wanted DS to be as secure as possible before moving on to InstantX. There's going to be 1 more version (11.0.12) after this with some stability fixes (still some segfaults happing for some people). - Protocol change: Masternode operators / Darksend users please update! - Fix unlocking wallet on ds toggle event (UdjinM6) - Fix incorrect DS txes + few small things including some cleanup / debugging (UdjinM6) - Implemented DarkSend convertability (thx Aswan/UdjinM6/Minotaur for the idea) Darksend defaults to a new mode which enables inputs/outputs of each session to be different. For example 10DRK can be input and 1DRKx10 can be output. This strengthens the anonymity of Darksend greatly, which also increasing the usability (Users who run out of .1DRK denominations can simply turn on Darksend to split up larger inputs). https://darkcointalk.org/threads/0-11-0-darkcoin-core-release.3601/page-16
|
|
|
|
|
The network has updated to v11 (about 95% of the miners) and enforcement is back on! Everything looks good
|
|
|
|
|
Anyone gotten money out of Mintpal? I have a friend who's DRK is stuck in there.
|
|
|
|
this needs to be fixed... he's running an old version, not doing anything for the network but getting paid 2x in 1 hr. Date Found Height Found by Difficulty Gen+Fees MN Payment MNP Ratio
Expected/Actual Masternode Masternode version
1 minute ago 206561 miningpoolhub 2794.7 5.0015 1.75052 35%/35% XdLQCURemVDnHzRFN7W2CyBWiby7nG2jWa Core (0.11.0.10+)
42 minutes ago 206548 miningpoolhub 2785.11 5 1.75 35%/35% XdLQCURemVDnHzRFN7W2CyBWiby7nG2jWa Core (0.11.0.10+) There were network issues from the switch from v10 to v11, so I had to turn enforcement off for the time being. After the network updates, we'll stop paying old nodes and they'll be paid on a schedule again. |
|
|
|
11.0.10 Core - All UsersDownloads: https://darkcointalk.org/threads/0-11-0-darkcoin-core-release.3601/page-12#post-37320Darksend users please update and remix your coins to try this and improve your anonymityNearly perfect darksend ( https://github.com/darkcoin/darkcoin/commit/bbd869589cb08945680627d60c5c091cbd2e8208). - Found the collateral issue that's been causing users to get charged when they shouldn't be. Now collateral should be charged in about 1 in 40 sessions. - Improvements to DS anonymity - no change will ever be returned to a user in a pool. - DS Anonymity improvements for smaller wallets (will have a positive effect on all wallets though) - DS should also be much faster at mixing - EXACT DS anonymitizing amounts are now supported (UdjinM6) - There's a known issue anonymizing small amounts of DRK, try larger amounts if you have any problem (UdjinM6 is working on this) Performance improvements- Found the top 5 reasons why performance is suffering for the Darkcoin client and fixed them. Now performance should be similiar to Darkcoil unless you're running Darksend mixing (DS is intensive on the CPU) InstantX - I'm officially moving onto finishing implementation of InstantX, expect more great things in the near future 
|
|
|
|
Looks like your blockchain is corrupt, we've seen a lot of this when upgrading from v10 to v11. 27 org.darkcoinfoundation.Darkcoin-Qt 0x000000010025cbae leveldb_error::~leveldb_error() + 108750
28 org.darkcoinfoundation.Darkcoin-Qt 0x000000010025b355 leveldb_error::~leveldb_error() + 102517
29 org.darkcoinfoundation.Darkcoin-Qt 0x000000010025e322 leveldb_error::~leveldb_error() + 114754
30 org.darkcoinfoundation.Darkcoin-Qt 0x000000010026098f leveldb_error::~leveldb_error() + 124591
31 org.darkcoinfoundation.Darkcoin-Qt 0x0000000100261fa4 leveldb_error::~leveldb_error() + 130244
32 org.darkcoinfoundation.Darkcoin-Qt 0x000000010026de42 leveldb_error::~leveldb_error() + 179042
33 org.darkcoinfoundation.Darkcoin-Qt 0x000000010024350d leveldb_error::~leveldb_error() + 4653 Can you try syncing from scratch and see if that helps? It should just go away |
|
|
|
Yep, windows link should be fixed. Let's wait for @edufield or @flare to do this.
EDIT: Sorry guys, I removed the direct link as it brings too much traffic
Opps, fixed. |
|
|
|
Version 11.0.9 has been released!Change Log:
11.0.8 / 11.0.9:
- Version bump: Masternodes / Darksend users please update!
- Removed non-denomational inputs, this vastly improves the anonymity provided by the system by removing any traceable element into the mixing of coins (UdjinM6)
- Sessions now have randomized maximum amounts, also improving the anonymity
- corrected getblocktemplate coinbasevalue output, causing some mining issues
- "--litemode" added, which allows the client to run without Darksend, Masternodes or InstantX but still be compatible with the network (for slower computers or if you're not using any of that technology)
- MacOSX is now fixed and supported (flare and UdjinM6)
https://darkcointalk.org/threads/0-11-0-darkcoin-core-release.3601/
|
|
|
|
Sigh....We have not seen over 0.007 since 16th November last year.....
I wonder when we will finally break free and attain our true value
Alas, what is our true value? LOL. Note: 686 views on the Bitcoin Rush show. Even if everyone doesn't like it, at least we've gotten a lot of people to look and they have been informed  Finally, I'm wondering if enforcement is off again for the upgrade because one of my nodes is overdue for payment by a while, and the other node has gotten more than it should have. Both seem to be functioning well, on the right block and running the latest version? Enforcement is off while the network updates to v11. As soon as we have 80%, it'll turn back on. |
|
|
|
Evan -- the Spreadcoin dev is supposedly working on allowing masternodes to have dynamic IPs: https://bitcointalk.org/index.php?topic=715435.msg10193497#msg10193497Initial masternode implementation will not require you to have a static IP. Instant transactions simply don't require this: someone broadcasts transaction, masternode receive this transactions, sign it and broadcasts this signature, there is no need for anyone to directly connect to masternodes. Nodes will monitor time delays between receiving transactions and confirmations from masternodes and will assign scores for each masternode according to these delays. This score and deposit amount will affect which masternodes will receive payments.
What is actually important here is not a whether your IP address is static or dynamic but whether or not you can accept incoming connections. I want to make it optional in the future so that if your masternode can accept connections you will broadcast your IP address, if your IP address is dynamic then you will just broadcast another message to announce your new address. Both initiator of transaction and masternodes want to confirm transaction as fast as possible and initiator will be able send transaction directly to required masternodes, since this will decrease delays between transactions and confirmations masternodes which can accept connections will be valued higher.
Requiring masternodes to have static IPs and accept connections makes network more centralized because many people will run their masternodes on hostings like Amazon, we don't want many of our masternodes to be located in the same datacenter, right? Possibility to rebroadcast your address fixes this at least partially because you don't need to have static IP and may be able to accept connections on your home computer (this depends on your ISP). Is there any possibility of us doing this? I currently spend over $80.00 per month on VPS and going up. At some point when I'm done buying DRK, I will need to sell DRK each month to cover my VPS costs and I'm sure others will do the same, causing downward price pressure. But I have a 100mb pipe available to me and a load of laptops. If I was able to use dynamic ips, I could save a boatload of money and not pressure DRK with eventual sells. The IP obfuscation technology I'm working on supports local IPs. The direction we were going is to create a multi-path communication technology, where traffic flows through the peers, not directly. However, I'm not sure it's a good idea to allow local IPS. We want the masternode network to run on high quality datacenters for the most part, for the syncing capabilities, propagation, Darksend and InstantX. High quality machines will make a much more robust network. |
|
|
|
Does anyone know how long a node must be offline to be out of the payment cycle? Is restrarting a node with -reindex going to put me out of the cycle?
71 minutes and no. |
|
|
|
Happy Birthday Darkcoin and great job everyone  . I'm really excited to see what we can do next year! |
|
|
|
|
Show Posts
