Pocket Network is a decentralized infrastructure network that connects applications needing blockchain data with independent service providers. POKT coordinates access, staking and rewards. Its practical role is easiest to understand through a wallet checking a balance: the wallet needs a reliable route to blockchain data, even when the user has no reason to run a full node.
What does decentralized RPC actually do?
RPC means remote procedure call. In a blockchain application, it lets software ask a remote node for information or submit an already signed transaction. A balance query, a contract read and checking transaction status are familiar examples. The endpoint is a communication route; it does not become the owner of the user's private key merely because it receives a request.
Relying on one provider can create an access bottleneck. If its endpoint is unavailable, a wallet may struggle to display balances or broadcast a transaction even while the blockchain itself continues operating. Distributing service across providers can improve resilience, but performance still depends on endpoints, routing, supported methods and backend synchronization.
Pocket's current Shannon protocol separates the data-serving work from coordination and settlement. An Ethereum request still needs an Ethereum backend; Pocket does not replace Ethereum's execution or consensus. A returned response also should not be confused with independent light-client verification of every piece of data.
Applications, Suppliers and validators have different jobs
The Shannon architecture documentation describes several cooperating roles. An Application is the protocol participant requesting service, not necessarily every individual wallet user. A Gateway can make access simpler by handling requests and service quality on the application's behalf.
| Participant | Main job | Important distinction |
|---|---|---|
| Application | Funds and requests specified data services | End users need not manage a protocol account individually |
| Supplier | Registers services and serves relays | Data delivery is different from producing Pocket blocks |
| Gateway | Routes delegated requests and handles failover | A service intermediary, not the queried blockchain |
| Validator | Participates in Pocket consensus and block validation | Does not replace the target chain's validators |
| Source Owner | Registers a service and its work-pricing configuration | Defines a service rather than necessarily serving each request |
For example, a wallet service can delegate routing to a Gateway, which chooses among available Suppliers. The Supplier's backend answers the request. Separately, Pocket records the service relationships and settles eligible work. This explains why running a Pocket validator and maintaining a data-serving Supplier are different operational commitments.
How do nodes qualify and get paid?
Suppliers stake POKT and configure the services they can provide. Sessions assign eligible Suppliers to an Application and service for a bounded period. Under the current design, Supplier stake is an eligibility condition, rather than a rule giving larger stakes proportionally better session-selection odds.
Selection is only the first step. Gateways can direct more traffic toward endpoints with better latency and reliability. A node that qualifies but receives little useful traffic may earn little. Operators must maintain the relevant blockchain backends, bandwidth, software and monitoring, rather than expect rewards simply for leaving tokens untouched.
RelayMiner summarizes work in claims; cryptographic proofs are required under the applicable audit rules. Missing a required proof can forfeit payment and trigger a protocol penalty. The governance parameters also govern staking requirements, settlement windows and unbonding. Unstaking does not necessarily make funds immediately transferable.
Rewards therefore need to be assessed after infrastructure costs, service demand, proof obligations and token-price movements. A third-party operator or staking arrangement adds its own fees and control conditions. Neither operating a node nor delegating through a provider guarantees a fixed dollar return.
What is POKT used for, and how does burning work?
POKT supports protocol fees, participant staking and service settlement. Applications pay for consumed work through token burning; settlement mints rewards for eligible recipients. Compute units measure service work, so a raw request count alone does not describe all economic activity.
The current PIP-41 mechanism specifies a 0.975 mint ratio: if 100 POKT is burned for service consumption, 97.5 POKT is minted back, leaving a 2.5 POKT net reduction from that settlement. This is an illustration of the stated rule, not an estimate of daily usage or a promised annual deflation rate.
Usage and price remain separate questions. More paid work can increase token consumption, but market supply, selling by reward recipients, liquidity and changes to governance parameters affect investment outcomes. A useful infrastructure service does not create an automatic entitlement to company profits or a guaranteed appreciation in its token.
Native POKT is different from Ethereum xPOKT
The project's official multichain bridge repository identifies the following Ethereum contract as xPOKT, a bridged representation:
0x764a726d9ced0433a8d7643335919deb03a9a935
Native POKT operates on Pocket mainnet, whose Shannon addresses use the pokt1 format. The Ethereum representation uses an ERC-20 contract and EVM addresses. Holding it does not by itself stake a native Supplier or grant access to native protocol operations.
Moving between forms requires the supported conversion and bridge route. Check the asset and destination at each step; a matching ticker does not make every network interchangeable. Bridge security, contract permissions, fees and service availability remain relevant even when the underlying project is established.
How to assess the POKT market on KTX
Use the POKT Ethereum page on KTX On-Chain Trading to identify the relevant asset and review available market information. Confirm the Ethereum network and full address, then inspect liquidity, recent activity, estimated execution and costs before deciding whether to trade.
The supplied market view shows sparse recent activity and a very small liquidity figure. Its quote should not be treated as the price obtainable for a large order, and its holder or valuation figures should not be read as totals for the entire Pocket ecosystem. The DEX Screener research guide explains how token, pool and network data differ.
Check the route for the intended amount and consider the eventual exit as well as entry. Our crypto liquidity guide explains why a displayed portfolio value can differ from realizable proceeds. Trading an on-chain representation and arranging native-node participation are separate actions; do not assume a trading page provides a direct path to staking.
Frequently asked questions
Must wallet users buy POKT for every balance check?
No. A service provider can manage protocol access behind the application. The end-user payment arrangement depends on the wallet or application.
Does Pocket eliminate Ethereum gas fees?
No. Data access and target-chain execution are separate. Sending a transaction on Ethereum still follows Ethereum's gas rules.
Does a quiet trading pool mean Pocket has no RPC users?
No. A pool measures trading in a specific market. Protocol service demand must be assessed through service activity and settlement data.
Is a higher Supplier reward necessarily higher profit?
No. Costs, provider fees, token valuation and the time capital remains committed all affect the outcome.
Reviewed October 29, 2026. Protocol parameters and product availability can change. POKT carries market, infrastructure, contract, bridge and liquidity risks. This article is educational, not investment advice.