[Public Testnet] testnet.bitshares.eu

Started by xeroc, January 19, 2016, 10:54:35 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

NeoReel

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 - [url="//neoreel.com"]NeoReel.com[/url]
CTO- [url="//moclip.com"]MoClip.com[/url]
CEO- [url="//relinked.com"]Relinked.com[/url]

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

crazybit

Quote from: crazybit on September 14, 2017, 11:39:24 AM
finally syned the blocks, pls help to vote(crazybit.witness) in on testnet.

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

abit

My testnet witness abit-test id 1.6.60 is ready.
BitShares committee member: abit
BitShares witness: in.abit

xiangxn

my testnet witness:"necklace-wit"  is ready, votes will be really appreciated.
{
  "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:[url="https://btsgo.net/"]https://btsgo.net/[/url]

pc

Quote from: startail on September 16, 2017, 10:19:08 AM
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 [url="http://bitcoin.quisquis.de"]http://bitcoin.quisquis.de[/url]

startail

Quote from: fav on September 16, 2017, 09:09:26 AM
Quote from: startail on September 16, 2017, 08:38:52 AM
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?

fav

Quote from: startail on September 16, 2017, 08:38:52 AM
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
Join us on Hive: [url="https://peakd.com/c/hive-120117/created"]https://peakd.com/c/hive-120117/created[/url]

startail

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

freedom

my witness freedom-t is ready, pls help to vote in on testnet.

freedom-t
"id": "1.6.59"

Harvey

delegate-oraclechain (1.6.57) is ready on the testnet, votes will be really appreciated. ^^

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:[url="wss://128.199.143.47"]wss://128.199.143.47[/url]:2016 
MUSE   Witness:harvey-xts Seed:128.199.143.47:2017 API:[url="ws://128.199.143.47:2018"]ws://128.199.143.47:2018[/url]

startail

Quote from: pc on September 14, 2017, 06:30:52 PM
Quote from: startail on September 14, 2017, 04:59:30 PM
So, in less than 24 hours we will activate the new hard fork on BitShares.

...on BitShares *testnet*.

Obviously

pc

Quote from: startail on September 14, 2017, 04:59:30 PM
So, in less than 24 hours we will activate the new hard fork on BitShares.

...on BitShares *testnet*.

Quote from: startail on September 14, 2017, 04:59:30 PM
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 [url="http://bitcoin.quisquis.de"]http://bitcoin.quisquis.de[/url]

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?

crazybit

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