Integrate with exisiting dApp

[jacque006]

Idea

In order to speed up and allow earlier integration with the bls-wallet system from external teams, we should attempt to create an example web app, service, or script which uses bls-wallet-clients and a local or hosted aggregator without using the Quill extension.

This will also:

• Document and provide an example for non-extension use cases, such as if an exchange, other 3rd party provider, or user/service/bot which controls private keys wants to integrate with bls-wallet.
• Expose any issues with our current code.
• Highlight deficiencies and improvements we can make to our current documentation.

Depends on

• Aggregator: Support receiving sets of pre-aggregated transactions (to still potentially be further aggregated before sending) #35 :
• Potentially other a few other issues/client package updates

Possible path

Create a web wallet, service, or script. Then:

1. Create a BLSWallet https://github.com/jzaki/bls-wallet/blob/main/contracts/clients/README.md#blswalletwrapper
2. Create an unsigned transaction for the dApp/contract interaction from ethers https://docs.ethers.io/v5/api/contract/contract/#contract-populateTransaction
3. Sign the transaction using the BLSWallet
4. Submit the transaction to the aggregator https://github.com/jzaki/bls-wallet/blob/main/contracts/clients/README.md#aggregator