Publish Chain 138 RPC capability metadata
This commit is contained in:
@@ -0,0 +1,62 @@
|
||||
{
|
||||
"name": "Chain 138 RPC Capabilities",
|
||||
"version": {
|
||||
"major": 1,
|
||||
"minor": 0,
|
||||
"patch": 0
|
||||
},
|
||||
"generatedBy": "SolaceScanScout",
|
||||
"timestamp": "2026-03-28T00:00:00Z",
|
||||
"chainId": 138,
|
||||
"chainName": "DeFi Oracle Meta Mainnet",
|
||||
"rpcUrl": "https://rpc-http-pub.d-bis.org",
|
||||
"explorerUrl": "https://explorer.d-bis.org",
|
||||
"explorerApiUrl": "https://explorer.d-bis.org/api/v2",
|
||||
"walletSupport": {
|
||||
"walletAddEthereumChain": true,
|
||||
"walletWatchAsset": true,
|
||||
"notes": [
|
||||
"MetaMask primarily relies on JSON-RPC correctness for balances, gas estimation, calls, and transaction submission.",
|
||||
"Explorer-served network metadata and token list metadata complement wallet UX but do not replace RPC method support."
|
||||
]
|
||||
},
|
||||
"http": {
|
||||
"supportedMethods": [
|
||||
"web3_clientVersion",
|
||||
"net_version",
|
||||
"eth_chainId",
|
||||
"eth_blockNumber",
|
||||
"eth_syncing",
|
||||
"eth_gasPrice",
|
||||
"eth_feeHistory",
|
||||
"eth_estimateGas",
|
||||
"eth_getCode"
|
||||
],
|
||||
"unsupportedMethods": [
|
||||
"eth_maxPriorityFeePerGas"
|
||||
],
|
||||
"notes": [
|
||||
"eth_feeHistory is available for wallet fee estimation.",
|
||||
"eth_maxPriorityFeePerGas is currently not exposed on the public RPC, so some wallets will fall back to simpler fee heuristics."
|
||||
]
|
||||
},
|
||||
"tracing": {
|
||||
"supportedMethods": [
|
||||
"trace_block",
|
||||
"trace_replayBlockTransactions"
|
||||
],
|
||||
"unsupportedMethods": [
|
||||
"debug_traceBlockByNumber"
|
||||
],
|
||||
"notes": [
|
||||
"TRACE support is enabled for explorer-grade indexing and internal transaction analysis.",
|
||||
"Debug tracing is intentionally not enabled on the public RPC tier."
|
||||
]
|
||||
},
|
||||
"ws": {
|
||||
"notes": [
|
||||
"Use the dedicated public WebSocket endpoint for subscriptions and live wallet/provider events.",
|
||||
"HTTP and WebSocket method coverage should be treated as separate operational surfaces."
|
||||
]
|
||||
}
|
||||
}
|
||||
Reference in New Issue
Block a user