Author Topic: [Public Testnet] testnet.bitshares.eu  (Read 81549 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
I can vote you up in a few days .. be patient until i am back at the office please ..

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
Ok. My testnet witness is "test-3".

Next vote update 4 hours ... :-\ . Need more votes please :-) Thanks.

+Valerian
Try create more accounts and vote for yourself ;)
BitShares committee member: abit
BitShares witness: in.abit

Offline valerian

Ok. My testnet witness is "test-3" "salvation-2016".

Next vote update 4 hours ... :-\ . Need more votes please :-) Thanks.

+Valerian
« Last Edit: March 27, 2016, 05:14:44 pm by valerian »

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
Hey all. New kid on the block. Surprisingly I have been able to setup a witness node and account on the main net and was advised that most start on the testnet before campaigning for witness votes.

So, I am trying to get onto the testnet and I cannot seem to make it passed an internal c++ error when compiling graphene-testnet. I have tried g++4.8 and g++4.9 on 14.04 ubuntu. Anyone else ran into this issue?

It's a memory issue. Had to stop the main net witness node from hogging all the resources.

+Valerian

Code: [Select]

Linking CXX executable cat-parts
[ 54%] Built target cat-parts
Scanning dependencies of target build_hardfork_hpp
File "/opt/graphene-testnet/libraries/chain/include/graphene/chain/hardfork.hpp" up-to-date with .d directory
[ 54%] Built target build_hardfork_hpp
Scanning dependencies of target graphene_chain
[ 55%] Building CXX object libraries/chain/CMakeFiles/graphene_chain.dir/database.cpp.o
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.9/README.Bugs> for instructions.
make[2]: *** [libraries/chain/CMakeFiles/graphene_chain.dir/database.cpp.o] Error 4
make[1]: *** [libraries/chain/CMakeFiles/graphene_chain.dir/all] Error 2
make: *** [all] Error 2
root@valerian7:/opt/graphene-testnet#
Good to know that. Looking forward to hearing more progresses from you.
BitShares committee member: abit
BitShares witness: in.abit

Offline valerian

Hey all. New kid on the block. Surprisingly I have been able to setup a witness node and account on the main net and was advised that most start on the testnet before campaigning for witness votes.

So, I am trying to get onto the testnet and I cannot seem to make it passed an internal c++ error when compiling graphene-testnet. I have tried g++4.8 and g++4.9 on 14.04 ubuntu. Anyone else ran into this issue?

It's a memory issue. Had to stop the main net witness node from hogging all the resources.

+Valerian

Code: [Select]

Linking CXX executable cat-parts
[ 54%] Built target cat-parts
Scanning dependencies of target build_hardfork_hpp
File "/opt/graphene-testnet/libraries/chain/include/graphene/chain/hardfork.hpp" up-to-date with .d directory
[ 54%] Built target build_hardfork_hpp
Scanning dependencies of target graphene_chain
[ 55%] Building CXX object libraries/chain/CMakeFiles/graphene_chain.dir/database.cpp.o
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-4.9/README.Bugs> for instructions.
make[2]: *** [libraries/chain/CMakeFiles/graphene_chain.dir/database.cpp.o] Error 4
make[1]: *** [libraries/chain/CMakeFiles/graphene_chain.dir/all] Error 2
make: *** [all] Error 2
root@valerian7:/opt/graphene-testnet#
« Last Edit: March 26, 2016, 05:39:57 pm by valerian »

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
@abit made me aware of an issue with the latest hardfork, which made me update the code.
There is going to be another hardfork at
Thu Mar 24 22:13:59 CET 2016

Please update your block producers!

I presume, based on the title of this thread, you are referring only to the testnet.

Is that correct?
Yes, testnet only. By the way it still need a bit more changes to make it right.
BitShares committee member: abit
BitShares witness: in.abit

Offline Thom

@abit made me aware of an issue with the latest hardfork, which made me update the code.
There is going to be another hardfork at
Thu Mar 24 22:13:59 CET 2016

Please update your block producers!

I presume, based on the title of this thread, you are referring only to the testnet.

Is that correct?
Injustice anywhere is a threat to justice everywhere - MLK |  Verbaltech2 Witness Reports: https://bitsharestalk.org/index.php/topic,23902.0.html

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
@abit made me aware of an issue with the latest hardfork, which made me update the code.
There is going to be another hardfork at
Thu Mar 24 22:13:59 CET 2016

Please update your block producers!

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Notice

I have hard forked the testnet network. Please upgrade your code and resync/reply the blockchain!


Please pull the most recent version and upgrade your node!
« Last Edit: March 17, 2016, 11:35:39 am by xeroc »

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
@xeroc it seems that current GUI is compatible with new back-end (with BSIP10 implemented)?

Just want to let you know that I've finished refactoring BSIP 10 code, new code is here which can be merged to latest develop branch. And this branch contains BSIP10 + free transaction feature. Wish you have time to merge them to test network. Thanks! 8)

Pinging @jakub by the way.
CNX is currently testing STEALTH on the testnet .. for that reason I don't want to upgrade the testnetwork just yet ..
I also need to look into the hard forking stuff to understand what I am doing before planning for a hard fork ..
OK, good to know that. I'll contact svk.
BitShares committee member: abit
BitShares witness: in.abit

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
@xeroc it seems that current GUI is compatible with new back-end (with BSIP10 implemented)?

Just want to let you know that I've finished refactoring BSIP 10 code, new code is here which can be merged to latest develop branch. And this branch contains BSIP10 + free transaction feature. Wish you have time to merge them to test network. Thanks! 8)

Pinging @jakub by the way.
CNX is currently testing STEALTH on the testnet .. for that reason I don't want to upgrade the testnetwork just yet ..
I also need to look into the hard forking stuff to understand what I am doing before planning for a hard fork ..

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
@xeroc it seems that current GUI is compatible with new back-end (with BSIP10 implemented)?

Just want to let you know that I've finished refactoring BSIP 10 code, new code is here which can be merged to latest develop branch. And this branch contains BSIP10 + free transaction feature. Wish you have time to merge them to test network. Thanks! 8)

Pinging @jakub by the way.
BitShares committee member: abit
BitShares witness: in.abit

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
How about 6h? or would you prefer 3h?
I set it to 5 minutes in my own testnet.  ;)
BitShares committee member: abit
BitShares witness: in.abit

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
How about 6h? or would you prefer 3h?

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
@xeroc I seems that I was voted out, and right now `noisy` is no longer a witness, `necklace` is. Could I ask for the votes of the committee-members? I think it will be better to have better distribution of nodes.
done .. I removed some more init delegates so that we can start decentralizing the testnet
It seems not the case..
Confirmed. Maintenance interval is so long.
« Last Edit: February 12, 2016, 12:49:47 am by abit »
BitShares committee member: abit
BitShares witness: in.abit