BitShares Forum
Main => General Discussion => Topic started by: xeroc on January 19, 2016, 10:54:35 am
-
Hello there,
let me start with thanking @Riverhead for providing a machine the machine for this! Please give him some +5% or even better, some BROWNIE.PTS
Anyway, @puppies brought up the idea of constructing a public testnet and I took the idea and used it to also document the steps necessary to deploy a graphene-based blockchain.
This is the result:
- http://testnet.bitshares.eu
- http://docs.bitshares.eu/testnet/
Since I also installed a faucet, if you register an account in the web wallet, you will be donated 10k TEST so you can play around.
I planned to have three MPAs on that chain of which only two are currently "running" (price feeds). The third one got globally settled already due to a bug in one of my scripts.
Backend Code:
Please clone https://github.com/bitshares/bitshares-core, checkout "testnet" branch or latest tag starts with "test".
Have fun!
-
This could have saved me around 200k BTS . :D
-
+5%
But he should really be compensated for the cost of running and maintaining it. How about a worker proposal for it?
-
+5%
-
+5%
But he should really be compensated for the cost of running and maintaining it. How about a worker proposal for it?
Come on now. Not everything has to be monetized.. the various electrum-{dash,btc,ltc} operators run their servers for free, and accept donations.
Imo that's more than enough.
-
+5%
But he should really be compensated for the cost of running and maintaining it. How about a worker proposal for it?
Thank you but the server is still useful to me for its intended purpose - perhaps even more useful now with a testnet running on it. Nevertheless I've been too busy with non-crypto life type stuff to really dig in and get involved with the various Bitshares efforts and projects. In lieu of time I can donate resources.
-
+5%
But he should really be compensated for the cost of running and maintaining it. How about a worker proposal for it?
Thank you but the server is still useful to me for its intended purpose - perhaps even more useful now with a testnet running on it. Nevertheless I've been too busy with non-crypto life type stuff to really dig in and get involved with the various Bitshares efforts and projects. In lieu of time I can donate resources.
Thanks for your kind generousity. Appreciate it. :)
-
This is the result:
- http://testnet.bitshares.eu
- http://docs.bitshares.eu/testnet/
@xeroc , I can see that you've updated the docs and removed this description about setting up a private network:
https://github.com/BitSharesEurope/docs.bitshares.eu/blob/3ea1f3f4d3cf222a421362efff0bb8b2db1dafb2/source/testnet/Private.rst
Does it mean that the removed chapters are no longer needed because your current description refers to both private and public networks?
-
This is the result:
- http://testnet.bitshares.eu
- http://docs.bitshares.eu/testnet/
@xeroc , I can see that you've updated the docs and removed this description about setting up a private network:
https://github.com/BitSharesEurope/docs.bitshares.eu/blob/3ea1f3f4d3cf222a421362efff0bb8b2db1dafb2/source/testnet/Private.rst
Does it mean that the removed chapters are no longer needed because your current description refers to both private and public networks?
Effectively therr is no difference between private and public chains except maybe for
- who may connect to the seed node
- who may connect to the p2p network
- who controls the committee
- who controls the witnesses
The only thing i still want to add is a tutorial about how to run a local (temporary) graphene blockchain for development
-
The only thing i still want to add is a tutorial about how to run a local (temporary) graphene blockchain for development
While you are at it, would you clarify what you meant here:
For testing purposes, the --dbg-init-key option will allow you to quickly create a new chain against any genesis file, by replacing the witnesses' block production keys.
Which command uses this option?
And what is the output of this command when used with this option?
-
I have connected my CLI client to ws://testnet.bitshares.eu:11011
When I try to execute this command :
unlocked >>> import_key neura-sx 5JMVW3catu7r2pza1yhDpVmocbJckL8jUdzpsy8THSuW6sFh3XS
I get this error:
10 assert_exception: Assert Exception
base58str.substr( 0, prefix_len ) == prefix:
{"base58str":"TEST4xx4dqbdPAbjPbGi3YJbURdXGYMYxRzow3Po4ioS4qiWK4Hqbb"}
th_a types.cpp:57 graphene::chain::public_key_type::public_key_type
Does anybody know what reason is?
-
@xeroc
You a have typo here http://docs.bitshares.eu/testnet/4-cli-wallet.html
The get_private_key command allows us to obtain the public private key corresponding to the block signing key
-
@xeroc
I've gone through your docs related to testnet but I could not find any information how and at which stage you set up the TEST core currency.
I guess you've done by editing the my-genesis.json file but you gave no details how it's done.
-
I have connected my CLI client to ws://testnet.bitshares.eu:11011
When I try to execute this command :
unlocked >>> import_key neura-sx 5JMVW3catu7r2pza1yhDpVmocbJckL8jUdzpsy8THSuW6sFh3XS
If this is a private key which you're using in the real network, change it now.
I get this error:
10 assert_exception: Assert Exception
base58str.substr( 0, prefix_len ) == prefix:
{"base58str":"TEST4xx4dqbdPAbjPbGi3YJbURdXGYMYxRzow3Po4ioS4qiWK4Hqbb"}
th_a types.cpp:57 graphene::chain::public_key_type::public_key_type
Does anybody know what reason is?
You need to modify libraries/chain/include/graphene/chain/config.hpp to set the prefix and/or other values to "TEST".
And maybe need to modify libraries/chain/protocol/types.cpp
Same for the quoted question below.
@xeroc
I've gone through your docs related to testnet but I could not find any information how and at which stage you set up the TEST core currency.
I guess you've done by editing the my-genesis.json file but you gave no details how it's done.
-
If this is a private key which you're using in the real network, change it now.
The key I pasted is a private key from the testnet so it's all safe (thank you anyway).
I was trying to import a testnet account from the GUI into the CLI.
I copied the private key from the GUI and wanted to use it in the import_key command in the CLI but it failed.
You need to modify libraries/chain/include/graphene/chain/config.hpp to set the prefix and/or other values to "TEST".
And maybe need to modify libraries/chain/protocol/types.cpp
Would it mean I need to recompile the CLI to be able to access the testnet?
I hope there is a more practical solution - I'm sure xeroc will shed some light on this.
-
+5%
Great job @xeroc!
-
While you are at it, would you clarify what you meant here:
For testing purposes, the --dbg-init-key option will allow you to quickly create a new chain against any genesis file, by replacing the witnesses' block production keys.
Which command uses this option?
And what is the output of this command when used with this option?
Sorry about that .. that is nonsense at this point and I will remove it ..
the purpose of this thing (afaik) is to use any predefined genesis and simply replace the block producers to some you own .. then you don't need to fiddle around with the genesis file
-
I have connected my CLI client to ws://testnet.bitshares.eu:11011
When I try to execute this command :
unlocked >>> import_key neura-sx 5JMVW3catu7r2pza1yhDpVmocbJckL8jUdzpsy8THSuW6sFh3XS
I get this error:
10 assert_exception: Assert Exception
base58str.substr( 0, prefix_len ) == prefix:
{"base58str":"TEST4xx4dqbdPAbjPbGi3YJbURdXGYMYxRzow3Po4ioS4qiWK4Hqbb"}
th_a types.cpp:57 graphene::chain::public_key_type::public_key_type
Does anybody know what reason is?
you can't use the testnet with your BTS cli-wallet .. you need to compile the graphene-testnet sources from the github/bitshareseurope repository
@xeroc
You a have typo here http://docs.bitshares.eu/testnet/4-cli-wallet.html
The get_private_key command allows us to obtain the public private key corresponding to the block signing key
thanks .. fixed
@xeroc
I've gone through your docs related to testnet but I could not find any information how and at which stage you set up the TEST core currency.
I guess you've done by editing the my-genesis.json file but you gave no details how it's done.
you need to define those in the config.hpp .. the initial distribution is part of the genesis block
-
you can't use the testnet with your BTS cli-wallet .. you need to compile the graphene-testnet sources from the github/bitshareseurope repository
Just to make sure I understand it correctly - I could also stick to the official repository and make these changes in config.hpp:
+#define GRAPHENE_SYMBOL "TEST"
+#define GRAPHENE_ADDRESS_PREFIX "TEST"
and recompile the cli-wallet to be able to use it for testnet.
Is this correct?
And two "stupid questions":
(1) Is this the only change you've made after you've cloned your repository from https://github.com/cryptonomex/graphene?
https://github.com/BitSharesEurope/graphene-testnet/commit/7250a5d99a9af47ed7d6cf937908c036703f4a9a
(2) You say in your docs that you've "forked CNX’s code base".
But https://github.com/BitSharesEurope/graphene-testnet is not labelled as "forked from cryptonomex/graphene" on github. Why is that?
-
you can't use the testnet with your BTS cli-wallet .. you need to compile the graphene-testnet sources from the github/bitshareseurope repository
Just to make sure I understand it correctly - I could also stick to the official repository and make these changes in config.hpp:
+#define GRAPHENE_SYMBOL "TEST"
+#define GRAPHENE_ADDRESS_PREFIX "TEST"
and recompile the cli-wallet to be able to use it for testnet.
Is this correct?
Nop .. you also need the genesis block which I fogot to include in the
graphene-testnet repository ... Only then will you be able to connect
your witness ndoe to the testnet.
I am currently testing this my own and will update the repo shortly
And two "stupid questions":
(1) Is this the only change you've made after you've cloned your repository from https://github.com/cryptonomex/graphene?
https://github.com/BitSharesEurope/graphene-testnet/commit/7250a5d99a9af47ed7d6cf937908c036703f4a9a
Those ... plus the genesis block that will be added to the repo shortly.
Yes
(2) You say in your docs that you've "forked CNX’s code base".
But https://github.com/BitSharesEurope/graphene-testnet is not labelled as "forked from cryptonomex/graphene" on github. Why is that?
Very good question ..
Maybe I should have forked using the github fork button.
But I cloned CNX and changed gits origin .. let me try to fix that
-
Only then will you be able to connect your witness ndoe to the testnet.
But I only meant connecting the CLI-wallet to testnet.bitshares.eu.
I assume the CLI does not care about the genesis block so I guess changing the config.hpp and recompiling the cli-wallet should suffice. Correct?
-
Only then will you be able to connect your witness ndoe to the testnet.
But I only meant connecting the CLI-wallet to testnet.bitshares.eu.
I assume the CLI does not care about the genesis block so I guess changing the config.hpp and recompiling the cli-wallet should suffice. Correct?
I fixed the repo in the bitshareseurope account ..
and to answer your question .. you will need to define a --chain-id then ..
it is 39f5e2ede1f8bc1a3a54a7914414e3779e33193f1f5693510e73cb7a87617447
-
and to answer your question .. you will need to define a --chain-id then ..
it is 39f5e2ede1f8bc1a3a54a7914414e3779e33193f1f5693510e73cb7a87617447
Yes, I use this command to run it:
cli_wallet --wallet-file my-wallet.json --chain-id 39f5e2ede1f8bc1a3a54a7914414e3779e33193f1f5693510e73cb7a87617447 --server-rpc-endpoint ws://testnet.bitshares.eu:11011
-
Fantastic :) Great for demos.
-
Thank you for this effort!
-
Great for testing bots:
http://testnet.bitshares.eu/#/market/PEG.RANDOM_TEST
http://testnet.bitshares.eu/#/market/PEG.PARITY_TEST
-
After recompiling the CLI (with config.hpp appropriately modified) I've managed to import a private key (for my testnet account neura-sx) from the testnet GUI to the testnet CLI.
Prior to importing the key this account has been upgraded to LTM.
However when I try to register a new account called zajac in the CLI:
register_account zajac TEST652Ynn6QAP518Po2GM7t8Ws5gJGTyFYBsfyvNr9KjzH2pgJZaT TEST652Ynn6QAP518Po2GM7t8Ws5gJGTyFYBsfyvNr9KjzH2pgJZaT neura-sx neura-sx 0 true
I get this error:
3030001 tx_missing_active_auth: missing required active authority
What might be the reason?
EDIT: I get the same error when I try to create an account using the brian key:
create_account_with_brain_key "CYANIDE PAROECY PUB ..." zajac neura-sx neura-sx true
-
However when I try to register a new account called zajac in the CLI:
register_account zajac TEST652Ynn6QAP518Po2GM7t8Ws5gJGTyFYBsfyvNr9KjzH2pgJZaT TEST652Ynn6QAP518Po2GM7t8Ws5gJGTyFYBsfyvNr9KjzH2pgJZaT neura-sx neura-sx 0 true
Looks like you need to import the active key of neura-sx.
//Update:
Yes I checked it's the reason. Although I don't know why the API still need active_key when you already have owner_key. Will check when have time.
-
However when I try to register a new account called zajac in the CLI:
register_account zajac TEST652Ynn6QAP518Po2GM7t8Ws5gJGTyFYBsfyvNr9KjzH2pgJZaT TEST652Ynn6QAP518Po2GM7t8Ws5gJGTyFYBsfyvNr9KjzH2pgJZaT neura-sx neura-sx 0 true
Looks like you need to import the active key of neura-sx.
//Update:
Yes I checked it's the reason. Although I don't know why the API still need active_key when you already have owner_key. Will check when have time.
Thanks @abit , you are right, I forgot about the active private key.
After importing it everything works fine.
I'll prepare another round of FAQs and publish them together with answers I got so far from xeroc, abit and others.
-
So
I learned something in the progress of launching a graphene chain...
Namely to read the given documentation carefully. It turns out that I made a mistake when launching the chains such that I cannot provide you a genesis file that you can use to build your own witness node for that network ..
I fixed the documentation accordingly: https://github.com/BitSharesEurope/docs.bitshares.eu/commit/830a3e0bbfd2a8a126220b0ed80f4c7adeae1260
Since I want others to join block production in the test network, I need to restart the network from scratch
Fortunatelly, it is not so old, not many accounts have been created and certainly no one managed to run a witness node against the test network. With test network 2, thing can only get better :)
-
@xeroc
What is the meaning of the number 10 here?
--genesis-timestamp 10
Could it be a different number or does it have to be 10?
-
@xeroc
What is the meaning of the number 10 here?
--genesis-timestamp 10
Could it be a different number or does it have to be 10?
can be anything any positiv number .. it sets the timestamp of the genesisblock at now()+x
-
This note is unclear to me:
Unless no other witness produces blocks and witness participation is high enough, subsequent runs which connect to an existing witness node over the p2p network, or which get blockchain state from an existing data directory, need not have the --enable-stale-production flag.
Does it mean that if I have a private testnet on a single computer, I need to use this flag at all times when I run the witness node or just for the very first run of the witness node when the first block gets produced?
Also you effectively say that if the witness participation is high enough I need this flag to be on - which makes little sense to me. Shouldn't it be the other way round?
-
This note is unclear to me:
Unless no other witness produces blocks and witness participation is high enough, subsequent runs which connect to an existing witness node over the p2p network, or which get blockchain state from an existing data directory, need not have the --enable-stale-production flag.
Does it mean that if I have a private testnet on a single computer, I need to use this flag at all times when I run the witness node or just for the very first run of the witness node when the first block gets produced?
Yes .. this flag ensures that blocks are generated even if the
blockchain has been stuck due to a server crash or something similar
Also you effectively say that if the witness participation is
high enough I need this flag to be on - which makes little sense
to me. Shouldn't it be the other way round?
Woops .. double negation
-
Any chance of using another port for the web sockets? I requested and unblocked the testnet.bitshares.eu from a generic corporate proxy. But port 11011 is not use.
-
Any chance of using another port for the web sockets? I requested and unblocked the testnet.bitshares.eu from a generic corporate proxy. But port 11011 is not use.
what port do you prefer?
Maybe I can even setup a proxy redirect similar to openledger and have it accessible via /ws
-
OpenLedger works behind the corporate firewall, so that would be good :)
-
Ok .. I'll try to work this one out ..
//edit: fixed it .. if you refresh it should probably use another connection URL (ending with /ws) .. otherwise you can put this url into your connection manually:
http://testnet.bitshares.eu/ws
-
So
I learned something in the progress of launching a graphene chain...
Namely to read the given documentation carefully. It turns out that I made a mistake when launching the chains such that I cannot provide you a genesis file that you can use to build your own witness node for that network ..
I fixed the documentation accordingly: https://github.com/BitSharesEurope/docs.bitshares.eu/commit/830a3e0bbfd2a8a126220b0ed80f4c7adeae1260
Since I want others to join block production in the test network, I need to restart the network from scratch
Fortunatelly, it is not so old, not many accounts have been created and certainly no one managed to run a witness node against the test network. With test network 2, thing can only get better :)
I just figured this out, fixed the documentation and have the genesis.json added to the repo. Everyone compiling from
https://github.com/BitSharesEurope/graphene-testnet
should be able to connect to the seed node. I will add the default seed node stuff today
https://github.com/BitSharesEurope/graphene-testnet/commit/94f0a95be6f80cb5a7926ba6cc920dd795eb3a19
-
I just figured this out, fixed the documentation and have the genesis.json added to the repo. Everyone compiling from
https://github.com/BitSharesEurope/graphene-testnet
should be able to connect to the seed node. I will add the default seed node stuff today
https://github.com/BitSharesEurope/graphene-testnet/commit/94f0a95be6f80cb5a7926ba6cc920dd795eb3a19
@xeroc
Does it mean you've managed to re-launch the testnet without changing its id?
39f5e2ede1f8bc1a3a54a7914414e3779e33193f1f5693510e73cb7a87617447
-
I have not relaunched the testnet ..
I just figured out what needs to be done to have the default repository be able to connect to the testnet ..
The issues I had have been that anytime I tried to connect my witnesses to the seed node, the chain id was wrong ... and the reason was that I didn't include the genesis file properly ..
that is all now done and documented in the tutorial
give it a try.. if you recompile the latest master cleanly .. you should autoconnect to the seed node and the testnetwork
-
I've been trying to build graphene from source on ubuntu 15.10 and am stuck at this point of the documentation (https://github.com/cryptonomex/graphene/wiki/build-ubuntu):
To actually run cmake we now need the following parameters:
cmake -DCMAKE_PREFIX_PATH="$QT_ROOT" -DCMAKE_MODULE_PATH="$QT_ROOT/lib/cmake/Qt5Core" -DQT_QMAKE_EXECUTABLE="$QT_ROOT/bin/qmake" -DBUILD_QT_GUI=TRUE \
-DGRAPHENE_EGENESIS_JSON="$GENESIS_JSON" -DBOOST_ROOT="$BOOST_ROOT" -DCMAKE_BUILD_TYPE=Debug .
It says "CMake Error: The source directory "/home/***/qt-everywhere-opensource-src-5.5.0" does not appear to contain CMakeLists.txt." Is it correct to try this line in the /home/***/qt-everywhere-opensource-src-5.5.0 directory?
Anybody knows what the problem is?
Edit: Ahh, I see, it's probably configuration of cmake for building graphene.. so it should be executed in graphene folder.. right?
-
@xeroc
After compiling from your testnet repository (https://github.com/BitSharesEurope/graphene-testnet), when I try to run the witness node (without any parameters):
witness_node
I get this:
2499229ms th_a witness.cpp:86 plugin_initialize ] witness plugin: plugin_initialize() begin
2499231ms th_a witness.cpp:96 plugin_initialize ] key_id_to_wif_pair: ["TEST6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV","5KQwrPbwdL6PhXujxW37FSSQZ1Jiws
ST4cqQzDeyXtP79zkvFD3"]
2499234ms th_a witness.cpp:114 plugin_initialize ] witness plugin: plugin_initialize() end
2499236ms th_a object_database.cpp:91 open ] Opening object database from D:/Program Files/BitShares 2/bin64t/witness_node_data_dir/blockchain ...
2499273ms th_a object_database.cpp:97 open ] Done opening object database.
2499275ms th_a thread.cpp:95 thread ] name:ntp tid:388
2499276ms th_a thread.cpp:95 thread ] name:p2p tid:412
2499366ms ntp ntp.cpp:177 read_loop ] ntp_delta_time updated to 229455 us
2499375ms th_a application.cpp:144 reset_p2p_node ] Adding seed node 46.101.188.80:11010
2499377ms th_a application.cpp:155 reset_p2p_node ] Configured p2p node to listen on 0.0.0.0:54055
2499380ms th_a witness.cpp:119 plugin_startup ] witness plugin: plugin_startup() begin
2499381ms th_a witness.cpp:136 plugin_startup ] No witnesses configured! Please add witness IDs and private keys to configuration.
2499383ms th_a witness.cpp:137 plugin_startup ] witness plugin: plugin_startup() end
2499384ms th_a main.cpp:176 main ] Started witness node on a chain with 0 blocks.
2499385ms th_a main.cpp:177 main ] Chain ID is 1f3e7fde05994c55443606e2c4186f6e7943d2333c6db139c42031eff1d19a38
... and it gets stuck at this point.
The chain ID is clearly different than it should be:
I have:
1f3e7fde05994c55443606e2c4186f6e7943d2333c6db139c42031eff1d19a38instead of this which I got :
39f5e2ede1f8bc1a3a54a7914414e3779e33193f1f5693510e73cb7a87617447which I believe is the testnet's blockchain id.
I did not modify the genesis.json file or add any seed nodes. Should I?
----------------------------------------------
EDIT: After further investigation, I've come to the conclusion that this problem stems from the genesis.json file:
When I download the repository from graphene-testnet (https://github.com/BitSharesEurope/graphene-testnet) as a zip file and use the genesis.json file extracted from the zip, everything works fine and I get the correct blockchain id (i.e. compatible with the testnet).
However when I clone the repository from graphene-testnet (https://github.com/BitSharesEurope/graphene-testnet) and use the genesis.json file from the cloned copy, I get some strange blockchain id (i.e. incompatible with the testnet).
I've checked it several times, so there is very little chance that I've made a mistake.
It's very strange, as there is no apparent difference between the content of those files.
But this might be some Windows-related issue.
-
What is the reason all newly created accounts on the testnet have committee-account as their proxy?
Is it a bug?
(http://i.imgur.com/uptTWLz.png)
-
I've been trying to build graphene from source on ubuntu 15.10 and am stuck at this point of the documentation (https://github.com/cryptonomex/graphene/wiki/build-ubuntu):
To actually run cmake we now need the following parameters:
cmake -DCMAKE_PREFIX_PATH="$QT_ROOT" -DCMAKE_MODULE_PATH="$QT_ROOT/lib/cmake/Qt5Core" -DQT_QMAKE_EXECUTABLE="$QT_ROOT/bin/qmake" -DBUILD_QT_GUI=TRUE \
-DGRAPHENE_EGENESIS_JSON="$GENESIS_JSON" -DBOOST_ROOT="$BOOST_ROOT" -DCMAKE_BUILD_TYPE=Debug .
It says "CMake Error: The source directory "/home/***/qt-everywhere-opensource-src-5.5.0" does not appear to contain CMakeLists.txt." Is it correct to try this line in the /home/***/qt-everywhere-opensource-src-5.5.0 directory?
Anybody knows what the problem is?
Edit: Ahh, I see, it's probably configuration of cmake for building graphene.. so it should be executed in graphene folder.. right?
The QT part has been abandoned.
Use this tutorial instead:
http://docs.bitshares.eu/bitshares/installation/Build.html
-
I've checked it several times, so there is very little chance that I've made a mistake.
It's very strange, as there is no apparent difference between the content of those files.
But this might be some Windows-related issue.
I had these kind of issues as well .. do you have a CLEAN repository? Cmake creates some temporary files that WILL screw things up.
make clean
find . -name "CMakeCache.txt" | xargs rm -f
find . -name "CMakeFiles" | xargs rm -Rf
cmake -DCMAKE_BUILD_TYPE=Release .
-
What is the reason all newly created accounts on the testnet have committee-account as their proxy?
Is it a bug?
It certainly was not on purpose ..
No idea what the reason for this is .. and since this is a clone of the official repository, I assume it's the same behavior on the real network
-
What is the reason all newly created accounts on the testnet have committee-account as their proxy?
Is it a bug?
It's a whatever "feature". I don't know why it's designed like this though.
-
I've checked it several times, so there is very little chance that I've made a mistake.
It's very strange, as there is no apparent difference between the content of those files.
But this might be some Windows-related issue.
I had these kind of issues as well .. do you have a CLEAN repository? Cmake creates some temporary files that WILL screw things up.
make clean
find . -name "CMakeCache.txt" | xargs rm -f
find . -name "CMakeFiles" | xargs rm -Rf
cmake -DCMAKE_BUILD_TYPE=Release .
I'll try with "make clean".
But the symptoms I have, do not indicate that Cmake is the culprit:
(a) When I clear the witness folders (i.e. witness_node_data_dir & object_database) and run:
witness_node --genesis-json zip-genesis.json(where the zip-genesis.json file originates from the github zip)
everything is fine, I get the correct blockchain id.
(b) When I clear the witness folders (i.e. witness_node_data_dir & object_database) and run the same witness:
witness_node --genesis-json git-genesis.json(where the git-genesis.json file originates from cloning the github repo)
I get a different blockchain id.
So I use the same compilation of witness node, just "different" genesis.json files (though their content is the same) and, as a result, the blockchain ids are different.
There must be some difference between those files but I'm not able to determine this difference.
-
(a) When I clear the witness folders (i.e. witness_node_data_dir & object_database) and run:
witness_node --genesis-json zip-genesis.json(where the zip-genesis.json file originates from the github zip)
everything is fine, I get the correct blockchain id.
I though that the genesis.json is automatically added to the
witness_node but it seems the compile process should be differently.
This is my observation from a fresh checkout:
git clone github:BitSharesEurope/graphene-testnet
cd graphene-testnet
git submodule update --init --recursive
cmake -DCMAKE_BUILD_TYPE=Release .
make
programs/witness_node/witness_node
# Turned out with the wrong chain id
programs/witness_node/witness_node --genesis-json genesis.json
# turned out out with correct chain id and connected
-
What is the reason all newly created accounts on the testnet have committee-account as their proxy?
Is it a bug?
It's a whatever "feature". I don't know why it's designed like this though.
I've added it as a potential issue on github:
https://github.com/cryptonomex/graphene/issues/543
-
(a) When I clear the witness folders (i.e. witness_node_data_dir & object_database) and run:
witness_node --genesis-json zip-genesis.json(where the zip-genesis.json file originates from the github zip)
everything is fine, I get the correct blockchain id.
I though that the genesis.json is automatically added to the
witness_node but it seems the compile process should be differently.
This is my observation from a fresh checkout:
git clone github:BitSharesEurope/graphene-testnet
cd graphene-testnet
git submodule update --init --recursive
cmake -DCMAKE_BUILD_TYPE=Release .
make
programs/witness_node/witness_node
# Turned out with the wrong chain id
programs/witness_node/witness_node --genesis-json genesis.json
# turned out out with correct chain id and connected
I might have discovered something interesting.
Look at the binary representations of these two files:
This is the genesis.json file that you receive when you clone the repo:
(http://i.imgur.com/czlJntn.png)
The above file produces the "wrong" blockchain id.
Whereas this is the genesis.json file that you receive when you download a zipped version of the repo:
(http://i.imgur.com/HP0yyEH.png)
The above file produces the "correct" blockchain id.
-
wow .. that is weird
-
This is the genesis.json file that you receive when you clone the repo:
The above file produces the "wrong" blockchain id.
Whereas this is the genesis.json file that you receive when you download a zipped version of the repo:
The above file produces the "correct" blockchain id.
Differences are the carriage returns (CR) aka "\r" or 0D in hex.
The first one is in windows text file format, which has both "\r"s and "\n"s, or 0D 0A in hex.
The second one is in linux text file format, which has only "\n"s, or 0A in hex.
So the difference may come from:
* editor settings
* git repo settings
* git client settings
* zip tool settings
Thoughts?
-
This is the genesis.json file that you receive when you clone the repo:
The above file produces the "wrong" blockchain id.
Whereas this is the genesis.json file that you receive when you download a zipped version of the repo:
The above file produces the "correct" blockchain id.
Differences are the line feeds aka "\r" or 0D in hex.
The first one is in windows text file format, which has both "\r"s and "\n"s, or 0D 0A in hex.
The second one is in linux text file format, which has only "\n"s, or 0A in hex.
So the difference may come from:
* editor settings
* git repo settings
* git client settings
* zip tool settings
Thoughts?
The thing is, those slight differences produce different behavior of the witness node.
The process of calculating the blockchain id seems to depend on those small differences.
And xeroc seems to have similar issues on Linux.
IMO, it's a bug.
-
@xeroc please correct me if am wrong, but I think right now there is no possibility to create USD in testnet, because borrowing is possible only for assets which has price feed.
Could you run a price feed for all bitAssets which has price feed in real network? Could you add a documentation how to run such price feed for all assets for testnetwork?
-
There is a PEG.FAKEUSD for that purpose and it should have a price feed.
I will not use USD to make clear the those tokens are worthless
-
@xeroc please correct me if am wrong, but I think right now there is no possibility to create USD in testnet, because borrowing is possible only for assets which has price feed.
Could you run a price feed for all bitAssets which has price feed in real network? Could you add a documentation how to run such price feed for all assets for testnetwork?
@noisy BTW feel free to play around with PEG.FAKEUSD if you are ok with some parameter tweaks... it uses one price-feed from Poloniex.
(Note: Parameters are: MSSR: 100.1%, MCR: 175%, forced settlement at 90%)
-
There is a PEG.FAKEUSD for that purpose and it should have a price feed.
I will not use USD to make clear the those tokens are worthless
Testnet in my opinion should looks like ideal place to trade assets. USD:BTC exchange should behave like a real exchange. All assets like USD, BTC, EUR, GOLD, SILVER should have price feeds. Ours bots should provide a liquidity for those markets :)
In my opinion we should just add the reminder about fact, that this is just a test network to footer of wallet. We already emphasize that with URL address. Additional information (more elaborated) could be in deposit-withdraw section.
-
There is a PEG.FAKEUSD for that purpose and it should have a price feed.
I will not use USD to make clear the those tokens are worthless
Testnet in my opinion should looks like ideal place to trade assets. USD:BTC exchange should behave like a real exchange. All assets like USD, BTC, EUR, GOLD, SILVER should have price feeds. Ours bots should provide a liquidity for those markets :)
In my opinion we should just add the reminder about fact, that this is just a test network to footer of wallet. We already emphasize that with URL address. Additional information (more elaborated) could be in deposit-withdraw section.
I completely removed the deposit-withdraw section from the account settings, so that shouldn't be a big deal.
My thinking is that we need to make as clear as possible that this is a testnet and it's tokens are worthless. Calling them USD and pegging them similar to BTS:USD is counterproductive imho ..
But I certainly agree that everyone should put a bot into PEG.FAKEUSD:TEST
-
My thinking is that we need to make as clear as possible that this is a testnet and it's tokens are worthless.
I agree. But I would like to treat a testnet like a staging environment, where things should be as close as possible to real network. Maybe an alert/reminder after loading a page would be enough?
Calling them USD and pegging them similar to BTS:USD is counterproductive imho ..
In my opinion we have too many assets, what is very confusing for new users. For example, we have BTC, openBTC, metaBTC, etc. now we are going to have even more assets in the testnet, like PEG.FAKEBTC, because without making a pegged assets there is no possibility of creating those assets by collateral. Am I right?
-
I've managed to add a witness node to the testnet.
It's called neura-sx and it runs on a Ubuntu server.
There were no issues while setting up the witness, expect for this one: the embedded version of the genesis.json file did not work for me as it generated a wrong blockchain ID.
The workaround is simple: apply the genesis.json file manually like this:
graphene-testnet/programs/witness_node/witness_node --genesis-json graphene-testnet/genesis.json --witness-id '"<your-witness-id>"' --private-key '["<your-witness-public-key>","<your-witness-private-key>"]'
-
Yes, i noticed that too and there is a bug report about whatever went wrong with the embedded genesis block.
I'll let vote you in asap
-
@xeroc
I think you haven't copied some js widgets for the testnet web GUI.
As a result, some features are malfunctioning e.g. the settings pop-up for the price history chart does not work.
Compare:
https://bitshares.openledger.info/widgets/1/w.js
with the missing file here:
http://testnet.bitshares.eu/widgets/1/w.js
-
My thinking is that we need to make as clear as possible that this is a testnet and it's tokens are worthless.
I agree. But I would like to treat a testnet like a staging environment, where things should be as close as possible to real network. Maybe an alert/reminder after loading a page would be enough?
Calling them USD and pegging them similar to BTS:USD is counterproductive imho ..
In my opinion we have too many assets, what is very confusing for new users. For example, we have BTC, openBTC, metaBTC, etc. now we are going to have even more assets in the testnet, like PEG.FAKEBTC, because without making a pegged assets there is no possibility of creating those assets by collateral. Am I right?
You can create those assets by yourself if they're currently not available. Ask xeroc for funds. Ask xeroc for electing your witnesses so that you can publish price feeds.
-
Ask xeroc for funds. Ask xeroc for electing your witnesses so that you can publish price feeds.
Those two can be done even without xeroc's help - each new account in the web GUI is well funded by default.
-
@xeroc
I think you haven't copied some js widgets for the testnet web GUI.
As a result, some features are malfunctioning e.g. the settings pop-up for the price history chart does not work.
Compare:
https://bitshares.openledger.info/widgets/1/w.js
with the missing file here:
http://testnet.bitshares.eu/widgets/1/w.js
Interesting. I though those would be installed automatically by `npm` .. @svk: do you know more?
-
Ask xeroc for funds. Ask xeroc for electing your witnesses so that you can publish price feeds.
Those two can be done even without xeroc's help - each new account in the web GUI is well funded by default.
Not enough.
Xeroc votes with 9.8 billion for his own witnesses (from the faucet account). Every new account get funded with 1 million only. Unless you create 10K accounts and all vote for your witness. You can try create 5K accounts (with a script maybe) so your combined voting power will be higher than faucet.
Or maybe you only need to vote for all current active witnesses + your witness, so the total number of active witnesses will increase by 1, so you're voted in?
//Update: init9 is voted in with 0 votes, so there is at least one witness position available in testnet. However I think it's best if at least 3 witnesses provide price feeds to a MPA.
-
I think I added witness called "issuer", but it is not appear on http://testnet.bitshares.eu/#/explorer/witnesses, but I still have Votes: 0.
Should I do something more or a committee member has to vote for this witness?
-
Ask xeroc for funds. Ask xeroc for electing your witnesses so that you can publish price feeds.
Those two can be done even without xeroc's help - each new account in the web GUI is well funded by default.
Not enough.
Xeroc votes with 9.8 billion for his own witnesses (from the faucet account). Every new account get funded with 1 million only. Unless you create 10K accounts and all vote for your witness. You can try create 5K accounts (with a script maybe) so your combined voting power will be higher than faucet.
Or maybe you only need to vote for all current active witnesses + your witness, so the total number of active witnesses will increase by 1, so you're voted in?
//Update: init9 is voted in with 0 votes, so there is at least one witness position available in testnet. However I think it's best if at least 3 witnesses provide price feeds to a MPA.
you don't need witnesses to run feeds .. you can do this with privatized bitassets as well ..
https://github.com/BitSharesEurope/testnet-pythonscripts/blob/master/create_mpa.py
-
@xeroc
I think you haven't copied some js widgets for the testnet web GUI.
As a result, some features are malfunctioning e.g. the settings pop-up for the price history chart does not work.
Compare:
https://bitshares.openledger.info/widgets/1/w.js
with the missing file here:
http://testnet.bitshares.eu/widgets/1/w.js
Interesting. I though those would be installed automatically by `npm` .. @svk: do you know more?
That would also explain my general impression that the testnet GUI gets stuck due to unhandled exceptions (and needs reloading) much more frequently than the live one.
-
I think I added witness called "issuer", but it is not appear on http://testnet.bitshares.eu/#/explorer/witnesses, but I still have Votes: 0.
Should I do something more or a committee member has to vote for this witness?
The witnesses can be voted in by anybody, no committee member needs to be involved.
Next vote update is in 12 hours, we need to wait till then to see the votes supporting your witness applied.
-
@xeroc
I think you haven't copied some js widgets for the testnet web GUI.
As a result, some features are malfunctioning e.g. the settings pop-up for the price history chart does not work.
Compare:
https://bitshares.openledger.info/widgets/1/w.js
with the missing file here:
http://testnet.bitshares.eu/widgets/1/w.js
Interesting. I though those would be installed automatically by `npm` .. @svk: do you know more?
I'm not sure what that widget is for but it seems to be related to the Electron build, so it's no problem that it's missing.
I assume you're building with "npm run build" and hosting with nginx or Apache? Shouldn't need to do anything other than that.
-
I assume you're building with "npm run build" and hosting with nginx or Apache? Shouldn't need to do anything other than that.
exactly that .. (with nginx/passenger and ruby for faucet)
Here, the testnet works almost flawlessly. The only issue I see is that the equivalent price is not shown and the fee schedule in the explorer is "empty"
-
Identified testnet GUI problems:
- the Settings pop-up does not work (see the screen-shot for details)
- ugly scroll bars on the DEX page (even in Chrome)
(http://i.imgur.com/b87qrPB.png)
-
Ask xeroc for funds. Ask xeroc for electing your witnesses so that you can publish price feeds.
Those two can be done even without xeroc's help - each new account in the web GUI is well funded by default.
Not enough.
Xeroc votes with 9.8 billion for his own witnesses (from the faucet account). Every new account get funded with 1 million only. Unless you create 10K accounts and all vote for your witness. You can try create 5K accounts (with a script maybe) so your combined voting power will be higher than faucet.
Or maybe you only need to vote for all current active witnesses + your witness, so the total number of active witnesses will increase by 1, so you're voted in?
//Update: init9 is voted in with 0 votes, so there is at least one witness position available in testnet. However I think it's best if at least 3 witnesses provide price feeds to a MPA.
you don't need witnesses to run feeds .. you can do this with privatized bitassets as well ..
https://github.com/BitSharesEurope/testnet-pythonscripts/blob/master/create_mpa.py
In my testnet I created a privatized bitasset and transferred it to committee-account, so it become a public smart coin. I think this is what @noisy wants -- let the testnet look more like the real one.
-
OK, me witness appear in among witnesses:
(http://i.imgur.com/uK8T1pN.png)
however it seems, that it is not producing any blocks.
(http://i.imgur.com/ZQSOXC7.png)
any suggestions? Previously I had a lot of information in my logs, that other witnesses produced new block. Right now my witness seems to be stuck :(
-
OK, me witness appear in among witnesses:
(http://i.imgur.com/uK8T1pN.png)
however it seems, that it is not producing any blocks.
(http://i.imgur.com/ZQSOXC7.png)
any suggestions? Previously I had a lot of information in my logs, that other witnesses produced new block. Right now my witness seems to be stuck :(
* Don't use "--enable-stale-production"
* You need to either set signing key and witness id in config.ini, or add them as parameters of startup command. See http://docs.bitshares.eu/testnet/private-testnet.html
-
* You need to either set signing key and witness id in config.ini, or add them as parameters of startup command. See http://docs.bitshares.eu/testnet/private-testnet.html
I think I have already did that:
(http://i.imgur.com/WNJR4Ya.png)
* Don't use "--enable-stale-production"
Ok, now I have something like that. Is it downloading old blocks or what exactly is happening?
(http://i.imgur.com/ygCRmUc.png)
-
* You need to either set signing key and witness id in config.ini, or add them as parameters of startup command. See http://docs.bitshares.eu/testnet/private-testnet.html
I think I have already did that:
* Don't use "--enable-stale-production"
Ok, now I have something like that. Is it downloading old blocks or what exactly is happening?
Connect a CLI wallet to it and you can check the status by command "info".
-
Connect a CLI wallet to it and you can check the status by command "info".
bitshares@tardis:~/graphene-testnet$ programs/cli_wallet/cli_wallet --wallet-file my-wallet.json -s ws://127.0.0.1:11011 -H 127.0.0.1:8090 -r 127.0.0.1:8099
Logging RPC to file: logs/rpc/rpc.log
1083490ms th_a main.cpp:117 main ] key_to_wif( committee_private_key ): 5KCBDTcyDqzsqehcb52tW5nU6pXife6V2rX9Yf7c3saYSzbDZ5W
1083490ms th_a main.cpp:121 main ] nathan_pub_key: TEST6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV
1083490ms th_a main.cpp:122 main ] key_to_wif( nathan_private_key ): 5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3
1083491ms th_a main.cpp:169 main ] wdata.ws_server: ws://127.0.0.1:11011
1083492ms th_a main.cpp:174 main ] wdata.ws_user: wdata.ws_password:
1083496ms th_a wallet.cpp:752 load_wallet_file ] Could not find account 1.2.143 : "issuer" does not exist on the chain!
1083496ms th_a main.cpp:215 main ] Listening for incoming RPC requests on 127.0.0.1:8099
1083496ms th_a main.cpp:240 main ] Listening for incoming HTTP RPC requests on 127.0.0.1:8090
1083496ms th_a thread.cpp:95 thread ] name:getline tid:140593050920704
unlocked >>> info
info
{
"head_block_num": 0,
"head_block_id": "0000000000000000000000000000000000000000",
"head_block_age": "16 days old",
"next_maintenance_time": "46 years ago",
"chain_id": "39f5e2ede1f8bc1a3a54a7914414e3779e33193f1f5693510e73cb7a87617447",
"participation": "100.00000000000000000",
"active_witnesses": [
"1.6.1",
"1.6.2",
"1.6.3",
"1.6.4",
"1.6.5",
"1.6.6",
"1.6.7",
"1.6.8",
"1.6.9",
"1.6.10",
"1.6.11"
],
"active_committee_members": []
}
my witness id is 1.6.13, which is not available here... but if I use ws://testnet.bitshares.eu:11011
bitshares@tardis:~/graphene-testnet$ programs/cli_wallet/cli_wallet --wallet-file my-wallet.json -s ws://testnet.bitshares.eu:11011 -H 127.0.0.1:8090 -r 127.0.0.1:8099
Logging RPC to file: logs/rpc/rpc.log
1134303ms th_a main.cpp:117 main ] key_to_wif( committee_private_key ): 5KCBDTcyDqzsqehcb52tW5nU6pXife6V2rX9Yf7c3saYSzbDZ5W
1134303ms th_a main.cpp:121 main ] nathan_pub_key: TEST6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV
1134303ms th_a main.cpp:122 main ] key_to_wif( nathan_private_key ): 5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3
1134303ms th_a main.cpp:169 main ] wdata.ws_server: ws://testnet.bitshares.eu:11011
1134322ms th_a main.cpp:174 main ] wdata.ws_user: wdata.ws_password:
1134389ms th_a wallet.cpp:761 load_wallet_file ] Account 1.2.143 : "issuer" updated on chain
1134389ms th_a main.cpp:215 main ] Listening for incoming RPC requests on 127.0.0.1:8099
1134389ms th_a main.cpp:240 main ] Listening for incoming HTTP RPC requests on 127.0.0.1:8090
1134390ms th_a thread.cpp:95 thread ] name:getline tid:139910882080512
unlocked >>> info
info
{
"head_block_num": 247953,
"head_block_id": "0003c891857b50cfc639183eb1fa285dcfd0f82e",
"head_block_age": "3 seconds in the future",
"next_maintenance_time": "23 hours in the future",
"chain_id": "39f5e2ede1f8bc1a3a54a7914414e3779e33193f1f5693510e73cb7a87617447",
"participation": "90.62500000000000000",
"active_witnesses": [
"1.6.1",
"1.6.2",
"1.6.3",
"1.6.4",
"1.6.5",
"1.6.6",
"1.6.7",
"1.6.8",
"1.6.9",
"1.6.12",
"1.6.13"
],
"active_committee_members": [
"1.5.11",
"1.5.12",
"1.5.13",
"1.5.14",
"1.5.15",
"1.5.16",
"1.5.17",
"1.5.18",
"1.5.19",
"1.5.20",
"1.5.0"
]
}
-
Check p2p.log.
Looks like you haven't connected to other nodes.
-
.
.
.
2016-02-03T01:38:29 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 46.101.188.80:11010's last block the delegate has seen is now 000007cfd012949b26c8a6c40d593a3f623d91f4 (actual block #1999) node.cpp:2581
2016-02-03T01:38:29 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 46.101.188.80:11010's last block the delegate has seen is now 000007d067a7b54a67501e3427d50dbfbc1ed227 (actual block #2000) node.cpp:2581
2016-02-03T01:38:29 p2p:message read_loop on_blockchain_item_i ] after removing all items we have already seen, item_hashes_received.size() = 0 node.cpp:2585
2016-02-03T01:38:29 p2p:message read_loop read_loop ] message transmission failed 10 assert_exception: Assert Exception
e.block_id != block_id_type(): Empty block_id in block_database (maybe corrupt on disk?)
{}
th_a block_database.cpp:141 fetch_block_id
{"block_num":0}
th_a db_block.cpp:54 get_block_id_for_num
{}
th_a application.cpp:790 get_blockchain_synopsis message_oriented_connection.cpp:185
2016-02-03T01:38:29 p2p:message read_loop read_loop ] disconnected 10 assert_exception: Assert Exception
e.block_id != block_id_type(): Empty block_id in block_database (maybe corrupt on disk?)
{}
th_a block_database.cpp:141 fetch_block_id
{"block_num":0}
th_a db_block.cpp:54 get_block_id_for_num
{}
th_a application.cpp:790 get_blockchain_synopsis message_oriented_connection.cpp:202
2016-02-03T01:38:29 p2p:message read_loop on_connection_closed ] Remote peer 46.101.188.80:11010 closed their connection to us node.cpp:2957
2016-02-03T01:38:29 p2p:message read_loop display_current_conn ] Currently have 1 of [20/200] connections node.cpp:1728
2016-02-03T01:38:29 p2p:message read_loop display_current_conn ] my id is c59d2ae291d36a09cc5727cf4412debfd535948fc6928f2faf3e0a7d398e73e823 node.cpp:1729
2016-02-03T01:38:29 p2p:message read_loop display_current_conn ] handshaking: 149.202.50.152:43304 with 000000000000000000000000000000000000000000000000000000000000000000 [outbound] node.cpp:1743
2016-02-03T01:38:29 p2p:message read_loop trigger_p2p_network_ ] Triggering connect loop now node.cpp:985
2016-02-03T01:38:29 p2p:message read_loop schedule_peer_for_de ] scheduling peer for deletion: 46.101.188.80:11010 (this will not block) node.cpp:1637
2016-02-03T01:38:29 p2p:message read_loop schedule_peer_for_de ] asyncing delayed_peer_deletion_task to delete 1 peers node.cpp:1642
2016-02-03T01:38:29 p2p:delayed_peer_deletion_task delayed_peer_deletio ] beginning an iteration of delayed_peer_deletion_task with 1 in queue node.cpp:1601
2016-02-03T01:38:29 p2p:delayed_peer_deletion_task destroy ] calling close_connection() peer_connection.cpp:124
2016-02-03T01:38:29 p2p:delayed_peer_deletion_task destroy ] close_connection completed normally peer_connection.cpp:126
2016-02-03T01:38:29 p2p:delayed_peer_deletion_task destroy ] canceling _send_queued_messages task peer_connection.cpp:139
2016-02-03T01:38:29 p2p:delayed_peer_deletion_task destroy ] cancel_and_wait completed normally peer_connection.cpp:141
2016-02-03T01:38:29 p2p:delayed_peer_deletion_task destroy ] canceling accept_or_connect_task peer_connection.cpp:154
2016-02-03T01:38:29 p2p:delayed_peer_deletion_task destroy ] accept_or_connect_task completed normally peer_connection.cpp:156
2016-02-03T01:38:29 p2p:delayed_peer_deletion_task destroy_connection ] in destroy_connection() for message_oriented_connection.cpp:283
2016-02-03T01:38:29 p2p:delayed_peer_deletion_task destroy_connection ] Exception thrown while canceling message_oriented_connection's read_loop, ignoring: {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"warn","file":"message_oriented_connection.cpp","line":204,"method":"read_loop","hostname":"","thread_name":"p2p","timestamp":"2016-02-03T01:38:29"},"format":"disconnected: ${e}","data":{"e":"10 assert_exception: Assert Exception\ne.block_id != block_id_type(): Empty block_id in block_database (maybe corrupt on disk?)\n {}\n th_a block_database.cpp:141 fetch_block_id\n\n {\"block_num\":0}\n th_a db_block.cpp:54 get_block_id_for_num\n\n {}\n th_a application.cpp:790 get_blockchain_synopsis"}}]} message_oriented_connection.cpp:296
2016-02-03T01:38:29 p2p:delayed_peer_deletion_task destroy_connection ] in destroy_connection() for message_oriented_connection.cpp:283
2016-02-03T01:38:29 p2p:delayed_peer_deletion_task destroy_connection ] Exception thrown while canceling message_oriented_connection's read_loop, ignoring: {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"warn","file":"message_oriented_connection.cpp","line":204,"method":"read_loop","hostname":"","thread_name":"p2p","timestamp":"2016-02-03T01:38:29"},"format":"disconnected: ${e}","data":{"e":"10 assert_exception: Assert Exception\ne.block_id != block_id_type(): Empty block_id in block_database (maybe corrupt on disk?)\n {}\n th_a block_database.cpp:141 fetch_block_id\n\n {\"block_num\":0}\n th_a db_block.cpp:54 get_block_id_for_num\n\n {}\n th_a application.cpp:790 get_blockchain_synopsis"}}]} message_oriented_connection.cpp:296
2016-02-03T01:38:29 p2p:delayed_peer_deletion_task delayed_peer_deletio ] leaving delayed_peer_deletion_task node.cpp:1604
2016-02-03T01:38:32 p2p:connect_to_task connect_to ] established outbound connection to 149.202.50.152:43304 peer_connection.cpp:253
2016-02-03T01:38:32 p2p:connect_to_task connect_to_task ] Sent "hello" to peer 149.202.50.152:43304 node.cpp:4336
2016-02-03T01:38:32 p2p:message read_loop on_message ] handling message hello_message_type ecf06255dd4c9559ac60ed8f40f14d1de1ae101e size 528 from peer 149.202.50.152:43304 node.cpp:1754
2016-02-03T01:38:32 p2p:message read_loop on_hello_message ] Received a hello_message from peer 149.202.50.152:43304, sending reply to accept connection node.cpp:2070
2016-02-03T01:38:32 p2p:message read_loop on_message ] handling message connection_accepted_message_type 9c1185a5c5e9fc54612808977ee8f548b2258d31 size 0 from peer 149.202.50.152:43304 node.cpp:1754
2016-02-03T01:38:32 p2p:message read_loop on_connection_accept ] Received a connection_accepted in response to my "hello" from 149.202.50.152:43304 node.cpp:2095
2016-02-03T01:38:32 p2p:message read_loop on_message ] handling message address_request_message_type 9c1185a5c5e9fc54612808977ee8f548b2258d31 size 0 from peer 149.202.50.152:43304 node.cpp:1754
2016-02-03T01:38:32 p2p:message read_loop on_address_request_m ] Received an address request message node.cpp:2152
2016-02-03T01:38:32 p2p:message read_loop on_message ] handling message address_message_type c8cdb333919f75f861da5c27eacb0e490dd5f8db size 54 from peer 149.202.50.152:43304 node.cpp:1754
2016-02-03T01:38:32 p2p:message read_loop on_address_message ] Received an address message containing 1 addresses node.cpp:2181
2016-02-03T01:38:32 p2p:message read_loop on_address_message ] 46.101.188.80:11010 last seen 2016-02-03T01:38:36 node.cpp:2184
2016-02-03T01:38:32 p2p:message read_loop trigger_p2p_network_ ] Triggering connect loop now node.cpp:985
2016-02-03T01:38:32 p2p:message read_loop fetch_next_batch_of_ ] sync: sending a request for the next items after 0000000000000000000000000000000000000000 to peer 149.202.50.152:43304, (full request is []) node.cpp:2424
2016-02-03T01:38:32 p2p:message read_loop on_message ] handling message current_time_request_message_type a9c590e7455b934f7057ef7d2eb0d5294de2bf1f size 8 from peer 149.202.50.152:43304 node.cpp:1754
2016-02-03T01:38:32 p2p:message read_loop on_message ] handling message fetch_blockchain_item_ids_message_type caab587a9bffc5b3698c2e05cfc7a77fe605b078 size 85 from peer 149.202.50.152:43304 node.cpp:1754
2016-02-03T01:38:32 p2p:message read_loop on_fetch_blockchain_ ] sync: received a request for item ids after 0003c963c3e2e40ded830a81cc300ab6475ec6bb from peer 149.202.50.152:43304 (full request: ["0003c958adc42cc3efe4e7e57350e4d2fb623d10","0003c95e7a05007b148a20e31bf00d0b91648042","0003c961cc3af8cf1322ef1c5ea9835fd8d0c314","0003c963c3e2e40ded830a81cc300ab6475ec6bb"]) node.cpp:2241
2016-02-03T01:38:32 p2p:message read_loop on_fetch_blockchain_ ] reply_message: {"total_remaining_item_count":0,"item_type":1001,"item_hashes_available":[]} fetch_blockchain_item_ids_message_received.blockchain_synopsis: ["0003c958adc42cc3efe4e7e57350e4d2fb623d10","0003c95e7a05007b148a20e31bf00d0b91648042","0003c961cc3af8cf1322ef1c5ea9835fd8d0c314","0003c963c3e2e40ded830a81cc300ab6475ec6bb"] node.cpp:2264
2016-02-03T01:38:32 p2p:message read_loop on_fetch_blockchain_ ] sync: peer is already in sync with us node.cpp:2283
2016-02-03T01:38:32 p2p:message read_loop on_message ] handling message current_time_reply_message_type 255e5eb2ff190c918061df46907837e02510699f size 24 from peer 149.202.50.152:43304 node.cpp:1754
2016-02-03T01:38:32 p2p:message read_loop on_message ] handling message blockchain_item_ids_inventory_message_type 90fe7a7919709a8bb314ab8a071304bd22654e04 size 40010 from peer 149.202.50.152:43304 node.cpp:1754
2016-02-03T01:38:32 p2p:message read_loop on_blockchain_item_i ] sync: received a list of 2000 available items from 149.202.50.152:43304 node.cpp:2522
2016-02-03T01:38:32 p2p:message read_loop on_blockchain_item_i ] is_first_item_for_other_peer: false. item_hashes_received.size() = 2000 node.cpp:2568
2016-02-03T01:38:32 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 149.202.50.152:43304's last block the delegate has seen is now 000000019f4f403a2cffd9026f2fa6387cf4cf2f (actual block #1) node.cpp:2581
2016-02-03T01:38:32 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 149.202.50.152:43304's last block the delegate has seen is now 00000002a506a79b3549404d85beb5c418476a0d (actual block #2) node.cpp:2581
2016-02-03T01:38:32 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 149.202.50.152:43304's last block the delegate has seen is now 0000000319c00c322ce18137b7c2d948ff75c5e1 (actual block #3) node.cpp:2581
.
.
.
2016-02-03T01:36:32 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 149.202.50.152:43304's last block the delegate has seen is now 000007caa321ebb49d677fbcf4d8afe384c7b00b (actual block #1994) node.cpp:2581
2016-02-03T01:36:32 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 149.202.50.152:43304's last block the delegate has seen is now 000007cbc491a6f7d747983b11e9126652d18f04 (actual block #1995) node.cpp:2581
2016-02-03T01:36:32 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 149.202.50.152:43304's last block the delegate has seen is now 000007ccc3d140a6faf1e011b50fbaf940e4d89d (actual block #1996) node.cpp:2581
2016-02-03T01:36:32 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 149.202.50.152:43304's last block the delegate has seen is now 000007cda8361738f0dcff6ca291eb66a109ea6a (actual block #1997) node.cpp:2581
2016-02-03T01:36:32 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 149.202.50.152:43304's last block the delegate has seen is now 000007ce9c370aaf8ccf5dd7d71a4b9eec4df13a (actual block #1998) node.cpp:2581
2016-02-03T01:36:32 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 149.202.50.152:43304's last block the delegate has seen is now 000007cfd012949b26c8a6c40d593a3f623d91f4 (actual block #1999) node.cpp:2581
2016-02-03T01:36:32 p2p:message read_loop on_blockchain_item_i ] popping item because delegate has already seen it. peer 149.202.50.152:43304's last block the delegate has seen is now 000007d067a7b54a67501e3427d50dbfbc1ed227 (actual block #2000) node.cpp:2581
2016-02-03T01:36:32 p2p:message read_loop on_blockchain_item_i ] after removing all items we have already seen, item_hashes_received.size() = 0 node.cpp:2585
2016-02-03T01:36:32 p2p:message read_loop read_loop ] message transmission failed 10 assert_exception: Assert Exception
e.block_id != block_id_type(): Empty block_id in block_database (maybe corrupt on disk?)
{}
th_a block_database.cpp:141 fetch_block_id
{"block_num":0}
th_a db_block.cpp:54 get_block_id_for_num
{}
th_a application.cpp:790 get_blockchain_synopsis message_oriented_connection.cpp:185
2016-02-03T01:36:32 p2p:message read_loop read_loop ] disconnected 10 assert_exception: Assert Exception
e.block_id != block_id_type(): Empty block_id in block_database (maybe corrupt on disk?)
{}
th_a block_database.cpp:141 fetch_block_id
{"block_num":0}
th_a db_block.cpp:54 get_block_id_for_num
{}
th_a application.cpp:790 get_blockchain_synopsis message_oriented_connection.cpp:202
2016-02-03T01:36:32 p2p:message read_loop on_connection_closed ] Remote peer 149.202.50.152:43304 closed their connection to us node.cpp:2957
2016-02-03T01:36:32 p2p:message read_loop display_current_conn ] Currently have 0 of [20/200] connections node.cpp:1728
2016-02-03T01:36:32 p2p:message read_loop display_current_conn ] my id is c59d2ae291d36a09cc5727cf4412debfd535948fc6928f2faf3e0a7d398e73e823 node.cpp:1729
2016-02-03T01:36:32 p2p:message read_loop trigger_p2p_network_ ] Triggering connect loop now node.cpp:985
2016-02-03T01:36:32 p2p:message read_loop schedule_peer_for_de ] scheduling peer for deletion: 149.202.50.152:43304 (this will not block) node.cpp:1637
2016-02-03T01:36:32 p2p:message read_loop schedule_peer_for_de ] asyncing delayed_peer_deletion_task to delete 1 peers node.cpp:1642
2016-02-03T01:36:32 p2p:delayed_peer_deletion_task delayed_peer_deletio ] beginning an iteration of delayed_peer_deletion_task with 1 in queue node.cpp:1601
2016-02-03T01:36:32 p2p:delayed_peer_deletion_task destroy ] calling close_connection() peer_connection.cpp:124
2016-02-03T01:36:32 p2p:delayed_peer_deletion_task destroy ] close_connection completed normally peer_connection.cpp:126
2016-02-03T01:36:32 p2p:delayed_peer_deletion_task destroy ] canceling _send_queued_messages task peer_connection.cpp:139
2016-02-03T01:36:32 p2p:delayed_peer_deletion_task destroy ] cancel_and_wait completed normally peer_connection.cpp:141
2016-02-03T01:36:32 p2p:delayed_peer_deletion_task destroy ] canceling accept_or_connect_task peer_connection.cpp:154
2016-02-03T01:36:32 p2p:delayed_peer_deletion_task destroy ] accept_or_connect_task completed normally peer_connection.cpp:156
2016-02-03T01:36:32 p2p:delayed_peer_deletion_task destroy_connection ] in destroy_connection() for message_oriented_connection.cpp:283
2016-02-03T01:36:32 p2p:delayed_peer_deletion_task destroy_connection ] Exception thrown while canceling message_oriented_connection's read_loop, ignoring: {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"warn","file":"message_oriented_connection.cpp","line":204,"method":"read_loop","hostname":"","thread_name":"p2p","timestamp":"2016-02-03T01:36:32"},"format":"disconnected: ${e}","data":{"e":"10 assert_exception: Assert Exception\ne.block_id != block_id_type(): Empty block_id in block_database (maybe corrupt on disk?)\n {}\n th_a block_database.cpp:141 fetch_block_id\n\n {\"block_num\":0}\n th_a db_block.cpp:54 get_block_id_for_num\n\n {}\n th_a application.cpp:790 get_blockchain_synopsis"}}]} message_oriented_connection.cpp:296
2016-02-03T01:36:32 p2p:delayed_peer_deletion_task destroy_connection ] in destroy_connection() for message_oriented_connection.cpp:283
2016-02-03T01:36:32 p2p:delayed_peer_deletion_task destroy_connection ] Exception thrown while canceling message_oriented_connection's read_loop, ignoring: {"code":0,"name":"exception","message":"unspecified","stack":[{"context":{"level":"warn","file":"message_oriented_connection.cpp","line":204,"method":"read_loop","hostname":"","thread_name":"p2p","timestamp":"2016-02-03T01:36:32"},"format":"disconnected: ${e}","data":{"e":"10 assert_exception: Assert Exception\ne.block_id != block_id_type(): Empty block_id in block_database (maybe corrupt on disk?)\n {}\n th_a block_database.cpp:141 fetch_block_id\n\n {\"block_num\":0}\n th_a db_block.cpp:54 get_block_id_for_num\n\n {}\n th_a application.cpp:790 get_blockchain_synopsis"}}]} message_oriented_connection.cpp:296
2016-02-03T01:36:32 p2p:delayed_peer_deletion_task delayed_peer_deletio ] leaving delayed_peer_deletion_task node.cpp:1604
I have a problem with interpratation of that, however I doubt that this is because disk corruption, like logs suggest.
-
I have a problem with interpretation of that, however I doubt that this is because disk corruption, like logs suggest.
Maybe not enough space on disk?
Try this: remove the witness_node_data_dir and object_database folders and start over.
-
It just came to my attention that I made an error when deploying the last wallet wgich makes the testnet connect to the real net if you have a new wallet
-
It just came to my attention that I made an error when deploying the last wallet wgich makes the testnet connect to the real net if you have a new wallet
That's too bad if a test network witness_node connect to real network. Fixed?
-
It just came to my attention that I made an error when deploying the last wallet wgich makes the testnet connect to the real net if you have a new wallet
That's too bad if a test network witness_node connect to real network. Fixed?
I was not precise. Only the GUI was wrongly deployed. I fixed it by now .. the backend is still running ...
However, the currently centralized network server will have to reboot sometime tomorrow. I will try my best to keep block production going in the meantime ..
Hoefully we can improve decentralization eventually ..
-
There will be a downtime of the frontend of the testnet for maintenance reasons ..
Blockchain itselve is still producing blocks and I will do my best to keep it that way until the machine is back to operational ..
-
Testnet GUI back up
-
Testnet GUI back up
Its down for me :(
-
Testnet GUI back up
Its down for me :(
its up here .. what does "down" mean for you?
-
Testnet GUI back up
Its down for me :(
its up here .. what does "down" mean for you?
Its up and running now, sorry..
-
@xeroc @jakub
I have tried one more time, and I think I succeeded. But I am not sure.
(http://i.imgur.com/DppBtzj.png)
and..
(http://i.imgur.com/0ELhgUF.png)
This time my witness name is noisy. So far is not listed on http://testnet.bitshares.eu/#/explorer/witnesses, but I assume that I have to wait exactly like previously.
Is that ok? What next should be done, to produce blocks? I has to have enough votes, right? Could I ask for committees votes?
-
I thought your witness is "issuer"..
Vote for yourself and you'll be listed.
-
I thought your witness is "issuer"..
Vote for yourself and you'll be listed.
Yes, the first one, but I didn't know what I did wrong, so I created another one ;)
-
I thought your witness is "issuer"..
Vote for yourself and you'll be listed.
Yes, the first one, but I didn't know what I did wrong, so I created another one ;)
It's good you've changed the name, as the previous one could be quite confusing for non-advanced users.
I've voted for your witness (and removed my vote for "issuer") so in 3 hours you should be on the list.
In the GUI (http://testnet.bitshares.eu/#/explorer/witnesses):
Next vote update: in 3 hours
-
Success!!! :)
(http://i.imgur.com/fqeR4iO.png)
(http://i.imgur.com/dXfF6cb.png)
I would like to thanks for your help, especially for @jakub :)
-
@xeroc I seems that I was voted out, and right now `noisy` is no longer a witness, `necklace` is. Could I ask for the votes of the committee-members? I think it will be better to have better distribution of nodes.
-
@xeroc I seems that I was voted out, and right now `noisy` is no longer a witness, `necklace` is. Could I ask for the votes of the committee-members? I think it will be better to have better distribution of nodes.
done .. I removed some more init delegates so that we can start decentralizing the testnet
-
@xeroc I seems that I was voted out, and right now `noisy` is no longer a witness, `necklace` is. Could I ask for the votes of the committee-members? I think it will be better to have better distribution of nodes.
done .. I removed some more init delegates so that we can start decentralizing the testnet
It seems not the case..
Confirmed. Maintenance interval is so long.
-
How about 6h? or would you prefer 3h?
-
How about 6h? or would you prefer 3h?
I set it to 5 minutes in my own testnet. ;)
-
@xeroc it seems that current GUI is compatible with new back-end (with BSIP10 implemented)?
Just want to let you know that I've finished refactoring BSIP 10 code, new code is here (https://github.com/abitmore/bitshares-2/tree/dev-transfer-fee) which can be merged to latest develop branch. And this branch (https://github.com/abitmore/bitshares-2/tree/dev-free-trx) contains BSIP10 + free transaction feature. Wish you have time to merge them to test network. Thanks! 8)
Pinging @jakub by the way.
-
@xeroc it seems that current GUI is compatible with new back-end (with BSIP10 implemented)?
Just want to let you know that I've finished refactoring BSIP 10 code, new code is here (https://github.com/abitmore/bitshares-2/tree/dev-transfer-fee) which can be merged to latest develop branch. And this branch (https://github.com/abitmore/bitshares-2/tree/dev-free-trx) contains BSIP10 + free transaction feature. Wish you have time to merge them to test network. Thanks! 8)
Pinging @jakub by the way.
CNX is currently testing STEALTH on the testnet .. for that reason I don't want to upgrade the testnetwork just yet ..
I also need to look into the hard forking stuff to understand what I am doing before planning for a hard fork ..
-
@xeroc it seems that current GUI is compatible with new back-end (with BSIP10 implemented)?
Just want to let you know that I've finished refactoring BSIP 10 code, new code is here (https://github.com/abitmore/bitshares-2/tree/dev-transfer-fee) which can be merged to latest develop branch. And this branch (https://github.com/abitmore/bitshares-2/tree/dev-free-trx) contains BSIP10 + free transaction feature. Wish you have time to merge them to test network. Thanks! 8)
Pinging @jakub by the way.
CNX is currently testing STEALTH on the testnet .. for that reason I don't want to upgrade the testnetwork just yet ..
I also need to look into the hard forking stuff to understand what I am doing before planning for a hard fork ..
OK, good to know that. I'll contact svk.
-
Notice
I have hard forked the testnet network. Please upgrade your code and resync/reply the blockchain!
Please pull the most recent version and upgrade your node!
-
@abit made me aware of an issue with the latest hardfork, which made me update the code.
There is going to be another hardfork at
Thu Mar 24 22:13:59 CET 2016
Please update your block producers!
-
@abit made me aware of an issue with the latest hardfork, which made me update the code.
There is going to be another hardfork at
Thu Mar 24 22:13:59 CET 2016
Please update your block producers!
I presume, based on the title of this thread, you are referring only to the testnet.
Is that correct?
-
@abit made me aware of an issue with the latest hardfork, which made me update the code.
There is going to be another hardfork at
Thu Mar 24 22:13:59 CET 2016
Please update your block producers!
I presume, based on the title of this thread, you are referring only to the testnet.
Is that correct?
Yes, testnet only. By the way it still need a bit more changes to make it right.
-
Hey all. New kid on the block. Surprisingly I have been able to setup a witness node and account on the main net and was advised that most start on the testnet before campaigning for witness votes.
So, I am trying to get onto the testnet and I cannot seem to make it passed an internal c++ error when compiling graphene-testnet. I have tried g++4.8 and g++4.9 on 14.04 ubuntu. Anyone else ran into this issue?
It's a memory issue. Had to stop the main net witness node from hogging all the resources.
+Valerian
Linking CXX executable cat-parts
[ 54%] Built target cat-parts
Scanning dependencies of target build_hardfork_hpp
File "/opt/graphene-testnet/libraries/chain/include/graphene/chain/hardfork.hpp" up-to-date with .d directory
[ 54%] Built target build_hardfork_hpp
Scanning dependencies of target graphene_chain
[ 55%] Building CXX object libraries/chain/CMakeFiles/graphene_chain.dir/database.cpp.o
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.9/README.Bugs> for instructions.
make[2]: *** [libraries/chain/CMakeFiles/graphene_chain.dir/database.cpp.o] Error 4
make[1]: *** [libraries/chain/CMakeFiles/graphene_chain.dir/all] Error 2
make: *** [all] Error 2
root@valerian7:/opt/graphene-testnet#
-
Hey all. New kid on the block. Surprisingly I have been able to setup a witness node and account on the main net and was advised that most start on the testnet before campaigning for witness votes.
So, I am trying to get onto the testnet and I cannot seem to make it passed an internal c++ error when compiling graphene-testnet. I have tried g++4.8 and g++4.9 on 14.04 ubuntu. Anyone else ran into this issue?
It's a memory issue. Had to stop the main net witness node from hogging all the resources.
+Valerian
Linking CXX executable cat-parts
[ 54%] Built target cat-parts
Scanning dependencies of target build_hardfork_hpp
File "/opt/graphene-testnet/libraries/chain/include/graphene/chain/hardfork.hpp" up-to-date with .d directory
[ 54%] Built target build_hardfork_hpp
Scanning dependencies of target graphene_chain
[ 55%] Building CXX object libraries/chain/CMakeFiles/graphene_chain.dir/database.cpp.o
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.9/README.Bugs> for instructions.
make[2]: *** [libraries/chain/CMakeFiles/graphene_chain.dir/database.cpp.o] Error 4
make[1]: *** [libraries/chain/CMakeFiles/graphene_chain.dir/all] Error 2
make: *** [all] Error 2
root@valerian7:/opt/graphene-testnet#
Good to know that. Looking forward to hearing more progresses from you.
-
Ok. My testnet witness is
"test-3" "salvation-2016".
Next vote update 4 hours ... :-\ . Need more votes please :-) Thanks.
+Valerian
-
Ok. My testnet witness is "test-3".
Next vote update 4 hours ... :-\ . Need more votes please :-) Thanks.
+Valerian
Try create more accounts and vote for yourself ;)
-
I can vote you up in a few days .. be patient until i am back at the office please ..
-
I can vote you up in a few days .. be patient until i am back at the office please ..
(http://imgur.com/I9HM3Gv.png)
Great! I am on the board now. The new witness is "salvation-2016" . Would like to stay on the board :-).
Thanks.
+Valerian
-
I can vote you up in a few days .. be patient until i am back at the office please ..
(http://imgur.com/I9HM3Gv.png)
Great! I am on the board now. The new witness is "salvation-2016" . Would like to stay on the board :-).
Thanks.
+Valerian
The time "in 1 second" looks strange. Perhaps your local time is not accurate. Using a ntp daemon?
-
Hello,
Do you run an NTP server to keep the time synchronized?
I have an ntp server running but it seems to be 35 seconds off.
Hi,
Yes I use an ntp daemon. However I have noticed that there is an offset of 35 seconds. I am in a virtual container so I am wondering if the server I am on is not running a daemon.
+V
root@valerian7:/var/log# ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
*clock.xmission. .GPS. 1 u 47 64 177 24.965 35405.4 3.276
+fairy.mattnordh 200.98.196.212 2 u 59 64 177 89.176 35403.2 5.121
+198.60.73.8 .ACTS. 1 u 54 64 177 38.902 35404.1 2.995
+colonialone.pqx 216.218.254.202 2 u 58 64 177 22.820 35406.2 2.963
-golem.canonical 193.79.237.14 2 u 61 64 177 138.847 35409.3 3.182
root@valerian7:/var/log#
-
just added salvation-2016 to my set of witnesses
-
just added salvation-2016 to my set of witnesses
Nice!
+V
-
what do we need, to restart testnet?
-
what do we need, to restart testnet?
why would we?
-
what do we need, to restart testnet?
why would we?
when I told restart testnet I mean restart project because I thought that did not work for some time.
For me still doesn't work as a web page.
but today I added new API connection wss://testnet.bitshares.eu/ws to my wallet and now works fine i that way.
-
@all witness nodes on the *TESTNET*: please add the following checkpoint to your config.ini:
checkpoint = [6188623,005e6e4f7f47ace64ff6f5c83ebddb68ae14f235]
I messed with the testnet too much and kicked out all the other witnesses. My fault, shouldn't happen again.
Regards!
-
@everyone: Please note that there was a hard fork on the testnet recently as we updated the code base to be closer to bitshares code base (thanks @pc for the assistance).
If you want to be a block producer, please update from master branch (including submodules) and rebuild your node, thanks!
-
Please send some TEST to "crn", I'll set up a witness. Already got some from the faucet.
Witness "crn" is set up (currently syncing).
-
Please help with setup of active witness on testnet.bitshares.eu
I created a witness, upgraded it, but it does not generate new blocks and is not listed in active witnesses of testnet.
I followed instructions from this article: https://github.com/cryptonomex/graphene/wiki/How-To-become-an-active-witness-in-BitShares-2.0
and managed to pass all steps with upgrading account, creating a witness and voting for it.
import_key dev4bc ...
upgrade_account dev4bc true
create_witness dev4bc "http://izx.io" true
vote_for_witness dev4bc dev4bc true true
get_witness dev4bc
The final result is the following witness data:
locked >>> get_witness dev4bc
get_witness dev4bc
{
"id": "1.6.47",
"witness_account": "1.2.3340",
"last_aslot": 0,
"signing_key": "TEST7hJfPdJV3mgjnBwnbsGHbC9zWL5rDUUyqSkVQXeK4pZkRhaggB",
"vote_id": "1:78",
"total_votes": 465091782,
"url": "http://izx.io",
"total_missed": 0,
"last_confirmed_block_num": 0
}
after that i started a witness node with the configured pub/private key and got
2497960ms th_a witness.cpp:88 plugin_initialize ] witness plugin: plugin_initialize() begin
2497961ms th_a witness.cpp:99 plugin_initialize ] Public Key: TEST652WPZ6hm3n8X8xseUcQscDnnin8UUsHCxNHMgbgT28V18tYp2
2497961ms th_a witness.cpp:117 plugin_initialize ] witness plugin: plugin_initialize() end
2497961ms th_a application.cpp:426 startup ] Replaying blockchain due to: unclean shutdown detected
2497961ms th_a application.cpp:315 operator() ] Initializing database...
All looks correctly setup, but
However, i do not see my witness dev4bc in the list of active witnesses.
Any help i will greatly appreciate!
-
You must get voted in before you can sign blocks.
-
You must get voted in before you can sign blocks.
i did:
vote_for_witness dev4bc dev4bc true true
this is wrong?
what else should i do?
in test network i am not sure how to get votes
-
You voted for yourself with your stake which is correct but you simply don't have enough votes. I started voting for your witness.
-
You voted for yourself with your stake which is correct but you simply don't have enough votes. I started voting for your witness.
Thank you! Now i got some more votes:
unlocked >>> get_witness dev4bc
get_witness dev4bc
{
"id": "1.6.47",
"witness_account": "1.2.3340",
"last_aslot": 0,
"signing_key": "TEST7hJfPdJV3mgjnBwnbsGHbC9zWL5rDUUyqSkVQXeK4pZkRhaggB",
"vote_id": "1:78",
"total_votes": "97996139400",
"url": "http://izx.io",
"total_missed": 0,
"last_confirmed_block_num": 0
}
Will wait till somebody else will vote.
I have one other question related to test node setup:
when i tried started it, it failed due to out-of-memory before i set up by recommendations:
# Account ID to track history for (may specify multiple times)
track-account = "1.2.3340"
# Keep only those operations in memory that are related to account history tracking
partial-operations = true
# Maximum number of operations per account will be kept in memory
max-ops-per-account = 1
Only after that changes the node finally synced ad started.
I did not find any explanation how the settings related to account history affect the functionality of the node.
Does it affect witness? block generation? API operations?
Why in the hell the node should keep so much data _in memory_ by default?
-
I did not find any explanation how the settings related to account history affect the functionality of the node.
Does it affect witness? block generation? API operations?
These settings don't affect block generation. But you only query the account history for those accounts that you track, so some API operations are affected.
Why in the hell the node should keep so much data _in memory_ by default?
For speed, mostly.
-
I have approved witness dev4bc. You should begin signing blocks after the next maintenacne interval
-
@xeroc
I have added a full time server for a witness and a seed on the test net.
Witness: sahkan-bts-testnet
BTS Test net seed: 23.92.53.25:11010
-
@xeroc
I have added a full time server for a witness and a seed on the test net.
Witness: sahkan-bts-testnet
BTS Test net seed: 23.92.53.25:11010
Excellent!
-
I am few billion votes away from beating the inits, can you please throw some votes my way? We have only 3 testers atm and dev4btc is voted in but not producing.
-
I am few billion votes away from beating the inits, can you please throw some votes my way? We have only 3 testers atm and dev4btc is voted in but not producing.
voted
-
I am few billion votes away from beating the inits, can you please throw some votes my way? We have only 3 testers atm and dev4btc is voted in but not producing.
voted
Thank you, witness is up!
-
ｉ need 500000 TEST for testing, any quick way to get this?
-
| 37658344 | 10320787 | transfer (0) | Transfer from faucet to crazybit: 1,000,000.00000 TEST |
| 37658343 | 10320782 | transfer (0) | Transfer from xeroc to crazybit: 1,000,000.00000 TEST
-
Thanks to the BitShares Blockchain Foundation, the testnet now has an official mailing list:
BitShares Testnet Mailing list (http://lists.bitshares.foundation/cgi-bin/mailman/listinfo/testnet)
I encourage everyone that likes, uses, or develops on the testnet to join this mailing list.
-
Finally, I am glad to announce that witness "wackou" is operational on the testnet, and eagerly awaiting some votes :)
Also ready to test BSIP-018 when the code is deployed to the testnet. Let's revive those black-swanned assets!
-
Just today there is a downtime of the seed and public api nodes .. I will deal with it tomorrow and see if i might have messed up due to too little seed nodes .. Lets see :)
-
Just today there is a downtime of the seed and public api nodes .. I will deal with it tomorrow and see if i might have messed up due to too little seed nodes .. Lets see :)
I checked on my witness, it's running and producing blocks but no other nodes are producing. I wonder if Tom's witness is up...
-
As you might have noticed already, the seed node broke and the network for some reason split into two parts with me signing blocks on my majority "fork". This is interesting but I expected this to happen as we basically have a pretty weak p2p network. Those of you that are running the network, please resync the whole chain if you get errors while pushing blocks.
The seed node should be up again any moment.
To prevent this from happening again, I would like to request more SEED nodes to be added to the `testnet` code base.
Please consider setting up a seed node on the testnet (by opening up the p2p-node setting to 0.0.0.0:PORT) and send a pull request for this part of the code
https://github.com/bitshares/bitshares-core/blob/testnet/libraries/app/application.cpp#L163-L166
or send a mail to
testnet@lists.bitshares.foundation
Thanks!!
-
It seems reasonable to require all active witnesses on main net to be also active on test net, wdyt?
-
As you might have noticed already, the seed node broke and the network for some reason split into two parts with me signing blocks on my majority "fork". This is interesting but I expected this to happen as we basically have a pretty weak p2p network. Those of you that are running the network, please resync the whole chain if you get errors while pushing blocks.
The seed node should be up again any moment.
To prevent this from happening again, I would like to request more SEED nodes to be added to the `testnet` code base.
Please consider setting up a seed node on the testnet (by opening up the p2p-node setting to 0.0.0.0:PORT) and send a pull request for this part of the code
https://github.com/bitshares/bitshares-core/blob/testnet/libraries/app/application.cpp#L163-L166
or send a mail to
testnet@lists.bitshares.foundation
Thanks!!
Yep, will do. I am also short on votes after the restart.
-
anyone has the hash of a recent block? I think I always end up on a minority fork (re-synced twice already), although close to 100% with mostly the init witnesses...
here's what I got:
info
{
"head_block_num": 10806310,
"head_block_id": "00a4e42671894c00043e33f98551e3e3e21b499f",
"head_block_age": "8 seconds old",
"next_maintenance_time": "2 minutes in the future",
"chain_id": "39f5e2ede1f8bc1a3a54a7914414e3779e33193f1f5693510e73cb7a87617447",
"participation": "91.40625000000000000",
"active_witnesses": [
"1.6.1",
"1.6.2",
"1.6.3",
"1.6.4",
"1.6.5",
"1.6.6",
"1.6.7",
"1.6.8",
"1.6.9",
"1.6.10",
"1.6.23"
],
-
Looks right, I voted for your witness. I checked on my witness and it was stuck on"
762234ms th_a application.cpp:523 handle_block ] Got block: #10791565 time: 2017-09-07T01:12:42 latency: 234 ms from: init3 irreversible: 10791555 (-10)I have to restart and resync.
-
Looks right, I voted for your witness. I checked on my witness and it was stuck on"
762234ms th_a application.cpp:523 handle_block ] Got block: #10791565 time: 2017-09-07T01:12:42 latency: 234 ms from: init3 irreversible: 10791555 (-10)I have to restart and resync.
I found the issue, will fix it and have it back online today.
-
I think xeroc accidentally created a fork when he turned on his block producers without syncing first.
On my node, the last correct block was 10775881, but last irreversible was 10775883.
Solution: truncate your block db's index to 10775881 * 32 bytes and set a checkpoint:
checkpoint = [10775882, "00a46d4ad4fc72f0385ee5fda67155fd8d2cb7f9"]
Then replay.
-
Looks right, I voted for your witness. I checked on my witness and it was stuck on"
762234ms th_a application.cpp:523 handle_block ] Got block: #10791565 time: 2017-09-07T01:12:42 latency: 234 ms from: init3 irreversible: 10791555 (-10)I have to restart and resync.
I found the issue, will fix it and have it back online today.
The node shut down because my storage went to 100%. The P2P file filled my drive reporting this error:
2017-09-07T03:39:51 p2p:accept_loop accept_loop ] 0: 0 node.cpp:4192
2017-09-07T03:39:51 p2p:accept_loop destroy_connection ] in destroy_connection() for message_oriented_connection.cpp:286
2017-09-07T03:39:51 p2p:accept_loop destroy_connection ] in destroy_connection() for message_oriented_connection.cpp:286
2017-09-07T03:39:51 p2p:accept_loop accept_loop ] 0 exception: unspecified
Too many open files
{"message":"Too many open files"}
asio asio.cpp:60 error_handler
Unable to accept connection on socket.
{}
-
A hardfork has been scheduled on testnet for friday 2017-09-15 12:00:00 UTC.
Changes:
* BSIP-0018 https://github.com/bitshares/bitshares-core/pull/340
* Improved startup time https://github.com/bitshares/bitshares-core/pull/339
* Fix for early withdrawal claims https://github.com/bitshares/bitshares-core/pull/23
* Fix for bug in vote evaluation https://github.com/bitshares/bitshares-core/pull/369
* Fix to prohibit voting for non-existant entities https://github.com/bitshares/bitshares-core/pull/348
* Some API changes https://github.com/bitshares/bitshares-core/pull/352 https://github.com/bitshares/bitshares-core/pull/344 https://github.com/bitshares/bitshares-core/pull/347 https://github.com/bitshares/bitshares-core/pull/330 https://github.com/bitshares/bitshares-core/pull/311 https://github.com/bitshares/bitshares-core/pull/312 https://github.com/bitshares/bitshares-core/pull/306 https://github.com/bitshares/bitshares-core/pull/304
* new option --plugins for run-time selection of active plugins https://github.com/bitshares/bitshares-core/pull/288
* Fix for the "no blocks to pop" message during shutdown https://github.com/bitshares/bitshares-core/pull/336
* Fix for transaction signing in cli_wallet https://github.com/bitshares/bitshares-core/pull/321
* Improved error logging https://github.com/bitshares/bitshares-core/pull/332
* Get rid of broken flat_index https://github.com/bitshares/bitshares-core/pull/335
* Fix for blockchain crash https://github.com/bitshares/bitshares-core/pull/324
@witnesses this will be our test run for the hardfork on mainnet. Please create witness nodes on testnet and ask xeroc to vote you in.
Edit: forgot to mention the tag... https://github.com/bitshares/bitshares-core/tree/test-2.0.170909
-
My Testnet witness has been activated, kindly asking @xeroc to vote me in.
Witness: sc-bitshares-testnet
-
My witness node has been created and running. @xeroc, could you please vote me in?
Witness account: witness-still
-
My testnet witness is blocked at block 6693517. I have tried 3 times and failed. is there any others as me.
-
My testnet witness is blocked at block 6693517. I have tried 3 times and failed. is there any others as me.
Blocked in what way?
At around that time a load test was run, which means the blocks were huge. This can lead to problems if you're trying to sync on a slow connection.
Keep an eye on the block log and the corresponding index file. As long as they are growing your node is still alive. It'll speed up once you are past the large blocks.
-
My Testnet witness has been activated, kindly asking @xeroc to vote me in.
Witness: witness.yao.test
-
The test is schedule till tomorrow, just 24 hrs left, and so far we only have 3 witnesses joining. I'm also not a voted in witness on the main net, so just 2 regular witnesses so far. I think this is worrisome if witnesses aren't active in the community development.
-
@xeroc my witness is ready, please throw some votes this way.
agsexplorer-test
-
finally syned the blocks, pls help to vote(crazybit.witness) in on testnet.
-
So, in less than 24 hours we will activate the new hard fork on BitShares.
To make sure I'm correctly set up in case of anything needs to be analyzed, I'm throwing out the question here.
My node has been compiled with the "Release" flag. Is this suitable, or should we use the "Debug" flag?
Further more, am I supposed to be activating any kind of special debug in case of the need to trace anything?
-
So, in less than 24 hours we will activate the new hard fork on BitShares.
...on BitShares *testnet*.
To make sure I'm correctly set up in case of anything needs to be analyzed, I'm throwing out the question here.
My node has been compiled with the "Release" flag. Is this suitable, or should we use the "Debug" flag?
Further more, am I supposed to be activating any kind of special debug in case of the need to trace anything?
Using a release build is fine. If you feel capable of doing debugging in case of an emergency you can build in "RelWithDebInfo" mode, which will activate optimizations but still create debugging symbols.
-
So, in less than 24 hours we will activate the new hard fork on BitShares.
...on BitShares *testnet*.
Obviously
-
delegate-oraclechain (1.6.57) is ready on the testnet, votes will be really appreciated. ^^
get_witness delegate-oraclechain
{
"id": "1.6.57",
"witness_account": "1.2.3670",
"last_aslot": 0,
"signing_key": "TEST5hwhHZz21NkuGZDgKBFTNf8HSL6wond3S1TWQ3JDMAaFAJAkkP",
"vote_id": "1:88",
"total_votes": 998994119,
"url": "delegate-oraclechain",
"total_missed": 0,
"last_confirmed_block_num": 0
}
-
my witness freedom-t is ready, pls help to vote in on testnet.
freedom-t
"id": "1.6.59"
-
The testnet network is still running, so I assume the trial on the fork was successful?
-
The testnet network is still running, so I assume the trial on the fork was successful.
let's ask our 25 active witnesses how the test goes
-
The testnet network is still running, so I assume the trial on the fork was successful.
let's ask our 25 active witnesses how the test goes
I'm one of the testnet witnesses running, and have so far not seen any issues on my end. This is why I put the question out here to see how everything was going for the other ones.
Seeing the many things fixed in this version I'm unsure if it's enough to just run a witness to see the effects. I assume some tests have to be performed to see that they are actually working as expected.
I miss an actual schedule or plan on doing this, but maybe I'm not in the right place?
-
Seeing the many things fixed in this version I'm unsure if it's enough to just run a witness to see the effects. I assume some tests have to be performed to see that they are actually working as expected.
I miss an actual schedule or plan on doing this, but maybe I'm not in the right place?
I posted a small update in the BSIP-18 thread: https://bitsharestalk.org/index.php/topic,24322.msg310920.html#msg310920
IMO it's up to the witnesses to run acceptance tests on testnet, and it's also up to them to define how such a test should be run.
-
my testnet witness:"necklace-wit" is ready, votes will be really appreciated.
{
"id": "1.6.61",
"witness_account": "1.2.3822",
"last_aslot": 0,
"signing_key": "TEST7zNeKZ9N7NjAc93cjRyTYUNMHubFiTYERhRBntrvvVUABue3CT",
"vote_id": "1:92",
"total_votes": 0,
"url": "https://btsgo.net",
"total_missed": 0,
"last_confirmed_block_num": 0
}
-
My testnet witness abit-test id 1.6.60 is ready.
-
finally syned the blocks, pls help to vote(crazybit.witness) in on testnet.
my testnet witness is up and runing, vote would be appreciated.
-
Our testnet witness: test-hiblockchain is ready. Votes would be appreciated :D
-
Is it possible that this thread, at least the start of it is now a bit old? Seems like several info is now deprecated and I can't get my witness to connect to the proper testnet chain.
Any help on the latest and greatest tutorial?
Thanks for any help!
Cheers,
-
Is it possible that this thread, at least the start of it is now a bit old? Seems like several info is now deprecated and I can't get my witness to connect to the proper testnet chain.
Any help on the latest and greatest tutorial?
Thanks for any help!
Cheers,
Yes, the linked doc is a bit outdated. There is a link to a page about "open public testnet" in the middle, and links to "your own testnets" below it.
Please clone https://github.com/bitshares/bitshares-core, checkout "testnet" branch or latest tag starts with "test".
-
Woot!
Thanks for the info. I did eventually wander around that area...
Cheers,
-
Our testnet witness is ready to be voted in. Can you please give the witness "test-neoreel-1" some votes so we can further test this out?
Thank you!
Lol, I started creating a few more accounts like it was suggested in some post in order to vote myself in... When I got to 600,000TEST, I thought it would be enough... Oups, it is 600,000,000TEST required... Hmm... I'm not creating 6000 more accounts! :-)
-
Hello,Our testnet witness is ready to be voted in. Witness "for-one" which is full of vitality needs your votes to help us to further test this out.
Thank you!
-
Hello,Our testnet witness is ready to be voted in. Witness "for-one" which is full of vitality needs your votes to help us to further test this out.
Thank you!
The account does not exist in testnet.
-
I am few billion votes away from beating the inits, can you please throw some votes my way? We have only 3 testers atm and dev4btc is voted in but not producing.
voted
-
Hello,Our testnet witness is ready to be voted in. Witness "for-one" which is full of vitality needs your votes to help us to further test this out.
Thank you!
The account does not exist in testnet.
Sorry, the correct account is "testnet-for-one".
-
voted
-
my testnet witness:"necklace-wit" is ready, votes will be really appreciated.
{
"id": "1.6.61",
"witness_account": "1.2.3822",
"last_aslot": 0,
"signing_key": "TEST7zNeKZ9N7NjAc93cjRyTYUNMHubFiTYERhRBntrvvVUABue3CT",
"vote_id": "1:92",
"total_votes": 0,
"url": "https://btsgo.net",
"total_missed": 0,
"last_confirmed_block_num": 0
}
voted,I hope you support Poll - BSIP42 - Adjust price feed dynamically
-
@xeroc my witness is ready, please throw some votes this way.
agsexplorer-test
voted,I hope you support Poll - BSIP42 - Adjust price feed dynamically
-
**FYI**:
The domain and subdomains *.testnet.bitshares.eu are currently migrated and thus unavailable.
Of course, the blockchain itself operates as usual
In the meantime, feel free to use wallet.bitshares.org and point it to wss://testnet.nodes.bitshares.ws/.
-
Hi,
We're experimenting to run a small bookkeeping on bitshares testnet, and then have a profit/loss statement made based on the .csv list of transactions (nb via Robotic Process Automation; its for our local univ).
We came across three issues;
1. new accounts are receiving only 1.000 test token whereas the fee to create an asset is 5.000 test token meaning; is there a way to increase this or make e.g. one million test token available on our testaccount (a13) so we can send the necessary 'test' tokens over to the students?
2. the .csv file doesn't hold more than 50 lines. Our current bookkeeping is having appr 75 lines. Is there a way to have a .csv file with all activities in the testnet environment?
3. the .csv file did not seem to register the sales of an asset we created (nb it was created by team1000 and bought by a13), instead the .csv lines were ''4-3-2019 14:58:27,"fill_order","","0.00000 TEST"; anybody in the know of what might've happened here?
Much obliged.
-
Thank you, but for its intended purpose, the server is still useful to me - perhaps even more useful now with a testnet running on it.
-
I registered an account "doc-bts", but I didn't get the TEST asset.
May I ask for the test asset. or Need I register another account?
-
I registered an account "doc-bts", but I didn't get the TEST asset.
May I ask for the test asset. or Need I register another account?
Join https://t.me/BTS_Node_Admins and ask. You've done it.