Author Topic: Test Net for Advanced Users  (Read 263617 times)

0 Members and 1 Guest are viewing this topic.

Offline clayop

  • Hero Member
  • *****
  • Posts: 2033
    • View Profile
    • Bitshares Korea
  • BitShares: clayop
delegate-clayop is updated.
Bitshares Korea - http://www.bitshares.kr
Vote for me and see Korean Bitshares community grows
delegate-clayop

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore

On a side note, the delegate seems to be out of the list of active witnesses,  but has enough votes to be middle of the pack. Any thoughts?

Code: [Select]
{
  "id": "1.6.1531",
  "witness_account": "1.2.22396",
  "last_aslot": 138787,
  "signing_key": "GPH5DCL5nbhL13sXBh1mwQp5pUBSw7rmwjWeiiy5b2Z2UxuYf8spU",
  "pay_vb": "1.13.57",
  "vote_id": "1:1530",
  "total_votes": "9524676529409",
  "url": ""
}
Every hour, only votes of  (new) active witnesses will be updated.
BitShares committee member: abit
BitShares witness: in.abit

Offline lafona

  • Sr. Member
  • ****
  • Posts: 231
    • View Profile
  • BitShares: lafona
delegate-1.lafona updated.

On a side note, the delegate seems to be out of the list of active witnesses,  but has enough votes to be middle of the pack. Any thoughts?

Code: [Select]
{
  "id": "1.6.1531",
  "witness_account": "1.2.22396",
  "last_aslot": 138787,
  "signing_key": "GPH5DCL5nbhL13sXBh1mwQp5pUBSw7rmwjWeiiy5b2Z2UxuYf8spU",
  "pay_vb": "1.13.57",
  "vote_id": "1:1530",
  "total_votes": "9524676529409",
  "url": ""
}
BTS Witnesses: delegate-1.lafona     Witness Thread: https://bitsharestalk.org/index.php/topic,21569.msg280911/topicseen.html#msg280911
MUSE Witness: lafona

Offline bytemaster

I was just testing claiming of genesis collateral positions (those who were short at the time of the snapshot) and discovered a bug that prevented the authority checks from passing.   

I have fixed the bug, but it will require all testing witnesses to upgrade or the test network will fork as soon as someone does something with a usd-collateral-holder-# account. 

Please upgrade your test node as soon possible so I can continue testing this feature without disruption.
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 svk

For the last 12 hours I've been unable to access the GUI on https://graphene.bitshares.org
The browser constantly shows the message  "waiting for graphene.bitshares.org".
mee  too

I just told Valentine, he'll look into it.
Worker: dev.bitsharesblocks

Offline wuyanren

  • Hero Member
  • *****
  • Posts: 589
    • View Profile
For the last 12 hours I've been unable to access the GUI on https://graphene.bitshares.org
The browser constantly shows the message  "waiting for graphene.bitshares.org".
mee  too

jakub

  • Guest
For the last 12 hours I've been unable to access the GUI on https://graphene.bitshares.org
The browser constantly shows the message  "waiting for graphene.bitshares.org".

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
BitShares committee member: abit
BitShares witness: in.abit

Offline clayop

  • Hero Member
  • *****
  • Posts: 2033
    • View Profile
    • Bitshares Korea
  • BitShares: clayop
Bitshares Korea - http://www.bitshares.kr
Vote for me and see Korean Bitshares community grows
delegate-clayop

jakub

  • Guest
Where is the best place to report bugs in the GUI?

Offline bytemaster

What is the best practice for not missing any block during an update?

The update_witness command in CLI wallet allows you to change your witness's block signing key.  This architecture allows several different downtime-free update procedures according to your specific hosting situation:
...

Thanks theoretical! Great work!

 +5% indeed, very useful and sounds like a fool-proof way to do it with no risk of signing double blocks.

One question: how long does it take for the signing key to be updated after you call the update_witness command? As soon as the transaction is processed by the network? After the next maintenance interval? Sth else?

I seem to recall that in BitShares 0.9.x changing the signing key did take a bit of time to go into effect, so that set_block_production true/false was the preferred way. If in graphene the call to changing the signing key takes effect immediately, then that's really nice as it's a much better way of doing it.

bump question @theoretical @bytemaster

Instantly
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 wackou

What is the best practice for not missing any block during an update?

The update_witness command in CLI wallet allows you to change your witness's block signing key.  This architecture allows several different downtime-free update procedures according to your specific hosting situation:
...

Thanks theoretical! Great work!

 +5% indeed, very useful and sounds like a fool-proof way to do it with no risk of signing double blocks.

One question: how long does it take for the signing key to be updated after you call the update_witness command? As soon as the transaction is processed by the network? After the next maintenance interval? Sth else?

I seem to recall that in BitShares 0.9.x changing the signing key did take a bit of time to go into effect, so that set_block_production true/false was the preferred way. If in graphene the call to changing the signing key takes effect immediately, then that's really nice as it's a much better way of doing it.

bump question @theoretical @bytemaster
Please vote for witness wackou! More info at http://digitalgaia.io

Offline wackou

For redundancy I think I will run multiple nodes with different signing keys.  I will then set up a single node to switch signing keys when my witness misses a block.

I feel like that's the way to go in order to have a backup node ready to pop up in case the main witness goes down for some reason. I will do the same, and encourage other witnesses to get familiarized with this way of doing it.
Please vote for witness wackou! More info at http://digitalgaia.io

Offline jtme

jtml - what kind of difficulties are you having at the moment, you have missed quite a few blocks recently.

witness crashed

Code: [Select]
witness_node: /mon/g/graphene/libraries/fc/src/thread/thread_d.hpp:370: bool fc::thread_d::start_next_fiber(bool): Assertion `std::current_exception() == std::exception_ptr()' failed.

auto start did not work , there was an error when replaying blockchain

Code: [Select]
Unable to create directories object_database/0
    {"path":"object_database/0","inner":"Dynamic exception type: boost::filesystem::filesystem_error\nstd::exception::what: boost::filesystem::create_directories: Permission denied: \"object_database\"\n"}

After some investigation, I've realized that the problem was in using an absolute path
for --data-dir.  All is written under the given absolute path except object_database, which
is written relative to the current dir (and the proccess did not have write access to that dir)
And it seems that the object_database is not needed and writen during the initial sync,
so the witness was running fine without the need to write to object_database for a while.

Not sure if this could cause the initial crash

The witness is now up and running again.

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4664
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
BitShares committee member: abit
BitShares witness: in.abit