Author Topic: What keeping us from creating a test network?  (Read 1224 times)

0 Members and 1 Guest are viewing this topic.

Offline puppies

  • Hero Member
  • *****
  • Posts: 1659
    • View Profile
  • BitShares: puppies
I've had a mini testnet of 4 machines that I have been using to test a script running for the last week or so. I think it may technically be a breach of the license.  I'm almost done testing though, so I will be pulling it down pretty soon.

I could throw together a more permanent testnet, but it would need some discussion first. 

It needs to have a different chain id to prevent confusion.  The best way I know to do that is to modify the genesis.  Does anyone know of a better way to do that?  I would at the very least need to replace the signing keys of the init witnesses and the start date and time.

Would that be enough or would we want to modify the binary name and default ports?

Would this be a waste of time?  Is something like devshares coming that would just replace it?

Do we have cnx permission to create a permanent secondary chain for bitshares testing purposes?




https://metaexchange.info | Bitcoin<->Altcoin exchange | Instant | Safe | Low spreads

Offline sittingduck

  • Sr. Member
  • ****
  • Posts: 246
    • View Profile
I'm sure one will come out soon

Offline noisy

This was said many times on forum, that test network could help:

  • present potential of bitshares
  • test upcoming releases
  • reduce cost of development of 3rd party gateways/bots/tools

It should be very simple to do that. Why we are not doing that?
Take a look on: https://bitsharestalk.org/index.php/topic,19625.msg251894.html - I have a crazy idea - lets convince cryptonomex developers to use livecoding.tv