Public build log

RTC Viewer build log

This is the public record of website and product-information updates that matter to customers. Private security details and unfinished internal work are not included.

Legal entity
Real Time Crypto LLC
Location
Salt Lake City, Utah, USA
Last updated
August 30, 2026

The release targets were updated

Status: Public planning update

What changed

  • RTC 5 Core is now described as targeting late 2026 rather than a guaranteed month.
  • RTC 4.3 Mini remains planned after Core, with December 2026 identified as the earliest target.
  • RTC 7 Pro remains in development with its release date to be announced.

Release timing remains subject to final device validation, stability testing, and production readiness. These are planning targets, not guaranteed release, shipping, or delivery dates.

The website now focuses on RTC 5 Core

Status: Website update

What changed

  • The homepage now focuses on RTC 5 Core and links directly to its product details, display demo, and updates.
  • RTC 4.3 Mini and RTC 7 Pro remain visible as compact future-release previews with their detailed model pages preserved.
  • At that point, the public targets were November 2026 for Core, December 2026 for Mini, and TBA for Pro. The August 30 entry above records the later timing update.

Core can save five four-card sets

Status: Confirmed feature update

What changed

  • RTC 5 Core can save five separate four-card sets, with up to 20 coin selections in total.
  • Four cards remain visible at once; changing sets recalls another saved group.
  • The homepage, Core model page, comparison, disclosures, and controlled product records now use the same wording.

This is a confirmed development capability. Final production controls and release behavior will still be verified before sale.

The public build log was added

Status: Public accountability update

  • A dated public record was added for completed website and customer-facing product-documentation milestones.
  • The journal separates confirmed work from planned details and unfinished production verification.
  • Private security evidence, access information, and unreleased implementation details remain outside the public record.

Website dependency checks were tightened

Status: Website maintenance and security update

  • Production and build dependencies were pinned to reviewed versions instead of open-ended version ranges.
  • Clean-install, build, test, and dependency-audit checks were kept together as one release gate.
  • These checks make the website build more consistent while keeping private security and operating details off the public site.

Search information was corrected for the current development stage

Status: Public site update

What changed

  • Sale-ready product markup was removed while orders, public pricing, and customer reviews remain unavailable.
  • Search engines can still understand RTC Viewer, Real Time Crypto LLC, and the three-model development lineup without invented commerce data.
  • No placeholder offer, price, rating, or review information was added just to qualify for a richer search result.

RTC Viewer is easier to find and understand

Status: Public site update

  • The homepage now describes RTC Viewer directly as real-time crypto price display hardware.
  • A dedicated “What Is RTC Viewer?” page was added for people and search systems finding the project for the first time.
  • Company, brand, product-family, and model naming were aligned across public descriptions and page metadata.
  • Public page links, descriptions, canonical addresses, and the sitemap were checked together.

The goal was simple: someone should not need to know the project already to understand what it is.

Product details were checked across the site

Status: Public documentation review

  • Model pages, the comparison, FAQs, support copy, and public disclosures were checked against the approved product record.
  • Superseded dates, feature counts, and unsupported wording were removed or corrected.
  • The site now states plainly that RTC does not offer tokens, investments, or investment advice.
  • Official purchase information is reserved for this website when sales actually open.

The mobile layout was fixed

Status: Public experience update

  • The model comparison was rebuilt as a phone-first, vertical sequence instead of a wide desktop panel forced into a narrow screen.
  • Small section labels were enlarged, a long FAQ answer was shortened, and preview disclaimers were allowed to wrap cleanly.
  • Extra horizontal space and uneven model-panel heights were tightened across mobile and desktop layouts.
  • Public model descriptions were reconciled with the latest owner-confirmed display and layout facts.

Support and customer information were added

Status: Public documentation update

  • Support, privacy, accessibility, security, official-channel, and product-disclosure information was added or expanded.
  • Public feature statements adopted consistent labels for confirmed, planned, not included, and still-to-be-announced details.
  • Planning targets were updated while remaining clearly identified as targets rather than guaranteed shipping dates.
  • Mobile overflow and long-form disclaimer layouts received a dedicated cleanup pass.

Company and contact details were added

Status: Company information update

  • Real Time Crypto LLC, founder Brennan Andrews, official domains, contact email, and Utah business verification were connected in one public record.
  • The RTC logo and brand lockup were added across the site.
  • The site now links directly to model guides, company verification, contact information, and confirmed-email updates.
  • Use-case illustrations added context without presenting unfinished hardware as final product photography.

The first public RTC Viewer site went live

Status: Initial public release

  • The public site established the RTC Viewer model family and the roles of RTC Mini (4.3), RTC Core (5), and RTC Pro (7).
  • Illustrative device concepts were introduced as placeholders, not final product photography.
  • The launch message, model comparison, contact information, and educational-use disclosures were included in the first public version of the site.

What belongs in this log

This is a public build log, not a raw engineering diary. Entries describe customer-relevant work that has already reached the public site or its approved product record. Private security details, access information, internal locations, unreleased implementation notes, and speculative claims are intentionally excluded.

Confirmed development scope still requires release verification. Planned details may change. Concept renderings and development interfaces are not final product photographs.

Next public checkpoint

The next meaningful entry will follow approved final-product photography, a release-verified specification, another material model-scope change, an updated public target, or the opening of official sales.

Questions or corrections

Questions about this record, or a correction supported by evidence, may be sent to Real Time Crypto LLC at Creator@rtcrealtimecrypto.com.