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
The Prax registry currently provides default numeraires. These values are important given the block processor will be referencing these as it saves swaps to the PRICING tables in indexeddb.
At the moment, there is no way for users to change these.
Proposal
In onboarding, we add a numeraire selection step. It will be populated by choices (can select multiple) from the Prax registry. It also should not communicated as "Choose your numeraire", but use text that clearly associates this selection with the pricing their see in minifront. Something like: "In which token denomination would you prefer to price assets?"
This selection should also be featured in the extension's settings to allow them to change it. Making a change should likely require restarting the block processor (or ext services) so it pulls in the latest values and saves those to the DB. We should also likely invalidate entries in the PRICING table related to the numeraire we removed.
The text was updated successfully, but these errors were encountered:
The Prax registry currently provides default numeraires. These values are important given the block processor will be referencing these as it saves swaps to the PRICING tables in indexeddb.
At the moment, there is no way for users to change these.
Proposal
In onboarding, we add a numeraire selection step. It will be populated by choices (can select multiple) from the Prax registry. It also should not communicated as "Choose your numeraire", but use text that clearly associates this selection with the pricing their see in minifront. Something like: "In which token denomination would you prefer to price assets?"
This selection should also be featured in the extension's settings to allow them to change it. Making a change should likely require restarting the block processor (or ext services) so it pulls in the latest values and saves those to the DB. We should also likely invalidate entries in the PRICING table related to the numeraire we removed.
The text was updated successfully, but these errors were encountered: