Statements from Delegates Supporting BitShares 2.0 by Running 0.9.3

[cube]

*.bitcube will upgrade to 0.9.3 and cease producing blocks for BitShares 1.0 by 9AM EST on 13 OCT 2015

[iHashFury]

Standby delegate.ihashfury has updated to 0.9.3 and will support Bitshares 2.0

[betax]

I will be joining the witness party on 2.0. Ideally now 1 witness per company / person to avoid centralisation. That is the whole point  and let's see if we can have more than 101.

[BunkerChainLabs-DataSecurityNode]

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-reloaded

They will cease producing blocks for BitShares 1.0 at 9AM EST on Oct 13 2015

The following delegates will be taken OFFLINE and will no longer be operational on Oct 13 2015
www.minebitshares-com
www3.minebitshares-com

Delegates We Manage:

delegate.kencode
sollywood.sollars-com
delegate.rgcrypto

They will cease producing blocks for BitShares 1.0 at 9AM EST on Oct 13 2015

How 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?

I plan to in the future to provide a single witness. Looking at the whole situation with how the transition is happening I thought it would be better for now to maintain all my witnesses until after the transition is done. Sort of like when init1 init2 init3 etc made up the delegate space at first.. and once things got rolling others filled the space. So I felt it best to make all resources available through the transition and allow the votes to decide afterwards what will be needed to remain and then shutdown the rest as needed. In moving to one witness I would like the opportunity to create a new user identity that is more exactly identified with our corporation too. Until then, just want to make sure things move over smoothly.

[Empirical1.2]

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-reloaded

They will cease producing blocks for BitShares 1.0 at 9AM EST on Oct 13 2015

The following delegates will be taken OFFLINE and will no longer be operational on Oct 13 2015
www.minebitshares-com
www3.minebitshares-com

Delegates We Manage:

delegate.kencode
sollywood.sollars-com
delegate.rgcrypto

They will cease producing blocks for BitShares 1.0 at 9AM EST on Oct 13 2015

How 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?

[Ander]

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.

How does that make this an optional upgrade, as stated by bytemaster?

https://bitsharestalk.org/index.php/topic,18480.msg237028.html#msg237028

Its optional because we are all choosing to do it and vote for delegates that do it.  But if we all didnt want 2.0 we could choose otherwise.

[Xeldal]

*.xeldal and fund.bitsharesbreakout delegates will upgrade in due time. 

These 0.9.x servers will be taken offline after 2.0 snapshot on 13 Oct 2015.

With the launch of BitShares 2.0  these witness servers will be brought online to support the new 2.0 network.

[wackou]

Delegates wackou and btstools.digitalgaia on the BitShares 0.9.x network will support BitShares 2.0 by going offline when the snapshot for the genesis block of BitShares 2.0 is taken, currently scheduled for 9am EST on 13 Oct 2015.

When the BitShares 2.0 network comes up shortly after, they will come back up as witnesses, probably merging them into a single one at a later stage.

Eagerly waiting for the next testnet!

[puppies]

dele-puppy will upgrade to 0.9.3 in the next day or two.  I'm pretty busy with work, and I don't see this upgrade as super pressing.

I have multiple nodes in multiple jurisdictions rented from multiple companies ready to begin acting as a witness for 2.0. 

I have been very active in the testnet and will be ready to begin acting as a witness on day 1.  I am anxious to resume testing on the next testnet to ensure we are ready to upgrade as planned.

[CalabiYau]

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.

+5%

calabiyau will update in due time

[liondani]

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.

^THIS
+5%

[dannotestein]

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.

[liondani]

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?  ???

Good question.

there is no minimum required participation rate in BTS1 IIRC

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.

Even if we outvote the majority, the standby 0.9.2 delegates will automatically jump in... (the next ones with the most votes)
So it make more sense to concentrate o just up-voting 0.9.3 delegates...

[nomoreheroes7]

**waits for alphabar to campaign for the resurrection of BTS 1.0**....

:P

[maqifrnswa]

maqifrnswa and delegate1.maqifrnswa will upgrade to 0.9.3 and cease producing blocks for BitShares 1.0 at 9AM EST on 13 OCT 2015

both delegates will come on as witness nodes for as long as they are needed/useful in geographically distinct locations.

The PPA supported by these delegates will upgrade to bitshares 2.0 as well and be replaced by the worker proposal I'm floating around.