# POKT NETWORK ACTORS *Protocol actors enabling universal RPC infra layer of Web3* By [POKT HUB](https://paragraph.com/@pokt-hub) · 2024-06-05 shanon, upgrade, pokt, web3, rpc, testnet --- In the social media world, our attention to content is revenue for the company. In a blockchain world, the blocks are revenue for the chain. As a company shares its revenue among shareholders, employees and investors, blockchain revenue is generally shared among the contributors of the block. > In most chains,block contributors are, **_the demand side_**, **_the supply side_** and **the _DAO_**. * Demand side makes it possible for the user to consume whatever services the chain is offering. * The supply side does the same by ensuring the data produced from the activity of consuming the service is stored in a manner that is easy to retrieve. While the DAO, coordinates all activities ensuring they are beneficial to everyone. ![](https://paragraph.xyz/editor/callout/tip-icon.png) _POKT Network_, _a simple yet powerful protocol that is your API to the open internet._ In the most efficient manner, POKT Network coordinates the movement of data from over **60 blockchains** to their destination at **_low latency_** and **_high uptime_** using **_Remote Procedure Calls(RPC)_**. POKT Network’s revenue is brought in by **_gateways_** who represent the demand side and shared between the DAO and the Node runners, who represent the supply side. As we have come to learn in blockchains, revenue is earned only when work is done. This means there are different elements that work together to do the work, generally called **_actors_**. In the upcoming **_Shannon upgrade_**, work is done by **5 actors,** each with its own responsibilities. They all together seek to enable **_permissionless demand_**, where anyone unrestricted can **_use POKT to consume RPCs_**, revamp the **_tokenomics_** and **_provide opportunities to build_** exciting products that are not supported in the current version. Let’s learn more about these actors and understand what they do. [ ![](https://cdn.prod.website-files.com/651fe0a9a906d151784935f8/654378f9ff7ce59c23a18d61_wave.png) https://www.pokt.network Decentralised RPC | Web3 Infrastructure | POKT Network ------------------------------------------------------ Web3's decentralised RPC. With POKT Network, app can build on top of cost-effective, scalable, and resilient Web3 infrastructure that is DePIN. ](https://www.pokt.network/) * * * ### Applications POKT application actor enable the **_gateways to sign and relay transactions_**. Gateways have to stake an application to serve RPC requests to their customers. Staking an application takes two parameters: * **service\_ids** - This represents the chains whose relays the application needs, generally the service offered by POKT Network that the application consumes. * **stake\_amount** - This is an amount in upokt that the gateway has staked in order to relay requests to POKT Network on behalf of Applications. Upon Shannon upgrade, **_staking an application through running a gateway will be permissionless_**. [https://dev.poktroll.com/protocol/actors/application](https://dev.poktroll.com/protocol/actors/application) [![](https://paragraph.xyz/editor/youtube/play.png)](https://www.youtube.com/watch?v=ue1DK2rAZK0) ### Gateway Gateway actor in POKT Network are a first class citizen who live **_onchain_**. [https://dev.poktroll.com/protocol/actors/gateway](https://dev.poktroll.com/protocol/actors/gateway) With gateways being such an integral part of POKT network, a lightweight gateway server that allows anyone to **_spin up a gateway and start serving requests_** is available and requires at least **4 vCPUs+**, **1GB RAM**, and **1GB Storage.** If you would like to contribute or try the Gateway Server, see docs below. [https://docs.pokt.network/gateways/host-a-gateway](https://docs.pokt.network/gateways/host-a-gateway) > The gateway server makes it easier to interact with the onchain gateway actor. More about gateways form the link below : - [![](https://paragraph.xyz/editor/youtube/play.png)](https://www.youtube.com/watch?v=Q6xv5r4DmR4) ### Supplier Suppliers are an **_onchain actor_**. They **_stake their POKT to earn POKT in exchange for providing services_**. They are node runners who **_serve the relays requested by the applications_**. At the protocol level, they are supported by two onchain modules :- * **_Supplier module_** - This module covers the staking, unstaking and supplier querying transactions. * **_Proof module_** - This is the ‘work’ module, it is responsible for claims creation and querying besides the submission and querying of proofs. You can learn more about Supplier actors from the official docs. [https://dev.poktroll.com/protocol/actors/supplier](https://dev.poktroll.com/protocol/actors/supplier) ![](https://paragraph.xyz/editor/callout/tip-icon.png) The above 3 actors Applications, Gateways and Suppliers reside onchain. More about suppliers can be found in the link below :- [![](https://paragraph.xyz/editor/youtube/play.png)](https://www.youtube.com/watch?v=fIu2X3FiKGk) * * * ### AppGate Server AppGate Server is responsible for **_relaying a request from the client’s dApp to the supplier of the requested service_**. Executing the logic of a relay from the moment it leaves the client’s dApp to when it gets to the supplier. To put it into perspective, a Polygon wallet service that is **_under-DePIN-ed by POKT Network_** would require a **_Gateway_** to provide polygon endpoints that the wallet would then use to send requests to the POKT Network. The Gateway in this case would require an Application to be staked in order to sign and send requests on its behalf. To customize the business logic such that free tier is capped at 1,000,000 requests per month, this logic is implemented within AppGate Server. _This actor is utilized and consumed by the onchain Gateway Actor._ [https://dev.poktroll.com/protocol/actors/appgate\_server](https://dev.poktroll.com/protocol/actors/appgate_server) ### RelayMiner It provides the ability for **_individuals to offer services through POKT Network alongside a staked Supplier._** All Suppliers providing services on POKT Network have to run a relay miner alongside the software that is providing the service, as an example a node runner serving Polygon relays needs to have access to a Polygon node alongside a POKT node to **_serve Polygon relays on POKT Network_**. Through this actor, **_POKT Network supports non-custodial staking_**, since it is responsible for proxying relay requests between an AppGate Server and the supplied service. _This actor is utilized and consumed by the Supplier Actor._ [https://dev.poktroll.com/protocol/actors/relay\_miner](https://dev.poktroll.com/protocol/actors/relay_miner) > _The above two actors Relayminer and Appgate server reside offchain._ * * * ### Conclusion ![](https://paragraph.xyz/editor/callout/tip-icon.png) POKT Network is an important piece of infrastructure for Web3 with no comparison, both centralized and decentralized. To give an overview of how POKT Network has managed to achieve **_high uptime, cost-effectiveness and low latency in RPC,_** this is how it happens. The client’s dApp interacts with the **_Gateways_** through **_endpoints_**. Gateways interact with the staked **_Applications_**, enabling them to **_relay requests on their behalf to the protocol_**. Once at the protocol level, the **_RelayMiner_** run by the **_Supplier_** receives the relay request and proxies it to the required service. It is worth noting, for the RelayMiner to run, it requires a staked Supplier which is a staked POKT Node. Supplier A serving requests for the Polygon wallet service discussed earlier, would require a POKT Node running so that the RelayMiner can receive relay requests and proxy them to the Polygon node. How the interaction of all the actors of the protocol happens is a topic we will keep exploring. _Until next time, Stay POKT._ --- *Originally published on [POKT HUB](https://paragraph.com/@pokt-hub/pokt-network-actors)*