This issue is dependent on #32 and cannot meaningfully proceed until it has been resolved.
Once the mainnet namespace (provisionally under grid.hypr has been deployed) and all requisite account implementations have been created, the provider must then support permissionless self-registration: once a provider has been tested once, the subsequent "publish" action should take the user into a flow that has them sign a number of transactions in order to mint the appropriate sub-entry and then the appropriate notes.
This interface should take heavy inspiration from the core Hyperware onboarding flow where the user mints their name and sets their networking notes, although in this case it will be the already established ~provider-id, ~price, ~wallet, ~description, and ~instructions notes.
It should also mimic that onboarding flow in that it is intended to be used with a browser wallet (a la Metamask) and use RainbowKit to maintain consistency across Hyperware and Hypergrid.
This issue is dependent on #32 and cannot meaningfully proceed until it has been resolved.
Once the mainnet namespace (provisionally under
grid.hyprhas been deployed) and all requisite account implementations have been created, the provider must then support permissionless self-registration: once a provider has been tested once, the subsequent "publish" action should take the user into a flow that has them sign a number of transactions in order to mint the appropriate sub-entry and then the appropriate notes.This interface should take heavy inspiration from the core Hyperware onboarding flow where the user mints their name and sets their networking notes, although in this case it will be the already established
~provider-id,~price,~wallet,~description, and~instructionsnotes.It should also mimic that onboarding flow in that it is intended to be used with a browser wallet (a la Metamask) and use RainbowKit to maintain consistency across Hyperware and Hypergrid.