Author Topic: [Public Testnet] testnet.bitshares.eu  (Read 81536 times)

0 Members and 1 Guest are viewing this topic.

Offline betax

  • Hero Member
  • *****
  • Posts: 808
    • View Profile
Fantastic :) Great for demos.
https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

jakub

  • Guest
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

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: 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

  • Guest
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?

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: 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

Quote

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

Quote
(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

  • Guest
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?


Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: 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

@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

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
While you are at it, would you clarify what you meant here:
Quote
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

Offline merivercap

  • Hero Member
  • *****
  • Posts: 661
    • View Profile
    • BitCash
BitCash - http://www.bitcash.org 
Beta: bitCash Wallet / p2p Gateway: (https://m.bitcash.org)
Beta: bitCash Trade (https://trade.bitcash.org)

jakub

  • Guest
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.

Quote
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.

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
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
If this is a private key which you're using in the real network, change it now.

Quote
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 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.
BitShares committee member: abit
BitShares witness: in.abit

jakub

  • Guest
@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.

jakub

  • Guest
@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

jakub

  • Guest
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?

jakub

  • Guest
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:
Quote
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?