L1 vs L2 update timing snag

[thelifeandtimes]

Describe the bug
If you try to update your L1 seed (in this specific case the mananagement proxy) even through the L1 chain state updates immediately, if you try to fast follow with an L2 action (in this case, accepting a sponsorship request on L2 by an L2 planet), it will fail to recognize the updated seed.

To Reproduce
Steps to reproduce the behavior:

1. from an L2 point, send a request to a L1 star for sponsorship
2. Add a management proxy for your star
3. After the transaction confirms and your management proxy shows in bridge as the newly set address, try to accept the sponsorship request from the L2 point
4. See error

Expected behavior
An L1 update should be immediately actionable for any behaviors.

Screenshots

Desktop (please complete the following information):

• OS: MacOS
• Browser: Brave

Login method (please complete the following information):
Metamask, with newly set management proxy

Additional context
Came across this while trying to accept sponsorship request noted in #1144

[thelifeandtimes]

FTR, this worked smoothly ~ 10 hours later. All original attempts happened within ~60 mins of each other.