Imagine the HTTP protocol spec requiring browsers to route all HTTP traffic through g∗∗gle, and any browser routing traffic through g∗∗gle must pay for the privilege. And then describing this as a "Open protocol for connecting browsers to websites" first line of the README.

On a separate note: Walletbeat has never encouraged wallets to integrate @WalletConnect, as it exposes users to additional transaction censorship risks due to Reown's middleman role in the WalletConnect connection process. Seems like this isn't likely to change anytime soon.

@WalletConnect If you're considering building something that integrates WalletConnect: