web3j

See v2.1.0 for release notes.

Configurable polling intervals on contract deployment

The main purpose of this release is to enable users to configure the polling frequency on new smart contract deployments. Previously this was not possible, which meant that web3j-quorum users had to wait 15 seconds before their contracts could be deployed.

TransactionReceipts on contract deployment

It is now possible to obtain the TransactionReceipt associated with a contract deployment via <contract>.getTransactionReceipt(). This is only set when you call a <contract>.deploy(...) method, it will not be present on *<contract>.load(...)* methods, as no transaction takes place behind the scenes.

TransactionManager from addresses

TransactionManagers now contain a getFromAddress() method to provide the sender address associated with the TransactionManager. Thanks to androlo for the suggestion.

This release addresses https://github.com/web3j/web3j/issues/59 Contract deployments failing with ClientTransactionManager.

This is a minor release addressing https://github.com/web3j/web3j/issues/58 where the generated code for event functions wrappers was always using a lowercase function name.

This release only affects the smart contract wrapper generator, so will only require an upgrade to the web3j command line tools for most users.

See v2.0.0 for release notes.

This milestone release incorporates a number of key features:

Transaction managers

Transaction managers allow you to choose how you transact with Ethereum clients via web3j's smart contract wrappers. For instance, you can now choose if you wish to have web3j sign your transactions, or the Ethereum client that you submit the transaction to the network via. You can also specify the chain id as per EIP-155 to prevent replay of transactions.

This also simplifies working with other Ethereum platforms such Quorum via web3j-quorum, which works natively with web3j 2.0+ generated smart contract wrappers, with full transaction privacy support.

A fast transaction manager has also been created to facilitate sending multiple raw transactions per block.

Thanks to ferOnti for all of his input on working with higher throughput transactions.

Reactive, typed events

Events in generated smart contracts wrappers are now fully typed. E.g. in the ERC20 smart contract wrappers, you have the following event definition:

event Transfer(address indexed _from, address indexed _to, uint256 _value);

You now have the following event object type in the corresponding smart contract wrapper Java code:

public static class TransferEventResponse {
        public Address _from;

        public Address _to;

        public Uint256 _value;
    }

You can then get details of those events via the transaction receipt:

public List<TransferEventResponse> getTransferEvents(TransactionReceipt transactionReceipt)

Or get an Observable that creates a filter providing events as they happen on the blockchain:

public Observable<TransferEventResponse> transferEventObservable()

See HumanStandardToken for further details.

Thanks to @tramonex-nate for this great enhancement.

Default values

Default values are now available on all Solidity types. E.g. if you wish to provide an empty value to a smart contract wrapper, use <Type>.DEFAULT.

Thanks to @thedoctor who provided this change.

Versioning

web3j jars now contain details of the build version. You can query this from your code via the Version class.

The version is now provided with the web3j command line tools, which incidentally are now available on Homebrew.

$ brew tap web3j/web3j
$ brew install web3j
$ web3j version

              _      _____ _     _        
             | |    |____ (_)   (_)       
__      _____| |__      / /_     _   ___  
\ \ /\ / / _ \ '_ \     \ \ |   | | / _ \ 
 \ V  V /  __/ |_) |.___/ / | _ | || (_) |
  \_/\_/ \___|_.__/ \____/| |(_)|_| \___/ 
                         _/ |             
                        |__/              

Version: 2.0.0
Build timestamp: 2017-02-10 06:45:22.537 UTC

Light wallet generation

For working with resource constrained devices such as smartphones, web3j now provides two types of wallet file generation, full and light. Previously only the full generation was available. Running a simple benchmark locally, full wallet files can be generated in ~700 msecs, versus ~50 msecs for light.

See the WalletUtils class for more information.

Breaking changes

The Contract class has been migrated to the tx package along with the TransactionManager components.
Block and Transaction responses from Ethereum clients are no longer contained within an optional. This is to reduce the number of Optional.get() calls that were required when working with the Future and Observable APIs.

Bug fixes

• https://github.com/web3j/web3j/issues/43 RLP zero prefixed string
• https://github.com/web3j/web3j/pull/46 Replace Java internal API and make file seprator OS-specific
• https://github.com/web3j/web3j/issues/53 Compiling contract inside Java code

Provides IpcService for connecting to Ethereum clients over IPC for *nix based OS's.

Contains a number of bug fixes & pull requests submitted by the community.

Update web3j command line tools are now available via Homebrew of OS X users:

brew tap web3j/web3j
brew install web3j

This release contains a fix for the following issue:

• Public functions does not have a correct function name

Additionally web3j-tests.jar artifacts are now being published to Maven/JFrog.

This milestone release provides a couple of significant new features to web3j.

Firstly the JSON-RPC client API has been enhanced to integrate with RxJava's Observables. In addition to web3j.< methodName >.[ send() | sendAsync ], you also have observable() which will wrap the request in an observable, allowing straight forwards composition of JSON-RPC calls.

Secondly is the addition of web3j's filter API. web3j provides a fully asynchronous API for working with Ethereum client filters, so you no longer need to poll the client for filter updates. For instance, receiving a callback with all new blocks or transactions being created in Ethereum is very trivial. For more details refer to the new Filters and Events section in the documentation.

See v1.1.0 for release notes.

This release addresses issues with the Apache HttpClient on Android.
See here for details of core web3j changes.

Workaround for differences in the Transaction objects returned by Geth and Parity. See this issue for details.

See v1.0.8 for release notes.

1. Fixed #21 where multiple String values being returned by functions were not being decoded correctly.
2. Added Infura support to command line tools wallet.
3. Fixed async issue where RuntimeExceptions were not being captured on certain calls.

See v1.0.7 for release notes.

1. Updates to support new Geth Transaction Receipt fields added in 1.5 release.
2. Creation of a dedicated Infura client that manages Infura TLS certificates for you. So no more certificate imports!
3. Enhanced smart contract wrapper API to support multiple return values, such as those from a Solidity struct. See #18.

See v1.0.6 for release notes.

A couple of updates:

• Update to smart contract wrapper API - gas price & limit are now required upon contract object instantiation.
• Fixed potential issue for working with zero prefixed Ethereum addresses & public keys.

web3j's first Android release!

Note:

• The binary was built using jdk1.7.0_40 with target and source compatibility set to version 1.6
• The code generator uses JavaPoet which requires JDK 7+. Therefore for generating smart contract wrappers please use the command line tools that come as part of the 1.0.5 web3j distribution. All code generated is JDK 6+ compatible.

Updated code generator to generate Android/Java 1.6 compatible smart contract wrappers.