bridge
bridge copied to clipboard
urbit
Networking Key not included in passport folder when custodying L2 Planet via Invite Flow
Only the master ticket and management proxy were included? Really messes with the user experience because then they have to go back through Bridge if they want to boot. @nerveharp
To clarify, the bridge page for claiming a planet explicitly says a networking key was included in the zip file, but its not there
@tacryt-socryp @ixv What login method and browser was used when generating the invites?
We generated the invites ourselves in hoon. I don't think we messed anything up because we were able to log in with the master ticket that was generated.
The code for it is here: https://github.com/tirrel-corp/studio/blob/master/app/shop.hoon#L156 We do a spawn, configure-keys, and then transfer-point
@ixv Approximately how much time passed between the invite creation and activation? wondering if the roller had not yet processed the batch before the activation
Tagging @nerveharp about this and asking internally, thanks. Have you seen it happen again (tweet looks old, digging around see speculation about it being inconsistent/load related - trying to narrow down)
No, this is not resolved. This is a major issue, as it really affects the user experience of people buying L2 planets via an activation ticket.
I am fairly confident that the issue is that /app/shop does not set the management proxy like Bridge does.
This is a planet that exhibits the issue, and this one does not. The only difference in azimuth state is the management proxy stuff which happens here. Someone should test out this theory, @ixv @tacryt-socryp.
