Can not import xml on V0.6.0a about ot-node HOT 4 CLOSED

After I switch to "develop" branch. Now, everything can work. Thank you @schrink

from ot-node.

Hi,

Your import seems to pass well, what happens is that DH is not able to communicate with DC. You see the error "Invalid target in proof". It means that it's identity is with different difficulty that identity of DC. It could happen if you set one of them to run on test network and other not. I see in your .env that both are on the test network, but it is likely that when you first generated identity for one of them this switch was off.

Anyway, to solve this, you have to recreate the identity. To do this, delete all files in /keys folder (leave folder empty). Then make sure that bot .env have TEST_NETWORK_ENABLED=1 (or 0 but they must be the same), and then try everything again.

Please let me know if it works.

Regards, V.

from ot-node.

On bootstrap node, I have new error. You can check this photo

This is error on regular node. You can check this photo and this photo

I use this command for import to Regular node: curl -v -F importfile=@example_gs1.xml http://127.0.0.1:8901/import_gs1

I make the folder "key" empty on two node and run "npm run config" before "npm start".

Thank you.

from ot-node.

This is what happened. The DH node failed to reveal a bid (your bootstrap node), therefore the DC node also failed to choose bids as there are no revealed bids.

This may happen if transaction on blockchain takes too long (or even too short) as these are time synced operations. It is related to how Rinkeby is working at the moment. This is a known bug that happens sometimes. I can't reproduce it on my machine, but we had it happen to us as well few sometimes.

We are just finishing and testing improved version that will not depend on time but blockchain events. I will let you know as soon as it is pushed. It should completely solve this issue.

from ot-node.