Stability Protocol Documentation
website·Indexed 32 days ago
https://docs.stabilityprotocol.comDocumentation for Stability, a public, feeless, and open-source blockchain platform. It includes guides for Web3 developers on EVM compatibility, RPC endpoints, and precompiles, as well as resources for Web2 developers using Zero-Knowledge Transactions (ZKT). The platform features a Free Transactions API (1.0.0), token gating, and Business Share Revenue (BSR) mechanisms.
What's inside Stability Protocol
- Zero-Knowledge Transactions (ZKT) is an experimental feature of the Stability Blockchain that allows users to submit data to the blockchain via standard HTTP POST requests. This removes the requirement for Web3 libraries, enabling any application capable of making web requests to interact with the blockchain. The system acts as a RESTful bridge consisting of an API Gateway (for authentication and validation), a ZKT Service (for transaction construction and signing), and a Sequencer (for finalization).
Overview of Stability features for Web2 developers
Stability lowers the barrier to entry for traditional developers by replacing complex Web3 requirements with familiar web standards. Key advantages include:
- No Wallet Required: Applications can be built without forcing users to manage cryptocurrency wallets.
- Free Transactions: Developers and users do not need to manage gas fees.
- Familiar Tooling: Interaction occurs via standard REST APIs rather than specialized blockchain libraries.
Explore Stability Protocol sample applications
The Stability Protocol provides several reference implementations to demonstrate common blockchain use cases. These include:
- Stability Portal: An account dashboard for tracking free transaction balances and history.
- Mintify: A gasless application for minting NFTs and ERC-20 tokens.
- OracleStream: A service for oracle and data publication.
- PayNow: A simplified payment application for sending and receiving payments.
- Data Store: A secure application for storing and retrieving data on the blockchain.
Understand Token Gating for transaction fees on STABILITY
Token Gating on STABILITY allows transaction fees to be paid in multiple whitelisted ERC-20 tokens rather than a single native gas coin. STABILITY does not have a built-in native currency for fees. Users select a supported ERC-20 token for payment, and validators determine which of these tokens they accept and at what conversion rate. This abstracts the gas coin requirement, allowing users to pay with tokens they already hold (e.g., USDC). Transactions using non-whitelisted tokens are rejected or ignored by the mempool to prevent spam.Understand Stability Protocol's Proof of Authority (PoA) model
Stability Protocol uses a Proof of Authority (PoA) consensus model instead of Proof of Work (PoW) or Proof of Stake (PoS). This removes the requirement for tokens to validate transactions, relying instead on a network of known, trusted entities acting as validators to provide a stable environment for production applications.Stability Network technical specifications and architecture
The Stability Network is built with the following architectural characteristics:
- Consensus Mechanisms: Utilizes AuRa and GRANDPA to ensure a tamper-proof and resilient decentralized network.
- Scalability: Engineered for enterprise-grade throughput, capable of processing up to 10,000 transactions per second (tx/s).
- Access: A public network allowing any developer or organization to deploy dApps and interact with the ledger without financial entry requirements (tokens).
- Transparency: The core codebase is open-source and available on GitHub for community auditing and contribution.
Wallet and Address Compatibility on Stability
Stability is EVM-compatible. All EVM-compatible wallets (such as MetaMask) are supported. Because it follows EVM standards, private keys used on Ethereum or any other EVM-based blockchain will resolve to the same public address on Stability.Retrieve API key details for paid transactions
Retrieve information about your API keys using theGET /paid-transactions/keysendpoint. This request requires a Bearer token in the Authorization header using a Supabase Auth Token.curl -H "Authorization: Bearer ${SupabaseAuthToken}" https://stabilityprotocol.com/paid-transactions/keysResponse (200 OK):
[ { "api_key": "string", "email": "string", "created_at": "string", "granularity": "day", "enabled": true } ]Understand Business Share Revenue (BSR) fee sharing
Business Share Revenue (BSR) is a fee-sharing mechanism on STABILITY that splits transaction fees between the network validator and the smart contract (dApp) being interacted with. Unlike traditional blockchains where validators keep all fees, BSR allows dApp creators to earn a portion of the fees generated by their application's usage. The split percentage is configurable by the protocol. BSR is currently in Beta.Understand the Stability Network feeless transaction model
Stability Network replaces traditional blockchain 'gas' fees with an API-key-based model. Transactions are allocated via secure, unique RPC addresses. This allows users and developers to interact with applications on the network without the need to hold, manage, or pay with native cryptocurrency.Configure MetaMask for zero-fee transactions on Stability
Stability requires that the
Max Base FeeandMax Priority Feebe set to zero. Transactions with non-zero gas fees will revert. This applies to all networks, including GTN and Testnet. To configure MetaMask:- Initiate a transaction (e.g., via Remix).
- In the MetaMask confirmation popup, click the pencil icon in the estimated fee box.
- Select the advanced gas fee settings.
- Set both
Max Base FeeandPriority Feeto 0. - Check the 'Save these values as my default' box to apply this setting to future transactions.
Use free transactions on Stability Protocol
Stability Protocol provides zero gas price transactions to ensure a cost-effective experience. All registered API keys, regardless of the account plan, have access to unlimited transactions subject to a rate limit of 60 requests per minute. Users can monitor their real-time transaction count and reset timing via the Stability Portal.