Skip to content

Conversation

@jaycoolslm
Copy link

@jaycoolslm jaycoolslm commented Nov 23, 2025

Description

This PR adds a quickstart to enable devs to spin up json rpc relay

Related issue(s)

Fixes #

Testing Guide

Changes from original design (optional)

N/A

Additional work needed (optional)

N/A

Checklist

  • I've assigned an assignee to this PR and related issue(s) (if applicable)
  • I've assigned a label to this PR and related issue(s) (if applicable)
  • I've assigned a milestone to this PR and related issue(s) (if applicable)
  • I've updated documentation (code comments, README, etc. if applicable)
  • I've done sufficient testing (unit, integration, etc.)

jaycoolslm and others added 5 commits November 23, 2025 16:28
Updated the README to include quickstart instructions and environment variable configuration.

Signed-off-by: jaycoolslm <86686746+jaycoolslm@users.noreply.github.com>
Revise README for quickstart and configuration steps
Added instructions to copy the example environment file.

Signed-off-by: jaycoolslm <86686746+jaycoolslm@users.noreply.github.com>
Signed-off-by: Jake Hall <jake.hall@hashgraph.com>
Signed-off-by: jaycoolslm <86686746+jaycoolslm@users.noreply.github.com>
@jaycoolslm jaycoolslm requested review from a team as code owners November 23, 2025 16:33
@quiet-node quiet-node added the documentation Improvements or additions to documentation label Nov 25, 2025
@quiet-node quiet-node added this to the 0.74.0 milestone Nov 25, 2025
@@ -78,7 +78,6 @@
"version": "2.2.1",
"resolved": "https://registry.npmjs.org/@ampproject/remapping/-/remapping-2.2.1.tgz",
"integrity": "sha512-lFMjJTrFL3j7L9yBxwYfCq2k6qqwHyzuUl/XBnif78PWTJYyL/dfowQHWE3sp6U6ZzqWiiIZnpTMO96zhkjwtg==",
"peer": true,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you revert the changes to this file so the PR can focus solely on the document addition?

HEDERA_NETWORK= # Which network to connect to. Can be: previewnet, testnet, mainnet or a map of IPs and nodes e.g. {"127.0.0.1:50211":"0.0.3"}
MIRROR_NODE_URL= # The Mirror Node API endpoint e.g. https://testnet.mirrornode.hedera.com or https://mainnet.mirrornode.hedera.com
# Operator Account (Required for transaction execution; use the Hedera Portal (https://hubs.ly/Q03Vw-vN0) account for 1000 HBAR / day)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is https://hubs.ly/Q03Vw-vN0? Can we not include it?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, it might be better to use a faucet address with our domain.

Also, I would avoid the bracket-inside-a-bracket construction. Maybe use markdown format [Hedera Portal](address to hedera portal) instead?

Also, I'm missing information that the description about the faucet applies only to the testnet/previewnet configuration.

3. Run `npm run start`. This will start the server on port `7546`.
```bash
git clone https://github.com/hiero-ledger/hiero-json-rpc-relay.git
cd hiero-json-rpc-relay
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should still add steps to install packages and build the project as well, right?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not in the instructions for starting the dockerized version of the application, but we could include an alternative section on running it directly with npm start as well.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alternatively, we shouldn't keep Node/NPM in the requirements, because they no longer apply to the docker-only startup instruction.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants