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

0 Members and 1 Guest are viewing this topic.

Offline xeroc

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

Offline sahkan

  • Sr. Member
  • ****
  • Posts: 247
    • View Profile
    • BitShares DEX
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...

Offline xeroc

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

Offline wackou

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!
Please vote for witness wackou! More info at http://digitalgaia.io

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Thanks to the BitShares Blockchain Foundation, the testnet now has an official mailing list:

BitShares Testnet Mailing list

I encourage everyone that likes, uses, or develops on the testnet to join this mailing list.

Offline xeroc

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

Offline crazybit

i need 500000 TEST for testing, any quick way to get this?

Offline sahkan

  • Sr. Member
  • ****
  • Posts: 247
    • View Profile
    • BitShares DEX
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!

Offline xeroc

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

Offline sahkan

  • Sr. Member
  • ****
  • Posts: 247
    • View Profile
    • BitShares DEX
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.

Offline xeroc

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

Offline sahkan

  • Sr. Member
  • ****
  • Posts: 247
    • View Profile
    • BitShares DEX
@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

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
I have approved witness dev4bc. You should begin signing blocks after the next maintenacne interval

Offline pc

  • Hero Member
  • *****
  • Posts: 1530
    • View Profile
    • Bitcoin - Perspektive oder Risiko?
  • BitShares: cyrano
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.
Bitcoin - Perspektive oder Risiko? ISBN 978-3-8442-6568-2 http://bitcoin.quisquis.de

Offline studnev

  • Newbie
  • *
  • Posts: 3
    • View Profile
  • BitShares: dev4bc
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?