You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For Quorum, the RESTful semantics are identical, with the exception that if you wish to create
a private transaction, you populate a HTTP header name privateFor with a comma-separated
list of public keys
Build
To build a runnable jar file:
./gradlew clean build
Run
Using Java 1.8+:
java -jar build/libs/azure-demo-0.1.jar
By default the application will log to a file named erc20-web3j.log.
Configuration
The following default properties are used in the application:
# Port for service to bind toport=8080
# Log file path and namelogging.file=logs/erc20-rest-service.log
# Endpoint of an Ethereum or Quorum node we wish to use. # To use IPC simply provide a file path to the socket, such as /path/to/geth.ipcnodeEndpoint=https://localhost:22000
# The Ethereum or Quorum address we wish to use when transacting.# Note - this address must be already unlocked in the clientfromAddress=0xed9d02e382b34818e88b88a309c7fe71e65f419d
You can override any of these properties by creating a file name
application.properties in the root directory of your application, or in
config/application.properties relative to your root. If you'd rather use yaml,
simply change the filename to application.yml.
Usage
All available application endpoints are documented using Swagger.
You can view the Swagger UI at https://localhost:8080/swagger-ui.html. From here you
can perform all POST and GET requests easily to facilitate deployment of, transacting
with, and querying state of ERC-20 tokens.
Docker
We can use Docker to easily spin up a arbritrary instance
of our service connecting to an already running Ethereum or Quorum network.