0 Members and 1 Guest are viewing this topic.
The following delegates have been upgraded 0.9.3:riverhead-del-server-1backbone.riverheadbm.payroll.riverheadmarketing.methodxargentina-marketing.matt608fuzzy.beyondbitcoinI will campaign for a witness position in 2.0 running on a dedicated, hosted, server. Note this is not a VPS but a standalone box hosted in a data center.
dev0.theoretical will upgrade sometime before Oct. 1.
*.bitcube will upgrade to 0.9.3 and cease producing blocks for BitShares 1.0 by 9AM EST on 13 OCT 2015
Quote from: DataSecurityNode on September 17, 2015, 01:10:40 pmThe following delegates we represent will be upgraded to 0.9.3:minebts1.bunkermining-com minebts2.bunkermining-com minebts3.bunkermining-com minebts4.bunkermining-com minebts5.bunkermining-com minebts6.bunkermining-com minebitshares-reloadedThey will cease producing blocks for BitShares 1.0 at 9AM EST on Oct 13 2015The following delegates will be taken OFFLINE and will no longer be operational on Oct 13 2015www.minebitshares-comwww3.minebitshares-comDelegates We Manage:delegate.kencodesollywood.sollars-com delegate.rgcryptoThey will cease producing blocks for BitShares 1.0 at 9AM EST on Oct 13 2015How many witnesses are you planning to run in 2.0?While there was an argument for having multiple delegates, running more than 1 witness would be fairly redundant in terms of effective decentralisation?
The following delegates we represent will be upgraded to 0.9.3:minebts1.bunkermining-com minebts2.bunkermining-com minebts3.bunkermining-com minebts4.bunkermining-com minebts5.bunkermining-com minebts6.bunkermining-com minebitshares-reloadedThey will cease producing blocks for BitShares 1.0 at 9AM EST on Oct 13 2015The following delegates will be taken OFFLINE and will no longer be operational on Oct 13 2015www.minebitshares-comwww3.minebitshares-comDelegates We Manage:delegate.kencodesollywood.sollars-com delegate.rgcryptoThey will cease producing blocks for BitShares 1.0 at 9AM EST on Oct 13 2015
Quote from: Troglodactyl on September 17, 2015, 12:55:58 pmThis is why supporters of the upgrade should try to vote out every single 0.9.2 delegate before the 13th. Doing that will make it a "pitchfork" rather than a plain and simple snapshot because the original chain will terminate by protocol and we'll jump to the new chain.How does that make this an optional upgrade, as stated by bytemaster?https://bitsharestalk.org/index.php/topic,18480.msg237028.html#msg237028
This is why supporters of the upgrade should try to vote out every single 0.9.2 delegate before the 13th. Doing that will make it a "pitchfork" rather than a plain and simple snapshot because the original chain will terminate by protocol and we'll jump to the new chain.
It's a bit early to be voting delegates in/out for this. Let's wait a few days, and not put pressure on delegates to update to new version all at once.
Quote from: xeroc on September 17, 2015, 08:09:28 amQuote from: DataSecurityNode on September 17, 2015, 07:56:13 amQuote from: liondani on September 17, 2015, 07:27:46 amI would love somebody explains all scenarios....If even only 5 delegates for example don't upgrade the chain will "survive"(?). So after the snapshot it will be still possible to sell BTS1.0 shares on the exchanges? Good question.there is no minimum required participation rate in BTS1 IIRCThis is why supporters of the upgrade should try to vote out every single 0.9.2 delegate before the 13th. Doing that will make it a "pitchfork" rather than a plain and simple snapshot because the original chain will terminate by protocol and we'll jump to the new chain.
Quote from: DataSecurityNode on September 17, 2015, 07:56:13 amQuote from: liondani on September 17, 2015, 07:27:46 amI would love somebody explains all scenarios....If even only 5 delegates for example don't upgrade the chain will "survive"(?). So after the snapshot it will be still possible to sell BTS1.0 shares on the exchanges? Good question.there is no minimum required participation rate in BTS1 IIRC
Quote from: liondani on September 17, 2015, 07:27:46 amI would love somebody explains all scenarios....If even only 5 delegates for example don't upgrade the chain will "survive"(?). So after the snapshot it will be still possible to sell BTS1.0 shares on the exchanges? Good question.
I would love somebody explains all scenarios....If even only 5 delegates for example don't upgrade the chain will "survive"(?). So after the snapshot it will be still possible to sell BTS1.0 shares on the exchanges?
this summer
How does that make this an optional upgrade, as stated by bytemaster?https://bitsharestalk.org/index.php/topic,18480.msg237028.html#msg237028
Quote from: xeroc on September 17, 2015, 08:09:28 amQuote from: DataSecurityNode on September 17, 2015, 07:56:13 amQuote from: liondani on September 17, 2015, 07:27:46 amI would love somebody explains all scenarios....If even only 5 delegates for example don't upgrade the chain will "survive"(?). So after the snapshot it will be still possible to sell BTS1.0 shares on the exchanges? Good question.there is no minimum required participation rate in BTS1 IIRCso practically if exchanges don't take measures (freeze the market etc.) We will have the "opportunity" for a massive sell off ...PS It will be disastrous for the reputation of an exchange if they don't stop/abandon bts1.0 market.... hope they are all informed
Not really .. since all assets are 1:1, we don't see a SNAPSHOT but a HARDFORK (kind of)
What would it mean for the BTS market itself though?
BitShares 0.9.3 has been released: https://github.com/bitshares/bitshares/releases/tag/bts%2F0.9.3This release will stop block production on October 13th at 9AM EST and adds new API calls for exporting the wallet for Graphene. If delegates do not wish to stop producing blocks at the stated date/time then they need not upgrade. If you are a seed node then you do not need to upgrade.