abourget

The Web3 Gateway (W3G)

Problem

dapps today still rely on centrally hosted endpoints to do the bulk of their work, so dapp users are not fully independent: they cannot take the front end, run with it and still use the app living on the blockchain.

See: https://moxie.org/2022/01/07/web3-first-impressions.html

See the notion of "right to exit": https://medium.com/@danfinlay/what-moxie-missed-on-web3-wallets-8dc572e7f39b

abourget

Problem:

• We want to keep the experiments for payments/billing/usage report/authentication coherent and unified
• We also want to have multiple distributed gateways of the network.
• These are the tensions between a centralizing vs decentralizing different components.

Solution:

• Provide an API that allows someone to emerge as a great UI for payments/billing/usage report/authentication, yet distributes the provisioning of the service to various gateways operated by multiple organisations.
• By defining a protocol, there also exists competition at that UI level, but gateway operators/providers of service would have an established way of communicating with that UI, in a standardized way, and move to use the best front-end (or use multiple).
• May the best win!