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
{{ message }}
This repository has been archived by the owner on Aug 30, 2022. It is now read-only.
On the eosio contract the powerup action ABI states net_frac: int64cpu_frac: int64 stating that the data type is int64, however when interacting with the function from within the smart contract it requires us to use an unsigned integer uint64_t to power up, this has a discrepancy between working from within the smart contract and when serialising data type to send over RPC_URL.
I am looking for some clarification and the motivation behind this.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
On the
eosio
contract thepowerup
action ABI statesnet_frac: int64
cpu_frac: int64
stating that the data type is int64, however when interacting with the function from within the smart contract it requires us to use an unsigned integeruint64_t
to power up, this has a discrepancy between working from within the smart contract and when serialising data type to send overRPC_URL
.I am looking for some clarification and the motivation behind this.
The text was updated successfully, but these errors were encountered: