Search results

Yep, that's fine. The InstantX data is not persistent (yet anyway).

Yeah, you definitely can't spend them until they're confirmed via block confirmation. IX just tells you the transaction went through successfully.

***************************** Please update to 11.1.1 : InstantX Release ***************************** Version bump Source: https://github.com/darkcoin/darkcoin/tree/v0.11.1.x Windows 32bit: http://bamboo.darkcoin.qa/artifact/DRKW-DEV/JOB1/build-91/gitian-win-darkcoin-bin/32/darkcoin-qt.exe...

Compiling v0.11.1.1 right now, I forget to bump the protocol version which will be required for IX

***************************** Please update to 11.1.18 : InstantX Release ***************************** InstantX will begin working when we have ten masternodes updated on testnet. - Enabled InstantX and fixed all known issues. Please help test! - Improvements to DS - Many new languages are...

I'm happy to see DS is finally working pretty well for everyone :grin:

Actually the GetTime() function uses the average timestamps of recent blacks to calculate the current time. It's more like the current network time. But something like nTimeCap makes sense, seems like I could actually just reverse the nLockTime patch. Masternodes have no incentive to cash in...

Please welcome, Mario Müller, otherwise known as Aswan. Mario officially joins the team after discovering various ways to improve the robustness of anonymity provided by Darksend, including "Dead Change". Mario will help out by continuing his work to attempt to de-anonymizing DarkSend...

. Thankfully I've known about this one and already have a strategy to fix it, I just haven't had time to implement it yet. It's rather simple, when the participant makes the collateral transaction, they currently use the normal CScript, which is OP_DUP OP_HASH160 OP_EQUALVERIFY OP_CHECKSIG...

Ah ha, awesome. Thank you tungfa

Thanks Minotaur, Fernando and tungfa for spearheading this project, I'm really excited to see the results. :wink:

11.0.14 Core - All Users This update is not required - Improved syncing speed (eduffield) - Improved pre-mixing to create denominated amounts (UdjinM6) - Update darkcoin-qt.desktop (vertoe) - fix overpaying for DSTX - If you're using Darksend, please update (eduffield) - make collateral inputs...

When you have a consistent list of masternodes via blockchain technology, it's pretty easy to deterministically generate the winning node per block. I have a pretty decent implementation of a deterministic round robin algorithm I wrote that will work quite well and be very fair.

Now that the network has updated to version 11 and is stable, I thought it might be a good idea to lay out what the next we have in store for the next release and future plans. We’ll be leveraging our larger development team and working on a few projects at once to enable to a few new exciting...

Example Darksend Transaction: As an example of the type of anonymity Darkcoin provides, I’ve listed a fully anonymous transaction here. This transaction went more than 10 layers deep (mixed funds went through the process on more than 10 separate masternodes, each with 3 total participants)...

It’s a well known fact that the anonymity of Bitcoin is trivial to break, and many projects have started with an intention to bring anonymity to digital currency to protect consumers and businesses. Darkcoin is the first privacy-centric digital currency. Founded in 2014, Darkcoin uses its...

11.0.13 Core - All Users - This includes the full fix to the segfault issue from Bitcoin. Source: https://github.com/darkcoin/darkcoin Windows .exe: https://github.com/darkcoinproject/darkcoin-binaries/raw/master/darkcoin-0.11.0.13-win.zip Mac OSX...

enforce_masternode_payments is always true now, the spork has been removed. However, the network is in "fallback" mode, where miners pick who to pay and nothing is enforced. I'll turn back on the reference node when everything is stable and everyone is up-to-date. It's a bit confusing and...

v0.11.0.12 - Fixed 2 segfault causes, 1 due to a null reference in the Bitcoin code (https://github.com/bitcoin/bitcoin/issues/5698) upon a fork and the later due to the Bitcoin core code modifying the coins view without a lock on mempool.cs. The client should be much more stable now. - Fixed...

That's completely supported by the reference node, but first we need a stable version with no crashes (should be v11.0.12) and enforcement turned on successfully.