This takes token action and returns whether it is valid or not.
After the router is defined, define the inputs and responses for this queryIsTokenActionValid:

Notes on the above code:
This query request ONE path-parameter which refer to token action. The output type should be something that is both JSON marshalable and stringable (implements the Golang fmt.Stringer interface). The returned bytes should be the JSON encoding of the output result.
For the output of IsTokenActionValid, the normal IsTokenActionValid struct is already JSON marshalable, but we need to add a .String() method on it.
Parameters
| Name | Type | Default | Required | Description |
|---|---|---|---|---|
| path | string | false | false | Path to the data (eg. "/a/b/c") |
| data | []byte | false | true | Data |
| height | int64 | 0 | false | Height (0 means latest) |
| prove | bool | false | false | Include proofs of the transactions inclusion in the block, if true |
Example
In this example, we will explain how to query IsTokenActionValid with abci_query.
Run the command with the JSON request body:
curl 'http://localhost:26657/'
{
"method": "abci_query",
"params": [
"/custom/fee/is_token_action_valid/assign-msg",
"",
"0",
false
],
"id": 0,
"jsonrpc": "2.0"
}
The above command returns JSON structured like this:
{
"jsonrpc": "2.0",
"id": 0,
"result": {
"response": {
"code": 0,
"log": "",
"info": "",
"index": "0",
"key": null,
"value": "ZmFsc2U=",
"proof": null,
"height": "345",
"codespace": ""
}
}
}