We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
let abi = """ { "inputs": [{ "internalType": "uint256", "name": "id", "type": "uint256" }], "name": "getGISTProof", "outputs": [ { "components": [ { "internalType": "uint256", "name": "root", "type": "uint256" }, { "internalType": "bool", "name": "existence", "type": "bool" }, { "internalType": "uint256[64]", "name": "siblings", "type": "uint256[64]" }, { "internalType": "uint256", "name": "index", "type": "uint256" }, { "internalType": "uint256", "name": "value", "type": "uint256" }, { "internalType": "bool", "name": "auxExistence", "type": "bool" }, { "internalType": "uint256", "name": "auxIndex", "type": "uint256" }, { "internalType": "uint256", "name": "auxValue", "type": "uint256" } ], "internalType": "structIState.GistProof", "name": "", "type": "tuple" } ], "stateMutability": "view", "type": "function" } """ let contract = web3.contract(abi, at: receipt.contractAddress, abiVersion: 2)! let tx = contract.createReadOperation("testStaticArray") let result = try await tx!.callContractMethod()
result:
"[\"0\": [0, false, [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0],11111, 0, false, 0, 0]]"
.
The outputs should have its name.
3.2.1
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What happened?
result:
What are the steps to reproduce?
.
What is the expected behavior?
The outputs should have its name.
What is the error thrown?
.
What's the stack trace said?
.
OS version
.
Library version
3.2.1
The text was updated successfully, but these errors were encountered: