Author Topic: October 2nd Test Network  (Read 12225 times)

0 Members and 1 Guest are viewing this topic.

Offline ElMato

  • Sr. Member
  • ****
  • Posts: 288
    • View Profile
Re: October 2nd Test Network
« Reply #45 on: October 02, 2015, 06:02:51 pm »
Should we start publishing price feeds?
I want to test again the forced settlement  :)

Where should i look for the update feed script (@xeroc) ?

Offline pc

  • Hero Member
  • *****
  • Posts: 1530
    • View Profile
    • Bitcoin - Perspektive oder Risiko?
  • BitShares: cyrano
Re: October 2nd Test Network
« Reply #46 on: October 02, 2015, 06:25:27 pm »
Bitcoin - Perspektive oder Risiko? ISBN 978-3-8442-6568-2 http://bitcoin.quisquis.de

Offline CalabiYau

Re: October 2nd Test Network
« Reply #47 on: October 02, 2015, 07:04:31 pm »
List your nick here is you want 5000 CORE for register the witness

calabiyau - thank you !

edit:

 "id": "1.6.30",
  "witness_account": "1.2.14634",

still need some CORE
Code: [Select]
required 20.05566 COREto set voting proxy to 'dan'
thank you.
« Last Edit: October 02, 2015, 07:54:33 pm by CalabiYau »

Offline bytemaster

Re: October 2nd Test Network
« Reply #48 on: October 02, 2015, 08:06:04 pm »
I accidentally voted everyone out :(  I forgot to publish changes.   You all will be back in 55 minutes.
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

iHashFury

  • Guest
Re: October 2nd Test Network
« Reply #49 on: October 02, 2015, 08:14:15 pm »
I accidentally voted everyone out :(  I forgot to publish changes.   You all will be back in 55 minutes.

aka  'voter apathy test'  ;)

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4511
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
Re: October 2nd Test Network
« Reply #50 on: October 02, 2015, 08:29:16 pm »
in.abit is ready.
Code: [Select]
get_witness in.abit
{
  "id": "1.6.31",
  "witness_account": "1.2.38993",
  "last_aslot": 0,
  "signing_key": "GPH65XNUxWdYGqGyW9NtXdRpNntumLYT1cJ7CNE7F78Pwxrnx6cbV",
  "vote_id": "1:51",
  "total_votes": 0,
  "url": "https://github.com/abitmore",
  "total_missed": 0
}
BTS account: abit
BTS committee member: abit
BTS witness: in.abit

Offline bytemaster

Re: October 2nd Test Network
« Reply #51 on: October 02, 2015, 08:31:01 pm »
Sadly there is need for a hardfork for this testnet... this time I promise to upgrade the init nodes.

The issue discovered is that the witness count code was setting a threshold equal to 50% of all stake rather than 50% of voting stake so every witness got voted in unless over 50% of the stake voted for less than everyone.   In other words, the reverse case from the prior hardfork.   

I set the fork time for 24 hours from now.

For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4511
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
Re: October 2nd Test Network
« Reply #52 on: October 02, 2015, 08:33:30 pm »
Code: [Select]
info
{
  "head_block_num": 8144,
  "head_block_id": "00001fd007dda4aa0252b904036549e43452eba8",
  "head_block_age": "23 seconds old",
  "next_maintenance_time": "27 minutes in the future",
  "chain_id": "c746b258deb5e476601488d8dbb98cf6dcacc2dec857fda58514907257d461c3",
  "participation": "98.43750000000000000",

What's wrong?
BTS account: abit
BTS committee member: abit
BTS witness: in.abit

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4511
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
Re: October 2nd Test Network
« Reply #53 on: October 02, 2015, 08:37:07 pm »
Sadly there is need for a hardfork for this testnet... this time I promise to upgrade the init nodes.

The issue discovered is that the witness count code was setting a threshold equal to 50% of all stake rather than 50% of voting stake so every witness got voted in unless over 50% of the stake voted for less than everyone.   In other words, the reverse case from the prior hardfork.   

I set the fork time for 24 hours from now.
OK. Building.
in.abit updated.
« Last Edit: October 02, 2015, 08:52:52 pm by abit »
BTS account: abit
BTS committee member: abit
BTS witness: in.abit

Offline Fox

Re: October 2nd Test Network
« Reply #54 on: October 02, 2015, 08:52:29 pm »
Sadly there is need for a hardfork for this testnet... this time I promise to upgrade the init nodes.

The issue discovered is that the witness count code was setting a threshold equal to 50% of all stake rather than 50% of voting stake so every witness got voted in unless over 50% of the stake voted for less than everyone.   In other words, the reverse case from the prior hardfork.   

I set the fork time for 24 hours from now.
Is this why my witness was expected to produce blocks as soon as create_witness <accountname> "URL" true completed?  I was quite surprised to have 0 votes and missing blocks.

Rebuilding...
Witness: fox

Offline spartako

  • Sr. Member
  • ****
  • Posts: 401
    • View Profile
Re: October 2nd Test Network
« Reply #55 on: October 02, 2015, 08:59:00 pm »
Sadly there is need for a hardfork for this testnet... this time I promise to upgrade the init nodes.

The issue discovered is that the witness count code was setting a threshold equal to 50% of all stake rather than 50% of voting stake so every witness got voted in unless over 50% of the stake voted for less than everyone.   In other words, the reverse case from the prior hardfork.   

I set the fork time for 24 hours from now.

spartako updated to last master
wallet_account_set_approval spartako

Offline bytemaster

Re: October 2nd Test Network
« Reply #56 on: October 02, 2015, 08:59:56 pm »
Sadly there is need for a hardfork for this testnet... this time I promise to upgrade the init nodes.

The issue discovered is that the witness count code was setting a threshold equal to 50% of all stake rather than 50% of voting stake so every witness got voted in unless over 50% of the stake voted for less than everyone.   In other words, the reverse case from the prior hardfork.   

I set the fork time for 24 hours from now.
Is this why my witness was expected to produce blocks as soon as create_witness <accountname> "URL" true completed?  I was quite surprised to have 0 votes and missing blocks.

Rebuilding...

More or less.
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline bytemaster

Re: October 2nd Test Network
« Reply #57 on: October 02, 2015, 09:02:31 pm »
I had to take down init node to compile because while it was running I didn't have enough RAM :(
For the latest updates checkout my blog: http://bytemaster.bitshares.org
Anything said on these forums does not constitute an intent to create a legal obligation or contract between myself and anyone else.   These are merely my opinions and I reserve the right to change them at any time.

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4511
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
Re: October 2nd Test Network
« Reply #58 on: October 02, 2015, 09:14:58 pm »
"Normal" price feeding activated.
BTS account: abit
BTS committee member: abit
BTS witness: in.abit

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4511
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
Re: October 2nd Test Network
« Reply #59 on: October 02, 2015, 09:17:02 pm »
I had to take down init node to compile because while it was running I didn't have enough RAM :(
All init nodes are running in one VPS? Number of init nodes are more than 1/3 of all witnesses.. Will it kill the network?
BTS account: abit
BTS committee member: abit
BTS witness: in.abit