yjkellyjoo
c0c293bb2a
- Introduced a new .markdownlint.json file to enforce markdown linting rules. - Updated various documentation titles and descriptions across the site to enhance clarity and SEO, focusing on gasless transactions and Karma reputation. - Improved organization and consistency in the builder guides and overview sections. Signed-off-by: yjkellyjoo <yejinkellyjoo@gmail.com>
3.2 KiB
title, description, keywords
| title | description | keywords | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| JSON-RPC API: Status Network Extensions & Reference | Status Network JSON-RPC API reference. Explore custom extensions for gasless transactions, RLN proofs, and Karma-aware fee estimation for developers. |
|
JSON-RPC API
Status Network is based on Linea zkEVM, meaning most JSON-RPC methods behave exactly like a standard EVM node.
For the canonical list of supported methods and their standard semantics, refer to the following official documentations:
- Ethereum JSON-RPC API Reference — standard Ethereum RPC methods
- Linea JSON-RPC API Reference — Linea-specific methods, including
linea_estimateGas
Status Network extensions
Status Network extends the standard Linea JSON-RPC with Karma-aware fee estimation:
linea_estimateGas
On Linea, linea_estimateGas is the recommended way to estimate gas, returning gasLimit, baseFeePerGas, and priorityFeePerGas in a single call.
Status Network extends linea_estimateGas with Karma-aware behavior:
- Gasless users: Returns zero
baseFeePerGasandpriorityFeePerGasfor eligible users with available Karma quota - Deny-listed users: Applies a premium multiplier to fee fields for users on the deny list
Status Network RPC differences
On base Linea, linea_estimateGas is already the recommended method because it returns fee fields that account for L1 verification costs and data compression - something eth_estimateGas and other eth_ namespace calls do not provide.
Status Network's fork extends linea_estimateGas further to be Karma-aware; all other JSON-RPC methods retain their standard semantics.
That means using the traditional fee flow with eth_ methods (for example eth_gasPrice, eth_maxPriorityFeePerGas, or eth_feeHistory) can lead to inaccurate fee suggestions: they miss both Linea's L2-specific pricing and Status Network's Karma adjustments.
Use linea_estimateGas as the single source of truth for gasLimit, baseFeePerGas, and priorityFeePerGas on Status Network.
See Linea's gas-fee guide and Linea's linea_estimateGas reference for the base Linea behavior.
:::info For detailed integration guidance including code examples, migration steps, and common pitfalls, see the Using Karma guide. :::
Additional resources
- Linea's gas-fee guide
- Linea's
linea_estimateGasreference - Karmic Tokenomics — how Karma impacts gas fees
- Gasless Transactions — technical details of the RLN-based gasless system
- Ethereum Differences — opcode, precompile, and transaction type differences from Ethereum mainnet