search

urbit / bridge

An application for interacting with Azimuth.
MIT License
96 stars 25 forks source link

invites: star w/ L2 proxy missing L2 functionality #964

Open jamesacklin opened 2 years ago

jamesacklin commented 2 years ago

A L1 star with its spawn proxy set to L2 does not get the "Create Invites" button despite the L1 transaction succeeding.

This is visible on both Ropsten and mainnet.

image

Additionally, the "Spawn Proxy Address" says "Not set," despite the current address being set to 0x1111[...]1111.

image

image

jamesacklin commented 2 years ago

The correct details eventually appeared, but only after a considerable amount of time had passed. Leaving this in the critical path for now as it is relatively unsettling and likely to be reported as an error.

image

image

arthyn commented 2 years ago

So this works like you said, but it's another further case of migrating a ship puts it in a limbo state that we need to figure out how to track better. Getting a few people with more knowledge about what's happening transaction-wise would help and we can get a few of these similar tickets addressed.

tomholford commented 2 years ago

Per out of band conversation with @Fang- , we could potentially mitigate this limbo period with the roller's predicted state:

https://urbit.github.io/roller-rpc-client/index.html#getpredictedstate

kennyrowe commented 2 years ago

Is this limbo state permanent or does it resolve over time. I just move my spawn proxy to L2 and bridge seems to be unaware of the update.

lukestiles commented 2 years ago

How long does the limbo state last?

kennyrowe commented 2 years ago

How long does the limbo state last?

It took several hours for the UI to reflect the update in my case.