Skip to content

Releases: Dimkox/liqvera

Liqvera v0.0.5

Choose a tag to compare

@Dimkox Dimkox released this 01 Oct 02:41

Liqvera v0.0.5 — fresh quote browser rendering hotfix

v0.0.5 is a source hotfix release for the public Buildathon demo at
https://liqvera.site. It preserves the separately published Linux installer
at v0.0.2; no v0.0.5 installer is included.

What changed

  • Fresh live quote and paid-delivery timestamps now use the same
    standards-safe UTC formatter as the historical preview.
  • The removed duplicate formatter combined ECMA-402 dateStyle, timeStyle,
    and timeZoneName, which throws in Chromium and Node when a valid fresh
    quote reaches the browser.
  • Regression coverage exercises the real platform Intl implementation and
    prevents the forbidden option combination from returning.

Live validation

The web hotfix behavior commit
f34464521e85a2798a51a00c2d33cba60e809fbf was deployed by rebuilding and
recreating only web-live. Gateway, PostgreSQL, signed grant authority,
reservation budgets, and payment state were not changed.

A public headless Chrome smoke discovered an EIP-6963 provider, connected on
Mezo Testnet chain 31611, and created fresh live-public request
dc776db0-ecd9-4d46-8852-0d1fffde0f03 / quote
a9c8de9b-9cb9-4a63-b2ae-c41e1ca0f799. Snapshot and quote-expiry timestamps
rendered with no runtime or console exception. The smoke stopped before the
payment button: no signature, settlement submission, retry, or new payment was
performed.

Publication source commit:
19284fb07fedd4909672c7e9a641cb066efbb7cc.

Boundaries

  • Mezo Testnet funds only; no mainnet payment or real-fund claim.
  • No exchange mutation, trading, custody, withdrawal, or private venue access.
  • The public report is evidence of a captured order-book snapshot, not an
    execution promise or financial advice.
  • The installable operator package remains v0.0.2 and its assets are unchanged.
  • Overall F7 acceptance remains INCOMPLETE across the full A01–A30 matrix.

Liqvera v0.0.4

Choose a tag to compare

@Dimkox Dimkox released this 01 Oct 02:00

Liqvera v0.0.4 — verifiable live reports and signed testnet demo

v0.0.4 is a source and evidence release for the public Buildathon demo at
https://liqvera.site. It preserves the separately published Linux installer
at v0.0.2; no v0.0.4 installer is included.

What changed

  • Public Hyperliquid BTC perpetual snapshots can be sealed into a report and
    independently verified evidence ZIP. Source failure remains fail-closed;
    there is no fixture fallback in the live flow.
  • The browser includes a wallet-free, integrity-checked historical live report
    preview and ZIP download.
  • Injected EVM wallets are discovered through EIP-6963, with a legacy fallback,
    and are switched or added to Mezo Testnet chain 31611.
  • Mezo Testnet payment uses exact 0.01 test MUSD Permit2/EIP-2612 sponsored
    x402 terms. Default startup remains grant-required and fail-closed.
  • A release-pinned Ed25519 issuer can authorize a strictly bounded signed-v2
    public-demo policy. Durable count, total-amount, and one-per-payer reservations
    are append-only; UNKNOWN outcomes remain reconcile-only and are never retried.

Acceptance evidence

The deployed runtime was exact commit
dcdc7ae6086007d1ccaab8bc563c137c0e099feb. Its final paid acceptance used
one encrypted-signer submission for report
c956cd81-5ec2-439b-909b-4a9d8474cce3 and transaction
0x4a04dc72c9f4b9051262b5c14db18369b9140d3012f7b02c3c8d3c6952778455.
The delivered receipt recorded 23 confirmations and zero buyer native-gas
spend. JSON and ZIP delivery returned HTTP 200, and the exact ZIP passed the
repository offline verifier.

Publication source commit:
b4461ea3e3385f8bbeaa94194db57e89f3a97a23.

Boundaries

  • Mezo Testnet funds only; no mainnet payment or real-fund claim.
  • No exchange mutation, trading, custody, withdrawal, or private venue access.
  • The public report is evidence of a captured order-book snapshot, not an
    execution promise or financial advice.
  • The installable operator package remains v0.0.2 and its assets are unchanged.
  • Overall F7 acceptance remains INCOMPLETE across the full A01–A30 matrix; this
    release does not relabel NOT_RUN cases as passing.

Liqvera v0.0.3 — live report and automated testnet demo

Choose a tag to compare

@Dimkox Dimkox released this 30 Sep 22:48

Liqvera v0.0.3 — live report and automated testnet demo

v0.0.3 records the Buildathon MVP's live-public Hyperliquid report path and
three newly confirmed automated Mezo Testnet payments. It is an evidence and
source milestone; the checksum-bound Linux installer remains v0.0.2.

Added evidence

  • Live public BTC perpetual snapshot report
    820df2f8-5bd6-41ad-a94d-98b5078f4d64, report SHA-256
    770ba84eeaaec8d1092c9179c2079cebbe891b128b448e722e4367dee87eed9b,
    bundle SHA-256
    92fa784431cf92848dbdb8033b111367fb8d624c70906c1cd0c5cc94a1a5d527.
  • Three new payments of 0.01 test MUSD on Mezo Testnet:
    0x1ca6255bfd83de27feaafd805e27a4dae535e6c5d832be0c875e997dba2b181e,
    0x19304292f6a08d1061c4cf3e83d506f67ca0f7b88d67220c45d376c362b335a8,
    and 0xdab835ad81cd66b56911d6dd4b389ecf2c383e067ba9c52bbf293427eb113c23.
  • Every payment reached at least twelve canonical confirmations and recorded
    zero buyer native-gas spend. A client-side timeout that had settled on-chain
    was recovered confirm-only from its canonical MUSD Transfer log.

