Hi, thanks for the proposal. I've a hard time understanding what you really want to solve. Starting from the preamble: users being frustrated "realizing that the flow to connect to the application is either non-existent or completely different". What do you mean by non-existent? A Dapp without a connect button? I wonder what studies you've made to come to this conclusion. The standard for Dapp connection in Polkadot isn't perfect, but I don't think it's bad either, WalletConnect is also perfectly working.

It sounds like you are trying to mimick what wagmi does as a front-end library, but shoehorning in your own new standard (Beacon p2p? yet another standard, why?) and wallet (Airgap right?). Rather than building yet another one, why not help libs like Polkadot onboard: https://github.com/paritytech/polkadot-onboard or Polkadot cloud https://polkadot.cloud/extensions-provider that was already supported by the treasury and seem less biased as they have no wallet organization behind?

Hello @Andy | Beacon,

Thanks for the proposal. Going through the comments, I cannot seem to justify 44K DOT (~$440K as of today) funding for your project. I think a better path for you would be get involved with the ecosystem and build PoC(s) for your project at much smaller budgets.

Also in section 4.2.1.1 of your proposal you seem to be asking for $220 per developer hour ($179520/((40+8+15+15+15+9)*8) assuming 8-hour work days), which I think is very expensive considering the fact that the common developer rate is usually around $100 per hour in the ecosystem.

I'm voting against this proposal due to the above reasons.

Best regards,
kukabi | Helikon