BitShares Forum
Main => Technical Support => Topic started by: jamesc on July 23, 2014, 03:54:37 pm
-
By default, does this hook into the testnet?
https://github.com/BitShares/bitshares_toolkit.git
And this is the production one (make sure to checkout the latest tag):
https://github.com/dacsunlimited/bitsharesx.git
Please tell me, where can I look to see if I'm on the testnet or production?
I noticed that both builds try to reference the same config directory by default (~/.BitSharesX). I wonder what the implications are in getting that confused.
Do you provide testnet shares? I would like to try registering a testnet delegate.
thank you...
-
THey shouldn't be referencing the same directory!
The test net has the XT logo and comes from bitshares_toolkit
-
THey shouldn't be referencing the same directory!
The test net has the XT logo and comes from bitshares_toolkit
Sorry, you are correct.. It is .BitSharesXTS for test and .BitSharesX for production.
What is the best way to try out the delegate thing? Is it still possible to use test shares? My address is: XTS5VFxAACqe3BhRePDZe1pGzWfrUQ5KQWxrmBfUt3PGzQefGNCGn
-
We are preparing a new test network, then you will be able to get some initial stake.
-
Maybe we should have a directory with all blockchain ids
See: blockchain_get_config
-
The XT network will now display Test Network in the lower status bar.
-
Can we build and run the testnet code on the same machine as the livenet with only 1 or the other active at a time? Or can you run them simultaneously?
I'm thinking of a backup server that has both a livenet and testnet installation.
Edit: Now I'm thinking that the blockchain and wallets would collide??