SPS Validator Development Update and Invoice #9
Validators Development #9
JPTR Corporation
This document offers a clear and thoughtful summary of the tickets we’ve successfully closed over the past 30 days, along with an overview of the work currently in progress. It’s designed to give you a comprehensive snapshot of our significant achievements, all presented in an easy-to-read format, with insights summarized by ChatGPT from Jira issues.
A payment of $40,000.00 is required to be made to JPTR Corporation. Please ensure the payment is made in the form of USDC to the Ethereum address:
0x57d917726073D7582022897F753B034aA593220c.
Note: Before transferring the full amount, send a minimal test transaction to verify the accuracy of the transfer. Once confirmed, proceed with the full payment.
TL;DR
● Validator core: partition bug crushed, instant psql shell added, vote-weight sync fixed, daily unlock reports live, TeraBlock balances now count toward circulating supply.
● Endpoints: CoinMarketCap-ready /supply/cmc, detailed /richlist, and a refined health-check shipped with v1.1.0.
● Releases: grab v1.0.1 for stability or v1.1.0 for new features and a slimmer Docker footprint.
● Bridge sprint: dual testnets operational, BridgeVault + upgrade proxy written, bidirectional daemons testing locally, 100-tx load test passed, full CI/CD in place, TypeScript SDK almost complete, and main-net script drafted.
● ❤️❤️❤️
Validator Enhancements
Partitioned-table resiliency & local-database quality of life
- Resolved several edge-case failures that surfaced when the validator queried or vacuumed partitioned Postgres tables, particularly under high-throughput replay conditions. These fixes prevent dead tuples from piling up, shorten nightly maintenance windows, and ensure analytics endpoints stay snappy even as the
chain grows.
○ Added a psql helper to run.sh; operators can now drop into an authenticated Postgres shell with a single command—no more digging for container names or passwords. This streamlines ad-hoc troubleshooting and accelerates complex data forensics.
○ PR #71
- Resolved several edge-case failures that surfaced when the validator queried or vacuumed partitioned Postgres tables, particularly under high-throughput replay conditions. These fixes prevent dead tuples from piling up, shorten nightly maintenance windows, and ensure analytics endpoints stay snappy even as the
Supply & transparency endpoints
- Introduced a purpose-built /supply/cmc endpoint, returning the aggregated total, circulating, and max supplies in the exact JSON schema expected by CoinMarketCap. This eliminates manual data pushes and paves the way for automated exchange listings.
○ Launched a new /richlist service that compiles and serves the top 100 SPS holders (with pagination). Community analysts, journalists, and whales alike can now monitor concentration trends without scraping chain data themselves.
○ PR #65
- Introduced a purpose-built /supply/cmc endpoint, returning the aggregated total, circulating, and max supplies in the exact JSON schema expected by CoinMarketCap. This eliminates manual data pushes and paves the way for automated exchange listings.
Governance-weight correctness
- Fixed a subtle race condition where validator vote tallies did not immediately reflect SPS that had exited its 28-day unstaking window. Delegated voting power now updates atomically at the exact block the tokens become liquid, keeping governance outcomes mathematically sound.
○ PR #62
- Fixed a subtle race condition where validator vote tallies did not immediately reflect SPS that had exited its 28-day unstaking window. Delegated voting power now updates atomically at the exact block the tokens become liquid, keeping governance outcomes mathematically sound.
Circulating-supply precision improvements
- Validator now publishes a daily token-unlock synopsis that enumerates all accounts scheduled to receive unstaked SPS in the next 24 hours, giving speculators and liquidity providers better foresight into short-term inflation.
○ Integrated live TeraBlock exchange balances into the supply calculation. Off-chain liquidity parked on that CEX previously went uncounted, so the circulating metric now mirrors real-world float with far greater fidelity.
○ PR #71
- Validator now publishes a daily token-unlock synopsis that enumerates all accounts scheduled to receive unstaked SPS in the next 24 hours, giving speculators and liquidity providers better foresight into short-term inflation.
Release milestones for reproducible nodes
- v1.0.1 — our first production hot-fix bundle: addresses log-spam regression, re-pins Docker images to slimmer Alpine bases, and patches a potential nil-pointer in the price-feed worker.
○ PR #54
○ v1.1.0 — a feature release that introduces default light-mode, enhanced supply routes, migration docs, and a refactored health-check endpoint that plays nicely with Kubernetes liveness probes.
○ PR #66
- v1.0.1 — our first production hot-fix bundle: addresses log-spam regression, re-pins Docker images to slimmer Alpine bases, and patches a potential nil-pointer in the price-feed worker.
Bridge Development Progress (Hive ⇄ BSC)
- Dual, chain-faithful test networks spun up
- Deployed a local Hive testnet seeded with history and a reduced block interval to accelerate replay testing. No longer needed as testing will likely be done on production now.
○ Launched a private BSC chain using Hardhat + Anvil, forked from the latest main-net state so contract calls resolve against realistic liquidity pools and gas costs.
- Deployed a local Hive testnet seeded with history and a reduced block interval to accelerate replay testing. No longer needed as testing will likely be done on production now.
- Test-token instrumentation & faucets
- Minted SPS test tokens on both chains. Automated integration suites can now mint (Not needed for production), burn, and transfer without a manual reset between runs.
- Smart-contract core: BridgeVault
- Authored a lean BridgeVault contract that escrows SPS on BSC, transfers corresponding IOUs on Hive, and vice-versa. All events are fully indexed and emit structured logs compatible with sps validator.
○ Wrapped the vault behind an OpenZeppelin Transparent Proxy, letting us roll out audited upgrades without migrating balances—a crucial safety net as we iterate.
- Authored a lean BridgeVault contract that escrows SPS on BSC, transfers corresponding IOUs on Hive, and vice-versa. All events are fully indexed and emit structured logs compatible with sps validator.
- Validator daemon flows & heartbeat telemetry
- Forward flow: a lightweight Go daemon tails BSC blocks, signs
semi-deterministic proofs of lock events with the validator’s key, and broadcasts them to Hive.
○ Reverse flow: a sister process listens for Hive token-issuance events and triggers unlocks on BSC. Both ends exposed with metrics for latency, error rates, and signature quorum status.
- Forward flow: a lightweight Go daemon tails BSC blocks, signs
- Exhaustive unit & load testing
- Implemented Foundry-level fuzz tests that randomize deposit sizes, network hiccups, and re-org scenarios to guarantee accounting.
○ Ran a scripted 100-transfer stress test in both directions—achieved a 100% with outliers traced and resolved.
- Implemented Foundry-level fuzz tests that randomize deposit sizes, network hiccups, and re-org scenarios to guarantee accounting.
- Continuous integration & developer DX
- Set up GitHub Actions for solidity-coverage, static-analysis (Slither + Surya), artifact uploads, and npm publishing of the new TypeScript Bridge SDK (deposit(), withdraw(), getStatus() helpers with typed responses).
- Path to main-net
- Deployed contracts to BSC testnet and Hive.
○ Drafted a one-click main-net launch script that injects verified addresses, multi-sig owners, Cloudflare R2 secrets, and Grafana endpoints—almost ready for governance approval.
- Deployed contracts to BSC testnet and Hive.
Congratulations @jptrcorp! You have completed the following achievement on the Hive blockchain And have been rewarded with New badge(s)
Your next target is to reach 500 upvotes.
You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word
STOP