Lock Creation transactions stuck in "Submitted" state

[cnasc]

Describe the bug
On the creator dashboard, some transactions always show as "Submitted". We need to investigate that and fix it.

To Reproduce
This is visible on staging, if you have already created some locks you should see 1 or 2.

These lock creations also have some missing data in Redux:

I believe that the transactions which only have hashes are in that state because of unrelated contract issues, but the two with additional metadata are the locks in the screenshot above.

[cnasc]

I am so far unable to reproduce this locally

[cellog]

The bug is one I have seen many times, including locally. It seems it is caused by the lock address guesser guessing that the lock will be the next value. In other words, if you were to refresh and create another lock, it would have address 0x0250...

[cnasc]

Not sure if we're talking about the same thing, these locks persistently show in this state, not just temporarily after creation

[cellog]

ah, even on refresh you see 2 locks?

[cnasc]

Yep

[cnasc]

Aha. Contract fix has deployed, which cleared up a number of things. Now there is only one lock stuck at "Submitted" and here's why:

Two transactions for the same lock.

Edit: this is not the issue, that's one lock creation and a key purchase...

[cnasc]

This may be resolved