Skip to content
HEY Research Lab
Menu

AegisClear

Payments

Is this your project? Claim it →

AegisClear — SLA-backed payment channels for x402/USDG on Robinhood Chain: proportional ZK (Groth16) settlement with private terms & metrics

What HEY knows

Development

Last shipped 42 days agoActive: 0 counted ships in 30 days; latest ship 42 days ago. Evidence Source

Build Momentum 12How it is measured

Latest: Code changes, week of 2026-09-21 – 2026-09-27 · 12 commits

Token

No token tracked
FollowCreate alertTerminal preview
Get updates

Get updates

Follow puts AegisClear on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

Sign in to follow AegisClear

No account? Email me AegisClear’s changes

No account and no password. HEY stores the address and what you asked for, sends one confirmation, and nothing else until you confirm. Every email has a one-click unsubscribe that deletes the address.

Or read its RSS feed.

View latest ship
Share
More detail
Not yet known
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record.
Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Active.
“Active” by the activity rule's longer window: 2 counted ships in the last 45 days (the rule needs at least 2); the newest, 2026-09-23, is more than 30 days old.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-09-21 – 2026-09-27 · 12 commitsCode changes, week of 2026-09-14 – 2026-09-20 · at least 100 commitsv0.1.0-zkey — Groth16 proving key (single-contributor setup)What HEY derivedHEY’s activity rule reads the counted events as “Active”.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Verified Builder.
The quality gate found counted building from the project's own sources.
Source1 registered source, 0 of them context only.ReadRecordsCode changes, week of 2026-09-21 – 2026-09-27 · 12 commitsCode changes, week of 2026-09-14 – 2026-09-20 · at least 100 commitsv0.1.0-zkey — Groth16 proving key (single-contributor setup)+1 moreWhat HEY derivedThe quality gate’s stored decision: “Verified Builder”.Not concludedA verified builder is one whose shipping HEY confirmed from public evidence. It does not say who runs the project — that is the ownership claim, a separate check.
Research coverage: HEY can answer 7 of the 10 research questions that apply.
7 of 10 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 45d ago.

Building

  • Building activityMeasuredRead 15h ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 46d ago.
  • TimelineMeasured

Official site

  • Official docsNo sourceNo official website on record.
  • API descriptionNo sourceNo official website on record.
  • Official site changesNo sourceNo official website on record.

Code and packages

  • Repository detailsMeasuredRead 5h ago.
  • Published packagesMeasuredRead 5h ago.

Not applicable here: Package advisories, Contract creation, Contract activity, Published source code, Contract interface, Current market, Market history, Supply distribution, Locks, Market checks, Protocol economics.

A count of what HEY has read, never a score: projects are not compared or ordered by it. Unknown is never zero. The same states: coverage API.

Market figures are context only and never change activity status. Methodology
LinksGitHub (opens in a new tab)Sources

Latest ship

Checked

Code changes, week of 2026-09-21 – 2026-09-27 · 12 commits

Code activitySource-backed

Why it matters: One of a run of ships in the 30 days to it: building continued, not a one-off.

What changed, in the repository’s own words:

1 active day in mdlog/aegisclear.

This week HEY looked inside 3 of 12 commits to see what changed: 1 changed code, 2 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there.

Record ship:d2d8a200… · HEY counts it as building; it does not judge the release’s quality.

View evidence ↗ (opens in a new tab)

Shared change · Verified Builder

AegisClear is now a Verified Builder: HEY checked its builder sources.

Builder status: Active.

Observed by HEY on 2026-09-20Source: HEY Signal

View evidence ↗Evidence receipt

Builder activity

Bars: meaningful, source-backed ships per week (count). Weeks run Monday to Sunday, UTC, labelled by their Monday. Commits are aggregated, a code week counted once. Hatched: 4 weeks before HEY began reading this project’s sources — not yet read, not zero.

Build timeline

A code week counts as building when a commit HEY looked inside changed code; one is enough, so HEY stops there.

  1. Code changes, week of 2026-09-14 – 2026-09-20 · at least 100 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    at least 2 active days in mdlog/aegisclear since 2026-09-19; the count stops at the newest 100 commits listed.

    How HEY read this week

    This week HEY looked inside 6 of 88 commits to see what changed: 3 changed code, 3 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count.

    View evidence: Code changes, week of 2026-09-14 – 2026-09-20 · at least 100 commits (opens in a new tab)

  2. v0.1.0-zkey — Groth16 proving key (single-contributor setup)

    GitHub releaseSource-backed

    v0.1.0-zkey — Groth16 proving key for sla_settlement.circom Artefak trusted setup satu kontributor (hackathon; lihat spec §9.4 / T4 — bukan ceremony multi-pihak, jangan pakai untuk produksi tanpa ceremony ulang). Berkas ini tidak bisa dibangkitkan ulang secara identik dari… Show all

    v0.1.0-zkey — Groth16 proving key for sla_settlement.circom Artefak trusted setup satu kontributor (hackathon; lihat spec §9.4 / T4 — bukan ceremony multi-pihak, jangan pakai untuk produksi tanpa ceremony ulang). Berkas ini tidak bisa dibangkitkan ulang secara identik dari circuits/scripts/setup.sh karena kontribusi menarik entropi dari /dev/urandom; karena itu didistribusikan di sini. | Berkas | Isi | |---|---| | sla_final.zkey (100.834.787 B) | proving key phase-2 final (1 kontribusi + beacon) | | verification_key.json | vkey yang diekspor dari zkey — identik dengan…

    View evidence: v0.1.0-zkey — Groth16 proving key (single-contributor setup) (opens in a new tab)

Other changes on HEY’s record

5 changes on HEY’s record for AegisClear: 1 release · 1 new Verified Builder or owner proof · 1 build pace change · 2 weeks of code pushed.

All 5 changes for AegisClear →

The full change record holds 3 more, of kinds this list leaves out — new locks, unlock reminders and HEY’s own research bookkeeping among them. Full record (JSON)

Sources

1 place HEY reads for AegisClear