You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
celestia rpc state BalanceForAddress celestia10rtd9lhel2cuh6c659l25yncl6atcyt37umard
Expected result
balance of address
Actual result
message": "unmarshaling params for 'state.BalanceForAddress' (param: *types.Address): json: cannot unmarshal string into Go value of type types.Address"
Relevant log output
{
"jsonrpc": "2.0",
"id": 1,
"error": {
"code": -32700,
"message": "unmarshaling params for 'state.BalanceForAddress' (param: *types.Address): json: cannot unmarshal string into Go value of type types.Address"
}
}
Notes
No response
The text was updated successfully, but these errors were encountered:
While debugging #2322 , I noticed that it is not only an RPC issue, but
also a broken API one. All RPC methods that used the type
`state.Address` were unusable, both via the client and via raw JSON
calls. This is because the server was unable to marshal the address
string value back into the interface type.
To circumvent this, I have embedded the sdk.Address type in the same way
that we embed the fraud proof type, to allow us to unmarshal it back
into a concrete type. I have also added unit tests to fix this.
In addition, it fixes the RPC parsing - so it closes#2322 .
Celestia Node version
v0.11.0-rc2
OS
macOS
Install tools
https://docs.celestia.org/nodes/celestia-node/ for Mac (Apple) x Arabica
Others
No response
Steps to reproduce it
Expected result
balance of address
Actual result
message": "unmarshaling params for 'state.BalanceForAddress' (param: *types.Address): json: cannot unmarshal string into Go value of type types.Address"
Relevant log output
Notes
No response
The text was updated successfully, but these errors were encountered: