The problem Phlocket solves

Currently web3 is too many chains and too complex for normal people and even developers. With pholocket I aimed to bridge that gap by making lambda functions in blockchains that autoscale based on load. The Idea was to have a friendly ui take the code from the developer inject this code into the template surrounding it by some boilerplate for metrics. Build an indexer node and metrics DB for the metric dashboard of the function.

As any sort of scaling from backend would introduce an centralization component which in a dapp does not make sense. So for better management I thought of having a master slave architecture where a master contract is responsible for scaling these contracts through a decentralized indexer network feeding data about network congesation. For capturing state synchronization across various contract we have state synchronizers which encode the eth state_diff for more important states user deploying the contracts have the option to put variables on the App Chain Gateway and enjoy the security of pre execution. Here's the architechture that I thought off (i cannot enter a picture ;-;)

Challenges I ran into

Wasn't able to find a good parser. So wrote the parser myself which took little bit longer than I anticipated also got to know. Had an amazing idea will be building it after