Debug JSON-RPC API

Ten supports a subset of Geth's DEBUG JSON-RPC API. This page details which Debug JSON-RPC API methods are supported.

Supported JSON-RPC API methods

Ten nodes support the following JSON-RPC API methods over both HTTP and websockets:

• debug_traceTransaction
• debug_eventLogRelevancy: returns all event logs generated by the transaction Id, together with the relevancy metadata. Intended for developers on dev networks to debug smart contracts. This call is disabled for production networks

debug_LogVisibility

Request Payload:

{
    "jsonrpc": "2.0",
    "method": "debug_eventLogRelevancy",
    "params": [
        "0xb29737963fd6768587ede453ab90ff7668115db16915a7833705ef134e793814"
    ],
    "id": 1
}

Request result:

{
    "jsonrpc": "2.0",
    "id": 1,
    "result": [
            {
                "address": "0x9802f661d17c65527d7abb59daad5439cb125a67",
                "topics": [
                    "0xebfcf7c0a1b09f6499e519a8d8bb85ce33cd539ec6cbd964e116cd74943ead1a"
                    ],
                "data": "0x000000000000000000000000987e0a0692475bcc5f13d97e700bb43c1913effe0000000000000000000000000000000000000000000000000000000000000001",
                "blockNumber": "0x4",
                "transactionHash": "0xb29737963fd6768587ede453ab90ff7668115db16915a7833705ef134e793814",
                "transactionIndex": "0x0",
                "blockHash": "0x2dc21ffe5cf46b8babc3d3c4613a2b8b241013e9f39532a9c9161d81068aa9b6",
                "logIndex": "0x0",
                "removed": false,
                "lifecycleEvent": true,
                "relAddress1": null,
                "relAddress2": null,
                "relAddress3": null,
                "relAddress4": null
            }
    ]
}