openfort-backend-wallets

Automate developer-custody backend wallet creation and management for EVM and Solana.

2|Updated Feb 2, 2026
One-click install
npx skills add https://github.com/openfort-xyz/agent-skills --skill openfort-backend-wallets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openfort-backend-wallets
Source: https://github.com/openfort-xyz/agent-skills/tree/main/skills/backend-wallet
Command: npx skills add https://github.com/openfort-xyz/agent-skills --skill openfort-backend-wallets

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Manually managing server-side blockchain wallets for EVM and Solana chains requires handling secure private key storage, gas fee management, cross-chain operation logic, and access control rules, which is time-consuming and prone to security risks for development teams.

Core Features & Use Cases

  • Cross-chain backend wallet management: Create, list, import/export, and delete developer-custody wallets for EVM and Solana, with private keys stored in hardware-backed secure enclaves to prevent unauthorized access.
  • Gasless transaction execution: Send EVM transactions with automatic EIP-7702 delegation and Solana transactions via Kora fee payer, eliminating the need for end-users to hold native gas tokens, with support for atomic batching of multiple contract interactions.
  • Policy and fee sponsorship control: Define granular access rules via the policy engine to restrict allowed operations, and configure fee sponsorship strategies (full developer sponsorship, custom token payments, fixed rates) to automate gas cost management.
  • Use case example: A development team can use this skill to automate treasury operations, AI agent wallet functions, payroll disbursements, and cross-border stablecoin transfers across multiple blockchains without managing individual user wallet interactions.

Quick Start

Use the openfort-backend-wallets skill to create a gasless EVM backend wallet on Base, set up a fee sponsorship policy for USDC transfers, and send a batch transaction to 10 recipient addresses.

Frequently Asked Questions about openfort-backend-wallets

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate server-side blockchain wallets for EVM and Solana?

Server-side blockchain wallets for EVM and Solana are automated by using developer-custody backend wallets to handle programmatic signing, treasury operations, and payroll disbursements without user interaction. This skill manages secure enclaves for private key storage and automates cross-chain operations.

How do gasless transactions work for backend wallets on EVM and Solana?

Gasless transactions for backend wallets work by sponsoring gas fees via EIP-7702 delegation for EVM chains and using the Kora fee payer for Solana. This eliminates the need for end-users or automated systems to hold native gas tokens to execute transactions.

Can I restrict automated blockchain operations using a policy engine?

Yes, you can restrict automated blockchain operations using a granular policy engine to define specific access rules. This policy engine limits allowed operations for server-side wallets and configures fee sponsorship strategies, such as full developer sponsorship or custom token payments.

What's the best way to batch multiple contract interactions server-side?

The best way to batch multiple contract interactions server-side is through atomic batching of EVM transactions. This skill supports atomic batching combined with gasless transaction execution, allowing complex programmatic signing operations across multiple recipient addresses in a single transaction.

Do I need to manage private key storage manually for server-side wallets?

No, you do not need to manage private key storage manually for server-side wallets. This skill stores private keys in hardware-backed secure enclaves to prevent unauthorized access, while still supporting E2E encrypted private key import and export for developer custody.

When should I use backend wallets instead of user-managed wallets for blockchain automation?

You should use backend wallets instead of user-managed wallets for blockchain automation when no user interaction is required. This applies to treasury operations, AI agent wallets, payroll disbursements, airdrops, and cross-border payment disbursement where fully server-side automation is necessary.