This is a request for proposal to build a Chain Abstracted relayer, SDK, and accompanying documentation that allows apps, wallets, and users to leverage existing infrastructure.

The backend will be powered by a collection of existing metatransactions, relayers, gas stations, and account abstraction services on each chain that Chain Signatures supports. This includes ongoing maintenance as NEAR Chain Signatures expands to more chains.

Problems

As teams start building with Chain Signatures and bridges, there is limited infrastructure for managing different gas costs.
Developers often face challenges managing varying gas costs and protocol standards across multiple chains.
The steep learning curve and operational overhead of integrating different relayer infrastructures (NEAR, EVM, Solana, etc.) limit the participation of smaller teams in building on Chain Signatures.
Teams need an easy-to-use, self-service SDK that works with different gas relayers
While individual solutions exist on each chain, no one in the NEAR ecosystem coordinates these solutions centrally
While solution such as gas.zip could work as a cross chain gas station, there are multiple limitations:
- A minimum amount is always required, so a one-time transaction often leaves a residual balance in the destination address. Consequently, it is not feasible for developers to sponsor gas, as doing so on a mass scale would be prohibitively expensive.

Solution

Self-service platform that enables developers to either sponsor gas fees or allow users to pay the gas for themselves
The service must accept at least base tokens on integrated chains and major stable coins (USDT, USDC) for gas deposit.
Uses other solution like NEAR intents and omnibridge to top up gas
Integration with most other relayers
Services/Contracts deployed to each chain to manage relayers
Allow fees for relay service, other gas relayer services, and clients/front ends to integrate to incenticize all relevant stakeholder