RELVYK / METHOD & DOCS

How a read becomes
a traceable reflex.

RELVYK is a verifiable reflex engine for Solana. It reads public chain information, follows a predefined processing route, checks the returned data and saves the observation in your browser.

It uses deterministic parsing and rules. It does not call a language model, learn new code from a record, operate a global network, or send funds. The mechanical assemblies express the same task state shown in the workbench.

The six assemblies reuse the original engineering illustration. Rotation was not part of that SVG model. Explode, assemble, keyboard selection and reset operate on its existing geometry. The separate mechanical engine study is an illustration; its ignition is not a chain operation.

What “verified” means here.

A check can be Checked, a Finding, or Unknown. Each includes a finding, an evidence path and a limitation. A check describes what a defined rule could establish from the returned data.

These results are not a security audit, an investment recommendation, a guarantee or an on-chain proof. A parsed failed transaction can be a completed inspection while the chain execution itself remains failed. Missing permissions, balances, logs or metadata are never replaced with zero or a successful result.

The workbench separates the current task status, selected assembly, chain execution status, finality and saved observation. A selected historical stage is an inspection view; it does not claim that the stage is currently running.

Transaction Inspector.

A transaction signature must decode from base58 to 64 bytes. The reader requests getTransaction at confirmed commitment with jsonParsed encoding and maxSupportedTransactionVersion: 1. It also requests signature status to display observed finality separately. Legacy, v0 and v1 messages are supported; unsupported versions produce an explicit error.

For v0, the account list includes versioned lookup accounts in wire order. Version 1 carries its complete account list directly, without address lookup tables. Its signed transactionConfig is shown when returned: compute limit, heap size, loaded-account data limit and total priority fee in lamports. Missing configuration remains unknown; no per-compute-unit fee or ComputeBudget-derived configuration is invented. Top-level and returned internal instructions retain their program IDs, parsed details or original unparsed payloads. No unknown protocol is guessed. Signer addresses are observable; the human or service controlling them is not independently identified.

SOL and Token balance differences use exact integer arithmetic and decimal formatting. JSON integers too large for safe JavaScript numbers remain decimal strings. Fees, rent, created or closed accounts and wrapped SOL affect balances. Changes are not classified as Buy/Sell or investment profit.

A null transaction response means that this source did not return the transaction at the requested commitment. It may be on another network, unconfirmed or outside retained history. It does not prove that the transaction never existed. Official getTransaction reference ↗

Token Anatomy.

The account must be owned by the original Token Program or Token-2022 and the RPC parser must identify it as an initialized Mint. Wallet and Token Account addresses remain findings, rather than fabricated Mint details.

Supply and decimals, Mint Authority and Freeze Authority are read from returned Mint fields. Authorities have three states: present, revoked, or unknown. An unavailable field is never treated as revoked.

For Token-2022, a bounded binary read inventories extension IDs and cross-checks base fields. RPC-parsed extension states are shown alongside unparsed IDs. Coverage limits remain visible. This reader does not verify every extension's semantics, transfer hooks, confidential balances, fee policy or metadata authenticity.

On-account Token-2022 metadata is displayed as untrusted text. External metadata URLs are not fetched or rendered as HTML; names unavailable in the returned account stay unavailable. There are no invented prices or market statistics. Official Token/Mint concepts ↗ · Token extensions ↗

Account snapshots.

A capture reads public SOL balance and Token Accounts for both Token Programs. Balances are aggregated by Mint and program. The record includes timestamps, available context slots, read interval, truncation and failure limits. These independent RPC reads are not an atomic portfolio snapshot.

The first capture creates a baseline. A later capture for the same address and network compares two saved observations. It never reconstructs an arbitrary historical balance. A missing program response or truncated account set remains incomplete; an unknown balance cannot silently become zero.

Snapshot differences are observed balance changes, not investment returns. This scope does not claim to include all staking positions, protocol deposits, compressed assets or off-chain holdings. Deleting a run also removes the snapshot it captured. Previously exported or self-contained historical comparisons are unaffected. Official owner account query ↗

Versioned workflows, not new intelligence.

The library contains three executable routes: Inspect Transaction, Inspect Mint Controls, and Compare Account Snapshots. Their schemas, steps and checks can be expanded. A parameterized copy stores an input and network alongside an existing route; arbitrary text is never evaluated as code.

Execution counts are computed from actual saved reads for that template and version. Replaying a record does not read the chain, create a transaction, or increment its count. Deleting local records removes their contribution to the local count. A new template version does not automatically inherit old results.

Sources, timestamps and local records.

Queries pass through a same-origin read-only RPC Function. Its network and method whitelist excludes transaction submission. Inputs, response size, retries and timeout are bounded. Endpoint credentials remain server-side; the browser receives a source label, observation time and cache provenance.

Public Solana endpoints are used when no server RPC is configured. Public endpoints can be rate-limited or decline reads. A query failure preserves the input, error category and a retry action. The service never fills an unavailable response with sample data.

Short response caches preserve the original observation time and expose cache age. Per-instance caches and rate controls are bounded best-effort protections, not global quotas or durable shared storage.

Saved in this browser. IndexedDB stores run records, snapshots and parameterized workflows. These records are neither globally shared nor stored on-chain. If browser persistence is unavailable, the interface explicitly switches to page-session memory and offers JSON export. Clearing browser data removes local history. No public share link or cloud workspace is claimed.

Every displayed time uses UTC. Result exports safely serialize integer strings, inputs, source references, stage records and checks. Export is an explicit local download; task histories are not uploaded to a shared service.

Connect, read, authenticate.

Wallets are discovered through Wallet Standard and listed only when a real compatible provider registers in your browser. Connecting shares a public address. Accounts and network capabilities update when the provider changes them.

Public transaction, Mint and snapshot queries do not need a wallet, message signature or asset approval. RELVYK does not request seed phrases, private keys, transfers, approvals or transaction signatures. A rejected connection leaves the read-only experience available.

No private cloud workspace is exposed. Authentication would require a separate server-issued one-time nonce, verified domain, address, expiry and signature; a frontend success flag is not authentication. Official message and authentication guidance ↗

Project token configuration.

Basic inspections and public workflows are open without holding a project token. The project Mint, ticker, trading URL and holder thresholds are intentionally not inferred from the reference website. There is no unconfirmed contract address or buying entry in the interface.

A confirmed project Mint can enable explicit account-scoped page-session observations through the configuration. At most three selected public accounts are checked for recent signatures; observed data must actually match the Mint. Events retain per-instruction identity, cursors, deduplication and observed finality. Closing the page stops this observation. It is not an all-wallet, all-pool or continuous background service.

Holder access is disabled by default. No token distribution, supply, lock schedule, returns, dividend, tax, buyback or burning mechanism is promised. Project token privileges would be separate from Solana network fees. This application sends no transaction and therefore does not ask you to pay a chain transaction fee.

Mechanical source & licenses.

The mechanical illustrations and interactive geometry are adapted from the original MIT-licensed mechanical study and Anatomy drawing kit. Their geometry and retained animation code keep their original authorship and licensing. Brand and product changes do not remove third-party ownership notices.

Original MIT-licensed mechanical study · Anatomy drawing kit MIT license. The Solana query, task, local evidence and wallet modules in this project are independently implemented for this interface.