Last updated by Thinh Porrmann 3 months ago
Grindery is building a “Zapier for Web3”. Users will be able to send on-chain events (e.g: wallet deposits) to an off-chain system (e.g: browser notification) as well as sending off-chain data (e.g: Google Form entry) on-chain (e.g: creating a DAO proposal). Grindery Nexus is also built to send messages from one chain (e.g: event on Ethereum) to other chains (e.g: transactions on Near). For the w2-w3 and w3-w3 use cases users have to be able to pay gas fees. This payment has to be made as simple as possible, specially for DAOs our target market.
Whenever Grindery runs a workflow that executes a blockchain transaction (transfer of tokens, creating DAO proposals, etc) gas has to be paid on the target chain. Since this transaction will be executed in the background - without the user's real-time consent - users will have to pre-pay the gas for this transaction. These transactions can be on the same or a different chain than the users (or DAO’s) wallet.. This would require users to buy, deposit and maintain a positive balance of gas tokens for future transactions on all possible chains.
Allow users (DAOs) to prepay for gas on any (supported Blockchain) using their native (gas) token in their wallet/treasury.
Solutions in Detail
Payments (for gas) should be as simple as credit/debit card payments in the SaaS space: users can fund their cards in any local currency (USD, Euro, MX, ..) and the provider receives the payment in their local currency (USD, Euro, MX, ..). Neither customers nor providers need to worry about each other's preferred currencies. This could be achieved on blockchains the following way
Allowing users to deposit gas tokens into gas pools (smart contracts) on every supported blockchain from their wallet/treasury.
Reflecting this deposit on a central payment chain by minting pool tokens that represent the users deposit as a share in the aggregated value of all gas pools on all chains.
Allow selected smart contracts to receive gas tokens from any gas pool on any supported blockchain on behalf of the user within the limit of pool tokens owned by the user.
Reflecting the gas token withdrawal by burning the corresponding amount of pool tokens on the central payment chain .
This would allow the creation of a “Cross-Chain Gas Station Network ”. The purpose of this system is not to compete with cross-chain liquidity pools and bridges (that can exchange large sums of tokens) but rather to enable micro payments on behalf of the user. This should allow the implementation of additional security strategies at different levels/layers of the system that could significantly decrease risk compared to existing cross-chain bridges.
This solution could likely be deployed using a combination of protocols (Celer, Router Protocol, Synapse. Maplabs.io, thorchain, LayerZerom Axelar, Multichain, etc), Layer-0 technologies (Polkadot, Ignite/Cosmos) and/or different Oracles types (Chainlink, Reality.eth).