Statements from Delegates Supporting BitShares 2.0 by Running 0.9.3

[liondani]

39% of delegates don't officially support BitShares 2.0 running v0.9.3.... http://bitsharesblocks.com/delegates And the most of them are Chinese(?)... Should I assume that the plan for them is to dumb bts1.0  shares to exchanges that will continue to trade bts1? (like bter(?) and btc38(?)) Do we know which exchanges will continue to support bts1.0? Do we know which exchanges will migrate bts2.0? (poloniex etc.)
A list of the exchanges that made official announcement's  about bts2.0 support would be appreciated.
I personally will put exchanges, that will continue support of bts1, to my blacklist!

delegates/witnesses  be aware to publish feeds only from exchanges that will support bts2.0 migration. It would be wise 80%of published feeds to come from poloniex (since they have the most volume and officially have stated that they will support the migration )....

[liondani]

Obviously I support too the transition to the Graphene(bts2.0) chain on 13 October so I updated to version 0.9.3c for the delegates under my control:   

delegate.liondani   http://bitsharesblocks.com/delegate/info?name=delegate.liondani
jcalfee1-developer-team.helper.liondani  http://bitsharesblocks.com/delegate/info?name=jcalfee1-developer-team.helper.liondani
martin-38ptswarrior-raum http://bitsharesblocks.com/delegate/info?name=martin-38ptswarrior-raum

[rnglab]

The following delegates have been upgraded 0.9.3:

riverhead-del-server-1
backbone.riverhead
bm.payroll.riverhead
marketing.methodx
argentina-marketing.matt608
fuzzy.beyondbitcoin

I 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.

Many thanks for the upgrade Riverhead.

bitshares-argentina would like to campaign for a witness too. We think this respectable position would complement with our commitment on local community building, being a trusted referent for both Argentinians interested in implementing BitShares technology in their businesses as for foreign companies looking to apply it locally.

[BunkerChainLabs-DataSecurityNode]

All of the following delegates have been updated to the latest version 0.9.3c

minebts1.bunkermining-com
minebts2.bunkermining-com
minebts3.bunkermining-com
minebts4.bunkermining-com
minebts5.bunkermining-com
minebts6.bunkermining-com
minebitshares-reloaded
www.minebitshares-com
www3.minebitshares-com

Delegates We Manage that have also been upgraded to 0.9.3c:

delegate.dposhub-org
delegate.kencode
sollywood.sollars-com
delegate.rgcrypto

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

[liondani]

dev0.theoretical will upgrade sometime before Oct. 1.

me2

[theoretical]

dev0.theoretical will upgrade sometime before Oct. 1.

[xeroc]

Remark: cube upgraded the node of my witness with my approval!

Thx for the great service!!

[cube]

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

bitcube, dev-pc.bitcube, payroll.delegate.xeroc are upgraded to 0.9.3. It was a smooth operation.

[ag]

I added one hundedth of a percent to all of you on 0.9.3 ( a symbolic gesture! ) in advance of taking down my node.

[Riverhead]

The following delegates have been upgraded 0.9.3:

riverhead-del-server-1
backbone.riverhead
bm.payroll.riverhead
marketing.methodx
argentina-marketing.matt608
fuzzy.beyondbitcoin

I 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.

[triox]

triox-delegate updated to 0.9.3; looking forward to Bitshares 2.0

[CalabiYau]

calabiyau has updated to 0.9.3 - supporting BitShares 2.0

[clayop]

delegate-clayop supports BitShares 2.0 and has upgraded to 0.9.3

[kokojie]

I have upgrade my delegate "kokojie" to 0.9.3 and will support Bitshares 2.0

[38PTSWarrior]

martin-38ptswarrior-raum will transition into 2.0 with the help of master delegate liondani. Should be a smooth ride.

[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.

 

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
 

[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**....

 

[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.

[xeroc]

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

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

you can downvote 0.9.3! delegates and have the chain continue ..

[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

[monsterer]

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

[Troglodactyl]

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.

[Akado]

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

so 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 

Exchanges trade IOUs, shouldnt they be able to resume trading and then upgrade when they can? Maybe they can disable deposits and withdrawals temporarily if needed but they can resume trading within the exchange. It's just IOUs

[liondani]

i will make the upgrade and support it after I am more confident using the official testnet devshares2.0 client...
Imagine we must downgrade to 0.9.2 again at some point!!!

So please announce the devshares0.9.3 that will hard fork to devshares2.0 in 1 week for example from now @bytemaster

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

[monsterer]

Not really .. since all assets are 1:1, we don't see a SNAPSHOT but a HARDFORK (kind of)

It's a snapshot. Plain and simple.

[xeroc]

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

so 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) .. hence exchanges that do not upgrade their users will not be able to withdraw their funds ..

BTS2.0 is doing a PITCH FORK (read: hard fork) .. not a snapshot!!

What would it mean for the BTS market itself though?

All trades after the pitch fork will trade worthless tokens in a network that no one will honor .. (IMHO)

[spartako]

spartako, spartako1 and spartako2 active delegates updated to 0.9.3 (see http://bitsharesblocks.com/delegates)
and ready to produce 2.0 blocks at launch (active witness in previous test net)

[liondani]

Now I am thinking about it again...
Have the exchanges the right to freeze the market for bts1.0? I don't' think so !!!!!
What if some customers don't want to make the transition to bts2.0? How can a exchange make a decision for them ?...

[monsterer]

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? 

It'll be a massive double spending mess if exchanges do not disable their wallets before d-day.

[BunkerChainLabs-DataSecurityNode]

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

so 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 

What would it mean for the BTS market itself though?

[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

so 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 

[xeroc]

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

[xeroc]

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

[BunkerChainLabs-DataSecurityNode]

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.

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

[jsidhu]

Are exchanges going to halt trading hours or day before until a few hours after to prevent mass selloff and confusion like pts was?

[Ander]

Let us do what bitcoin cannot: fork successfully into a new and improved version, with community consensus.

When we get closer to Oct 13 I will remove votes from delegates that are not on version 0.9.3 and will vote for alternate delegates which are on 0.9.3.

[Fox]

Fox has upgraded all delegate nodes to 0.9.3

Fox will cease producing blocks for BitShares 1.0 at 9AM EST on 13 OCT 2015

Fox will have a set of geographically diverse witness nodes stage and online on 13 OCT 2015 available to publish blocks for BitShares 2.0 upon launch

[Fox]

BitShares 0.9.3 has been released:  https://github.com/bitshares/bitshares/releases/tag/bts%2F0.9.3

This 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. 

All delegates committed to transitioning from the existing BitShares network to BitShares 2.0 should upgrade their node(s) to 0.9.3, publish their version to the blockchain and be ready to produce 2.0 blocks using the Graphene codebase upon launch 13 OCT 2015. 

Stakeholders should watch each delegate's published versions (both active and stand by) and their statements below, then adjust their votes to support delegates that (will) produce blocks for the network they intend to follow after the announced hard fork time.  An updated list is visible at the bitsharesblocks website [1].

Stakeholders should take care to ensure their wallet client software and that of the third parties they may interface with also follow the chain of your choice after the hard fork.  These choices are yours to evaluate and act upon.  Decentralization welcomes you.

[1] http://bitsharesblocks.com/delegates