New Release and Hard Fork for March 23, 2016

[dannotestein]

Not quite the place...but whatever:

I have started to think that, the lack of marketing for BTS is intentional. Among the direct competitors, BTS has the best proven-on-live-network-TPS, best block time. It has a working DEX backend, with a better-then-before front end.
It has a solution to a real world problem: hacking of centralized exchanges
It has the ability to undergo a hardfork smoothly :)
It has ongoing development.
Well you can even say that, with the gateways alive, it has fiat on blockchain.

Only reason I can think of, for the lack of marketing, is that some future businesses are accumulating while it is very very cheap. And they do not want price to go up for now.

I know it may sound like a tin foil hat conspiracy theory... What do you guys think?

Is the price suppressed intentionally, or are you (not counting myself as i am not that active as a community member) not capable of marketing?

There's been a history of marketing errors for BitShares going back a long time, and there's a fairly limited amount of marketing now,  all done by individuals with their own funds.

[lakerta06]

Did it happen?

It happened and it happened in a quiet non-event way.  Good job devs!  Thanks for a stable, well tested release.

indeed .. quite boring :D

Not quite the place...but whatever:

I have started to think that, the lack of marketing for BTS is intentional. Among the direct competitors, BTS has the best proven-on-live-network-TPS, best block time. It has a working DEX backend, with a better-then-before front end.
It has a solution to a real world problem: hacking of centralized exchanges
It has the ability to undergo a hardfork smoothly :)
It has ongoing development.
Well you can even say that, with the gateways alive, it has fiat on blockchain.

Only reason I can think of, for the lack of marketing, is that some future businesses are accumulating while it is very very cheap. And they do not want price to go up for now.

I know it may sound like a tin foil hat conspiracy theory... What do you guys think?

Is the price suppressed intentionally, or are you (not counting myself as i am not that active as a community member) not capable of marketing?

[xeroc]

Did it happen?

It happened and it happened in a quiet non-event way.  Good job devs!  Thanks for a stable, well tested release.

indeed .. quite boring :D

[cube]

Did it happen?

It happened and it happened in a quiet non-event way.  Good job devs!  Thanks for a stable, well tested release.

[JonnyB]

Did it happen?

[fav]

Can someone summarize what all is new in this release? Thanks.

Ander??? https://github.com/bitshares/bitshares-2/releases/tag/2.0.160316

[Ander]

Can someone summarize what all is new in this release? Thanks.

[Thom]

I built on Saturday with no issues. I use a .BitShares2_build folder.

[puppies]

Code Select Expand

[ 55%] Building CXX object libraries/chain/CMakeFiles/graphene_chain.dir/database.cpp.o
In file included from /home/coinbox/bitshares-2/libraries/chain/database.cpp:30:0:
/home/coinbox/bitshares-2/libraries/chain/db_maint.cpp: In member function âvoid graphene::chain::database::update_worker_votes()â:
/home/coinbox/bitshares-2/libraries/chain/db_maint.cpp:105:53: error: âHARDFORK_607_TIMEâ was not declared in this scope
    bool allow_negative_votes = (head_block_time() < HARDFORK_607_TIME);


Building in Release.

Are you building 2.0.160316?

If so, there was an issue, the new one is 2.0.160316b.

Still, you should probably wait for a new release for API servers to fix an issue that seems to cause some crash

Any update on this api build before I update dele-puppy.com

[abit]

Build in 'Release' mode instead.
Anyway, this bug should be fixed

It's not fixed - the problem only occurs if you don't make in the bitshares-2 folder. For example:

Code Select Expand

mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Release ..
make

I remember alt submitted a patch some days ago.. will check.

//Update: found it. https://github.com/bitshares/bitshares-2/pull/9/commits/abae61477d84e1c3faaafb999a0d0c17833f4b7a
I'll cherry-pick and re-submit a pull request to develop branch.

//Update2:
@monsterer: as @xeroc mentioned, the issue has already been fixed in 2.0.160316b release, at least witness_node can be built without issue.
However, I noticed that alt's patch conflicts with latest release, and I remember that you have your own modifications on the source code, so I guess you're not building from a clean code base.. Have you applied alt's patch in your current code base? If yes, try apply your own modifications (without alt's patch) to a clean code base and try rebuild again. Wish it helps.

//Update3: build of cli_wallet is still broken if building outside source dir. Pull request submitted (thanks to alt) https://github.com/cryptonomex/graphene/pull/634

[monsterer]

Build in 'Release' mode instead.
Anyway, this bug should be fixed

It's not fixed - the problem only occurs if you don't make in the bitshares-2 folder. For example:

Code Select Expand

mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Release ..
make

[xeroc]

Build in 'Release' mode instead.
Anyway, this bug should be fixed

[Bhuz]

Code Select Expand

[ 55%] Building CXX object libraries/chain/CMakeFiles/graphene_chain.dir/database.cpp.o
In file included from /home/coinbox/bitshares-2/libraries/chain/database.cpp:30:0:
/home/coinbox/bitshares-2/libraries/chain/db_maint.cpp: In member function âvoid graphene::chain::database::update_worker_votes()â:
/home/coinbox/bitshares-2/libraries/chain/db_maint.cpp:105:53: error: âHARDFORK_607_TIMEâ was not declared in this scope
    bool allow_negative_votes = (head_block_time() < HARDFORK_607_TIME);


Building in Release.

Are you building 2.0.160316?

If so, there was an issue, the new one is 2.0.160316b.

Still, you should probably wait for a new release for API servers to fix an issue that seems to cause some crash

[monsterer]

Code Select Expand

[ 55%] Building CXX object libraries/chain/CMakeFiles/graphene_chain.dir/database.cpp.o
In file included from /home/coinbox/bitshares-2/libraries/chain/database.cpp:30:0:
/home/coinbox/bitshares-2/libraries/chain/db_maint.cpp: In member function âvoid graphene::chain::database::update_worker_votes()â:
/home/coinbox/bitshares-2/libraries/chain/db_maint.cpp:105:53: error: âHARDFORK_607_TIMEâ was not declared in this scope
    bool allow_negative_votes = (head_block_time() < HARDFORK_607_TIME);


Building in Release.

[Chris4210]

When can we upgrade the version to 2.1 and announce stealth and co?

[karnal]

Comrade bytemaster, wizard of much code, author of many posts, philosopher of many thoughts, first of all thank you for everything you and the team have been doing and for continuing pushing the vision forward. I love you man. +5%

Second of all, could you guys start signing the downloads with a PGP key announced here, in github, and on bitshares.org?

[bytemaster]

https://github.com/bitshares/bitshares-2/releases/tag/2.0.160316