Gasless Bundled Transactions about mexa-sdk

[tomarsachin2271]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Work has been started.

These users each claimed they can complete the work by 2 weeks, 4 days from now.
Please review their action plans below:

1) jochem-brouwer has started work.

I will create a contract which will handle multiple transactions in a tree structure. Every node will have a setting to either accept failed transactions OR to revert all changes done by any underlying transactions.

A question though: Biconomy must be integrated in this project. However, I will probably just use Biconomy as how I would use web3 by default. Am I missing something here or is that ok?

Learn more on the Gitcoin Issue Details page.

Make sure you handle the order of the transaction also.
And since ethereum has a block limit also, so transaction sender should be able to know if the transaction bundle is big enough to be included in a single block. Miners tends to include multiple small size transaction rather than one big size transaction. So the balance should also be there in the budle size.
If possible emit relevant events also.

[anubhavgirdhar]

From the Gitcoin bounty page it seems no one is working on this bounty, so I'm thinking of putting together a submission over the next two days. Let me know if the below proposal would be eligible for this bounty:

Design a contract similar to Multicall where an aggregate function takes an array of addresses and an array of calldata, enabling arbitrary function calls on any contract. Our contract would act as a smart contract wallet, so it would have an owner and only the owner can call aggregate, that way msg.sender on target contracts still works as expected. Biconomy would be integrated into this contract/app for meta-transaction support.

On the frontend, when a user visits the app they will connect their web3 wallet. On their first visit to the app we deploy their wallet contract. The app presents a selection of contract methods to the user (such as mint cDAI or join PoolTogether), and lets them execute all actions as a bundled transaction by calling aggregate.

@mds1 Sure. That's eligible. A nice DeFi/Gaming use case along with the smart contract layer would be awesome :)

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

This issue now has a funding of 1500.0 USDT (1500.0 USD @ $1.0/USDT) attached to it as part of the bcnmy fund.

• If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $112,812.73 more funded OSS Work available on the Gitcoin Issue Explorer

[tarun1475]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Work has been started.

These users each claimed they can complete the work by 2 weeks, 4 days from now.
Please review their action plans below:

1) jochem-brouwer has started work.

I will create a contract which will handle multiple transactions in a tree structure. Every node will have a setting to either accept failed transactions OR to revert all changes done by any underlying transactions.

A question though: Biconomy must be integrated in this project. However, I will probably just use Biconomy as how I would use web3 by default. Am I missing something here or is that ok?

Learn more on the Gitcoin Issue Details page.

Yes you can definitely use Biconomy as a web3 provider but the end goal is to use mexa sdk for the gasless transactions and use Biconomy relayer infrastructure to relay meta transactions.

[mds1]

From the Gitcoin bounty page it seems no one is working on this bounty, so I'm thinking of putting together a submission over the next two days. Let me know if the below proposal would be eligible for this bounty:

Design a contract similar to Multicall where an aggregate function takes an array of addresses and an array of calldata, enabling arbitrary function calls on any contract. Our contract would act as a smart contract wallet, so it would have an owner and only the owner can call aggregate, that way msg.sender on target contracts still works as expected. Biconomy would be integrated into this contract/app for meta-transaction support.

On the frontend, when a user visits the app they will connect their web3 wallet. On their first visit to the app we deploy their wallet contract. The app presents a selection of contract methods to the user (such as mint cDAI or join PoolTogether), and lets them execute all actions as a bundled transaction by calling aggregate.

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

Work has been started.

These users each claimed they can complete the work by 1 day, 19 hours from now.
Please review their action plans below:

1) mds1 has started work.

I'll design a contract similar to Multicall where an aggregate function takes an array of addresses and an array of calldata, enabling arbitrary function calls on any contract. This contract would act as a smart contract wallet, so it would have an owner and only the owner can call the aggregate function, that way msg.sender on target contracts still works as expected. Biconomy would be integrated into this contract/app for meta-transaction support.

On the frontend, when a user visits the app they will connect their web3 wallet. On their first visit to the app we deploy their wallet contract. The app presents a selection of contract methods to the user (such as mint cDAI or join PoolTogether), and lets them execute all actions as a bundled transaction by calling aggregate.

Learn more on the Gitcoin Issue Details page.

[tomarsachin2271]

From the Gitcoin bounty page it seems no one is working on this bounty, so I'm thinking of putting together a submission over the next two days. Let me know if the below proposal would be eligible for this bounty:

Design a contract similar to Multicall where an aggregate function takes an array of addresses and an array of calldata, enabling arbitrary function calls on any contract. Our contract would act as a smart contract wallet, so it would have an owner and only the owner can call aggregate, that way msg.sender on target contracts still works as expected. Biconomy would be integrated into this contract/app for meta-transaction support.

On the frontend, when a user visits the app they will connect their web3 wallet. On their first visit to the app we deploy their wallet contract. The app presents a selection of contract methods to the user (such as mint cDAI or join PoolTogether), and lets them execute all actions as a bundled transaction by calling aggregate.

Make sure the solution is generic in nature and handles cases like too many transactions in the bundle as each block has a Gas limit, and it should be generic enough for the caller to choose if while bundle should fail if one of the tx fail or not.
Check out our workshop video at the end to know more about the bounty..

https://youtu.be/L2QlOk5F80c

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

Work for 1500.0 USDT (1500.0 USD @ $1.0/USDT) has been submitted by:

1. @mds1

@tomarsachin2271 please take a look at the submitted work:

• PR by @mds1

---

• Learn more on the Gitcoin Issue Details page
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $119,583.21 more funded OSS Work available on the Gitcoin Issue Explorer

[mds1]

Hey all, just wanted to follow up on this bounty and see what the status was!

[gitcoinbot]

Issue Status: 1. Open 2. Cancelled

---

The funding of 1500.0 USDT (1500.0 USD @ $1.0/USDT) attached to this issue has been cancelled by the bounty submitter

• Questions? Checkout Gitcoin Help or the Gitcoin Chat
• $178,686.13 more funded OSS Work available on the Gitcoin Issue Explorer