Fictional specimen · Project Aster · exact delivery format · no live client data
Skip to report

Public screen — public sources only: does this opportunity warrant private diligence?

Recommendation

Advance

ADVANCE decision · open private verification

Go to screening decision
Public sources only · Decision screen

A credible public footprint.
A private record worth testing.

Project Aster · fictional specimen   /   Public-source screen

A dated external-evidence screen that decides whether this under-the-radar digital-settlement opportunity warrants private investment diligence.

Decision use
Whether to incur private-diligence cost
Recommendation
Advance
Evidence
Six public-source groups
Cutoff 14 September 2026
Prepared for / by
Commissioning investor
Luis Fontana · Mjolnir Capital

Confidential report simulation. Project Aster is fully fictional; every entity, person, source and figure is synthetic. The analytical form, evidence treatment and decision language match the intended client deliverable. Informational only — not an offer or solicitation. The commissioning investor retains the final decision.

Screening decision

Public-source screen · Advance

Advance to private verification; no public finding defeats the thesis.

The external record supports a live non-custodial settlement product, active development, valid corporate standing and named integrations. Public evidence cannot establish revenue quality, customer retention, ownership, cash, instrument rights or token controls. Those questions define the private workplan.

Decision
Advance
Open the private evidence room.
Public sources
6
Registry, product, partner, code, adverse-media and chain checks.
Material public flags
0
No critical adverse public finding at the 14 September 2026 cutoff.
Screening boundary. “Advance” means the opportunity warrants private diligence. It is not an investment approval and does not verify company-controlled public claims.

Public findings

The screen distinguishes what is observable from what only private records can prove.

Supported

A real product and current development footprint are observable.

Documentation, status history, tagged SDK releases and testnet deployments are mutually consistent. This supports product existence and ongoing technical work, but not production economics.

Supported

The company is active and the visible leadership record is coherent.

The registry shows a current company and directors consistent with the product record. No material sanctions, fraud or litigation match was identified in the scoped searches.

Partly supported

Five named relationships are corroborated; deployment status varies.

Partner-controlled sources confirm five named relationships. Two are explicitly pilots, so the screen does not count all announcements as paying production customers.

Not observable

Commercial quality remains a private-evidence question.

Public material gives no reliable population for transaction volume, recognized revenue, retention, pricing realization, concentration, refunds or settlement losses.

Not live

AQY is described but no live token or principal market exists.

No deployed AQY token is observed. Token price, liquidity and treasury value are therefore excluded from the screen and from the later base investment case.

Commercial context

Why it merits diligence

The product addresses stablecoin settlement operations for regional exporters and payment providers. The visible integrations and developer activity create a credible route to evidence, while the private record can test whether usage converts into durable revenue.

What the screen does not prove

It does not verify customer status, notional volume, take rate, revenue recognition, retention, security, licensing, custody, ownership, financing rights or the proposed token allocation.

Private-diligence handoff

PriorityQuestionClosure evidence
CriticalDo volume, invoices and cash reconcile?Processor population → customer contract → invoice → ledger → bank receipt for one complete quarter.
CriticalWhat does the investor own?Current cap table, board authority, final SAFT+T, token entitlement, dilution and amendment rights.
CriticalIs the product genuinely non-custodial?Architecture, wallet roles, production permissions, audit, incident log and processor confirmations.
ImportantAre retention and concentration acceptable?Dated cohort exports, customer-level billing and independent reference calls.
ImportantCan the plan survive without token liquidity?Monthly operating model, cash/liability bridge, approved budget and equity-only returns.

Recommended private scope: commercial reconciliation, financial and valuation re-performance, ownership and rights, token supply and custody, security, compliance, governance and targeted fraud tests.

Sources, method and limitations

PS01
Corporate registry extract

Entity status, directors and filing currency checked 14 September 2026.

PS02
Product documentation and status page

Non-custodial settlement architecture, supported corridors and incident history.

PS03
Published integration repositories

SDK activity, license and tagged release history.

PS04
Named partner announcements

Five relationships cross-checked to partner-controlled pages; two described as pilots.

PS05
Sanctions and adverse-media searches

Company, founders, directors and named affiliates; no material match identified.

PS06
Public chain and contract records

Testnet deployments and administrative addresses; no live AQY token observed.

Package control. Case ASTER-20260914 · version 1.2 · evidence cutoff 14 September 2026 · public-source subset of manifest SHA-256 fd4272efe1c5efdea3974525447809d95b6c7b8f720412a57f4418d366ff06ce.

No management interview or private document was used in this screen. Search results are time-bound and may omit sealed proceedings, private disputes, undisclosed affiliations or non-indexed records. The subsequent verification memorandum uses a separate private evidence set.