What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
RustChain’s public endpoints let you inspect node health, epoch activity, listed miners, wallet balances, wallet history and historical settlements. Read them as reports from the API—not as independent proof that every reported hardware or protocol claim is true. The guide below explains what each endpoint can tell you and where its limits are.
Start with the question you want to answer
RustChain’s documented base URL is https://rustchain.org. Its API reference says: “All public rustchain.org endpoints use HTTPS with a browser-trusted certificate. Use strict TLS verification for production calls.” The routes below are useful for different scopes and time periods; a health check is not a wallet lookup, and a current snapshot is not a historical settlement record.
| Question | Endpoint | Scope and time |
|---|---|---|
| Is a node responding, and what version does it report? | GET /health |
Node health snapshot |
| What epoch state does the API report? | GET /epoch |
Current network epoch snapshot |
| Which miners and hardware attributes are listed? | GET /api/miners |
Network-wide miner listing |
| What balance is reported for a wallet? | GET /wallet/balance?miner_id=... |
Wallet-scoped balance |
| What recent activity is associated with a wallet? | GET /wallet/history?miner_id=... |
Wallet-scoped activity records |
| What does a particular epoch’s settlement contain? | GET /api/settlement/{epoch} |
Historical epoch settlement |
Use the API reference for the public routes and their documented fields: RustChain API Reference. The settlement route is documented in the RustChain Unified API Reference. Documentation examples illustrate response shape; their IDs, balances, hashes, timestamps and epoch values are not live readings.
Check node health with /health
A GET /health response is the place to begin when you need to know whether the endpoint responds and what operational status it reports. The API reference lists fields including:
#1 Best Overall
ok: the health result reported by the endpoint.version: the version string reported by the node.uptime_s: reported uptime in seconds.db_rw: database read/write status.backup_age_hours: age of the reported backup, in hours.tip_age_slots: reported age of the chain tip, in slots.
Treat these as a point-in-time status report. Even a healthy response does not guarantee the node will remain available or current after you check it.
Read the epoch snapshot—and account for the duration conflict
GET /epoch reports current epoch and slot information, including the epoch number, slot, blocks per epoch, epoch pot, enrolled miner count and supply metadata. These fields help you understand what the API says about the network’s current cycle; they do not, by themselves, explain how a particular wallet’s balance was calculated.
The official documentation does not agree on epoch duration. The API reference describes 144 slots as approximately 24 hours, while the RustChain homepage describes rewards of 1.5 RTC per 10-minute epoch. Both figures are published by RustChain sources, and the discrepancy means you should not treat either duration statement as settled without checking current API behavior or an authoritative current specification. See the RustChain homepage and API reference.
Recommended Free Tools
Interpret the miner listing as reported attributes
GET /api/miners lists active or enrolled miners and may include a miner identifier, architecture, device family, hardware description, antiquity multiplier, entropy score and last-attestation timestamp. These labels describe what the API reports for each entry. A listing is not independent verification that a physical machine has the stated characteristics or that its attestation is valid.
RustChain’s protocol specification describes the network as Proof-of-Antiquity: hardware attestation establishes eligible physical-machine participation, while antiquity influences reward weight. It says epoch rewards are allocated proportionally according to eligible miner weights, with weight influenced by validated hardware presence, antiquity multiplier and fingerprint confidence or anti-emulation checks. Those are the protocol document’s descriptions, not an independent audit of the endpoint data. Read the RustChain Protocol Specification alongside the reported miner fields.
Look up a balance with the canonical wallet parameter
For a wallet balance, use GET /wallet/balance?miner_id=.... The API reference identifies miner_id as the canonical query parameter and says address remains accepted as a compatibility alias. The response reports both a human-readable RTC amount in amount_rtc and an integer micro-RTC value in amount_i64. Do not assume the alias is preferred for new integrations.
Use wallet history for activity, not a single balance figure
GET /wallet/history?miner_id=... is documented as a public, wallet-scoped view of transaction and reward activity. The unified response can contain different entry types; inspect each record’s type, timestamp, epoch, hash and any status field rather than treating every row as the same kind of event.
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallWhen a response includes a status, distinguish pending items from records that appear settled. A history response describes activity associated with the requested wallet; it is not the same view as the network-wide miner listing or an epoch settlement.
Best Value
Inspect a specific epoch with its settlement record
Use GET /api/settlement/{epoch} to inspect the historical settlement for a particular epoch. The unified reference documents fields such as total pot, distribution, miner count, settlement hash and individual rewards. Substitute the epoch you want to inspect for {epoch}; do not mistake values from documentation examples for current settlement data.
Keep public read routes separate from operator actions
The endpoint guide is about reading public data. The unified reference labels bridge initiation and administrative lock operations as authenticated, and the protocol specification notes that some operator routes are intentionally restricted. A route being documented does not mean it is publicly callable or that it is a read-only endpoint. Check its access requirements before integrating it.
Respect documented rate limits and version caveats
The API reference lists implementation limits of 100 public-endpoint requests per minute, one attestation per ten minutes per miner, and ten transfers per minute per wallet. These are figures in the documentation, not independent measurements of current enforcement. Avoid assuming a public read limit authorizes attestation or transfer activity at the same rate.
Free tools Windows power users keep installed
One-click scans. No signup required.
The API documentation describes version 2.2.1-rip200, but route availability and response details can change. Confirm the live response and the current documentation before building an integration around a field or route. The reference’s examples show formats, not a current network state.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
