-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invoke contract from RPC server #181
Invoke contract from RPC server #181
Conversation
CC @sreuland |
6c84be2
to
72444e7
Compare
pub struct SimulateTransactionResponse { | ||
pub footprint: String, | ||
pub cost: Cost, | ||
// TODO: add results and latestLedger |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@2opremio FYI because latestLedger
is an int64 value it will be represented as a String in the json response
@2opremio @leighmcculloch , in terms of using for e2e tests, what would the cli invocation look like for hello world: the contract fn prototype: assuing cli invocation would look something like:
|
What
Allow invoking a contract through a remote RPC server (i.e. from a real network) instead of local sandbox
Note that, as
getContractData
is yet to be implemented by the RPC server, it is allowed to provide the contract through the--wasm
flag. We should probably remove this in the future.Also:
Known limitations