Quote from: bytemaster on September 23, 2015, 05:48:12 PM
delegate-1.lafona  what happened to your node?

It looks like I am on a fork.

2813283ms th_a       fork_database.cpp:57          push_block           ] Pushing block to fork database that failed to link: 00020081f8a1dd2c575919181724f39ca247d8a1, 131201
2813283ms th_a       fork_database.cpp:58          push_block           ] Head: 131108, 00020024713817f57183d045cdecaf3303acbf0d
2813283ms th_a       application.cpp:415           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":"00020080759ee5c5fc93983b99af426e9d3fcf36","timestamp":"2015-09-23T15:02:12","witness":"1.6.7","transaction_merkle_root":"0000000000000000000000000000000000000000","extensions":[],"witness_signature":"1f65d50fe53a1c376657599d29910bf650086d48a4642b43f5b654d083ef6052a30997ecdac3dab252a2e0e83f9294363a9faacccec6f2852e94643ce22143a689","transactions":[]}}
    th_a  db_block.cpp:195 _push_block



I won't have much time to go through the logs until tonight, but if it helps I will send you a link to the log files.

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. 

Quote from: boombastic on September 23, 2015, 06:34:03 PM
All right, I stopped the double signing attack just now.  First of all, I did do that.  :)  But it feels that didn't happen.  I sent various transactions to account hoping to see some balance missing, etc, but in vain.  The network seems totally immune to double signing.

Is that safe to say that 'evil' double signing in BTS1 era now goes into witness's toolbox.  We can use two machines as redundancy to prevent accident server shutdown?

If each witness double signs, fork never gets resolved i guess?

Quote from: boombastic on September 23, 2015, 06:34:03 PM
All right, I stopped the double signing attack just now.  First of all, I did do that.  :)  But it feels that didn't happen.  I sent various transactions to account hoping to see some balance missing, etc, but in vain.  The network seems totally immune to double signing.

Is that safe to say that 'evil' double signing in BTS1 era now goes into witness's toolbox.  We can use two machines as redundancy to prevent accident server shutdown?

Please don't do that.

All right, I stopped the double signing attack just now.  First of all, I did do that.  :)  But it feels that didn't happen.  I sent various transactions to account hoping to see some balance missing, etc, but in vain.  The network seems totally immune to double signing.

Is that safe to say that 'evil' double signing in BTS1 era now goes into witness's toolbox.  We can use two machines as redundancy to prevent accident server shutdown?

Quote from: clayop on September 23, 2015, 06:18:16 PM
I found no difference with my node during the double signing attack :)

100% participation during the attack :)

I found no difference with my node during the double signing attack :)

Quote from: boombastic on September 23, 2015, 05:40:16 PM
Double Signing attack test

Since I can't find more information about how double signing will harm the network and what defensive mechanism network will have against double signing, I am going to perform a 30 minutes double signing attack on test net.  Double signing could happen due to honest witness mis-configuring node, witness server compromised by evil third party or corrupted witness.

I have 3 witness accounts voted in that I can coordinate, I am going to try double signing from 1, 2, 3 witnesses using 2 separate servers (US, Asia).

Here is the plan:

The attack will last for 30 minutes, 3 phases, each will last for 10 minutes.

phase I (0-10min): 1 double signing witness (boombastic)
phase II (10-20min): 2 double signing witness (boombastic and mr.agsexplorer)
phase III (20-30min): 3 double signing witness (boombastic and mr.agsexplorer and mrs.agsexplorer)
end (30min): stop double signing

Double signing will cause fork, I want to see after all this mess, if network can recover, and I will do some transactions during the attack and see how it's gonna affect normal user operations.  If you are here, you can perform normal operation and report back after the attack is finished.

bytemaster, if you see this, please do not vote out these double signing witness just yet.  In real world, if some witness starts double signing, voters might not react that quickly, network should survive on its own for at least 30 minutes.

The attack will start at today  2015-09-23 18:00 (UTC), which is 20 mintues from now

In the spirt of the scientific method I will submit the hypothesis on what should happen:

Phase 1:
   The next witness will receive one of your blocks first and then save (but not switch to the other block)
   The next witness will pick one of the blocks to build off of
   All of the other nodes will switch as soon as the next witness produces a block and everything will be in sync.

Phase 2:
   WIll be identical to Phase 1 except in the case that both witnesses are scheduled back to back.  If they are scheduled back to back then it may take two blocks to resolve any forks.

delegate-1.lafona  what happened to your node?

Double Signing attack test

Since I can't find more information about how double signing will harm the network and what defensive mechanism network will have against double signing, I am going to perform a 30 minutes double signing attack on test net.  Double signing could happen due to honest witness mis-configuring node, witness server compromised by evil third party or corrupted witness.

I have 3 witness accounts voted in that I can coordinate, I am going to try double signing from 1, 2, 3 witnesses using 2 separate servers (US, Asia).

Here is the plan:

The attack will last for 30 minutes, 3 phases, each will last for 10 minutes.

phase I (0-10min): 1 double signing witness (boombastic)
phase II (10-20min): 2 double signing witness (boombastic and mr.agsexplorer)
phase III (20-30min): 3 double signing witness (boombastic and mr.agsexplorer and mrs.agsexplorer)
end (30min): stop double signing

Double signing will cause fork, I want to see after all this mess, if network can recover, and I will do some transactions during the attack and see how it's gonna affect normal user operations.  If you are here, you can perform normal operation and report back after the attack is finished.

bytemaster, if you see this, please do not vote out these double signing witness just yet.  In real world, if some witness starts double signing, voters might not react that quickly, network should survive on its own for at least 30 minutes.

The attack will start at today  2015-09-23 18:00 (UTC), which is 20 mintues from now

Quote from: mindphlux on September 23, 2015, 05:09:48 PM
I cannot register a new account in the GUI, it's always hanging at this screen after entering username+password:

I deleted all cookie and local storage before..

What to do? Is something crashed?

http://imgur.com/HtDO4bA

Also the webserver seems kind of slow, looks overloaded to me..

lagging for me too at the moment

I cannot register a new account in the GUI, it's always hanging at this screen after entering username+password:

I deleted all cookie and local storage before..

What to do? Is something crashed?

http://imgur.com/HtDO4bA

Also the webserver seems kind of slow, looks overloaded to me..

USD/CORE market is active now. https://graphene.bitshares.org/#/exchange/trade/USD_CORE

It's strange that lowest price is on the top but highest price at bottom.

I have my witness node running.
Need some votes.

elmato

Quote from: bytemaster on September 23, 2015, 02:37:45 PM
PEBKAC?

Problem Exists Between Keyboard and Chair - the usual source of my bugs.

Quote from: bytemaster on September 23, 2015, 02:37:45 PM
The CLI wallet format is not compatible with the GUI import format.  There is not currently an easy way to migrate from one wallet to the other.

Understood, thank you.