Practical overview
When it fits
Use it when you have an Ethereum or Quorum node and want a REST and Swagger interface for ERC-20 contract operations instead of making those requests directly to the node.
Who it is for
- Developers integrating ERC-20 token operations into systems that use REST.
- Teams operating an Ethereum or Quorum node that need an HTTP interface for token deployment, transactions and state queries.
Documented uses
- Create and manage ERC-20 tokens through REST requests.
- Submit transactions against ERC-20 contracts.
- Query ERC-20 token state through GET requests.
- Send Quorum private transactions using the `privateFor` header.
Requirements & limits
The repository documents running the server from a JAR with Java 1.8+ or in Docker. It requires a running Ethereum or Quorum node and a sender address already unlocked in the client.
- The service connects to an existing Geth, Parity or Quorum node; it is not the node itself.
- Configuration includes the node endpoint and transaction sender address, with a default service port of 8080.
- The documentation describes Swagger UI for issuing the service’s POST and GET requests.
- Quorum private transactions use a
privateForheader containing a comma-separated list of public keys.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Configure and start the service from a JAR
Build and start the REST service with a configured Ethereum or Quorum node endpoint and sender address.
Before you start
- Java 1.8 or later
- An already running Ethereum or Quorum node
- A transaction address unlocked in the client
Steps
Build the runnable JAR with
./gradlew clean build.Set
nodeEndpointandfromAddressinapplication.propertiesorconfig/application.properties; the sender address must be unlocked in the client.Start the JAR with
java -jar build/libs/azure-demo-0.1.jar.Open the Swagger UI at
http://localhost:8080/swagger-ui.htmlto view the documented POST and GET endpoints.
Expected outcome
The service starts with its REST endpoint documentation available in Swagger UI for token deployment, transactions and state queries.
Guide limitations
- The guide documents configuration and access to the endpoint UI, not a particular successful token operation.
- The default service port is 8080; the node endpoint and sender address must match the environment.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 18 October 2026
- Original website title
- web3labs/erc20-rest-service · Official homepage title · retained in its source language

