Topic: BTCD is no more - page 56. (Read 1328503 times)

Thanks James!

not for a while. I dont want the hardfork to delay the pending releases, so will only be able to work on it here and there.

once the tech is done, then we will need to verify it follows the current network on various nodes. then we can schedule a hardfork block far enough into the future to give everyone a chance to switch.

then the hardfork release is deployed, we wait, the mainchain switches from old version to new version.  I will try to make it use the existing wallets, but it seems a good idea to put the data in a separate directory, ie. ~/.BitcoinDark2

So, even if the tech is ready now, it would be approx 1 month for validating that it properly follows the existing chain, then probably another month ahead for the hardfork block.

There will be plenty of notice. Maybe it would be cool to have it switchover on its birthday, but I dont want to commit to any specific date until the tech is done.

James

If this is going to happen, when will it be?

yes, everyone will have to update, that is why I want to make sure the vast majority are ok to do this

Voted yes - because it sounds like the common sense thing to do.

Presumably (and forgive my technical ignorance) the hard fork will necessitate an upgrade to the BTCD wallet. I'm currently running v.1.0.0.0

I didn't vote yet because I am confused a bit.
I thought btcd was going to improve btc and other coins. Now I see btc will help improve btcd. 

I voted for "yes". I my opinion the changes are too important in order to let them not go into the core.

Can't vote (due to my member status?): My vote is "yes"!

Maybe he means dividents

Voted!! i am agree 1000% 

Attention BitcoinDark community, Please read Jl777's message above and vote in the new poll!!!

which works out to ~365/6500 -> 5.6%, well within expected range

I guess if dust amounts (< 0.0001) are being staked that would be less than 1 BTCD staking, which would indeed stake dust amounts

From my experience, it seems one can earn approximately 1.0 BTCD per 24 hours by staking between 6k and 7k BTCD.

5% per year
how much are you staking?

Seems that the stake reward is dust.
Help me out, why is it?

Thanks for the memory-jog. I (regretfully) sold the bulk of my BTCD some time ago, but these low prices gave me a chance to refill my bag.

Tweeted!! https://twitter.com/MagicNxt/status/725814903022469121

I posted in slack about a 0.12 hardfork to very positive reaction, so I will describe here the plan:

Currently iguanacore is in testing of the RPC layer, this will allow iguanacore to be a dropin replacement for BitcoinDarkd/bitcoind for all except creating new blocks. During the transition phase, we still need the normal BitcoinDarkd nodes to create the blocks.

However, yesterday I studied the exact staking method and also the 0.12 codebase and realized I could relatively quickly get a BTCD0.12 release, once the staking code is put into an isolated module. I did get a 0.12 to start syncing with the existing BTCD network, but the protocol has changed enough that it didnt really get going, other than to find some peers after genesis

In my opinion, the safest path is to update the BitcoinDarkd to the 0.12 codebase and have it take over the block generation. The iguanacore would be able to submit staked blocks to the network, but by having the 0.12 nodes doing the actual new block creation, we will benefit from all the improvments in the bitcoin codebase. especially regarding all the various fork resolutions.

Eventually, iguanacore will handle all this, but by having the 0.12 nodes take this over, it allows a faster deployment. Also, it will allow me to create a (0.12 <-> iguanacore) interop network and enhance the 0.12 codebase with other iguana interop features.

as a bonus, I also figured out an enhanced staking that will add value to the staking process, but I dont want to disclose details until I get at least a proof of concept working.

This would require a hardfork, which means older nodes will eventually go off onto their own fork. So all nodes would need to upgrade. We can make it so that the 0.12 is deployed well ahead of time in a follow the existing chain mode, until the hardfork block. At that time, it takes over block generation.

The following are the release points, without the 0,12:

1. bitcoin RPC compatible
2. instantdex API stable
3. tradebots API stable
4. pangea API stable
5. PAX API stable
6. asset passport API stable

The RPC compatible iguanacore is doing quite well in testing and once that is released, theoretically all existing bitcoin RPC apps would be able to work with it.  We will test it with MGW and a few other standard bitcoin RPC based apps.

Now, I am speaking about the iguanacore and not the GUI, which is quite independent of the core by using the bitcoin RPC as the interface layer.

Assuming the community wants the 0.12 hardfork, we need someone to coordinate it. I will disclose to the hardfork coordinator the new enhanced staking, so proper marketing plans for that can be made. I just dont have time to deal with all the non-technical aspects for the hardfork

James

P.S. There is also the chrome app release that will require existing nodes to be deployed first, so that is not a specific release point.

It's a good question, I am also wondering if I should buy some.