What happended now?
I'm sure this has been answered before... but what about all the non upgraded delegates that are still producing bts 0.9.x blocks? Are there 2 chains running?Second chain is not up at the moment although if the snapshot has been taken which i believe i has (but not sure) all BTS transfer on the old BTS 1.0 chain is considered worthless / less valuable as any new owner of BTS after the snapshot occurred will not have a 1:1 peg with BTS 2.0 and therefore will only own the BTS from v1...
Come on ;) +5%+5%
Come on ;) +5%+5%
Google trend analysis for "Bitshares"
https://www.google.com/trends/explore#q=bitshares (https://www.google.com/trends/explore#q=bitshares)
(http://i.imgur.com/JSLu8gk.png)
The chart above does not include the last few days as far as i know... it will be interesting to see how we are trending in a weeks time; we are definitely heading in the right direction!!
Why wasn't the countdown set for the actual launch of the 2.0 chain instead of the demise of the 1.0 chain?
Why wasn't the countdown set for the actual launch of the 2.0 chain instead of the demise of the 1.0 chain?
The last bts1 block number is ?
3826419
I am shutting down my 0.9.3c server now. Regardless if your client is still "on", no blocks are bing produced. I always intended to stop it when 2.0 was launched, but it doesn't appear any blocks are being produced anyway, regardless of the client running or not.
BSB also confirms this.
Why wasn't the countdown set for the actual launch of the 2.0 chain instead of the demise of the 1.0 chain?
Come on ;) +5%+5%
Google trend analysis for "Bitshares"
https://www.google.com/trends/explore#q=bitshares (https://www.google.com/trends/explore#q=bitshares)
(http://i.imgur.com/JSLu8gk.png)
The chart above does not include the last few days as far as i know... it will be interesting to see how we are trending in a weeks time; we are definitely heading in the right direction!!
Why is Batman giving us the finger?
The last bts1 block number is ?Quote3826419
I am shutting down my 0.9.3c server now. Regardless if your client is still "on", no blocks are bing produced. I always intended to stop it when 2.0 was launched, but it doesn't appear any blocks are being produced anyway, regardless of the client running or not.
BSB also confirms this.
Correction, blocks are still being produced on 1.0, but I am shutting down my server now anyway.
Could you be more specific?
I just looked on github but it wasn't clear where this genesis is.
Is it a matter of just building from master and it will be included within the binaries produced?
I still don't get it exactly, what BM means by "join" and where the genesis is.
I am just building src from the master, clean get of lastest. Looking at the src tree now to "find the genesis", if it needs to be pulled out as a separate file like in the testnet. Based on posts I saw yesterday that seems unlikely. I just like things to be explicit, makes life so much easier!
[ 81%] Building CXX object libraries/app/CMakeFiles/graphene_app.dir/plugin.cpp.o
/home/admin/BitShares2_build/libraries/app/application.cpp: In lambda function:
/home/admin/BitShares2_build/libraries/app/application.cpp:277:16: error: ‘genesis’ was not declared in this scope
genesis.initial_chain_id = fc::sha256::hash( egenesis_json );
^
Is this normal, can it be safely ignored? I wouldn't have mentioned it if were only a warning, but it says error..Code: [Select][ 81%] Building CXX object libraries/app/CMakeFiles/graphene_app.dir/plugin.cpp.o
/home/admin/BitShares2_build/libraries/app/application.cpp: In lambda function:
/home/admin/BitShares2_build/libraries/app/application.cpp:277:16: error: ‘genesis’ was not declared in this scope
genesis.initial_chain_id = fc::sha256::hash( egenesis_json );
^
No, the build failed using the same method as I have always used.
Is this normal, can it be safely ignored? I wouldn't have mentioned it if were only a warning, but it says error..Code: [Select][ 81%] Building CXX object libraries/app/CMakeFiles/graphene_app.dir/plugin.cpp.o
/home/admin/BitShares2_build/libraries/app/application.cpp: In lambda function:
/home/admin/BitShares2_build/libraries/app/application.cpp:277:16: error: ‘genesis’ was not declared in this scope
genesis.initial_chain_id = fc::sha256::hash( egenesis_json );
^
No, the build failed using the same method as I have always used.
you are sure you have pulled the most recent version?
Is this normal, can it be safely ignored? I wouldn't have mentioned it if were only a warning, but it says error..Code: [Select][ 81%] Building CXX object libraries/app/CMakeFiles/graphene_app.dir/plugin.cpp.o
/home/admin/BitShares2_build/libraries/app/application.cpp: In lambda function:
/home/admin/BitShares2_build/libraries/app/application.cpp:277:16: error: ‘genesis’ was not declared in this scope
genesis.initial_chain_id = fc::sha256::hash( egenesis_json );
^
No, the build failed using the same method as I have always used.
you are sure you have pulled the most recent version?
Here are the commands used:
git clone https://github.com/cryptonomex/graphene.git "/home/admin/BitShares2_build
git fetch --all
git checkout master && git pull
git submodule update --init --recursive
Happy New Year!!made me lol :)
Is this normal, can it be safely ignored? I wouldn't have mentioned it if were only a warning, but it says error..Code: [Select][ 81%] Building CXX object libraries/app/CMakeFiles/graphene_app.dir/plugin.cpp.o
/home/admin/BitShares2_build/libraries/app/application.cpp: In lambda function:
/home/admin/BitShares2_build/libraries/app/application.cpp:277:16: error: ‘genesis’ was not declared in this scope
genesis.initial_chain_id = fc::sha256::hash( egenesis_json );
^
No, the build failed using the same method as I have always used.
you are sure you have pulled the most recent version?
Here are the commands used:
git clone https://github.com/cryptonomex/graphene.git "/home/admin/BitShares2_build
git fetch --all
git checkout master && git pull
git submodule update --init --recursive
the repository is github.com/bitshares/bitshares-2 now .. you need to follow the submodule procedure again too
#!/bin/bash
git clone https://github.com/bitshares/bitshares-2 /home/admin/BitShares2_build
git fetch --all
###git checkout bitshares-2 && git pull ######## Removed this checkout line on 2nd attempt below
git submodule update --init --recursive
admin@seed07:~$ ./buildIt
Cloning into '/home/admin/BitShares2_build'...
remote: Counting objects: 10363, done.
remote: Compressing objects: 100% (1002/1002), done.
remote: Total 10363 (delta 670), reused 0 (delta 0), pack-reused 9269
Receiving objects: 100% (10363/10363), 16.41 MiB | 4.37 MiB/s, done.
Resolving deltas: 100% (7124/7124), done.
Checking connectivity... done.
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
Without checkout...
admin@seed07:~$ rm -rf BitShares2_build/*
admin@seed07:~$ rm -rf BitShares2_build/.git*
admin@seed07:~$ nano buildIt
admin@seed07:~$ ./buildIt
Cloning into '/home/admin/BitShares2_build'...
remote: Counting objects: 10363, done.
remote: Compressing objects: 100% (1002/1002), done.
remote: Total 10363 (delta 670), reused 0 (delta 0), pack-reused 9269
Receiving objects: 100% (10363/10363), 16.41 MiB | 5.98 MiB/s, done.
Resolving deltas: 100% (7124/7124), done.
Checking connectivity... done.
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
fatal: Not a git repository (or any of the parent directories): .git
No.
Is that "now" part of the repository name?
Code: [Select]#!/bin/bash
git clone https://github.com/bitshares/bitshares-2 /home/admin/BitShares2_build
git fetch --all
###git checkout bitshares-2 && git pull ######## Removed this checkout line on 2nd attempt below
git submodule update --init --recursive
Can the bitshares homepage be updating with a message saying the the transition in progress, please check back today for further instructions or something?
No.
Is that "now" part of the repository name?Code: [Select]#!/bin/bash
git clone https://github.com/bitshares/bitshares-2 /home/admin/BitShares2_build
git fetch --all
###git checkout bitshares-2 && git pull ######## Removed this checkout line on 2nd attempt below
git submodule update --init --recursive
You must cd into /home/admin/BitShares2_build after cloning the repo, otherwise git will try to fetch in the current dir.
Good PR consists of all those little details that sum up into the overall perception.
(http://i.imgur.com/hxnv21T.gif)