Handle large payloads without hitting size limit

[124maa]

NPM Versions:

• @walletconnect/web3wallet: ^1.10.0
• @walletconnect/core: ^2.11.0
• @walletconnect/sign-client: ^2.11.0

When sending messages from wallet to dApp, the payload limit is constantly reached. The limit is roughly 71kb, but the 71kb limit isn't defined anywhere. This is the error message I get when the limit is reached:

Payload size limit exceeded. Maximum size for tag 1109 is 98304

This low limit is killing the UX for dApps and is our biggest pain point with WalletConnect. It would be nice if the limit was increased, or if there were an easy way to break up a large message and send the chunks.

Our wallet is for a private blockchain, so there's unfortunately no public data provider that can reduce the load on WalletConnect.

Originally posted by @jonandgon in #4100

[ganchoradkov]

hey @124maa, what size payloads are you trying to send?

[jonandgon]

Hey @ganchoradkov, I would need ~0.5 - 1.0 MB for now. As I said in the OP, we're building on a private blockchain (Aleo), and all the account data is sent from the wallet, and not through a data provider. 71kb is too little for us to properly display a dapp's state.

The ideal solution would be to have (basically) no limit, but streamed at whatever speed you decide. Or to allow wallets to run their own WalletConnect infra, but I understand that these changes would require significant work on your end.

[jonandgon]

hey @ganchoradkov any movement on increasing the payload size? Thanks!

[BrandtH22]

Hey @jonandgon , were you able to figure out a workaround or solution for this?

[jonandgon]

@BrandtH22 yes - by not using walletconnect wherever possible :)

[SayoshiNakamario]

Just a note that I hit this as well.
A 47.45kb raw transaction gets sent to the wallet as 1465kb then cannot be broadcasted after signing. In our case it's a BCH contract tx with 66 inputs and 132 outputs. These types of tx's are becoming more common so might have to figure something else out.