Supercall

Bundling complex transactions with a simple interface

Comment

Inspiration

As blockchain ecosystem has grown quickly, there have been over thousands of projects emerged in this space. Simultaneously, blockchain networks, trying to breakthrough technology limitation, spread out liquidity on different networks. The overall liquidity tracked by DeFiLlama to date (December 21, 2023) is over $52.5b, but those are fragmented in side different applications and blockchains. While smart contract enables interoperability among different applications, it's not easy to accomplish that due to its complexity.

Many edges and strategies can be developed using complex transactions across many applications. People who discover them has advantages over people who don't know. However, another challenge is the way to execute those complex transactions. Ones who want to send those complex transactions needs to handle multiple tabs on their browser and must proceed too many transaction approval to complete it. Supercall comes to solve this problem by providing an intuitive user interface to build complex transactions and enables single approval scheme for users.

What it does

Supercall is an intuitive user interface to build complex transactions across different smart contracts (and multiple blockchains in the near future). Users can select functions that they want to call and bundle them together into a transaction and send them into one shot. The project improves user experience and save gas for contract interaction.

How we built it

  1. The whole application has been built as Near BOS components. The components include:
  2. As the project opens for any builder to create their own Supercall, we have developed some example Supercall components:
  3. Existing Multicall3, Create2Deployer, and OwnableProxy are main smart contracts used as supercall smart account.

The published components

  1. SupercallDeployer (https://near.org/near/widget/ComponentDetailsPage?src=sainy.near/widget/SupercallDeployer)
  2. SupercallAccount (https://near.org/near/widget/ComponentDetailsPage?src=sainy.near/widget/SupercallAccount)
  3. SupercallBundler (https://near.org/near/widget/ComponentDetailsPage?src=sainy.near/widget/SupercallBundler)
  4. SupercallMain (https://near.org/near/widget/ComponentDetailsPage?src=sainy.near/widget/SupercallMain)
  5. SupercallTokenTransfer (https://near.org/near/widget/ComponentDetailsPage?src=sainy.near/widget/SupercallTokenTransfer)
  6. SupercallABI (https://near.org/near/widget/ComponentDetailsPage?src=sainy.near/widget/SupercallABI)

Challenges we ran into

  1. Showcasing the ability to interact with multiple applications and networks take quite a long time to prepare data (e.g., smart contract ABIs, smart contract addresses deployed on many different chains). Some contracts need to be re-deployed by ourselves
  2. Near BOS is still in beta version. So, we found that it doesn't clearly tell the errors when some problems occur (such as, rate limit reached when deploying a component using a free account).
  3. We do not have much time to prepare an expected showcase during the hackathon period as we need to join many sessions on the event and cannot work on the project when we listen to sessions

Accomplishments that we're proud of

  1. We have built a complete proof of concept of adapting Near BOS to a transaction bundling service.
  2. We come up with a simplified BOS component development framework specifically for building customized Supercall.
  3. We won the 1st runner up of the event.

What we learned

  1. We learned so much on the developer experience building on Near BOS. It is a new interesting way to make a transparent frontend application.
  2. We learned how to compose Near BOS component in a fancy way.
  3. We learned how to interact with EVM blockchains on Near BOS.

What's next for Supercall

  1. We will need to further simplify the user flow to build a transaction.
  2. We will enable cross chain interoperability on Supercall.
  3. If the project gets widely adopted, we will need to create a call marketplace. So that builders can monetize their creativity and skills to come up with an impactful calls.
  4. More importantly, the security issues need to be addressed properly. By opening call building and sharing in public, there might be potential malicious calls published on the network. To address this concern, DAO system can come into place for giving some badges to a safe call.

Built With

Share this project:

Updates