Main Menu

New release 2.0.151209

Started by theoretical, December 09, 2015, 11:57:01 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

clayop

delegate-clayop is updated to v2.0.151215
Bitshares Korea - [url="http://www.bitshares.kr"]http://www.bitshares.kr[/url]
Vote for me and see Korean Bitshares community grows
delegate-clayop

Bhuz

Quote from: Akado on December 16, 2015, 01:53:30 PM
Or since all the blocks are produced by witnesses and they have updated, they will be the ones "handling" the fork and everyone will be automatically stay in the right chain?
This

monsterer

Quote from: ngkong on December 16, 2015, 02:31:10 PM
I've just upgraded and all tx id changed? anyone can confirm?

For example tx id was 1.11.13306 , now it is changed to 1.11.13305.

My system rely on this tx id, as the result i get a lot of duplicate deposits recently, and forced to roll back our bts deposits.

I assume this tx id is not reliable for identifying a transaction? Are we doing it wrong?

Thank you

That would a completely critical failure - @bytemaster, @xeroc can you confirm
My opinions do not represent those of metaexchange unless explicitly stated.
[url="https://metaexchange.info"]https://metaexchange.info[/url] | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

ngkong

I've just upgraded and all tx id changed? anyone can confirm?

For example tx id was 1.11.13306 , now it is changed to 1.11.13305.

My system rely on this tx id, as the result i get a lot of duplicate deposits recently, and forced to roll back our bts deposits.

I assume this tx id is not reliable for identifying a transaction? Are we doing it wrong?

Thank you

spartako

spartako updated to v2.0.151215
wallet_account_set_approval spartako

Akado

#41
Shouldn't it be a release version for the light client users too since there will be a hardfork today? All I see is the cli_tools.exe which I think is for whoever is running the CLI like witnesses?

Or since all the blocks are produced by witnesses and they have updated, they will be the ones "handling" the fork and everyone will be automatically stay in the right chain?
[url="https://metaexchange.info"]https://metaexchange.info[/url] | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Harvey

harvey-xts updated
v2.0.151215
BTS       Witness:harvey-xts Seed:128.199.143.47:2015 API:[url="wss://128.199.143.47"]wss://128.199.143.47[/url]:2016 
MUSE   Witness:harvey-xts Seed:128.199.143.47:2017 API:[url="ws://128.199.143.47:2018"]ws://128.199.143.47:2018[/url]

BunkerChainLabs-DataSecurityNode

datasecuritynode updated to v2.0.151215
+-+-+-+-+-+-+-+-+-+-+
[url="//www.peerplays.com"]www.Peerplays.com[/url] | Decentralized Gaming Built with Graphene - Now with BookiePro and Sweeps!
+-+-+-+-+-+-+-+-+-+-+

abit

#38
@theoretical @cass Another URGENT update released?
https://github.com/bitshares/bitshares-2/releases/tag/v2.0.151215

"All full nodes will need to upgrade to this release by Thu 2015-12-17 at 19:00 UTC", it's just one day after the coming hard-fork introduced by v2.0.151209.
BitShares committee member: abit
BitShares witness: in.abit

taoljj

witness delegate.taolje updated
BTS      Witness: delegate.taoljj

sudo

BitShares-2.0.151209-x64-cli-tools.exe

why no 32bit?

Samupaha

Quote from: theoretical on December 09, 2015, 11:57:01 PM
Cleanup

- Remove unsupported full_web_node and light_client #457

Files seem to be still included.

alt

#34
witness delegate.baozi updated
but why can't get the new api?

locked >>> propose_builder_transaction2
propose_builder_transaction2
10 assert_exception: Assert Exception
itr != _by_name.end(): no method with name 'propose_builder_transaction2'

pc

Bitcoin - Perspektive oder Risiko? ISBN 978-3-8442-6568-2 [url="http://bitcoin.quisquis.de"]http://bitcoin.quisquis.de[/url]

ffwong

witness dragonball updated
Waiting for more votes to serve the net.
Cast me some votes. I am running:
- dragonball for Bitshares 2.0 net
- delegate.fftt for PTS (DPOS) net