This project is no longer under active development and has been archived. The repository is kept for historical purposes and read-only access. No further updates or pull requests will be considered.
This project provides a very simple starter application for working with web3j and the Ion Interoperability Framework using an Ethereum network (testnet) known as Rinkeby.
The demo deploys the Ion smart contract.
In order to run this demo, three pieces of information are required:
- Ethereum client (or node) endpoint. The simplest thing to do is request a free access token from Infura.
- A wallet file. This can be generated using the web3j command line tools.
- Some Ether. This can be requested from the Rinkeby Faucet.
Once these details have been added to the main Application class, you'll be good to go.
Below is a diagram with a high level overview of how components interact in the Ion Interoperability Framework
This application demonstrates a number of core features of web3j and Ethereum:
- Connecting to a node on the Ethereum network
- Loading an Ethereum wallet file
- Deploying the Ion Interoperability Framework
This application has purposefully been kept as simple as possible with the aim of demonstrating how to deploy the Ion Interoperability Framework on a decentralised Ethereum network.
If you require further background information about the above configuration items for the project you can refer to the below.
For a more comprehensive overview, I recommend you read the Java Magazine Article, watch the YouTube talk, and read all of the documentation.
The contained smart contract is based on the Ion Interoperability Framework
The associated Java smart contract wrappers reflect their respective Solidity smart contracts.
You should use /resource/build.sh to compile the contracts
For more background on smart contracts, refer to the smart contracts section of the docs.
If you don't want to sign up to Infura, and would like to run a node yourself, there are instructions in the getting started section of the docs.
For more information on the different Ethereum test networks (or testnets), refer to the testnet overview in the docs.
For background on Ether, refer to the transactions overview section of the docs.
For a more technical overview of working with wallet files, refer to the Offline transaction signing section of the docs.
A logback configuration is included in the project dependencies allowing the logging of protocol messages if required. To enable, simply change the following line in the logback configuration to read:
<logger name="org.web3j.protocol" level="DEBUG"/>