PR #174 rebuilds most of the foundation of the web-app to operate on the framework needed to leave the MVP phase. With this, WebSockets become integrated, followed by clean-up in the supporting areas.

We have had to handle a bit of technical debt in the beginning; thus, this PR rebuilds every piece of the app. While we knew that we would one day want WebSockets, we did not expect to change our approach in such a severe manner.

To support this, the pieces are being developed in parallel to make the:

• API
• Frontend
• Smart Contract

All work together without compromise. Avoiding the typical downfall of traditional web3 app development, the on-chain team is the same as the off-chain; thus, we can secure benefits built into the product's core.

Moving forward, the technical overhead and developer onboarding are significantly lower due to the approachability and general architecture of the API and the consuming routes.

Once the app experience has been updated, the brand will also be updated in this same PR.

• Resolved by feat: goodbye authentication #207 with the deprecation of auth: Authentication is nice and smooth.
• Minting badges #197
• feat: managers and hooks #198
• c2b041c : Implement API support for balances and Badges as source.
• fix: holder table multicall mint and revoking #211 Frontend consumption of feat: managers and hooks #198 & 658c7f4.
• feat: complete websocket usage  #206 Use the Badge websocket source as the data source for Badges.
  • This will require slight data shifting up one level to drill down.
• Badge managers (just people no configuration) on the frontend.

Nice to haves:

• bba0746 : Refactor background jobs to be balancing / non-critical functionality.
  • Make sure that we are constantly updated with balances.
  • Refresh the static metadata of the Organization every so often.
  • Fill in IPFS metadata asynchronously instead of blocking.