You are viewing a single comment's thread from:

RE: Forum steem

in #tokenbb6 years ago

Topic: HF Timeline Updates


For public reference there is currently discussion about a testnet being released soon and a tentative HF date being proposed for the 6th of August 2019, giving exchanges 30 days notice from the 6th of July.


View this topic on TokenBB

Sort:  

Reply to HF Timeline Updates


Isn't it kinda risky giving notice to exchanges that early in advance? Considering that a sucessful fork depends on 17/20 witnesses adopting the new software. If a HF failed, wouldn't that really mess with exchanges that were expecting a HF at that date and time?


View the topic on TokenBB

Reply to HF Timeline Updates


I believe there will be someone on hand all the time from Steemit.com liaising with the exchanges. I'm sure there will be a bit of exchange downtime but it will be managed, just giving them the heads up early to expect the change.


View the topic on TokenBB

Reply to HF Timeline Updates


@southernwolf, I have received better info from @smooth regarding how forks work with exchanges:

The way this works with most blockchain projects, most if not all of which are fundamentally experimental in some sense, is the devs tag a release and exchanges are advised to upgrade right at that point, which means 30 days notice to exchanges starts from the tag. Even if the fork ends up not activating, then assuming competent devs, there should be no ill effects from running the new release (and it may indeed have some beneficial non-fork bug fixes or improvements).


View the topic on TokenBB

Reply to HF Timeline Updates


From @smooth: To clarify though, tagged release is different from tagged release candidate. Until there is a release (which means release candidate has been available sufficiently for public testing including a public testnet), Once that process is complete then you get an actual tagged release.


View the topic on TokenBB

Reply to HF Timeline Updates


...upgrading just means that your node will switch over if the fork activates, but otherwise it will still continue functioning normally. By contrast if you don't upgrade and the fork does activate, your node will halt. Or to put it another way, under normal conditions there isn't ever a reason to not upgrade a non-witness node (abnormal conditions would include there being multiple competing forks and then it might not be clear what to upgrade to).


View the topic on TokenBB