|
| 1 | +# ERC-20 RESTful service |
| 2 | + |
| 3 | +This application provides a RESTful service for creating and managing |
| 4 | +[ERC-20 tokens](https://github.com/ethereum/EIPs/issues/20). |
| 5 | +It has been built using [Spring Boot](https://projects.spring.io/spring-boot/), and |
| 6 | +[web3j](https://web3j.io). |
| 7 | + |
| 8 | +It works with both [Geth](https://github.com/ethereum/go-ethereum), |
| 9 | +[Parity](https://github.com/paritytech/parity), and |
| 10 | +[Quorum](https://github.com/jpmorganchase/quorum). |
| 11 | + |
| 12 | +For Quorum, the RESTful semantics are identical, with the exception that if you wish to create |
| 13 | +a private transaction, you populate a HTTP header name *privateFor* with a comma-separated |
| 14 | +list of public keys |
| 15 | + |
| 16 | + |
| 17 | +## Build |
| 18 | + |
| 19 | +To build a runnable jar file: |
| 20 | + |
| 21 | +```bash |
| 22 | +./gradlew clean build |
| 23 | +``` |
| 24 | + |
| 25 | +## Run |
| 26 | + |
| 27 | +Using Java 1.8+: |
| 28 | + |
| 29 | +```bash |
| 30 | +java -jar build/libs/azure-demo-0.1.jar |
| 31 | +``` |
| 32 | + |
| 33 | +By default the application will log to a file named erc20-web3j.log. |
| 34 | + |
| 35 | + |
| 36 | +## Configuration |
| 37 | + |
| 38 | +The following default properties are used in the application: |
| 39 | + |
| 40 | +```properties |
| 41 | +# Port for service to bind to |
| 42 | +port=8080 |
| 43 | +# Log file path and name |
| 44 | +logging.file=logs/erc20-rest-service.log |
| 45 | + |
| 46 | +# Endpoint of an Ethereum or Quorum node we wish to use. |
| 47 | +# To use IPC simply provide a file path to the socket, such as /path/to/geth.ipc |
| 48 | +nodeEndpoint=http://localhost:22000 |
| 49 | +# The Ethereum or Quorum address we wish to use when transacting. |
| 50 | +# Note - this address must be already unlocked in the client |
| 51 | +fromAddress=0xed9d02e382b34818e88b88a309c7fe71e65f419d |
| 52 | +``` |
| 53 | + |
| 54 | +You can override any of these properties by creating a file name |
| 55 | +*application.properties* in the root directory of your application, or in |
| 56 | +*config/application.properties* relative to your root. If you'd rather use yaml, |
| 57 | +simply change the filename to *application.yml*. |
| 58 | + |
| 59 | + |
| 60 | +## Usage |
| 61 | + |
| 62 | +All available application endpoints are documented using [Swagger](http://swagger.io/). |
| 63 | + |
| 64 | +You can view the Swagger UI at http://localhost:8080/swagger-ui.html. From here you |
| 65 | +can perform all POST and GET requests easily to facilitate deployment of, transacting |
| 66 | +with, and querying state of ERC-20 tokens. |
| 67 | + |
| 68 | + |
| 69 | + |
| 70 | + |
| 71 | +## Docker |
| 72 | + |
| 73 | +We can use [Docker](https://www.docker.com/) to easily spin up a arbritrary instance |
| 74 | +of our service connecting to an already running Ethereum or Quorum network. |
| 75 | + |
| 76 | +All you need to do is build the Dockerfile: |
| 77 | + |
| 78 | +```docker |
| 79 | +docker build -f docker/Dockerfile -t blk-io/erc20-service . |
| 80 | +``` |
| 81 | + |
| 82 | +Then either run it with default configuration: |
| 83 | +```docker |
| 84 | +docker run -p 8080:8080 -v "$PWD/logs":/logs blk-io/erc20-service |
| 85 | +``` |
| 86 | + |
| 87 | +Or with a custom configuration: |
| 88 | + |
| 89 | +```docker |
| 90 | +export PORT=8081 |
| 91 | +docker run -p ${PORT}:${PORT} -v "$PWD/logs":/logs \ |
| 92 | + -e ENDPOINT="http://localhost:22001" \ |
| 93 | + -e FROMADDR="0xca843569e3427144cead5e4d5999a3d0ccf92b8e" \ |
| 94 | + -e PORT="$PORT" \ |
| 95 | + blk-io/erc20-service |
| 96 | +``` |
0 commit comments