v0.7.3: Transactions

The transactions update

Transactions and indexing

• The Transaction Index and inscription-related transaction locator builds are available. Optional related-locator creation and the retroactive action remain in the Inscription inspector.
• Index as you browse is an independent, persisted choice for Transaction Index and Inscriptions. Both are off by default. Opted-in browsing records exact validated blocks without starting a historical range job or advancing its sequential checkpoint.
• Block maps include every transaction in the validated block, beyond the first table page. Square sizes use output sats; a bounded passive preview shows only the first inscription in each transaction.
• Transaction selection opens its input/output flow in the viewport. Unknown input values and fees stay unestablished. Only verified reveal-output assignments receive output inscription badges; multiple inscriptions remain individually accessible. These assignments do not establish current ownership.

Workspace and navigation

• Details and Inspector share the left pane. Blocks and inscriptions use a square viewport; transactions can use a wider viewport. A draggable divider controls the split.
• The compact timeline is the default. Known block, transaction and output counts allow progressively closer navigation into transactions, outputs and output-local sat offsets in the same lane. Unknown counts remain unknown; these offsets are not global sat numbers.
• Wheel zoom anchors to the pointer; horizontal trackpad movement and Shift-wheel pan. Plain lane dragging pans, while a click moves the playhead without replacing indexing selections. Shift-click and Ctrl/Command-click edit indexing selections. Ruler scrubbing waits for the final position to settle.
• Map and flow navigation supports zoom, diagonal dragging, remembered views and Fit view. Returning to the containing block preserves the block's own view. Fullscreen and narrow layouts preserve timeline state.
• The global address field stays shared with the workspace. Missing inscription locations offer a reveal-block hint; known locations with unavailable bytes remain distinguishable from unknown locations. Status lives in the top-bar popover.

Validation and limits

The clean Windows Go suite passed 941 checks, with 48 expected skips and no failures, before the final narrow gesture, raster-policy and flow-note corrections. Targeted follow-up checks and seven affected browser suites passed. The final local Windows executable separately passed native content authorization and isolation, uncached recursive content without third-party cookies, image/audio/video wrappers, hostile-content responsiveness, saved choices, setup and shell checks. Real Bitcoin block maps, transaction navigation, the resizable split and the output-local tracker were checked separately from controlled content and picker fixtures. Linux build and static checks passed.

Numeric geometry checks compare the flow against pinned Mempool reference cases and ordered square placement against BitFeed reference cases. They do not establish full rendered pixel parity. The permanent CSS will-change hint was removed to let Chromium repaint at the current zoom; native sharpness and the reported feathering behavior still need user review because screenshot capture can force a repaint.

Fresh-install packages include a validated header snapshot; application-update packages omit it. Final release packaging, exact-file antivirus diagnostics, system installation, Linux CI for the final committed source, and hosted delivery are separate acceptance steps. Results for an earlier binary do not establish these checks for this pre-release. Windows executables are unsigned.

Gateway peerhood and later indexes remain gated. Inscription reveal evidence does not establish global numbering, current ownership, sat history or parent-child provenance. Content dependencies require known locations and available source bytes. The broader Details/Inspector reorganization remains a separate design proposal.

See the transaction tester guide, the acceptance record, status, known issues, privacy notes and the roadmap.

v0.7.2: Inscriptions

Gateway 0.7.2 — The Inscriptions Update

Scope

• An inscription content viewport within the timeline workspace, alongside Inspector and Explorer.
• Positional inscription resolution from a known Bitcoin block, using the same extraction handler as indexing.
• Lean inscription payloads containing compact positional coordinates; explicit Full mode for authenticated reveal records and bodies. Verification and coverage metadata remain separately committed.
• Shared groundwork for sparse transaction locators and scoped content dependency resolution, with transaction and Gateway peer stages gated.
• Related inscription locator controls in the Inscription inspector: optional enrichment during a build and a retroactive action. Both remain disabled in this first stage.
• Recovery when another process occupies the default Bitcoin serving port, with the actual port reported and explicitly configured addresses kept strict.

