Here what I see with my witness for block production:

Code: [Select]

new >>> info
info
{
  "head_block_num": 12057,
  "head_block_id": "00002f19643260855f86fdb11d4947d3cb7eec7b",
  "head_block_age": "7 hours old",
  "next_maintenance_time": "6 hours ago",
  "chain_id": "0682819add44adb68b5ae8fa24bcd23bca930d5fe9eda95e7e09343c53ee0859",
  "participation": "15.62500000000000000",

This is what I see with observer witness:

Code: [Select]

info
{
  "head_block_num": 14541,
  "head_block_id": "000038cd712f759764979352e3f068072ce7fabf",
  "head_block_age": "4 hours old",
  "next_maintenance_time": "3 hours ago",
  "chain_id": "0682819add44adb68b5ae8fa24bcd23bca930d5fe9eda95e7e09343c53ee0859",
  "participation": "41.40625000000000000",

And this error code:

Code: [Select]

1542346ms th_a       fork_database.cpp:57          push_block           ] Pushing block to fork database that failed to link: 000038e34c78828a6de58c8f7c45a4765d35702d, 14563
1542347ms th_a       fork_database.cpp:58          push_block           ] Head: 14542, 000038cee9a448ff754f72a7f2e575eaf72f37cd
1542430ms th_a       application.cpp:416           handle_block         ] Error when pushing block:
3080000 unlinkable_block_exception: unlinkable block
block does not link to known chain
    {}
    th_a  fork_database.cpp:79 _push_block

    {"new_block":{"previous":"000038e2edba3a14378292e57d79343e86ada943","timestamp":"2015-10-02T03:21:36","witness":"1.6.10","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f7c5fa17577ff0fdbe0d3966b2e858c8484e6ade8d55188331e46eddcf58d5e6b258951127c9e311446a61bd432a4854b376a75a9812a28f2793a16586aee5378","transactions":[]}}
    th_a  db_block.cpp:195 _push_block


same as me....

I'm up and ready, waiting for votes.

Any new nodes ? I have deleted the database, and try to sync, but after a few hours (just checked) still nothing.

Quote from: betax on September 28, 2015, 12:06:47 pm

Quote from: fav on September 28, 2015, 11:51:18 am

http://www.bbc.co.uk/news/world-europe-34372548

I think we got yet another use-case for pegged digital currencies coming soon.

Why? Even (if unlikely) they form a new state / country. They will use the Euro. In theory this should not affect Europe as a whole, just Spain central government getting less taxes.

I don't know that much about euro rule, but I very much doubt they can stay in the euro zone.

They won't separate if they cannot stay in the Euro, it won't make economical sense, which is one of the main drivers. Since Spain joined the ECC, separatists catalonians wanted to be more part of Europe than Spain. But yes you are right, it has also been mentioned that it will be an illegal separation and won't be back up by the ECC, hence they won't be able to use the Euro.

Quote from: Ander on September 27, 2015, 06:26:58 pm

Dang, think of how many bitshares you could get for the price of a ticket!

I'm thinking more of what opportunites this could bring in for BitShares in general

Exactly

im back up now...

Very good job!!!

Quote from: Riverhead on September 24, 2015, 09:04:24 pm

Missing some blocks - playing around with update_witness command and using past, present, and new keys.

1) On 1st server blocks are being signed.
1) On 2nd server I launched the witness_node with new keys.
2) On 2nd server I started a client with a new wallet
4) On 2nd server I import_key "riverhead" "privatekeyhere" and it returns "false"
5) On 2nd server if I type "list_my_accounts" I see riverhead but it has the key from server 1 (the active witness key)
6) On 2nd server if I type "dump_private_keys" I see the pub/priv key pair from step 4
7) On 2nd server type: update_witness "riverhead" "publickeyfromstep 4" which returns:

Code: [Select]

update_witness riverhead "" "GPH5AB42MtMGrcnjtgSjwSp7T6u79Te3FnGKC5gj7vdUKNQ9hU1AL" true
10 assert_exception: Assert Exception
it != _keys.end():
    {}
    th_a  wallet.cpp:602 get_private_key

    {"witness_name":"riverhead","url":"","block_signing_key":"GPH5AB42MtMGrcnjtgSjwSp7T6u79Te3FnGKC5gj7vdUKNQ9hU1AL","broadcast":true}
    th_a  wallet.cpp:1401 update_witness
unlocked >>>

Dumping private keys on the 2nd server returns the pub/priv key for the U1AL pair.

Hi,

Similar steps, but in the same server.

1. Update / compile previous installation in another directory.
2. Run witness / not producing blocks to sync
3. Open client pointing to original witness
4. suggest_brain_key
5. Close new witness and restart with new port for rpc, and new key pair.
6. Back to client (still running) and update_witness betaxtrade "" "PUBLIC KEY" true
7. Get witness, and signing key is the new one
8. Run a few times get witness to see i am producing blocks

9. Confusing part.. dump_private_keys has the old one.

10. Stop other witness
11. Start cli with new port

Yes, my UI is frozen on explorer blocks (Chrome), I'm currently sending 20 at a time.