HyperBEAM Integration / Dryrun Removal

[NickJ202]

The following processes / set of processes need to send patch messages to have state accessible directly from HyperBEAM in order to remove the need for dry-runs. Each item below contains the necessary migration steps in order to fully remove dry-run as well as global UCM reliance. There are also other overall updates listed under certain items that need to be completed before this can be released.

• Assets / Orderbooks
  • Add patch where necessary in ucm-bundled and activity-bundled
  • Create an update that creators can run which will spawn a new order book / activity process for all of their assets. This should account for the global UCM transferring any current listings / balances of the asset to the new order book processes.
• Profiles
  • Single
    • Zone migration update - Create all new zone processes and add patch accordingly.
    • Remove the need for the registry, with cache requests we should be able to fetch many profiles at once without relying on a central process. Also create lookups by wallet address via the gateway.
  • Registry
    • Remove the reliance on this process (see above).
• Collections
  • Single
    • Create an update that creators can run which adds a patch message when any part of the collection is updated.
  • Registry
    • Add a patch message on collection addition / removal.
• Stamps
  • On hold
• PIXL / Streaks
  • On hold