Main Menu

October 2nd Test Network

Started by bytemaster, October 02, 2015, 01:17:03 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

bytemaster

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: [url="http://bytemaster.bitshares.org"]http://bytemaster.bitshares.org[/url]
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.

bytemaster

Quote from: Fox on October 02, 2015, 08:52:29 PM
Quote from: bytemaster 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.
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: [url="http://bytemaster.bitshares.org"]http://bytemaster.bitshares.org[/url]
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.

spartako

Quote from: bytemaster 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.

spartako updated to last master
wallet_account_set_approval spartako

Fox

Quote from: bytemaster 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.
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

abit

#54
Quote from: bytemaster 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.
OK. Building.
in.abit updated.
BitShares committee member: abit
BitShares witness: in.abit

abit


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?
BitShares committee member: abit
BitShares witness: in.abit

bytemaster

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: [url="http://bytemaster.bitshares.org"]http://bytemaster.bitshares.org[/url]
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.

abit

in.abit is ready.

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
}
BitShares committee member: abit
BitShares witness: in.abit

iHashFury

Quote from: bytemaster 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.

aka  'voter apathy test'  ;)

bytemaster

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: [url="http://bytemaster.bitshares.org"]http://bytemaster.bitshares.org[/url]
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.

CalabiYau

#48
Quote from: spartako on October 02, 2015, 01:47:38 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
required 20.05566 CORE
to set voting proxy to 'dan'
thank you.

pc

Bitcoin - Perspektive oder Risiko? ISBN 978-3-8442-6568-2 [url="http://bitcoin.quisquis.de"]http://bitcoin.quisquis.de[/url]

ElMato

Should we start publishing price feeds?
I want to test again the forced settlement  :)

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

cass

Quote from: betax on October 02, 2015, 03:50:30 PM
I love how fast is the response to the ui, had to make a video ;) https://www.youtube.com/watch?v=Sa9Zmt8aVMM&feature=youtu.be

yeah   +5%-- small spelling mistake on video title

Bitshares 2.0 Tes t net UI
█║▌║║█  - - -  The quieter you become, the more you are able to hear  - - -  █║▌║║█

spartako

Quote from: spartako on October 02, 2015, 03:35:54 PM
Quote from: clayop on October 02, 2015, 03:28:52 PM
Quote from: spartako on October 02, 2015, 03:24:40 PM
It seems the network code is much better than previous testnet (1624 tx in block:  541 tx/sec)

https://graphene.bitshares.org/#/block/2577


I found that block interval is 6 second for that block. So... 270 tps :(

Yes it is true, some delegates lost is turn and the block interval was 6 second

1296 tx in block 3435 and it is 3s block -> 432 tps

https://graphene.bitshares.org/#/block/3435
wallet_account_set_approval spartako