[Public Testnet] testnet.bitshares.eu

[merivercap]

 

Great job [member=120]xeroc[/member]!

[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

[xeroc]

I have connected my CLI client to ws://testnet.bitshares.eu:11011

When I try to execute this command :

Code: [Select]

unlocked >>> import_key neura-sx 5JMVW3catu7r2pza1yhDpVmocbJckL8jUdzpsy8THSuW6sFh3XS
I get this error:

Code: [Select]

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

[member=120]xeroc[/member]
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

[member=120]xeroc[/member]
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

[jakub]

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:

Code: [Select]

+#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?

[xeroc]

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:

Code: [Select]

+#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

[jakub]

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?

[xeroc]

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

Code: [Select]

39f5e2ede1f8bc1a3a54a7914414e3779e33193f1f5693510e73cb7a87617447

[jakub]

and to answer your question .. you will need to define a --chain-id then ..
it is

Code: [Select]

39f5e2ede1f8bc1a3a54a7914414e3779e33193f1f5693510e73cb7a87617447

Yes, I use this command to run it:

Code: [Select]

cli_wallet --wallet-file my-wallet.json --chain-id 39f5e2ede1f8bc1a3a54a7914414e3779e33193f1f5693510e73cb7a87617447 --server-rpc-endpoint ws://testnet.bitshares.eu:11011

[betax]

Fantastic Great for demos.

[roadscape]

Thank you for this effort!

[xeroc]

Great for testing bots:
http://testnet.bitshares.eu/#/market/PEG.RANDOM_TEST
http://testnet.bitshares.eu/#/market/PEG.PARITY_TEST

[jakub]

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:

Code: [Select]

register_account zajac TEST652Ynn6QAP518Po2GM7t8Ws5gJGTyFYBsfyvNr9KjzH2pgJZaT TEST652Ynn6QAP518Po2GM7t8Ws5gJGTyFYBsfyvNr9KjzH2pgJZaT neura-sx neura-sx 0 true
I get this error:

Code: [Select]

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:

Code: [Select]

create_account_with_brain_key "CYANIDE PAROECY PUB ..." zajac neura-sx neura-sx true

[abit]

However when I try to register a new account called zajac in the CLI:

Code: [Select]

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.

[jakub]

However when I try to register a new account called zajac in the CLI:

Code: [Select]

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 [member=18687]abit[/member] , 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.

[xeroc]

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