No mainnet payment, exchange mutation, custody action, or deployment occurred.
The public evidence asset contains identifiers and hashes only; wallet material,
signatures, grants, passwords, and database credentials are excluded.

Liqvera v0.0.2 — Linux installer

Choose a tag to compare

@Dimkox Dimkox released this 30 Sep 18:06

Liqvera v0.0.2 — draft release notes

This follow-up candidate adds exact A07 live-public evidence to the retained
v0.0.1 payment and anonymous-publication evidence.

Linux installer

v0.0.2 adds a checksum-bound Linux-only installer for Ubuntu 22.04, Ubuntu
24.04, Debian 12, Fedora 40, Fedora 41, and RHEL 9 on amd64/arm64. It requires Bash
5.2, Python 3.9+ (standard library only), Docker Engine 27, Compose v2.30,
4 GiB free disk, and 2 GiB memory. The
archive is deterministic, contains exact migrations 001–005 and six
digest-pinned Docker Hub images, and is independently verified before any
member executes. Two builds from the final subject and both verifier results
must match before publication.

Installation starts only shadow mode on loopback with payment disabled. It
stores no wallet, payment grant, signature, database password, or service token;
only private secret-file references are accepted. Default uninstall preserves
data. Purge needs an exact preview token. Production update and rollback are
fail-closed because the shipped adapter has no coherent backup or database
ledger implementation; operators must reinstall the exact verified release or
apply a separately reviewed forward repair.

The checked-in acceptance harness covers the supported matrix with mocked host
facts, checksum and inventory rejection, reinstall, occupied-port failure,
systemd/Compose selection, update recovery, rollback and purge contracts. That
is contract evidence, not a real clean-host Docker run. Isolated clean-host
acceptance remains NOT_RUN; the release must not claim it as PASS.

Evidence added

  • A07 passed with canonical SOURCE_UNAVAILABLE, no fixture fallback, and no
    artifact emitted.
  • A13/A14 retain one confirmed 0.01 test-MUSD settlement with zero buyer native
    gas and no replay settlement.
  • A29 retains the credential-disabled anonymous recursive-clone proof from the
    published v0.0.1 release.

The combined sealed per-case projection has 9 PASS, 21 NOT_RUN, zero
BLOCKED_EXTERNAL, and zero FAIL. It remains INCOMPLETE and is not a single runner overall PASS. Component versions remain unchanged at 0.1.0 (root
workspace metadata 0.1.0.dev0); only the Liqvera product VERSION advances to
0.0.2.

No v0.0.2 tag, push, or GitHub Release has been created. Final artifact evidence
binds release commit 70141b662ff949c7d06e7801143e29ae14d253be, tree
1ede66694689d38e68b61560d67cd7a1dd614838, archive SHA-256
04e1cbc7b537be85addb1dd174fea2974f145685e782e589725b639cbc907b82
(42,226 bytes), and inner inventory
4c912e694b8ee1f44c5dd0c1b31a33fc3906e16d9c6295ac20688c4e4e0fba23.
Two builds were byte-identical and both independently materialized 25 files.
The detached checksum, bootstrap, bootstrap checksum, and verifier hashes are
recorded in the release artifact manifest. All five Liqvera images use
anonymous Docker Hub refs with unchanged multiarch index digests; PostgreSQL is
the pinned official multiarch digest. Assets remain NOT_PUBLISHED pending
exact-fingerprint independent reviews.

Liqvera v0.0.1 — Market reports you can verify

Choose a tag to compare

@Dimkox Dimkox released this 29 Sep 20:21

Liqvera v0.0.1

Liqvera produces market reports whose source data and deterministic analysis can be verified offline.

This release adds the fail-closed Mezo Testnet x402 payment boundary using Permit2 with EIP-2612 gas sponsorship, durable one-shot settlement consumption, 12-block receipt finality, and the A01–A30 acceptance evidence workflow.

Verified evidence:

  • A13 paid access and A14 replay passed on Mezo Testnet with one settlement of 0.01 test MUSD, the same transaction for both cases, 50 observed confirmations, and zero buyer native-gas spend.
  • Transaction: https://explorer.test.mezo.org/tx/0xfb5ab4a116966204dcece95a7ff099f53494074d84584ad072e140ff25453c06
  • The corrected offline candidate passed A01, A08, A09, A27, and A30 with zero FAIL rows.
  • Final source commit: a0fd5f0884a3fd1a6663982ea5df387b47528bdd.
  • Final source tree: 8759823e6b077d7e52017a79bb12215abc103099.

Explicit limitations:

  • The offline acceptance result remains INCOMPLETE: 5 PASS, 4 BLOCKED_EXTERNAL, 21 NOT_RUN, 0 FAIL.
  • The retained full live run is overall FAIL because A08/A09 were initially invoked with the wrong Python interpreter. Only its sealed A13/A14 PASS evidence is accepted; the runner defect is fixed in this release.
  • No mainnet, custody, exchange mutation, private venue access, or investment-performance promise is included.
  • Product version is 0.0.1. Inherited component package versions remain 0.1.0 and the root workspace metadata remains 0.1.0.dev0.