github.com/amazechain/amc@v0.1.3/docs/jsonrpc/rpc.md (about)

     1  # `rpc` Namespace
     2  
     3  The `rpc` API provides methods to get information about the RPC server itself, such as the enabled namespaces.
     4  
     5  ## `rpc_modules`
     6  
     7  Lists the enabled RPC namespaces and the versions of each.
     8  
     9  | Client | Method invocation                         |
    10  |--------|-------------------------------------------|
    11  | RPC    | `{"method": "rpc_modules", "params": []}` |
    12  
    13  ### Example
    14  
    15  ```js
    16  // > {"jsonrpc":"2.0","id":1,"method":"rpc_modules","params":[]}
    17  {"jsonrpc":"2.0","id":1,"result":{"txpool":"1.0","eth":"1.0","rpc":"1.0"}}
    18  ```
    19  
    20  ## Handling Responses During Syncing
    21  
    22  When interacting with the RPC server while it is still syncing, some RPC requests may return an empty or null response, while others return the expected results. This behavior can be observed due to the asynchronous nature of the syncing process and the availability of required data. Notably, endpoints that rely on specific stages of the syncing process, such as the execution stage, might not be available until those stages are complete.
    23  
    24  It's important to understand that during pipeline sync, some endpoints may not be accessible until the necessary data is fully synchronized. For instance, the `eth_getBlockReceipts` endpoint is only expected to return valid data after the execution stage, where receipts are generated, has completed. As a result, certain RPC requests may return empty or null responses until the respective stages are finished.
    25  
    26  This behavior is intrinsic to how the syncing mechanism works and is not indicative of an issue or bug. If you encounter such responses while the node is still syncing, it's recommended to wait until the sync process is complete to ensure accurate and expected RPC responses.