Staged capabilities

Headers, Blocks and Inscriptions are the enabled indexes in this source stage. Related inscription transaction locator construction and the complete Transaction Index will be enabled in the transaction stage. Gateway peer locator requests and public serving will be enabled in a later, separately validated peer stage.

Inscription reveal evidence does not establish global numbering, current ownership, sat history or parent-child provenance. Recursive and delegated content needs a known location for each referenced inscription; missing locations and unavailable block bytes must remain visible. Indexing positions alone does not recursively fetch referenced content.

Testing and limits

Use the inscription tester guide, known issues, privacy notes and roadmap. The exact Windows build passed 921 Go checks with 46 expected skips and no failures, native viewport/isolation checks, real Bitcoin positional lookup without a transaction index, and a local signed automatic upgrade from 0.7.1 with settings and all bundled headers preserved. The final installer and four app components had no threats reported by local Defender diagnostics with unchanged definitions. These checks do not establish hosted delivery, system installation, global identity evidence, or cloud/other-machine antivirus clearance. Linux CI passed build, tests, static checks, race, helper, packaging and browser checks. Windows executables remain unsigned. See this build's acceptance record.

Additional review checks

• Scrubbing the block playhead debounces Block Explorer loading. Inscription marker/address navigation loads the viewport separately; rapid changes must not let obsolete content replace the current selection.
• Explicit local Ord adapter answers remain provider-reported. They must not acquire native witness, selected-chain, numbering or ownership claims. Renderer fixtures and real Bitcoin reveal verification are separate checks.
• Use Inspect saved storage to compare Lean and Full records, retained source data and the separate content cache. The report counts encoded file bytes within its stated traversal/read limits, shows partial or unavailable results honestly, and must not fetch data or start indexing.
• Delegated preview content may follow its target; raw/download actions should preserve the requested inscription's own body.
• If the default Bitcoin serving port is busy, automatic fallback chooses a different available port when Gateway LAN discovery is inactive. An explicitly configured address remains strict.

v0.7.1: Timeline

Gateway 0.7.1 — Timeline workspace testing release

Gateway's Indexes page now provides a timeline workspace for exploring Bitcoin and preparing indexing ranges. Bitcoin Headers and Bitcoin Blocks remain the enabled indexes. Bitcoin Core is optional.

Downloads

• Windows installer — application and bundled header snapshot.
• Windows portable ZIP — extract the complete archive and start GatewayOnDemand.exe.
• Linux ZIP — application and bundled header snapshot.
• Checksums and artifact manifest.

Application-only ZIPs are update payloads. First-time testers should use the installer or a ZIP ending in -fresh.zip. The installer is a separate download, not contained in the portable ZIP.

What's changed

• A bottom-docked timeline with a resizable upper pane, default Headers and Blocks tracks, shared block-height ruler, and exact local coverage and gaps. Expanding details scrolls within its pane instead of pushing the timeline off screen.
• Custom scrollbar handles for zoom and track height, pointer-anchored wheel/pinch zoom, Space-drag panning, keyboard navigation, and halving/difficulty landmarks.
• Shift-click selects an inclusive range; Ctrl-click or Command-click toggles individual blocks. Separate ranges have their own editable markers. Selections prepare indexing intent; work still requires reviewing and explicitly starting a plan.
• An independent playhead follows the explored block across track changes. Scrubbing waits briefly before loading the settled block; direct block clicks load immediately.
• Inspector and Block Explorer tabs share the upper pane. Browse block evidence, paginated transactions, transaction inputs/outputs and value flow without leaving the timeline.
• A circled plus beneath the tracks adds available indexes. Removing a track preserves stored data and indexing jobs; the foundational Headers track cannot be removed.
• Previous output index zero now appears correctly in real transaction details and copied outpoints.

Filled Blocks coverage describes present local block files. Headers and completed processing alone do not establish possession of those block bodies. Additional derived indexes and Gateway-to-Gateway sharing remain locked.

