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

0 Members and 1 Guest are viewing this topic.

Offline NeoReel

  • Full Member
  • ***
  • Posts: 51
  • Entrepreneur
    • View Profile
    • NeoReel
  • BitShares: neoreel-1
Is it possible that this thread, at least the start of it is now a bit old? Seems like several info is now deprecated and I can't get my witness to connect to the proper testnet chain.
Any help on the latest and greatest tutorial?

Thanks for any help!
Cheers,
President - NeoReel.com
CTO- MoClip.com
CEO- Relinked.com

Offline HiBlockchain

  • Newbie
  • *
  • Posts: 5
    • View Profile
    • HiBlockchain
Our testnet witness: test-hiblockchain is ready. Votes would be appreciated  :D
Hi区块链 - 最靠谱不忽悠的区块链资讯平台

HiBlockchain - the promoter of DAC, an information site that focuses on promoting blockchain and Graphene 2.0

Offline crazybit

finally syned the blocks, pls help to vote(crazybit.witness) in on testnet.

my testnet witness is up and runing, vote would be appreciated.

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4592
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
My testnet witness abit-test id 1.6.60 is ready.
BitShares committee member: abit
BitShares witness: in.abit

Offline xiangxn

my testnet witness:"necklace-wit"  is ready, votes will be really appreciated.
Code: [Select]
{
  "id": "1.6.61",
  "witness_account": "1.2.3822",
  "last_aslot": 0,
  "signing_key": "TEST7zNeKZ9N7NjAc93cjRyTYUNMHubFiTYERhRBntrvvVUABue3CT",
  "vote_id": "1:92",
  "total_votes": 0,
  "url": "https://btsgo.net",
  "total_missed": 0,
  "last_confirmed_block_num": 0
}
Please vote for my witness: xn-delegate
My wallet:https://btsgo.net/

Offline pc

  • Hero Member
  • *****
  • Posts: 1530
    • View Profile
    • Bitcoin - Perspektive oder Risiko?
  • BitShares: cyrano
Seeing the many things fixed in this version I'm unsure if it's enough to just run a witness to see the effects. I assume some tests have to be performed to see that they are actually working as expected.

I miss an actual schedule or plan on doing this, but maybe I'm not in the right place?

I posted a small update in the BSIP-18 thread: https://bitsharestalk.org/index.php/topic,24322.msg310920.html#msg310920

IMO it's up to the witnesses to run acceptance tests on testnet, and it's also up to them to define how such a test should be run.
Bitcoin - Perspektive oder Risiko? ISBN 978-3-8442-6568-2 http://bitcoin.quisquis.de

Offline startail

The testnet network is still running, so I assume the trial on the fork was successful.

let's ask our 25 active witnesses how the test goes

I'm one of the testnet witnesses running, and have so far not seen any issues on my end. This is why I put the question out here to see how everything was going for the other ones.

Seeing the many things fixed in this version I'm unsure if it's enough to just run a witness to see the effects. I assume some tests have to be performed to see that they are actually working as expected.

I miss an actual schedule or plan on doing this, but maybe I'm not in the right place?

Offline fav

  • Administrator
  • Hero Member
  • *****
  • Posts: 4278
  • No Pain, No Gain
    • View Profile
    • Follow Me!
  • BitShares: fav
The testnet network is still running, so I assume the trial on the fork was successful.

let's ask our 25 active witnesses how the test goes

Offline startail

The testnet network is still running, so I assume the trial on the fork was successful?
« Last Edit: September 16, 2017, 10:19:56 am by startail »

Offline freedom

  • Sr. Member
  • ****
  • Posts: 303
    • View Profile
my witness freedom-t is ready, pls help to vote in on testnet.

freedom-t
"id": "1.6.59"

Offline Harvey

  • Sr. Member
  • ****
  • Posts: 244
    • View Profile
delegate-oraclechain (1.6.57) is ready on the testnet, votes will be really appreciated. ^^

Code: [Select]
get_witness delegate-oraclechain
{
  "id": "1.6.57",
  "witness_account": "1.2.3670",
  "last_aslot": 0,
  "signing_key": "TEST5hwhHZz21NkuGZDgKBFTNf8HSL6wond3S1TWQ3JDMAaFAJAkkP",
  "vote_id": "1:88",
  "total_votes": 998994119,
  "url": "delegate-oraclechain",
  "total_missed": 0,
  "last_confirmed_block_num": 0
}
BTS       Witness:harvey-xts Seed:128.199.143.47:2015 API:wss://128.199.143.47:2016 
MUSE   Witness:harvey-xts Seed:128.199.143.47:2017 API:ws://128.199.143.47:2018

Offline startail

So, in less than 24 hours we will activate the new hard fork on BitShares.

...on BitShares *testnet*.

Obviously

Offline pc

  • Hero Member
  • *****
  • Posts: 1530
    • View Profile
    • Bitcoin - Perspektive oder Risiko?
  • BitShares: cyrano
So, in less than 24 hours we will activate the new hard fork on BitShares.

...on BitShares *testnet*.

To make sure I'm correctly set up in case of anything needs to be analyzed, I'm throwing out the question here.

My node has been compiled with the "Release" flag. Is this suitable, or should we use the "Debug" flag?
Further more, am I supposed to be activating any kind of special debug in case of the need to trace anything?

Using a release build is fine. If you feel capable of doing debugging in case of an emergency you can build in "RelWithDebInfo" mode, which will activate optimizations but still create debugging symbols.
Bitcoin - Perspektive oder Risiko? ISBN 978-3-8442-6568-2 http://bitcoin.quisquis.de

Offline startail

So, in less than 24 hours we will activate the new hard fork on BitShares.

To make sure I'm correctly set up in case of anything needs to be analyzed, I'm throwing out the question here.

My node has been compiled with the "Release" flag. Is this suitable, or should we use the "Debug" flag?
Further more, am I supposed to be activating any kind of special debug in case of the need to trace anything?

Offline crazybit

finally syned the blocks, pls help to vote(crazybit.witness) in on testnet.