Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug hunting: attempt to lock coins for Tap addr until 10min time out #515

Closed
wants to merge 1 commit into from

Conversation

ffranr
Copy link
Contributor

@ffranr ffranr commented Sep 20, 2023

This PR shouldn't be merged.

This PR attempts to reproduce bug: #508

It does so by creating an itest that does the following using the same Tap address throughout:

  1. Kick off an asset send event. Do not mine.
  2. Kick off another send event. This should through up a coin lock error and force the address to get stuck behind a timeout.
  3. Mine 6 blocks.
  4. Kick off another send event which should have succeeded (but does not) were it not for step 2.

In it's current state, this PR does not capture the bug. I thought that it used to, but having cleaned up the code, it doesn't anymore.

@Roasbeef
Copy link
Member

In it's current state, this PR does not capture the bug. I thought that it used to, but having cleaned up the code, it doesn't anymore.

I thought it was more like:

  • send to asset using addr A
  • mine a block
  • send again using addr A
  • it fails oddly

@ffranr
Copy link
Contributor Author

ffranr commented Sep 22, 2023

Closing in favour of #529

@ffranr ffranr closed this Sep 22, 2023
@guggero guggero deleted the multi-send-bug branch October 11, 2023 21:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: ✅ Done
Development

Successfully merging this pull request may close these issues.

Generalise multiverse method names to support all proofs.
2 participants