1. Overview
Interacting with the MultiversX blockchain is done via Observers in different shards. The complexity of deciding where to send transactions when it comes to sending/receiving eGLD and interacting with a SmartContract was simplified by the MultiversX Team with the delivery of a Proxy Application. We’ve deployed such an instance for the MainNet on our infrastructure to support the MultiversX Builders community and to sustain the #hypergrowth of the network.
2. ARC Stake MultiversX API Architecture
The ARC Stake MultiversX API infrastructure is deployed across multiple servers to provide additional performance and redundancy through our load balancer. The figure below would describe the high level architecture for the API:
3. Elrond Proxy Architecture
In the figure above:
- The MultiversX Network – consists of Nodes grouped within Shards. Some of these Nodes are Observers.
- One or more instances of the MultiversX Proxy – connect to Observer Nodes in order to forward incoming requests to the Network and to query state within the Blockchain.
- The Client Applications connect to the Network through the MultiversX Proxy. Is is also possible for client applications to talk directly to Observer and Validator Nodes.
4. Access Details
API URL: https://elrond.api.arcstake.com
Quick Test GET Request: https://elrond.api.arcstake.com/network/config
Rate Limits: 1000 requests / second
5. Additional Resources
REST API Documentation : https://github.com/ElrondNetwork/elrond-proxy-go
Official MultiversX Proxy Documentation: https://docs.elrond.com/sdk-and-tools/proxy/
Official MultiversX Proxy GitHub Repository: https://github.com/ElrondNetwork/elrond-proxy-go
