client unique identifier.
Normally the RevisionHeight is incremented at each height while keeping RevisionNumber the same. However some consensus algorithms may choose to reset the height in certain conditions e.g. hard forks, state-machine breaking changes In these cases, the RevisionNumber is incremented so that height continues to be monitonically increasing even as the RevisionHeight gets reset
the commitment key path.
POST /ibc/core/client/v1/verify_membership HTTP/1.1 Host: inj.nownodes.io Content-Type: application/json Accept: */* Content-Length: 194 { "client_id": "text", "proof": "text", "proof_height": { "revision_number": "text", "revision_height": "text" }, "merkle_path": { "key_path": [ "text" ] }, "value": "text", "time_delay": "text", "block_delay": "text" }
A successful response.
{ "success": true }