Recovery mode doesn't work.

[hsynorg]

Hello,

Recovery mode seems like doesn't work.

Here is an example:

https://imgur.com/ODgAwSG

What's the reason and what's the solution?

I've also tried to test as much as I can. I found some other issues as well, I will post them.

[teutsch]

Thanks for the feedback! Recovery mode only resumes a task with bonded deposit. In this case, this deposit was slashed, so there's nothing left to do. The task has already ended.

[hsynorg]

It's really not good experience. The deposit is slasing due to waiting for network (It's not related to gas fee, even if I set high gas fee sometimes it got confirmantion after 3-4 mins.)

I think it's not tested enough on Mainnet. Because in eth mainnet tx can not be so fast and in many steps there a timings (timeout to 240 sec.) I can't understand why a blockchain solution would depend on time? (The network is not stable always)

For example, many times I faced error on task finalizing step.

Let's make it clear.

Task submitter, submitted the task on the network.
Solver: Successfully submitted the solution.
Verifier: Successfully verifying the task.

But then in final step.

Finalizing the task..

Submitted the commit.

Waiting..

Re-Finalizing.. (? I think in my opinion it's not needed. Because there is already one which submitted)

Waiting...

Re-Finalizing.. (C'mon whats happening? There is already 2 commit, it's awaiting approvement from the network)

Waiting...

Re-Finalizing.. (? more)

..
..

Ups slahed?

Oh no!

OK, Lets try to recover the task. Oh wait, there is no task can be recovered. (But why? I can see the list there is my task.)

[paidee]

Jason, I've also tried testing as well and it fails. Any ideas on what might be going wrong? Thanks, Pat Aidee

…

On Tue, Jun 1, 2021 at 8:19 AM hsynorg ***@***.***> wrote: Hello, Recovery mode seems like doesn't work. Here is an example: https://imgur.com/ODgAwSG What's the reason and what's the solution? I've also tried to test as much as I can. I found some other issues as well, I will post them. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#8>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACRVAMORRDV5NKEBJSEKZELTQTF4LANCNFSM454RUDLA> .

[teutsch]

We need to investigate this further. @paidee @hsynorg Have you seen this problem on Görli as well, or just Ethereum mainnet? It would be helpful if you could share some Etherscan link(s) to transactions that were connected to these tasks.

[hsynorg]

@teutsch Thanks for replying. Actually on testnet I didn't get too much (I guess because network is fast and stable).

I did more tests and I'd like to share with you.

1. Registering IPFS.. But seems like it's trying to register my local IP. I've tried few time but always local IP (127 and 192)
   
   

2. Task giver, after got the solution and verified by 2 verifiers. Just canceled? Really bad experience.
   

3. Task submitter. 1 tx (contract creation) confirmed, waiting second and third tx. But while awaiting for the 3rd tx. just canceled because of 240 seconds. (I think this shouldn't be at all at least it has to be more long, it should wait for the network. I tried to change blockLimit from the file but seems like it doesn't take in consideration (or might I didn't do in correct way)
   

I have more test. I'd love to share more.

[paidee]

Thank you hsynorg. Thanks, Pat Aidee

…

On Tue, Jun 1, 2021 at 8:19 AM hsynorg ***@***.***> wrote: Hello, Recovery mode seems like doesn't work. Here is an example: https://imgur.com/ODgAwSG What's the reason and what's the solution? I've also tried to test as much as I can. I found some other issues as well, I will post them. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#8>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACRVAMORRDV5NKEBJSEKZELTQTF4LANCNFSM454RUDLA> .

[paidee]

Sorry. I have been tied up with other tasks.

…

On Wed, Jun 2, 2021 at 12:13 PM Pat Aidee ***@***.***> wrote: Thank you hsynorg. Thanks, Pat Aidee On Tue, Jun 1, 2021 at 8:19 AM hsynorg ***@***.***> wrote: > Hello, > > Recovery mode seems like doesn't work. > > Here is an example: > > https://imgur.com/ODgAwSG > > What's the reason and what's the solution? > > I've also tried to test as much as I can. I found some other issues as > well, I will post them. > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#8>, or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ACRVAMORRDV5NKEBJSEKZELTQTF4LANCNFSM454RUDLA> > . >

[teutsch]

1. You can use ipfs id at the Docker command line or inside Truebit OS. If you want to register a specific address in Truebit OS, you can use the -i flag, e.g. ipfs register -i 2, otherwise Truebit OS randomly chooses one of your addresses to register.

2. It looks like the Solver dropped out here. What behavior would you expect in this situation?

3. The 240 second timeout has nothing to do with the blockLimit -- that's just built in to web3.js. This error means that your transaction did not get included in a block. The blockLimit pertains to a different kind of timeout, namely the amount of time that Solvers and Verifiers have to compute their solutions locally.

Please share all your feedback on Canny. We welcome any comments, feedback, and suggestions! https://truebit.canny.io/truebit-feedback @smfang

[teutsch]

@smfang Shall we port this thread over to Canny?

[hsynorg]

@teutsch I'd create more posts on Canny for sure.

[teutsch]

@hsynorg Thank you!

[hsynorg]

@hsynorg Thank you!

You're welcome. I lost about 2 ETH for testing :) I should have enough test feedbacks :) By the way I'm also a test developer.

I will post on Canny when I have free time.

[paidee]

:)

…

On Wed, Jun 2, 2021 at 1:13 PM hsynorg ***@***.***> wrote: @hsynorg <https://github.com/hsynorg> Thank you! You're welcome. I lost about 2 ETH for testing :) I should have enough test feedbacks :) By the way I'm also a test developer. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#8 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACRVAMJXCVEKM3JKYN5GKMDTQZRDXANCNFSM454RUDLA> .

[teutsch]

@hsynorg Could you please send your resume to hello@truebit.io?

[hsynorg]

@hsynorg Could you please send your resume to hello@truebit.io?

It will be my pleasure. I will definitely do!