Stop playing w fire, say no to Burner accts

Our objective was add a missing feature to MUD. Following a swift discussion, we unanimously concluded that MUD required a mechanism enabling users to leverage their personal accounts, while simultaneously utilizing burner wallets, managed by the client, for transaction execution.

We worked on creating and refining the tech design (https://www.figma.com/file/nme50Thgp2rr3AFOPl48J9/Account-Abstraction-WIP?type=whiteboard&node-id=0%3A1&t=6RcrdntG3fLPXFow-1), and then we started coding the smart contracts (including limit checker, account systems, external-to-MUD Account, and auth helper contracts), along with a user interface that simplifies the process of creating a new account and signing messages to grant the client transaction execution permissions from their Account.

Our work was condensed into a single weekend, which was both an exhilarating experience and a significant learning opportunity. We hope that our efforts will prove beneficial for the MUD team and other developers within the MUD ecosystem :)

Our project was entirely built using the MUD framework. We just used the OZ library to do message signing.

While we did attempt to experiment with modifying the OP Stack, we found it to be quite complex and time-consuming, particularly given the limited duration of the hackathon.

We successfully ran and modified two projects, ticking-optimism(https://github.com/therealbytes/ticking-optimism) and ticking-conway (https://github.com/therealbytes/ticking-conway). Our goal was to integrate an automation system into the Account via the Tick mechanism. However, this integration with the existing MUD boilerplate proved challenging. Based on our observations from the ticking-conway repository, a significant number of complex and disruptive changes would need to be made to our boilerplate to support the ticking-optimism network. So we chose to not develop that feature :(

We know that both OP Stack and MUD are young projects, so no pressure at all, but it'd be awesome if the flow of modifying the OP Stack was better integrated into the MUD lifecycle.

On MUD, we also found that it's great for fast prototyping, but if you want to get your hands dirty and dig though how it works underneath it becomes quite an obscure place without much documentation or examples. Having said this, the MUD team did a GREAT job at helping and providing feedback in a timely manner <3