Test and report

Use the timeline tester guide, Getting started, and the setup and browser QA checklist. Browser registration and .bitcoin address entry remain available. See known issues, privacy notes, roadmap, and bug reports.

Gateway checks block identity, commitments and selected-chain context; it does not replace Bitcoin Core's full script/UTXO consensus validation. This remains testing software.

Validation and updater status

The release source passed all Linux CI stages, including Go tests, vet, race, packaging and browser regressions. The full Windows Go suite passed 858 checks with 54 expected skips and no failures.

Live testing used ordinary Bitcoin peers with Bitcoin Core RPC and mounted files disabled. Headers synchronized beyond the bundled snapshot, and blocks 840000, 840001 and 850000 were fetched and retained as two separate coverage ranges. Native browser checks used no API mocks and exercised block 840000's 3,050 transactions, pagination, a known transaction, selection, delayed scrubbing and narrow layout. Browsing did not start indexing jobs, and headers and blocks survived restart.

The exact final installer and four Windows app components passed local Defender scans with protection active and definitions unchanged. Windows executables remain unsigned. Windows may show an unknown-publisher or reputation warning; antivirus and download-protection results can vary. No universal antivirus clearance is claimed. If a file is flagged, stop that check and report the exact filename and alert; do not disable protection to complete testing.

The existing signed update channel and installer update choices remain supported. Current delivery acceptance is recorded in release status. The approved-release renewal workflow refreshes signed metadata without automatically choosing a new application release.

Gateway's own code uses the MIT license; third-party notices are included in the downloads.

v0.7.0: Blocks

Gateway v0.7.0: Blocks (Public testing release)

Gateway retrieves Bitcoin blocks on demand and lets you explore their transactions, inputs, outputs and positions. Bitcoin Core is optional. This is the first release prepared for public testing from the new Gateway repository.

Downloads

• Windows installer — application and bundled header snapshot.
• Windows portable ZIP — extract the complete archive and start GatewayOnDemand.exe.
• Linux ZIP — application and bundled header snapshot.
• Checksums and artifact manifest.

The application-only ZIPs are update payloads. First-time testers should use the installer or a ZIP ending in -fresh.zip. The installer is a separate download, not contained in the portable ZIP.

Available now

Headers and Bitcoin Blocks; the block explorer and schema; transactions within known blocks; indexing jobs within the enabled scope; optional read-only Bitcoin Core and mounted block sources; ordinary Bitcoin peer serving; peer aliases; private-cache controls; Windows browser integration and .bitcoin address entry.

The installer has a dedicated Updates page. Choose automatic checks, explicitly opt into automatic download and installation, or select manual updates. Advanced source settings remain available. Additional indexes and Gateway-to-Gateway sharing are visibly locked until separately promoted.

Test and report

Start with Getting started and the QA tester guide, including browser registration and address entry. See the roadmap, known issues, privacy notes and bug reports.

Gateway verifies blocks and chain context; it does not replace Bitcoin Core's full script/UTXO consensus validation. This is testing software.

Validation and updater status

The final runtime source passed all Linux CI stages, including race checks and browser tests. Windows checks, final binary/payload audits and a native automatic update-and-restart fixture passed, including tamper rejection and preservation of settings and headers. The acceptance record distinguishes each test's scope.

The exact installer and four Windows app components passed local Defender scans without changing definitions or protection settings. Windows executables remain unsigned; local scan results do not guarantee acceptance by other machines, cloud scanners or download protection.

The public hosted updater passed an automatic download, installation and restart with settings and headers preserved. A fresh installation configured the public channel and checked both signed feeds without manual source setup. Independent HTTPS checks verified both app packages and all 97 header chunks.

Gateway uses its bundled verification key and public update address; users need no GitHub account or download credential. The approved-release renewal workflow is configured to refresh signed metadata weekly. See the current operations status for live renewal validation and maintenance records.

Gateway's own code uses the MIT license; third-party notices are included in the downloads.