Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteRustChain’s public endpoints let you inspect node health, epoch state, listed miners, wallet balances, wallet activity, and historical settlements. Read them as reports of what the API returns—not as independent proof that every protocol claim or hardware attestation is correct. The endpoint map below follows the official RustChain API documentation, which describes version 2.2.1-rip200; live routes and fields may change.
Start with the question you need answered
Use the endpoint that matches the scope and time frame of your question. Health, epoch, and miner routes describe network or node state; wallet routes are scoped to a miner identifier; settlement records describe a particular epoch.
As an Amazon Associate I earn from qualifying purchases.
| Question | Endpoint | Scope and time orientation |
|---|---|---|
| Is the node responding, and what version does it report? | GET /health |
Node snapshot |
| What epoch state does the node report? | GET /epoch |
Current network state |
| Which miners and hardware details are listed? | GET /api/miners |
Enrolled or active miner listing |
| What balance is reported for a wallet? | GET /wallet/balance?miner_id=... |
Wallet-scoped balance |
| What activity is associated with a wallet? | GET /wallet/history?miner_id=... |
Wallet-scoped activity |
| What settlement data is recorded for an epoch? | GET /api/settlement/{epoch} |
Historical epoch record |
The official API reference gives https://rustchain.org as the base URL and says: “All public rustchain.org endpoints use HTTPS with a browser-trusted certificate. Use strict TLS verification for production calls.”
Windows 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 reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteCheck node health with /health
GET /health is the place to check what a node reports about its availability and operation. The API reference describes fields including:
#1 Best Overall
- Wire-o bound with high visibility yellow cover
- Wire-o 4 ⅞ x 7 ¼
- Ruled light blue with red vertical lines
- Six vertical columns left page and 8x4 to the inch right page
- Inside quality white ledger paper is special formulated for maximum archival service with material that is 50 percent cotton and water resistant
ok: a health indicator.version: the reported software version.uptime_s: uptime in seconds.db_rw: database read/write status.backup_age_hours: age of the latest reported backup, in hours.tip_age_slots: reported age of the chain tip, in slots.
These values are a snapshot. A successful health response does not guarantee that the node will remain available or that a later request will succeed. Interpret each field using the API reference’s description rather than treating a reassuring overall status as a substitute for checking database or tip details.
Read epoch state with /epoch
GET /epoch reports information such as the epoch number, current slot, blocks per epoch, epoch pot, enrolled miner count, and supply metadata. It is useful for understanding what the API says is happening now, but the official RustChain sources disagree about how long an epoch lasts.
The RustChain API Reference describes 144 slots as approximately 24 hours. The RustChain homepage instead says rewards are 1.5 RTC per 10-minute epoch. Because those statements conflict, do not infer a definitive epoch duration or reward schedule from either statement alone. Check current authoritative documentation and the live API response before relying on timing.
Rank #2
- Brand New in box. The product ships with all relevant accessories
Interpret miner listings as reported fields
GET /api/miners returns a listing of active or enrolled miners. The API documents fields for miner identifier, architecture, device family, hardware description, antiquity multiplier, entropy score, and last-attestation timestamp.
These are values the endpoint reports. A hardware label or attestation timestamp is not, by itself, independent verification that a physical machine is present or that the reported classification is accurate. The protocol specification describes hardware attestation as a way to establish eligible physical-machine participation, while antiquity influences reward weight; that is the protocol’s stated design, not an audit conclusion established by reading a miner-list response.
Look up a wallet balance
For a balance, use GET /wallet/balance?miner_id=.... The API reference identifies miner_id as the canonical query parameter and says address is still accepted as a compatibility alias. Prefer the canonical name for new requests.
The response reports both amount_rtc, a human-readable RTC amount, and amount_i64, an integer amount in micro-RTC. Read the units before comparing values or doing arithmetic; the two fields express the amount at different scales.
Free tools Windows power users keep installed
One-click scans. No signup required.
Use wallet history for associated activity
GET /wallet/history?miner_id=... is documented as a public, wallet-scoped view of transaction and reward activity. The unified response can include entry types, timestamps, epochs, hashes, and status fields. If a status is present, distinguish pending activity from records presented as settled; do not assume every listed item is finalized solely because it appears in the response.
Wallet history and a balance answer different questions: history shows associated activity, while the balance endpoint reports an amount. A transaction or reward entry is not a substitute for checking the balance endpoint when the question is the wallet’s reported balance.
Inspect an epoch settlement
For a specific historical epoch, the unified reference documents GET /api/settlement/{epoch}. Its settlement fields include total pot, distribution, miner count, settlement hash, and rewards. Use the epoch identifier in the path to inspect the record for that epoch.
Examples in API documentation illustrate response shape; their epoch numbers, balances, miner IDs, hashes, and timestamps are not live network readings. Treat a sample payload as a schema example unless it is fetched from the endpoint as current data.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Understand what endpoint data can establish
The protocol specification describes epoch rewards as a proportional allocation based on eligible miner weights. It says weight is influenced by validated hardware presence, an antiquity multiplier, and fingerprint confidence or anti-emulation checks. Endpoint fields can show the values the API reports, but they do not independently demonstrate that the underlying validation or reward calculation was performed correctly.
Best Value
- Bright yellow extra stiff casebound covers
- Standard size 4 ⅝ x 7 ¼
- Ruled light blue with red vertical lines
- Six vertical columns left page and 8x4 to the inch right page
- Outside cover is waterproof and inside quality white ledger paper is special formulated for maximum archival service with material that is 50 percent cotton and water resistant
For a sound reading, separate three layers: the value returned by the endpoint, the meaning assigned to that field in the API documentation, and the protocol’s explanation of how the system is intended to work. Each layer supports a different kind of claim.
Keep public reads separate from operator actions
Public read-only routes are not interchangeable with routes that change state or require elevated access. The unified reference labels bridge initiation and administrative lock operations as authenticated, and the protocol specification says some operator routes are intentionally restricted. Do not treat an authentication requirement as a missing public data field or try to infer an operator action from a read-only response.
Account for limits and changing documentation
The API reference lists a public-endpoint limit of 100 requests per minute, an attestation limit of one per ten minutes per miner, and a transfer limit of ten per minute per wallet. These are implementation figures stated in the documentation, not independent measurements of live enforcement. If you are building a client, avoid assuming that repeated polling is unlimited and consult the current reference for route-specific behavior.
The documentation describes API version 2.2.1-rip200, but endpoint availability and response details can change. Confirm the current documentation and response before relying on a field for an operational or financial decision.
Quick Recap
References
- RustChain API Reference
- RustChain Unified API Reference
- RustChain Protocol Specification
- RustChain homepage
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.
