Reddcoin's JavaScript stack just got a foundation it can grow on for the next decade. We've consolidated four drifting repositories into a single monorepo called reddcore, rebased it onto the latest bitpay/bitcore, and published the first reddcoin-specific packages to npm under @reddcoinproject. Integrators can now npm install them like any other dependency.

This post explains what changed, what's reddcoin-specific, and what it unlocks.

Why we did this

Bitcore is BitPay's work. It's a mature, well-tested JavaScript stack for Bitcoin-family chains, and BitPay already maintains chain-specific forks for Dogecoin and Bitcoin Cash as small companion packages (e.g. bitcore-lib-doge, bitcore-lib-cash). Reddcoin has lived in that same neighbourhood for years, but our copy of the neighbourhood was falling further behind and unmaintained.

Before this work, the reddcoin JS effort was spread across four working trees:

• A fork of the bitcore monorepo
• A standalone bitcore-lib-redd repository
• A standalone bitcore-p2p-redd repository
• A vendored copy of bitcore-build

Each carried pieces of the same effort. None of them agreed on which patches were canonical. And the monorepo fork was 1598 commits behind bitpay/bitcore upstream.

Refactoring in place would have meant carrying that 1598-commit gap forward forever. Every upstream improvement would land as a merge conflict instead of a fast-forward. So we did the harder thing once, to make the next thousand commits easy.

The reset

We hard-reset the monorepo onto bitpay/bitcore v11.8.1 (tag 33de7ae98, 2026-04-15) and replayed the reddcoin-specific work on top as small, reviewable commits. Each one isolated to a *-redd package in exactly the way BitPay isolates their own -doge and -cash forks.

Nothing was lost. The old state is preserved as the tag archive/pre-migration-2026-04-27, and the final pre-publish checkpoint is tagged phase-6.0d-smoke-test. Phases 0 through 5 of the migration are complete, plus the pre-publish smoke-test suite (41/41 assertions passing).

The test results match the upstream baseline almost exactly:

• bitcore-lib-redd: 4687 passing, 5 failing. The 5 failures are pre-existing tapscript edge cases in upstream v11.8.1, unrelated to reddcoin, and the same 5 failures BitPay's own CI shows.
• bitcore-p2p-redd: 173 passing, 19 failing. The 19 are framework-level sinon/dns stub issues shared with upstream bitcore-p2p. The same code in the upstream package fails identically.

In other words: we're at parity with BitPay's baseline. Our patches don't regress it.

What's reddcoin-specific in reddcore

The whole point of isolating patches into -redd packages is that the reddcoin surface area becomes small enough to read in an afternoon.

In bitcore-lib-redd:

• Proof of Stake Velocity (PoSV) support on Block
• isProofOfStake() / isProofOfWork() helpers and block signature field
• Transaction nTime field for v2+ PoS transactions, with toSigningBuffer separated from toBuffer so signing stays correct
• Reddcoin networks. mainnet and testnet
• Reddcoin URI scheme for payment requests
• Electrum-format hashes where reddcoin diverges from Bitcoin

In bitcore-p2p-redd:

• Protocol version 80016
• User-agent string /Reddcore:VERSION/
• Network magic bytes fbc0b6db
• New sendaddrv2 message (BIP155)
• addr messages at the standard 4-byte timestamp

For bitcore-node:

• Included the REDD module and rewritten against the modern 4-argument signature (services, chain, network, config)
• The REDD module loads via a config-driven module path, with no loader hack required.
• ReddcoinP2PWorker now extends LitecoinP2PWorker, the same inheritance pattern upstream uses for Dogecoin

Now on npm

The first two packages are published and installable today.

npm install @reddcoinproject/bitcore-lib-redd
npm install @reddcoinproject/bitcore-p2p-redd

No more pulling from GitHub URLs. No more pinning to a commit SHA and hoping nothing drifts. The @reddcoinproject npm scope is claimed, live, and the home for every publishable package in the reddcoin JS ecosystem.

Next up on the same scope: bitcore-node, then bitcore-wallet-service, bitcore-wallet-client, and insight. Each one ships when it passes the same smoke-test bar the first two cleared.

A reddcoin-flavoured block explorer

The explorer story deserves its own section, because we're not just porting Insight with a reddcoin logo on it. We're using the consolidation as a chance to ask: what should a block explorer actually tell you about a PoSV chain?

The standard surface is there: chain enum, branding, address validation via bitcore-lib-redd, a PoSV vs PoW badge on every block and transaction. That part is table stakes.

The interesting part is what we're adding on top:

• Rich-list page with activity columns and a freshness indicator (snapshotAt), so you can see not just who holds the most but who's actually moving coins
• Active addresses as a dedicated page plus a summary tile on the home dashboard
• First and last activity on every address page, so you can tell a dormant whale from an active one at a glance
• Self-pay collapsing on address transaction lists so change outputs stop drowning out real activity
• Dormant-vs-active address analytics as a first-class view
• Numbered pagination and server-driven sort on every large list, so deep exploration doesn't time out

A technology preview is currently hosted at insight.redd.ink

And ultimately will find a home at insight.reddcoin.com.

What this unlocks

The technical debt was never the point. The point is what becomes possible once it's paid down.

• Wallet projects can build against a registry. npm install @reddcoinproject/bitcore-lib-redd is now a one-line dependency, the same as any other library. No forks, no vendored copies.
• New integrations land in one place. A single monorepo means a single issue tracker, a single CI pipeline, and a single review surface for community contributions.
• Upstream merges become routine. Catching up to BitPay's next release is now a normal rebase, not a 1598-commit cliff. We expect to track upstream on a sustainable cadence going forward.
• The pattern is reusable. Anyone running a bitcore-family chain can follow the same -redd template. The same one BitPay uses for -doge and -cash and ride the same rails.
• Upstream features land alongside the catch-up. Taproot, descriptor wallets, threshold signatures, and the future ReddId come along for free.

How to help

The work is open-source at reddcoin-project/reddcore. This is collaborative downstream-of-BitPay work: bitcore is their stack, we contribute the reddcoin-specific pieces as the same kind of chain-fork package they themselves maintain for other communities, and we welcome contributions back.

The most useful thing you can do right now is install the packages, build something against them, and tell us what breaks. File issues on GitHub. If you maintain a wallet, an exchange integration, or a block explorer that touches reddcoin, the registry-installable packages are ready for you to depend on today.

With this foundation in place, the next phases (bitcore-node on npm, the wallet service and client, and the hosted Insight explorer) become incremental ships rather than heroic efforts.