0 Members and 1 Guest are viewing this topic.
get_witness delegate.baozi{ "id": "1.6.1569", "witness_account": "1.2.22439",
What is the best practice for not missing any block during an update?
Quote from: bytemaster on September 21, 2015, 10:18:20 pmAll witnesses please upgrade to the latest master. We have checked in a few "hard-forking" fixes for publishing price feeds. This hardfork was required due to a misconfigured genesis state for bitassets preventing us from publishing feeds. Please do not attempt to publish price feeds for at least 24 hours to give all testers a chance to upgrade to the latest.Fox I voted you in. The least approved witness is bitcube which as 13M votes...Forgive my ignorance. How to "upgrade to latest master"?Is this just "git pull master" and restart witness?, or does this require a complete rebuild and "git checkout master" ??I assume "git checkout test3" would just be the same thing I'm already running.
All witnesses please upgrade to the latest master. We have checked in a few "hard-forking" fixes for publishing price feeds. This hardfork was required due to a misconfigured genesis state for bitassets preventing us from publishing feeds. Please do not attempt to publish price feeds for at least 24 hours to give all testers a chance to upgrade to the latest.Fox I voted you in. The least approved witness is bitcube which as 13M votes...
git checkout mastergit pullgit submodule update --init --recursivecmake .make
Upgraded to the master, during the update I missed 2 blocks.What is the best practice for not missing any block during an update?
do delegates or witnesses produce feeds?
The Fox witness node is operational. Thanks in advance for your votes.Code: [Select]get_witness fox{ "id": "1.6.2104", ... "total_votes": "1306663376502", ...}
get_witness fox{ "id": "1.6.2104", ... "total_votes": "1306663376502", ...}
>>get_global_properties ], "active_witnesses": [ "1.6.1", ... "1.6.5252" ]
@bytemaster can we test the affiliate system, or is this still in development?