Repository navigation
Releases
v1.2.1
qbit-explorer v1.2.1 stops pool statistics from loading the database on every transaction page: GET /api/v1/mining/pools/:interval now keeps each answer for 60 seconds, and transaction pages no longer fetch it. It also renames BTC.com to CloverPool, with its current name, slug, logo and block tag, and adds a pool definition for SwitchPoolProfit. Two API answers change: /api/v1/mining/pool/btccom answers 404, and an interval the pool statistics route doesn't know answers 400. Read Upgrading if a client of yours uses either.
Fixed
- A page load no longer costs the database a full pass over the pool statistics. Every transaction page fetched
GET /api/v1/mining/pools/1m, and each request ran ten queries, two of them aggregations overblocks, with nothing shared between requests. Crawlers walking transaction pages drove hundreds of megabytes a second of MariaDB disk reads on each mainnet origin. The backend now keeps each interval's answer, block count included, in memory for 60 seconds, and requests that arrive while one is being worked out share that one computation. The transaction page and the mobile tracker fetch the statistics only for an accelerated transaction's ETA (#104).
Changed
- The pool this explorer called BTC.com is now CloverPool, as it has called itself since 2024 and as the upstream pool registry now has it. Its definition keeps id 7, so the import renames the database row in place and its blocks and hashrate history stay with it. Its slug is
cloverpool, which brings in the upstreamcloverpool.svglogo, and/mining/pool/btccomredirects to/mining/pool/cloverpool. The API has no alias:/api/v1/mining/pool/btccom, with its/blocksand/hashrateroutes, answers 404 (see Upgrading). The definition also matches thecloverpooltag, which the pool has signed its Bitcoin blocks with since qbit height 147597, besidebtccom, which it signed until height 166921 (#109, #111). - SwitchPoolProfit has a pool definition, matched by its coinbase tag
/SPP switchpoolprofit/, with the logo its operator supplied. Its blocks, on the permissionless lane, attributed to Unknown before (#106). GET /api/v1/mining/pools/:intervalanswers400 {"error":"Invalid interval"}for an interval it doesn't know, before any SQL. It used to answer with the statistics of the whole indexed history. The intervals are1h,24h,3d,1w,1m,3m,6m,1y,2y,3y,4yandall(#104).- The same route answers 500 when a hashrate-window query fails in the database, where it used to answer 200 with zeroed hashrates. A window the hashrate indexers haven't completed still answers 200 with zeroes, as before. After a failure the interval answers 500 for five seconds before the database is asked again (#104).
- Pool statistics lag the chain by up to 60 seconds. The
Expiresheader is unchanged, so a client or CDN that honours it can hold an answer for up to two minutes in all (#104).
Documentation
- docs/mining-pools.md has the evidence for CloverPool's two tags, with a census of its 883 qbit blocks, and for SwitchPoolProfit's tag and its two reward schemes.
- AGENTS.md, docs/qbit-local-dev.md and the Docker and production READMEs cite qbit v1.0.1, the mainnet maintenance release, and the regtest smoke job in CI runs against its qbitd (#107).
Upgrading
- No database migration and no config change: the schema stays at version 113.
- On its first start the backend imports the new pool definitions. It renames CloverPool's row, matches its blocks and the Unknown pool's blocks again, which moves SwitchPoolProfit's blocks to its own pool, and has the hashrate indexers run again. The mining pages can be behind until that finishes.
- If a client of yours calls
/api/v1/mining/pool/btccom, change it to/api/v1/mining/pool/cloverpool. Pool ids don't change. - If a client of yours sends
mining/pools/:intervalan interval outside the list above, it now gets 400.
v1.2.0
qbit-explorer v1.2.0 fixes broadcasting under the esplora backend (POST /api/tx and /api/txs/test now go through qbitd, accept the hex in any body and answer 503 while qbitd is unavailable), repairs duplicate canonical block rows that older releases left below the indexing window, follows invalidateblock and chain wipes without waiting for a new block, makes /blocks and the mining dashboard follow reorgs live, and brings Node.js 26.13.1, nginx and dependency security updates. The Docker Compose example now needs qbitd's RPC login in docker/.env: read Upgrading before you update a Compose setup.
Fixed
- Under
MEMPOOL.BACKENDesplora,POST /api/txandPOST /api/txs/testanswered 400 for every transaction. Neither the Broadcast Transaction page nor clients of the esplora API'sPOST /txcould broadcast, and the Test Transactions page couldn't test. Both routes now go through qbitd, asPOST /api/tx/pushdoes. A broadcast answers the txid, and a transaction qbitd refuses gets 400 with qbitd's error code (sendrawtransaction RPC error: {"code":N}). Thenoneandelectrumbackends already sent both to qbitd. POST /api/txtakes the hex as the whole body, whatever its content type, as qbit-electrs'sPOST /txdoes. A form, whichcurl -dsends and the API docs show, anapplication/octet-streambody and one without a content type got 400sendrawtransaction RPC error: {"code":-1}under every backend, without reaching qbitd, as the route only read a body sent as text.- The backend follows
invalidateblock, and a chain wiped while it runs, such as a regtest reset, without waiting for a new block. It took a qbitd tip below its cached blocks for a node catching up, and kept them.GET /api/blocks/tip/heightand the block lists showed the invalidated blocks until qbitd's next block, and a wiped chain's blocks until the new chain reached their heights or the backend restarted. Now the backend asks qbitd whether it is still syncing. While qbitd is in initial block download, or has headers above its tip, the blocks stay, as before. Otherwise the backend drops them, as it drops blocks a reorg replaced, and sends pages one reorg. /blocksand the mining dashboard's block list follow a reorg without a reload. They used to keep the blocks a reorg replaced, and never showed a block replaced at the same height. After a reorg to a shorter chain, they skipped new blocks until the chain passed the old tip. Now the WebSocket's blocks win at their heights, a page the reorg reached takes the new chain's blocks, and the page count follows the new tip on every page. When the WebSocket's blocks would leave a gap on the first page, as after the tab missed more blocks than they hold, the page asks the API again. When an answer from/api/v1/blocksdoesn't fit the WebSocket's chain, such as a browser's or CDN's copy from before the reorg, the list asks again 10 seconds later, past caches. From the third request of a page load on, failed ones included, it shows the blocks that fit instead.- With indexing on, the chain check repairs heights below the indexing window that hold two or more canonical block rows, which releases before 1.1.0 could leave. 1.1.0's check stopped above the window's lowest height. At each such height, it makes qbitd's block the only canonical row, and has the hashrate indexers index the daily and weekly periods they skipped. They logged
Hashrate window is not consecutive at heights <h> and <h>and skipped the periods around such a height, and block lists showed either row. The period that begins right after it wasn't skipped: its block window starts at that height and took either row, so the check deletes its hashrates to have them computed again. The window's lowest height gets qbitd's block as its only canonical row, indexed first if no row is it. Below that height, a height where none of the rows is qbitd's block is left as it is, with one warning. If it holds two canonical rows, the hashrate periods around it stay skipped, and the one after it keeps hashrates computed with either row. Hashrates computed with a lone row from another chain that the check replaces are computed again. - With CPFP indexing on, a repair at the window's lowest height deletes the CPFP clusters from there to the tip, as the chain check's repairs above it do, and the CPFP indexer rebuilds them, which can take a long time on a large window. Below that height, which the CPFP indexer doesn't cover, CPFP clusters stay as they are.
- A new block's coinbase that qbit-electrs hasn't indexed yet no longer logs an error. The backend fetches it as the block arrives, and logged
Cannot fetch tx <txid>. Reason: Request failed with status code 404before it got the coinbase from qbitd. On testnet4 that was about one block in three. A first fetch that finds no such transaction now logs at debug level. Any other first failure, such as a refused connection, a timeout or a 5xx, still logs an error, even when qbitd then returns the transaction.
Changed
docker/docker-compose.ymltakes qbitd's RPC login fromCORE_RPC_USERNAMEandCORE_RPC_PASSWORDindocker/.env, instead of settingmempoolandmempool, so a copied compose file no longer carries a known password.docker/.env.examplelists both. The compose file has no default for them: until both are set, everydocker composecommand indocker/stops,down,psandlogsincluded. This breaks existing Compose setups untildocker/.envhas the login (see Upgrading). The backend image'sstart.shstill defaults both tomempoolfor a container started without them.POST /api/tx,/api/tx/push,/api/txs/testand/api/v1/txs/packageanswer 503qbitd is unavailable, try again laterwhen qbitd can't take the call: it can't be reached or doesn't answer in time, is warming up (-28) or not ready (-10), turns the backend away with 401 or 403, or has a full work queue. They answered 400, which a wallet can take for a refused transaction. qbitd's refusals still get 400 with its code. A malformed body gets 400 with the reason, such asNon-hex request body, instead of an RPC error with a code the explorer made up.- With
MEMPOOL.BACKENDelectrumand qbitd's txindex disabled or still building,GET /api/address/:address/txsandGET /api/scripthash/:scripthash/txsanswer 503 and name qbitd's txindex, as the transaction routes have since 1.1.0. They answered 500. Both routes look up anafter_txidoutside the history, and the page's own transactions, in qbitd, so even a first page with a confirmed transaction answered 500. Their other answers keep their status. - Node.js 26.12.1 to 26.13.1, the 26.x security release of 2026-11-10, in the backend image, the frontend image's build stage,
.nvmrcand CI. The backend serves plain HTTP, so the release's high-severityhttp2and TLS fixes don't reach it, but its llhttp update andhttps.Agentfix do. - The frontend image's
nginx:1.30.6-alpinebase is pinned to the digest Docker Hub rebuilt on Alpine 3.24.4, for its curl, expat and brotli security fixes. nginx stays 1.30.6. - Backend dependencies:
bitcoinjs-lib6.1.8 to 6.1.10, for three high advisories in its PSBT fee calculation andBlock.checkProofOfWork(), which the explorer doesn't use, and the test tools'@babel/core7.28.5 to 7.29.13, for a low one. Of the code 6.1.10 changes, the explorer calls onlyPsbt.updateInput, fromPOST /api/v1/psbt/addparents, which now also clears cached fee and transaction data the route doesn't read. Frontend dependencies:domino2.1.6 to 2.1.9, which only the SSR server uses, for CVE-2026-101895 and 2.1.9's serialization XSS fixes.
Documentation
- docker/README.md shows how to make qbitd's RPC login with qbit's
share/rpcauth/rpcauth.pyand put it indocker/.env, or to use qbitd's RPC cookie instead, and which characters to keep out of the password. - docs/qbit-local-dev.md describes the regtest smoke script's new last check, which mines a block, runs
invalidateblockon it and expects the backend's tip to follow. It runs only with the regtest harness'ssmoke.envand a node onregtest. - .github/rulesets/README.md says how to rename a required check, as a Node update does to five of them, so that pull requests can still merge.
Upgrading
-
Docker Compose: set
CORE_RPC_USERNAMEandCORE_RPC_PASSWORDindocker/.envbefore you run anydocker composecommand indocker/. If your qbitd still accepts the old sample's login, this line, run from the repository root, puts it there:printf '\nCORE_RPC_USERNAME=mempool\nCORE_RPC_PASSWORD=mempool\n' >> docker/.env
That keeps a known password, so replace it next: give qbitd an rpcauth line in place of the old login, restart qbitd, and put the new login in docker/.env, as docker/README.md shows.
- No database migration and no config change: the schema stays at version 113. With indexing on, the first chain check may repair rows below the indexing window, as described under Fixed.
- With a full-history index (
MEMPOOL.INDEXING_BLOCKS_AMOUNTat-1, as in theproduction/templates), duplicate canonical rows are inside the walk instead, which has repaired them since 1.1.0. With CPFP indexing on, as there too, its first repair deletes the CPFP clusters from the lowest repaired height to the tip, and the CPFP indexer rebuilds them, which can take hours on a long chain. A database that ran 1.1.0 with-1has had that repair already. - Rebuild both images: the backend image and the frontend image's build stage use Node.js 26.13.1, and the frontend image serves from the new nginx digest. If you run the backend outside Docker, update Node.js to 26.13.1 too.
Known limits
- After a reorg deeper than the indexing window, which in practice only a regtest chain sees, the chain check doesn't look again at the heights below the window that it repaired or left alone.
- With CPFP indexing on, a block...
v1.1.0
v1.1.0 catches the reorgs the block sync used to miss and repairs the chain index, serves the esplora routes the API docs listed, models more of qbit's relay policy, measures broadcasts in qbit's weight (so wallets can send standard transactions with up to the node's limit of inputs), builds the Docker images as production does, fixes the SSR build, and removes the unused Lightning backend. It has a database migration (113, dropping the unused Lightning tables) and changes the Docker build: read Upgrading below before you deploy.
Added
GET /api/address/:address/txs/chain, with an optional/:last_seen_txid, andGET /api/address/:address/txs/mempool, which the API docs listed but the backend didn't serve. They pass through to qbit-electrs, so they needMEMPOOL.BACKENDesplora. The other backends answer 405.GET /api/block/:hash/status,GET /api/tx/:txid/raw,GET /api/tx/:txid/outspend/:voutandGET /api/tx/:txid/merkleblock-proof, the other routes the API docs listed but the backend didn't serve. Block status and the merkleblock proof needMEMPOOL.BACKENDesplora, and the other backends answer 405. The raw transaction and the outspend work with every backend.MEMPOOL.HTTP_HOST, and the Docker image'sMEMPOOL_HTTP_HOST: the IP address the backend's HTTP port listens on. It defaults to"", every interface, as before, and theproduction/templates set it to127.0.0.1. A host name such aslocalhoststops the backend at startup.- The WebSocket
blocksmessage sent after a reorg carries"reorg": true, so pages can follow a reorg to a shorter chain. - An optional
github_tokenbuild secret for the frontend Docker image. The build lists the mining pool logos through the GitHub API, and a token keeps it under GitHub's rate limit. - CI tests a fee bump (RBF) in the browser, checks the translations for stale English text, and runs the Rust block-template builder's tests and a RustSec audit of its crates.
Fixed
- The Block Fees, Block Fees Vs Subsidy and Block Rewards graphs draw their QBT data. They were empty because their queries needed a USD price for each block, which qbit doesn't have.
GET /api/v1/mining/blocks/fees/:intervalandGET /api/v1/mining/blocks/rewards/:intervalnow return rows, withoutUSD. - Search suggests addresses when qbit-electrs runs with
--address-search. In esplora mode,GET /api/address-prefix/:prefixused to answer 500 for every prefix. It now answers[]when qbit-electrs has address search off, or when the text can't begin an address. - A mining graph opened at a range whose button is hidden opens at ALL. Examples are pools dominance's default 6M and the dashboard's link to the hashrate chart at 1Y. Such a graph used to load that range with no button highlighted. The visitor's saved range is kept.
- After an upgrade, transactions restored from the mempool cache are classified by the new release's rules. They used to keep the older release's flags, so after the v1.0.1 upgrade some qscriptions weren't highlighted in the block preview.
- Error messages over HTTP/2 show the status code alone, such as
400, instead of400 OK. - Enterprise mode (
customize.enterprise) applies from the first page a visitor opens. It used to wait until a transaction, tracker or preview page loaded. Abrandingwithout atitlekeeps the default page title. - With
ESPLORA.FALLBACKhosts, a healthy qbit-electrs host is no longer failed over because it refused bad requests, such as invalid addresses. Only the host's own errors, timeouts and errors from a proxy in front of it count, and they count against the host that failed. - With
MEMPOOL.BACKENDelectrum, address and scripthash histories page after anafter_txidas they do in esplora mode. Anafter_txidmissing from the history used to return the first page again, and the next page repeated the newest transaction. One that qbitd doesn't have gets 422, and a malformed one gets 400 on the scripthash route too. - The backend catches reorgs with indexing off, and a block replaced at the same height reaches pages within one poll, instead of when the next block arrives. With indexing off, a reorg used to leave the replaced block cached below the new ones.
- At startup, cached blocks that qbitd doesn't have, as in a disk or Redis cache from before a chain wipe, are dropped and synced again from qbitd. The tip height and the block list used to show the old chain until qbitd passed it. Blocks above qbitd's tip stay cached while qbitd catches up on the same chain, or is still syncing.
- With indexing on, chain validation makes qbitd's block the only canonical one at each height it checks, and indexes hashrates and CPFP clusters again from the first block it repairs. A chain wipe used to leave the old chain's blocks canonical below the cached ones, in block lists and mining stats.
- On a chain of up to 8 blocks, such as a fresh regtest chain, the backend caches every block, not only genesis and the tip.
- After a reorg to a shorter chain, such as a chain wipe, pages lower their tip and show new blocks as they arrive. They used to ignore new blocks until the chain passed the old tip, so the mempool blocks stood still and a transaction confirmed in one of them still showed as unconfirmed.
- A failed block or mempool update, such as during a qbitd or qbit-electrs outage, no longer logs a false
stallederror two minutes later. /tx/previewshows a transaction's weight and vsize as qbit counts them. It overstated both by three times the size without witnesses, and judged standardness by them.POST /api/v1/tx,/api/v1/tx/pushand/api/v1/txs/testaccept standard transactions with more than about 100 KB of non-witness data. Their size check used Bitcoin's weight.- With
MEMPOOL.ALLOW_UNREACHABLEfalse, pushed P2MR spends whose leaf script holdsOP_FALSE OP_IFare refused, as that setting intends. The check let every P2MR spend through. - Opcodes
0xbbto0xbdshow asOP_CHECKTEMPLATEVERIFY,OP_CHECKDATASIGPQCandOP_CHECKDATASIGADDPQC, as qbitd names them, where the explorer writes its own ASM: on/tx/preview, withMEMPOOL.BACKENDnone, and for mempool transactions restored from the cache. They showed asOP_RETURN_187toOP_RETURN_189. - With
MEMPOOL.BACKENDnoneorelectrum,OP_RETURNand other unspendable outputs show as unspent, as qbit-electrs has them. They showed as spent. npm run build:ssrbuilds the server-side rendering (SSR) server again, on Angular 20 and Express 5, and the server renders pages. It renders for the host names inNG_ALLOWED_HOSTS, by defaultlocalhost,127.0.0.1and thePROD_DOMAINSwith their subdomains. Any otherHost, or one that isn't a host name or IP address with an optional port, gets 400. A page that takes longer thanSSR_RENDER_TIMEOUT_MS, 5 seconds by default, is sent for the browser to render. CI builds the server and renders a page.
Changed
- The non-standard flag follows more of qbit's relay policy. Dust thresholds use qbit's spend sizes and round up, so a P2MR output is dust below 2,855 bits instead of 82. TRUC transactions over 50,000 vB, outputs to witness versions 3 to 16, and P2MR spends with an annex or beyond qbit's witness limits are flagged. Taproot script-path spends no longer skip the remaining checks. Sigops are counted over decoded scripts, as qbitd counts them, instead of over ASM text.
/tx/previewalso checks the rules qbitd applies when a transaction enters its mempool: outputs only to P2MR,OP_RETURNor the anchor, except on regtest; TRUC's version inheritance, its one unconfirmed ancestor and its 45,500 vB limit for a child; and spending all of an unconfirmed parent's dust. It loads the unconfirmed parents to do this, and says so when it can't. Elsewhere the flag still judges each transaction on its own.- P2MR inputs with an annex get the annex flag, as Taproot inputs do.
- Transactions no longer show the struck-through Taproot badge or its hint to save fees with Taproot, which don't fit qbit's P2MR addresses.
- Reward stats on the mining dashboard cover the last 1,440 blocks, a day of qbit blocks, instead of 144. Translated pages show those labels in English until their translations catch up.
MEMPOOL.RUST_GBTdefaults totrue, as it does upstream, so projected blocks come from the faster Rust block-template builder. The builder now uses qbit's weights. It used to overstate fee rates fourfold. The Docker image and theproduction/templates still set it tofalse.MEMPOOL.INDEXING_BLOCKS_AMOUNTdefaults to 110,000 blocks, about 76 days of 60-second blocks, up from 11,000, in the Docker image too.- Malformed txids, block hashes and scripthashes get 400 instead of 501, on every route, including
GET /api/block/:hash/txid/:index.GET /api/v1/transaction-timeswithouttxId[]andGET /api/v1/txs/outspendswithouttxidsget 400 instead of 500. - An unknown transaction or block gets 404 instead of 500 from eight more routes, such as
GET /api/tx/:txid/outspendsandGET /api/block-height/:height. A malformed height gets 400. WithMEMPOOL.BACKENDnone,GET /api/tx/:txid/merkle-proofanswers 405. - With
MEMPOOL.BACKENDnoneorelectrum, the transaction routes answer 503 and name qbitd's txindex when it's disabled or still building. They answered 404, as for a transaction that doesn't exist. - A relative
MEMPOOL_CONFIG_FILEis resolved against the backend's working directory, notbackend/dist/. A file found only at the old location is still read, with a deprecation warning. - With
CORE_RPC.COOKIEtrue, the backend authenticates only with qbitd's RPC cookie, even whenCOOKIE_PATHis empty. It no longer falls back toUSERNAMEandPASSWORD. It logs an error at startup when it can't read the cookie. When qbitd restarts with a new cookie and turns a call away, the backend retries that call once with the new cookie.SECOND_CORE_RPCworks...
v1.0.1
v1.0.1 adds qscriptions and qrune mints and transfers to transaction pages, moves the charts to echarts 6.1.0, and fixes documentation. There's no database migration and no change to the Docker build.
Added
- Qscriptions, qord's inscriptions, on P2MR inputs. The transaction badge, the decoded content and the inscription flag now read P2MR leaf scripts. The interface calls them qscriptions; API fields, flags and filter keys still say
inscription. GET /api/block/:hash/txid/:indexreturns the txid at that index in a block astext/plain.- A malformed index gets 400.
- An unknown block, or an index past the last transaction, gets 404.
- A malformed block hash gets 501, like the other block routes.
Fixed
- Qrune mints and transfers no longer show "Error decoding data". The explorer now finds each qrune's etching through the route above.
- Without prevouts, the backend no longer throws while checking a two-item witness for an inscription.
Changed
- Qrune
1:0is no longer shown as upstream's UNCOMMON•GOODS, which qord doesn't have. It resolves like any other qrune ID. - Charts run on echarts 6.1.0, with their legends kept above the plot.
- Frontend dependencies:
qs6.14.3 to 6.16.2, andexpress4.22.1 to 4.22.3.
Documentation
- The README now fetches upstream without its tags, whose names clash with ours. It also shows how to fix a clone that already has them.
- SECURITY.md asks for reports through GitHub's private vulnerability reporting, with email as the alternative.
Full changelog: v1.0.0...v1.0.1
v1.0.0
v1.0.0 is the first public release of qbit-explorer, a block explorer and mempool visualizer for qbit, based on mempool/mempool v3.3.1. These notes describe the qbit-specific delta from that upstream baseline.
Highlights
- qbit mainnet, testnet4 and regtest, with qbit address formats, P2MR scripts and post-quantum signatures.
- qbit's block rules: 2,000,000 weight-unit blocks with no witness discount, so a transaction's size, virtual size and weight are equal, and fees are in bits and bits/vB.
- Mining views for qbit's 60-second block target: every block shows whether it came from the permissionless or the AuxPoW lane, AuxPoW blocks are attributed to their parent-chain pools, and graph ranges are sized for qbit's block rate.
- qbit's standardness policy from genesis, with dust and sigops counted the way qbitd counts them.
- qbit.org's site header and footer, which operators can turn off.
qbit Behavior
- AuxPoW blocks show their parent work hash on the block page.
- Invalid addresses get a 400 response with the reason, for example
invalid qbit address HRP: expected tq, got bc, instead of a 500. GET /api/blocks/tip/heightanswers 503 until the backend finishes its first block sync.- The Rust block-template builder stays off (
MEMPOOL.RUST_GBT), because it still applies Bitcoin's witness scale factor. The backend projects the next blocks with its TypeScript implementation.
Operator Notes
- qbit-explorer needs an unpruned
qbitdwithtxindex=1and RPC enabled. qbit-electrs is optional and adds address pages (MEMPOOL.BACKEND=esplora). - No prebuilt images are published. docker/README.md shows how to build and run them.
QBIT_SITE_CHROME=falseremoves qbit.org's header and footer and stops the page from contacting qbit.org.- Upstream's paid, account and externally hosted services are off by default, and the Lightning explorer is removed.
- You may keep the Qbit name and logo on your own instance, but don't present it as an official Qbit service.
Known Issues
- The Block Fees, Block Fees Vs Subsidy and Block Rewards graphs are empty, because their queries need fiat price data, which qbit doesn't have.
- Search doesn't suggest addresses as you type:
/api/address-prefixanswers 500.
Validation
- CI builds and tests the backend and frontend in development and production modes, runs the backend integration tests against MariaDB, builds both Docker images and checks that the compose stack becomes healthy.
- CI also runs the backend and the browser tests against a qbit regtest stack of qbitd, qbit-electrs and MariaDB.
- The same code, apart from the version number and documentation, ran on both testnet4 origins before this release, with read-only checks of each host and an API comparison against the previous build.
Verifying
The v1.0.0 tag is signed. Check it in a fresh clone, not one that also tracks upstream mempool, whose tags use the same names:
git clone https://github.com/Qbit-Org/qbit-explorer.git
cd qbit-explorer
git verify-tag v1.0.0
git rev-parse 'v1.0.0^{commit}'The last command should print 382a1c447115dca212792a91ab6fdd9d01f689d4.