You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are three RPC responses to the register call:
unregistered, no deposits (failure 1)
registered already (failure 2)
unregistered, deposit exists (success)
Should use binary search to find the next available sequence number for user. Prax can store it directly and the latest sequence number can be found on demand with at most 16 RPC requests
Let's say someone has already generated 50 addresses. Any sequence <=50 will result in an RPC success (aka already deposited). Anything >50 will return an error. So we keep splitting the address space in half, checking for success/error until we come down to two (50 success, 51 error).
Proposed design
States to consider:
If toggling the noble one, should replace the identicon with Noble icon + Noble address
Likely should ditch the incognito icons
Have a disable UI state so two can't be toggled at once
Requires refactoring this component
Needs loading/loaded/error states
The text was updated successfully, but these errors were encountered:
maybe this should be moved back into the backlog / blocked – according to henry, "forwarding addresses may have slipped schedule and might be pushed to next year."
Implement the web version in Prax of penumbra-zone/penumbra#4878. Noble launching feature Early Nov.
Follows this userflow:
Getting sequence numbers
There are three RPC responses to the register call:
Should use binary search to find the next available sequence number for user. Prax can store it directly and the latest sequence number can be found on demand with at most 16 RPC requests
Let's say someone has already generated 50 addresses. Any sequence <=50 will result in an RPC success (aka already deposited). Anything >50 will return an error. So we keep splitting the address space in half, checking for success/error until we come down to two (50 success, 51 error).
Proposed design
States to consider:
The text was updated successfully, but these errors were encountered: