Web3.swift
Web3.swift copied to clipboard
A pure swift Ethereum Web3 library
This PR adds a new `invokeMethod` to the contract object allowing the usage of `[ABIParameter]` instead of the variadic parameters I also added a simple test for the method to...
Hi there I'm using a dynamic contract and can make calls to it successfully. However when using 'contract.createTransaction' methods on the same contract, I keep receiving the error: > Web3.RPCResponse.Error(code:...
## Problem Currently we have this method to invoke methods of a contract: ```Swift public subscript(_ name: String) -> ((ABIEncodable...) -> SolidityInvocation)? { return methods[name]?.invoke } ``` However, variadic functions...
The `from` value for the `createTransaction` function in `SolidityInvocation` should be optional just like in the `EthereumTransaction` initializer as it is not really required if you want to send a...
I am talking about `ERC20Contract` in this issue but it applies to all our static contracts. ### Problem Currently all functions we provide in `ERC20Contract` return a `SolidityInvocation`. This makes...
Hello! I have my own ERC20 contract, with transfer, transferFrom methods, etc. I would like to know how to get a reference to such a contract (via ABI + address...
The aim is not to increase the code coverage value but rather to make sure our code meets the specifications in as many cases as possible.
We need those types for fixed/ufixed in the upcoming contract abi module.
This is less of an issue, but more of a question. I'm wondering how you're thinking about handling the equivalent of web3.js' PromiEvent (promise + event emitter). More specifically, I'm...