Bu sayfa henüz yerel dilinizde mevcut değildir. Daha fazla dil seçeneği eklemek için yoğun bir şekilde çalışıyoruz. Desteğiniz için teşekkür ederiz.
- What's New
- Service Overview
- Getting Started
- User Guide
- User Guide (Staking Nodes)
-
Developer Guide
-
Ethereum Node Engine
- Introduction
- JSON-RPC API Request Examples
- Application Development
- Smart Contract Development
-
Ethereum APIs
- Dedicated Edition
-
Shared Edition
- eth_blocknumber
- eth_getBlockByNumber
- eth_getUncleByBlockNumberAndIndex
- eth_getUncleByBlockHashAndIndex
- eth_getUncleCountByBlockNumber
- eth_getUncleCountByBlockHash
- eth_getBlockByHash
- eth_getTransactionByHash
- eth_getTransactionCount
- eth_getTransactionByBlockHashAndIndex
- eth_getTransactionByBlockNumberAndIndex
- eth_getBlockTransactionCountByHash
- eth_getBlockTransactionCountByNumber
- eth_getTransactionReceipt
- eth_sendRawTransaction
- eth_call
- eth_createAccessList
- eth_estimateGas
- eth_feeHistory
- eth_maxPriorityFeePerGas
- eth_gasPrice
- eth_getBalance
- eth_subscribe
- eth_unsubscribe
- eth_getStorageAt
- eth_getCode
- eth_getProof
- eth_getLogs
- eth_getFilterChanges
- eth_getFilterLogs
- eth_newBlockFilter
- eth_newFilter
- eth_newPendingTransactionFilter
- eth_uninstallFilter
- eth_chainId
- web3_sha3
- web3_clientVersion
- net_version
- net_listening
- TRON Node Engine
-
Polygon PoS
- Polygon PoS Introduction
- HTTP Request Examples
- WebSocket Request Examples
-
Polygon PoS APIs
- Dedicated Edition
-
Shared Edition
-
Ethereum JSON-RPC APIs
- eth_blocknumber
- eth_getBlockByNumber
- eth_getUncleByBlockNumberAndIndex
- eth_getUncleByBlockHashAndIndex
- eth_getUncleCountByBlockNumber
- eth_getUncleCountByBlockHash
- eth_getBlockByHash
- eth_getTransactionByHash
- eth_getTransactionCount
- eth_getTransactionByBlockHashAndIndex
- eth_getTransactionByBlockNumberAndIndex
- eth_getBlockTransactionCountByHash
- eth_getBlockTransactionCountByNumber
- eth_getTransactionReceiptsByBlock
- eth_getTransactionReceipt
- eth_sendRawTransaction
- eth_call
- eth_createAccessList
- eth_estimateGas
- eth_feeHistory
- eth_maxPriorityFeePerGas
- eth_gasPrice
- eth_getBalance
- eth_getRootHash
- eth_subscribe
- eth_unsubscribe
- eth_getStorageAt
- eth_accounts
- eth_getCode
- eth_getProof
- eth_getLogs
- eth_getFilterChanges
- eth_getFilterLogs
- eth_newBlockFilter
- eth_newFilter
- eth_newPendingTransactionFilter
- eth_uninstallFilter
- eth_chainId
- web3_sha3
- web3_clientVersion
- Polygon JSON-RPC APIs
-
Ethereum JSON-RPC APIs
-
Arbitrum
- Arbitrum Introduction
- HTTP Request Examples
- WebSocket Request Examples
-
Arbitrum APIs
-
Shared Edition
-
Ethereum JSON-RPC APIs
- eth_blocknumber
- eth_getBlockByNumber
- eth_getUncleByBlockNumberAndIndex
- eth_getUncleByBlockHashAndIndex
- eth_getUncleCountByBlockNumber
- eth_getUncleCountByBlockHash
- eth_getBlockByHash
- eth_getTransactionByHash
- eth_getTransactionCount
- eth_getTransactionByBlockHashAndIndex
- eth_getTransactionByBlockNumberAndIndex
- eth_getBlockTransactionCountByHash
- eth_getBlockTransactionCountByNumber
- eth_syncing
- eth_getTransactionReceipt
- eth_sendRawTransaction
- eth_call
- eth_createAccessList
- eth_estimateGas
- eth_feeHistory
- eth_maxPriorityFeePerGas
- eth_gasPrice
- eth_getBalance
- eth_subscribe
- eth_unsubscribe
- eth_getStorageAt
- eth_accounts
- eth_getCode
- eth_getProof
- eth_getLogs
- eth_getFilterChanges
- eth_getFilterLogs
- eth_newBlockFilter
- eth_newFilter
- eth_newPendingTransactionFilter
- eth_uninstallFilter
- eth_chainId
- web3_sha3
- web3_clientVersion
-
Ethereum JSON-RPC APIs
-
Shared Edition
-
BNB Smart Chain
- BNB Smart Chain Introduction
- HTTP Request Examples
- WebSocket Request Examples
-
BNB Smart Chain APIs
- Dedicated Edition
-
Shared Edition
- eth_blocknumber
- eth_getBlockByNumber
- eth_hashrate
- eth_getUncleCountByBlockNumber
- eth_getUncleCountByBlockHash
- eth_getBlockByHash
- eth_getTransactionByHash
- eth_getTransactionCount
- eth_getTransactionByBlockHashAndIndex
- eth_getTransactionByBlockNumberAndIndex
- eth_getBlockTransactionCountByHash
- eth_getBlockTransactionCountByNumber
- eth_syncing
- eth_getTransactionReceipt
- eth_sendRawTransaction
- eth_call
- eth_mining
- eth_estimateGas
- eth_feeHistory
- eth_maxPriorityFeePerGas
- eth_gasPrice
- eth_getBalance
- eth_subscribe
- eth_unsubscribe
- eth_getStorageAt
- eth_accounts
- eth_getCode
- eth_getProof
- eth_getLogs
- eth_getFilterChanges
- eth_getFilterLogs
- eth_newBlockFilter
- eth_newFilter
- eth_newPendingTransactionFilter
- eth_uninstallFilter
- eth_chainId
- web3_sha3
- web3_clientVersion
- txpool_status
- net_listening
- net_version
- Batch Requests
-
Ethereum Node Engine
- API Reference
-
FAQs
-
APIs
- How Do I Determine Whether Flow Control Is Triggered for an API?
- What Are the Flow Control Policies for Full Nodes?
- How Many Methods Can Be Included in a JSON-RPC Batch Request for the Dedicated Version?
- How Many WebSocket Connections Can Be Made Each Time?
- How Do I Use HTTP Endpoints and Authentication Credentials to Access Nodes?
- Staking Nodes
-
APIs
- General Reference
Show all
Copied.
VPC Endpoint (VPCEP) Connection
VPC endpoints are used for connecting your staking nodes with backend resources, such as Elastic Cloud Server (ECS) and Cloud Container Engine (CCE), through a Huawei Cloud private network.
Prerequisites
You have created at least one staking node and enabled VPC Endpoint (VPCEP) for it.
Precautions
- The staking node, VPC endpoint, and backend resources must be in the same region, for example, AP-Singapore.
- The VPC endpoint and backend resources must be in the same Virtual Private Cloud (VPC).
Procedure
- Obtain the VPC endpoint service name.
- Log in to the NES console.
- Choose Dedicated > Network Management.
- Click a node ID and obtain the VPC Endpoint on the node details page.
- Buy a VPC endpoint.
- Log in to the VPC Endpoint console.
- Choose VPC Endpoint > VPC Endpoints.
- Click Buy VPC Endpoint and configure parameters. For details, see Buying a VPC Endpoint.
NOTE:
Set Service Category to Find a service by name. Then, paste the obtained VPC endpoint service name in VPC Endpoint Service Name.
- Click Next, confirm parameters, and submit the order.
- On the VPC Endpoints page, click the ID of the purchased VPC endpoint, and obtain its Private Domain Name.
- Access the staking node using its port number and the private domain name of the VPC endpoint.
gRPC endpoint: Private network domain name:Port number
HTTP endpoint: Private network domain name:Port numberNOTE:
Obtain the port numbers on the NES console. They are the values of gRPC Endpoint (for Validators) and HTTP Endpoint (for Validators) on the node details page.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot