Is gloam still being built?

Shipping: 7 meaningful events in 30 days; latest ship today.

What did gloam ship last?

Code changes this week (since Mon 19 Oct) · 1 commit — Code activity, today.

What does HEY not know about gloam?

2 gaps: Published packages (not enough yet), API description (no source). Packages name its repository, but none is confirmed as the project’s own.

gloam

No narrative yet

HEY verified shipping evidence from the project’s own public sources; ownership of this page is not claimed yet.

Is this your project? Claim and verify →

Trade and Move Money Privately on Robinhood Chain

What HEY knows

Building: Shipping consistentlyShipping: 7 meaningful events in 30 days; latest ship today. Evidence Source
Build Momentum 75How it is measured
Latest ship: Code changes this week (since Mon 19 Oct) · 1 commit · 3h ago · Code activity
Why it matters: One of 7 meaningful events in the last 30 days: building continued, not a one-off.

FollowCreate alert Terminal previewView latest ship

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

No account? Email me gloam’s changes

Or read its RSS feed.

Token market · context: No token tracked
Not yet known: Unknown2 gaps: Published packages (not enough yet), API description (no source). Packages name its repository, but none is confirmed as the project’s own.
HEY can answer 8 of the 10 research questions that apply · Research coverage

Compare with…The same summary, with every line’s evidence: snapshot API

What HEY checked — why it says this

Shipping.: “Shipping” by the activity rule: 7 meaningful events in the last 30 days, the newest 2026-10-19.; SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.Read2h agoRecordsCode changes this week (since Mon 19 Oct) · 1 commit Code changes, week of 2026-10-12 – 2026-10-18 · 64 commits Trusted setup: final keys+2 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Shipping”.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 verified building evidence from the project's own sources.; Source18 registered sources, 0 of them context only.Read1mo agoRecordsCode changes this week (since Mon 19 Oct) · 1 commit Code changes, week of 2026-10-12 – 2026-10-18 · 64 commits Trusted setup: final keys+7 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.; Market figures are context only and never change activity status. Methodology

LinksWebsite GitHub Sources

Latest ship

Checked just now

Code changes this week (since Mon 19 Oct) · 1 commit

3h ago

Code activitySource linked

What changed, in the repository’s own words:

Bridge in: bring stablecoins from other chains through Relay

1 active day in cryptoduke01/gloam.

This week HEY looked inside 1 commit to see what changed: 1 changed code.

Record ship:518fc68a… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.

View evidence ↗

Shared change · Release

gloam shipped Trusted setup: round 000.

7 meaningful development events were recorded in the last 30 days. Builder status: Shipping.

Dated 2026-10-16 by the sourceSource: github

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.

Questions HEY can answer about gloam — as of 2026-10-19

Is gloam still being built?: DerivedShipping: 7 meaningful events in 30 days; latest ship today. Evidence
What did gloam ship last?: FactCode changes this week (since Mon 19 Oct) · 1 commit — Code activity, today. Evidence
What does HEY not know about gloam?: Unknown2 gaps: Published packages (not enough yet), API description (no source). Packages name its repository, but none is confirmed as the project’s own. Details

Build timeline

Code changes, week of 2026-10-12 – 2026-10-18 · 64 commits
19h ago
Code activitySource linked
What changed, in the repository’s own words:
6 active days in cryptoduke01/gloam.
This week HEY looked inside 3 of 64 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.
View evidence: Code changes, week of 2026-10-12 – 2026-10-18 · 64 commits (opens in a new tab)
14 releases in cryptoduke01/gloam on 17 Oct
2d ago
GitHub release
Show all 14 releasesHide the releases
1. Trusted setup: final keys
  2d ago
  GitHub releaseSource verified
  Gloam's trusted setup is complete. These are the final keys for the six mainnet circuits: shield, unshield, transfer, solvency (proof of funds), receipt (proof of payment) and payroll_total. How they were made · Phase 1: the public Hermez Powers of Tau… Show allShow less
  - Gloam's trusted setup is complete. These are the final keys for the six mainnet circuits: shield, unshield, transfer, solvency (proof of funds), receipt (proof of payment) and payroll_total. How they were made
  - Phase 1: the public Hermez Powers of Tau (powersOfTau28_hez_final_16.ptau, 54 contributors).
  - Phase 2: thirteen contributions in turn on 17 October 2026, by Gift, Duke, deviykee, Sage, wilcardjayx, GodwinXbt, Romeo, Maverick, SamY, Bob, Xavier Okolie, ubadineke and Viktor. Every round was checked against round 000 and phase 1 before the next person took it, and each one is a…
  View evidence: Trusted setup: final keys (opens in a new tab)
2. Trusted setup: round 013 (Viktor)
  2d ago
  GitHub releaseSource linked
  Round 013 of Gloam's trusted setup, the last contribution: one contribution, by Viktor, on top of round 012. Checked before publishing: every key comes from round 000 and the public phase 1 file, with exactly thirteen contributions. The contribution hashes are in manifest.json… Show allShow less
  Round 013 of Gloam's trusted setup, the last contribution: one contribution, by Viktor, on top of round 012. Checked before publishing: every key comes from round 000 and the public phase 1 file, with exactly thirteen contributions. The contribution hashes are in manifest.json inside the zip and in TRANSCRIPT.md. Contributions are closed. The final beacon is drand mainnet round 6561386 (2026-10-17, 21:30 UTC), applied to this…
  View evidence: Trusted setup: round 013 (Viktor) (opens in a new tab)
3. Trusted setup: round 012 (ubadineke)
  2d ago
  GitHub releaseSource linked
  Round 012 of Gloam's trusted setup: one contribution, by ubadineke, on top of round 011. Checked before publishing: every key comes from round 000 and the public phase 1 file, with exactly twelve contributions. The contribution hashes are in manifest.json inside the zip and in… Show allShow less
  Round 012 of Gloam's trusted setup: one contribution, by ubadineke, on top of round 011. Checked before publishing: every key comes from round 000 and the public phase 1 file, with exactly twelve contributions. The contribution hashes are in manifest.json inside the zip and in TRANSCRIPT.md. Next contributor: download round-012.zip, unzip it inside contracts/ceremony/, and follow…
  View evidence: Trusted setup: round 012 (ubadineke) (opens in a new tab)
4. Trusted setup: round 011 (Xavier Okolie)
  2d ago
  GitHub releaseSource linked
  Round 011 of Gloam's trusted setup: one contribution, by Xavier Okolie, on top of round 010. Checked before publishing: every key comes from round 000 and the public phase 1 file, with exactly eleven contributions. The contribution hashes are in manifest.json inside the zip and… Show allShow less
  Round 011 of Gloam's trusted setup: one contribution, by Xavier Okolie, on top of round 010. Checked before publishing: every key comes from round 000 and the public phase 1 file, with exactly eleven contributions. The contribution hashes are in manifest.json inside the zip and in TRANSCRIPT.md. Next contributor: download round-011.zip, unzip it inside contracts/ceremony/, and follow…
  View evidence: Trusted setup: round 011 (Xavier Okolie) (opens in a new tab)
5. Trusted setup: round 010 (Bob)
  2d ago
  GitHub releaseSource linked
  Round 010 of Gloam's trusted setup: one contribution, by Bob, on top of round 009. Checked before publishing: every key comes from round 000 and the public phase 1 file, with exactly ten contributions. The contribution hashes are in manifest.json inside the zip and in… Show allShow less
  Round 010 of Gloam's trusted setup: one contribution, by Bob, on top of round 009. Checked before publishing: every key comes from round 000 and the public phase 1 file, with exactly ten contributions. The contribution hashes are in manifest.json inside the zip and in TRANSCRIPT.md. Next contributor: download round-010.zip, unzip it inside contracts/ceremony/, and follow…
  View evidence: Trusted setup: round 010 (Bob) (opens in a new tab)
6. Trusted setup: round 009 (SamY)
  2d ago
  GitHub releaseSource linked
  Round 009 of Gloam's trusted setup: one contribution, by SamY, on top of round 008. Checked before publishing: every key comes from round 000 and the public phase 1 file, with exactly nine contributions. The contribution hashes are in manifest.json inside the zip and in… Show allShow less
  Round 009 of Gloam's trusted setup: one contribution, by SamY, on top of round 008. Checked before publishing: every key comes from round 000 and the public phase 1 file, with exactly nine contributions. The contribution hashes are in manifest.json inside the zip and in TRANSCRIPT.md. To check this round yourself, use the .r1cs files from the round 000 release.
  View evidence: Trusted setup: round 009 (SamY) (opens in a new tab)
7. Trusted setup: round 008 (Maverick)
  2d ago
  GitHub releaseSource linked
  Round 008 of Gloam's trusted setup: one contribution, by Maverick, on top of round 007. Checked before publishing: every key comes from round 000 and the public phase 1 file, with exactly eight contributions. The contribution hashes are in manifest.json inside the zip and in… Show allShow less
  Round 008 of Gloam's trusted setup: one contribution, by Maverick, on top of round 007. Checked before publishing: every key comes from round 000 and the public phase 1 file, with exactly eight contributions. The contribution hashes are in manifest.json inside the zip and in TRANSCRIPT.md. Next contributor: download round-008.zip, unzip it inside contracts/ceremony/, and follow…
  View evidence: Trusted setup: round 008 (Maverick) (opens in a new tab)
8. Trusted setup: round 007 (Romeo)
  2d ago
  GitHub releaseSource linked
  Round 007 of Gloam's trusted setup: one contribution, by Romeo, on top of round 006. Checked before publishing: every key comes from round 000 and the public phase 1 file, with exactly seven contributions. The contribution hashes are in manifest.json inside the zip and in… Show allShow less
  Round 007 of Gloam's trusted setup: one contribution, by Romeo, on top of round 006. Checked before publishing: every key comes from round 000 and the public phase 1 file, with exactly seven contributions. The contribution hashes are in manifest.json inside the zip and in TRANSCRIPT.md. Next contributor: download round-007.zip, unzip it inside contracts/ceremony/, and follow…
  View evidence: Trusted setup: round 007 (Romeo) (opens in a new tab)
9. Trusted setup: round 006 (GodwinXbt)
  2d ago
  GitHub releaseSource linked
  Round 006 of Gloam's trusted setup: one contribution, by GodwinXbt, on top of round 005. Checked before publishing: every key comes from round 000 and the public phase 1 file, with exactly six contributions. The contribution hashes are in manifest.json inside the zip and in… Show allShow less
  Round 006 of Gloam's trusted setup: one contribution, by GodwinXbt, on top of round 005. Checked before publishing: every key comes from round 000 and the public phase 1 file, with exactly six contributions. The contribution hashes are in manifest.json inside the zip and in TRANSCRIPT.md. Next contributor: download round-006.zip, unzip it inside contracts/ceremony/, and follow…
  View evidence: Trusted setup: round 006 (GodwinXbt) (opens in a new tab)
10. Trusted setup: round 005 (wilcardjayx)
  2d ago
  GitHub releaseSource linked
  Round 005 of Gloam's trusted setup: one contribution, by wilcardjayx, on top of round 004. Checked before publishing: every key comes from round 000 and the public phase 1 file, with exactly five contributions. The contribution hashes are in manifest.json inside the zip and in… Show allShow less
  Round 005 of Gloam's trusted setup: one contribution, by wilcardjayx, on top of round 004. Checked before publishing: every key comes from round 000 and the public phase 1 file, with exactly five contributions. The contribution hashes are in manifest.json inside the zip and in TRANSCRIPT.md. Next contributor: download round-005.zip, unzip it inside contracts/ceremony/, and follow…
  View evidence: Trusted setup: round 005 (wilcardjayx) (opens in a new tab)
11. Trusted setup: round 004 (Sage)
  2d ago
  GitHub releaseSource linked
  Round 004 of Gloam's trusted setup: one contribution, by Sage, on top of round 003. Checked before publishing: every key comes from round 000 and the public phase 1 file, with exactly four contributions. The contribution hashes are in manifest.json inside the zip and in… Show allShow less
  Round 004 of Gloam's trusted setup: one contribution, by Sage, on top of round 003. Checked before publishing: every key comes from round 000 and the public phase 1 file, with exactly four contributions. The contribution hashes are in manifest.json inside the zip and in TRANSCRIPT.md. Next contributor: download round-004.zip, unzip it inside contracts/ceremony/, and follow…
  View evidence: Trusted setup: round 004 (Sage) (opens in a new tab)
12. Trusted setup: round 003 (deviykee)
  2d ago
  GitHub releaseSource linked
  Round 003 of Gloam's trusted setup: one contribution, by deviykee (Ghost), on top of round 002. Checked before publishing: every key comes from round 000 and the public phase 1 file, with exactly three contributions. The contribution hashes are in manifest.json inside the zip… Show allShow less
  Round 003 of Gloam's trusted setup: one contribution, by deviykee (Ghost), on top of round 002. Checked before publishing: every key comes from round 000 and the public phase 1 file, with exactly three contributions. The contribution hashes are in manifest.json inside the zip and in TRANSCRIPT.md. Next contributor: download round-003.zip, unzip it inside contracts/ceremony/, and follow…
  View evidence: Trusted setup: round 003 (deviykee) (opens in a new tab)
13. Trusted setup: round 002 (Duke)
  2d ago
  GitHub releaseSource linked
  Round 002 of Gloam's trusted setup: one contribution, by Duke (@dukedotsol), on top of round 001. Checked before publishing: every key comes from round 000 and the public phase 1 file, with exactly two contributions. The contribution hashes are in manifest.json inside the zip… Show allShow less
  Round 002 of Gloam's trusted setup: one contribution, by Duke (@dukedotsol), on top of round 001. Checked before publishing: every key comes from round 000 and the public phase 1 file, with exactly two contributions. The contribution hashes are in manifest.json inside the zip and in TRANSCRIPT.md. Next contributor: download round-002.zip, unzip it inside contracts/ceremony/, and follow…
  View evidence: Trusted setup: round 002 (Duke) (opens in a new tab)
14. Trusted setup: round 001 (Gift)
  2d ago
  GitHub releaseSource linked
  Round 001 of Gloam's trusted setup: one contribution, by Gift, on top of round 000. Checked before publishing: every key comes from round 000 and the public phase 1 file, with exactly one more contribution. The contribution hashes are in manifest.json inside the zip and in… Show allShow less
  Round 001 of Gloam's trusted setup: one contribution, by Gift, on top of round 000. Checked before publishing: every key comes from round 000 and the public phase 1 file, with exactly one more contribution. The contribution hashes are in manifest.json inside the zip and in TRANSCRIPT.md. Next contributor: download round-001.zip, unzip it inside contracts/ceremony/, and follow…
  View evidence: Trusted setup: round 001 (Gift) (opens in a new tab)
Trusted setup: round 000
3d ago
GitHub releaseSource linked
Round 000 of Gloam's trusted setup: the starting keys for the six mainnet circuits, made from the public Hermez Powers of Tau file with no contribution yet. Files · round-000.zip: the round folder (six .zkey files and manifest.json). Unzip it inside contracts/ceremony/.… Show allShow less
- Round 000 of Gloam's trusted setup: the starting keys for the six mainnet circuits, made from the public Hermez Powers of Tau file with no contribution yet. Files
- round-000.zip: the round folder (six .zkey files and manifest.json). Unzip it inside contracts/ceremony/. Contributors start from the latest round, so only the first contributor uses this one.
- .r1cs: the compiled circuits. To check a round with node verify.mjs, put each one at build/ / .r1cs.
- ceremony-info.json: the compiler and snarkjs versions, the phase 1 file hash, and the hash…
View evidence: Trusted setup: round 000 (opens in a new tab)
Code changes, week of 2026-10-05 – 2026-10-11 · 128 commits
8d ago
Code activitySource linked
What changed, in the repository’s own words:
7 active days in cryptoduke01/gloam.
This week HEY looked inside 3 of 128 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.
View evidence: Code changes, week of 2026-10-05 – 2026-10-11 · 128 commits (opens in a new tab)
Code changes, week of 2026-09-28 – 2026-10-04 · 7 commits
17d ago
Code activitySource linked
What changed, in the repository’s own words:
2 active days in cryptoduke01/gloam.
This week HEY looked inside 1 of 7 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.
View evidence: Code changes, week of 2026-09-28 – 2026-10-04 · 7 commits (opens in a new tab)
Code changes, week of 2026-09-21 – 2026-09-27 · 2 commits
23d ago
Code activitySource linked
What changed, in the repository’s own words:
- App: plain language everywhere + kill remaining purple
- MCP: one-command agent-on-Tempo demo (fund -> shield -> private pay -> verify)
2 active days in cryptoduke01/gloam.
This week HEY looked inside 1 of 2 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.
View evidence: Code changes, week of 2026-09-21 – 2026-09-27 · 2 commits (opens in a new tab)
Code changes, week of 2026-09-14 – 2026-09-20 · at least 17 commits
1mo ago
Code activitySource linked
What changed, in the repository’s own words:
3 active days in cryptoduke01/gloam.
This week HEY looked inside 1 of 17 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.
View evidence: Code changes, week of 2026-09-14 – 2026-09-20 · at least 17 commits (opens in a new tab)
Code changes, week of 2026-09-07 – 2026-09-13 · at least 50 commits
1mo ago
Code activitySource linked
What changed, in the repository’s own words:
8 active days in cryptoduke01/gloam.
This week HEY looked inside 3 of 50 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count. 1 automated commit (bot accounts or a repeating scripted message) not counted.
View evidence: Code changes, week of 2026-09-07 – 2026-09-13 · at least 50 commits (opens in a new tab)
Code changes, week of 2026-08-31 – 2026-09-06 · at least 30 commits
1mo ago
Code activitySource linked
What changed, in the repository’s own words:
10 active days in cryptoduke01/gloam.
This week HEY looked inside 3 of 30 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.
View evidence: Code changes, week of 2026-08-31 – 2026-09-06 · at least 30 commits (opens in a new tab)

Research notes

Written by HEY researchers and reviewed before publishing. Commentary with sources — not the project's own claims, and not evidence of shipping.

Know something about gloam? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

35 changes on HEY’s record for gloam: 15 releases · 11 official source changes · 1 build pace change · 8 weeks of code pushed.

Code pushed3h ago
Code changes this week (since Mon 19 Oct) · 1 commit
See the change Source ↗
Code pushed19h ago
Code changes, week of 2026-10-12 – 2026-10-18 · 64 commits
See the change Source ↗
Release2d ago · 14 releases
Trusted setup: final keys
See the change Source ↗
Build pace3d ago
3 meaningful ships in the 7 days to 16 Oct, 0 the 7 days before
See the change Source
Release3d ago
Trusted setup: round 000
See the change Source ↗

All 35 changes for gloam →

The full change record holds 16 more, of kinds this list leaves out — lock records and HEY’s own research bookkeeping among them. Full record (JSON)

Research coverage

HEY can answer 8 of the 10 research questions that apply.

8 of 10 applicable dimensions measuredShow each dimension

Identity

IdentityMeasuredRead 1mo ago.

Building

Building activityMeasuredRead just now.
RepositoriesMeasured
ReleasesMeasuredRead 2d ago.
TimelineMeasured

Official site

Official docsMeasuredRead 1m ago.
API descriptionNo sourceIts website links no API description.
Official site changesMeasuredRead 7d ago.

Code and packages

Repository detailsMeasuredRead 1d ago.
Published packagesNot enough yetPackages name its repository, but none is confirmed as the project’s own.

Not applicable here: Package advisories, Contract creation, Contract activity, Verified source, 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.

Sources

Website
https://gloam.tradeUnverified
Docs
https://www.gloam.trade/docsOfficial
Docs
https://www.gloam.trade/docs/agentsOfficial
Repository
https://github.com/cryptoduke01/gloamOfficial

14 more sources (docs)

Docs
https://www.gloam.trade/docs/chainOfficial
Docs
https://www.gloam.trade/docs/compareOfficial
Docs
https://www.gloam.trade/docs/encryptionOfficial
Docs
https://www.gloam.trade/docs/payrollOfficial
Docs
https://www.gloam.trade/docs/privacy-modelOfficial
Docs
https://www.gloam.trade/docs/private-payOfficial
Docs
https://www.gloam.trade/docs/productOfficial
Docs
https://www.gloam.trade/docs/proofsOfficial
Docs
https://www.gloam.trade/docs/quickstartOfficial
Docs
https://www.gloam.trade/docs/sdkOfficial
Docs
https://www.gloam.trade/docs/sdk/disclosureOfficial
Docs
https://www.gloam.trade/docs/sdk/referenceOfficial
Docs
https://www.gloam.trade/docs/sealed-tradeOfficial
Docs
https://www.gloam.trade/docs/testnetOfficial

Security context: a published security contact. An audit shows an audit took place; it is not a guarantee of safety.

Build Momentum

Shipping consistently · Build Momentum 75

SHIPPING: 90
CONSISTENCY: 100 — strongest component
SIGNIFICANCE: 20
EVIDENCE: 73
SOURCES: 67

How steadily, how recently and how verifiably this project ships, from 0 to 100 — this project on its own, never price. How it is measured

Shipping weeks / last 12

8-week shipping streak

Builder Radar

#38 on today’s Builder Radar▲ 10 over 7 days

The board that ranks builders against each other on verified development, on-chain use and research standing. Price never counts.

The three parts

Development: 75
On-chain use: Not measured: no contract
Research standing: 100
Overall: 64

Methodology

Public code activity

84/ 100

A reading of the public repositories over 60 days — active days, releases, contributors and how recent — kept apart from Build Momentum.

Days with recorded activity: 29 / 60
Contributors: 1
GitHub releases: 15
Last code update: today

Observed development days. Commit volume is capped and never ranked.

Merged pull requests not measured; the remaining dimensions are reweighted rather than counted as zero.

Is this your project?

Claim the profile to post what you ship and keep this page accurate.

Claiming verifies ownership; by itself it changes no status, score or order.

Claim this project

Builders: show this status. Your HEY badge — Show it on your site or README; it changes no status, score or order.

For the builders: share this research profile — a post, the README badge, an embed and the evidence links.

Something wrong here? Report an error on this page

How HEY researches your project

Your HEY research profile is liveFor the team behind gloam: share it, badge it, embed it.

HEY verified gloam as a builder: an official source with a meaningful ship, and evidence on Robinhood Chain. This page updates itself as you ship.

Open the full share pack

Share verified builder status

Post on X Share card image

gloam — Shipping · Verified Builder · latest ship 19 Oct: Code changes this week (since Mon 19 Oct) · 1 commit · on HEY Research Lab
https://heyresearch.xyz/project/cryptoduke01-gloam

Add HEY badge to GitHub

Paste into your README. It shows your activity status and last ship, and links here.

[![gloam on HEY Research Lab](https://heyresearch.xyz/api/badge/cryptoduke01-gloam)](https://heyresearch.xyz/project/cryptoduke01-gloam?utm_source=badge&utm_medium=readme)

Add HEY intelligence to your site

A live builder widget, the same facts as this page. Choose a variant and theme.

<script src="https://heyresearch.xyz/embed/hey-project.js" async></script>
<hey-project project="cryptoduke01-gloam" variant="builder" theme="auto">
  <a href="https://heyresearch.xyz/project/cryptoduke01-gloam">gloam on HEY Research Lab</a>
</hey-project>

Canonical page: https://heyresearch.xyz/project/cryptoduke01-gloam
API: https://heyresearch.xyz/api/projects/cryptoduke01-gloam/snapshot
Changes feed: https://heyresearch.xyz/api/changes?project=cryptoduke01-gloam
Research receipts: An agent citing this project names it as { "subjectType": "project", "subject": { "chainId": 4663, "projectSlug": "cryptoduke01-gloam" } }. How receipts work

Everything here is public. HEY never contacts builders about it.

Embeddable badgeMethodology

gloam shipped Trusted setup: round 000.

Builder activity

Questions HEY can answer about gloam — as of 2026-10-19

Build timeline

Code changes, week of 2026-10-12 – 2026-10-18 · 64 commits

14 releases in cryptoduke01/gloam on 17 Oct

Trusted setup: final keys

Trusted setup: round 013 (Viktor)

Trusted setup: round 012 (ubadineke)

Trusted setup: round 011 (Xavier Okolie)

Trusted setup: round 010 (Bob)

Trusted setup: round 009 (SamY)

Trusted setup: round 008 (Maverick)

Trusted setup: round 007 (Romeo)

Trusted setup: round 006 (GodwinXbt)

Trusted setup: round 005 (wilcardjayx)

Trusted setup: round 004 (Sage)

Trusted setup: round 003 (deviykee)

Trusted setup: round 002 (Duke)

Trusted setup: round 001 (Gift)

Trusted setup: round 000

Code changes, week of 2026-10-05 – 2026-10-11 · 128 commits

Code changes, week of 2026-09-28 – 2026-10-04 · 7 commits

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

Code changes, week of 2026-09-14 – 2026-09-20 · at least 17 commits

Code changes, week of 2026-09-07 – 2026-09-13 · at least 50 commits

Code changes, week of 2026-08-31 – 2026-09-06 · at least 30 commits