Quote from: number435398 on October 06, 2018, 08:57:25 PM

Quote from: Chicago on September 21, 2018, 05:49:44 PM

Quote from: layer1gfx on April 07, 2018, 10:36:17 PM

as mentioned before, a DEcentralized Dexchange would be more cool and noodlier

Hey what's up?

I've been down this road a bit -- and wanted to share the following.
NoodlyAppendageCoin will need to do a network upgrade in order to participate in DEX.

Basically, the v0.10.4 Bitcoin code gets the job done as it brings SuperMajority for BIP 66 and BIP 65.

It is BIP 65 which enables DEX.

Best Regards,
-Chicago

What more do you have on that? I've nearly completed upgrading to Bitcoin and Litecoin version 0.16.3. What exactly do you mean by "network upgrade"?

Hello,

So the "network upgrade" means features have been integrated by the block version changing through SuperMajority or otherwise via a softfork.

For example, BIP 34 would have its enforcement hash defined here:
https://github.com/bitcoin/bitcoin/blob/49e34e288005a5b144a642e197b628396f5a0765/src/chainparams.cpp#L80-L81

There are also remnants of where BIP 66 becomes active.
https://github.com/bitcoin/bitcoin/blob/49e34e288005a5b144a642e197b628396f5a0765/src/chainparams.cpp#L83

Similarly you will find a remnant of where BIP 65 becomes active.
https://github.com/bitcoin/bitcoin/blob/49e34e288005a5b144a642e197b628396f5a0765/src/chainparams.cpp#L82

Other parts of the network upgrade are where BIP 9 softforks would start.

For example, CSV.
https://github.com/bitcoin/bitcoin/blob/49e34e288005a5b144a642e197b628396f5a0765/src/chainparams.cpp#L97

Or SegWit.
https://github.com/bitcoin/bitcoin/blob/49e34e288005a5b144a642e197b628396f5a0765/src/chainparams.cpp#L102

==========

If you inspect the same src/chainparams.cpp file in the 0.13 branch's last release you will see the only specific block height with regards to network upgrades which must be hard-coded is for the version 2 block enforcement with BIP 34.

https://github.com/bitcoin/bitcoin/blob/v0.13.2/src/chainparams.cpp

-- and in that file you would be able to set nStartTime / nTimeout for the BIP 9 softfork activation for CSV and SegWit -- which left unmodified will never upgraded on this network and otherwise would be marked "failed" in the getblockchaininfo output because the triggers for them are for 2016 - 2017.

Best Regards,
-Chicago