What did Gloam ship last?

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

What does HEY not know about Gloam?

4 gaps: Published packages (not enough yet), API description (not enough yet), Official site changes (not enough yet), +1 more. Packages name its repository, but none is confirmed as the project’s own.

Gloam

$GLOAM

Payments · Utility

Contract 0xdcd885f5c60b3ad49f6d58718696417314e8724d

HEY holds 72 other Robinhood Chain tokens that use $GLOAM. This page is only the contract above. See them

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 →

Gloam is private money on public chains. Add stablecoins to a shared vault, pay people privately inside it, and cash out with a real zero-knowledge proof.

What HEY knows

Building

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

Build Momentum 74How it is measured

Latest ship

Code changes this week (since Mon 19 Oct) · 23 commits · 57m ago · Code activity

Why it matters: One of 7 meaningful events in the last 30 days: building continued, not a one-off.

This change

Code changes, read from the team’s GitHub · not a deployment

What it names: 1 of 1 commit HEY read changed code. A week of code names no capability.
Stage: Code changes are not a deployment: HEY has not observed a release or a deployment of this code.
Reported by: Read from the team’s GitHub. Reported in the team’s own source. No independent record HEY holds corroborates it.
Release and deployment: Not a release or a deployment: code is not a deployment.
Activity: No contract is tied to this change, so no product activity is attributed to it. Product usage is read on its own.
When: The source dates it to the week of 2026-10-20; HEY first knew on 2026-10-19.
Not known: No source HEY holds names what this change does.
HEY has not observed a deployment of this change.

Evidence: ship record

A ship says what was shipped and where HEY read it. It is not a judgement of quality, of the team, or of what the token will do.

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.

Attention: Building and market attention rank about level among comparable projects: 99.2 of 100 for building, 91.6 of 100 for market attention (a gap of 7.6). What the Discovery Gap is
It compares building with market attention; it is not a prediction and not a reason to trade.

Product usage: Fact1 of 1 watched contract active · 20,809 calls over the 3 of 7 days HEY holds — all token transfers and approvals (ERC-20), which trading alone produces; none reached another function HEY watches; the rest unknown, not zero.
Counted from the chain. Usage says the contracts are used, not that anyone is building.
Contracts: Fact1 contract on record for code changes, 1 with verified source; no implementation or interface change recorded.
Token market · context: Active market$255K fully diluted valuationToken verified
Not yet known: Unknown4 gaps: Published packages (not enough yet), API description (not enough yet), Official site changes (not enough yet), Contract creation (not enough yet). Packages name its repository, but none is confirmed as the project’s own.
HEY can answer 15 of the 19 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-20.; SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.Read43m agoRecordsCode changes this week (since Mon 19 Oct) · 23 commits 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.; Source20 registered sources, 0 of them context only.Read6h agoRecordsCode changes this week (since Mon 19 Oct) · 23 commits 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.
Token verified.: Token verified: the project's own site, a deploy record in its own repository, or an on-chain signature names this contract.; SourceThe project's own published sources and HEY's check of the contract.Read2h agoWhat HEY derivedToken verified: the project’s own site names it.Not concludedIt says whether the project itself names this contract. It is not a safety check, and a token is not the project.
Active market.: Active market: the pool holds liquidity and the token traded in the last day.; Source6 readings from HEY's own market tables.Read3m agoWhat HEY derivedHEY’s market rule reads this token’s market as “Active market”.Not concludedMarket status is context only. It never changes activity status or Build Momentum, and it is not a view on the price.; Market figures are context only and never change activity status. Methodology

LinksWebsite GitHub X DEX Screener RHTools Sources

Latest ship

Checked 55m ago

Code changes this week (since Mon 19 Oct) · 23 commits

57m 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 23 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

Record ship:eb10f435… · 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: final keys.

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

Dated 2026-10-17 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-20

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) · 23 commits — Code activity, today. Evidence
Is 0xDcD885F5c60b3aD49F6D58718696417314e8724d Gloam’s own contract?: FactToken verified: The project’s own site names this contract. Details
What does HEY not know about Gloam?: Unknown4 gaps: Published packages (not enough yet), API description (not enough yet), Official site changes (not enough yet), +1 more. Packages name its repository, but none is confirmed as the project’s own. Details

Build timeline

Verified contract source: OrynthLaunchToken
1h ago
Contract source verifiedSource verified
OrynthLaunchToken at 0xdcd8…724d has verified source on the Robinhood Chain explorer (compiler 0.8.26+commit.8a97fa7a).
View evidence: Verified contract source: OrynthLaunchToken (opens in a new tab)
Code changes, week of 2026-10-12 – 2026-10-18 · 64 commits
2d 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
3d ago
GitHub release
Show all 14 releasesHide the releases
1. Trusted setup: final keys
  3d 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)
  3d 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)
  3d 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)
  3d 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)
  3d 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)
  3d 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)
  3d 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)
  3d 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)
  3d 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)
  3d 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)
  3d 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)
  3d 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)
  3d 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)
  3d 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
4d 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
9d 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
18d 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
24d 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)

Around a recent ship

Observed after, 19 Oct so far: price +2925.2% · calls 20,783/day · volume $409K/day (before: $55.7/day).

The latest ship, in the week of 19 Oct (week precision) — the week is in progress, 19 Oct so far, is too recent to compare: the days after it have not begun. This is the newest ship whose days after HEY has observed.

Code changes, week of 2026-10-12 – 2026-10-18 · 64 commitsCode activityin the week of 12 Oct (week precision)

Observed before (5–11 Oct) and Observed after (19 Oct so far): Code changes, week of 2026-10-12 – 2026-10-18 · 64 commits
Measure	Observed before5–11 Oct	Observed after19 Oct so far
Priceprovider archiveAround this event:down 11.2 percent over 5 days· 13 Oct–18 Oct closes	Not measured: only one close in this span	up 2,925 percent over the day18 Oct–19 Oct closes so far
Volume per dayprovider archive	$55.7/day1 of 7 days	$409K/day1 of 7 days so farup 733,859 percent against the days beforevs beforeagainst before
Calls per day	Not measured: HEY began counting this project’s calls on 2026-10-17, during this ship’s week	20,783/day1 of 7 days so far
Calls to own functions per day	Not measured: HEY began counting this project’s calls on 2026-10-17, during this ship’s week	01 of 7 days so far
Active contracts (busiest day)	Not measured: HEY began counting this project’s calls on 2026-10-17, during this ship’s week	11 of 7 days so far
Distinct caller addresses (busiest day)	Not measured: HEY began counting this project’s calls on 2026-10-17, during this ship’s week	6301 of 7 days so far

Price and volume on days HEY holds no price reading of its own come from GeckoTerminal’s daily candles (provider archive, read 20 Oct), not from HEY’s own readings. The archive holds no liquidity or valuation.

Not shown: Liquidity and valuation: not in the provider’s daily archive, and HEY holds no reading of its own

Observed around the same time — HEY does not claim this event caused it.

Market context and product usage, placed by time. Seven days either side; the day in progress is never compared. Open evidence As data

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

25 changes on HEY’s record for Gloam: 15 releases · 1 new project on HEY · 1 build pace change · 8 weeks of code pushed.

Code pushed57m ago
Code changes this week (since Mon 19 Oct) · 23 commits
See the change Source ↗
Build pace2h ago
3 meaningful ships in the 7 days to 20 Oct, 1 the 7 days before
See the change Source
New on HEY2h ago
Project page published (Verified builder)
See the change
Code pushed2d ago
Code changes, week of 2026-10-12 – 2026-10-18 · 64 commits
See the change Source ↗
Release3d ago · 14 releases · recorded by HEY 2h ago
Trusted setup: final keys
See the change Source ↗

All 25 changes for Gloam →

The full change record holds 25 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 15 of the 19 research questions that apply.

15 of 19 applicable dimensions measuredShow each dimension

Identity

IdentityMeasuredRead 6h ago.

Building

Building activityMeasuredRead 55m ago.
RepositoriesMeasured
ReleasesMeasuredRead 3d ago.
TimelineMeasured

Official site

Official docsMeasuredRead 5m ago.
API descriptionNot enough yetHEY has not read its website’s published files yet.
Official site changesNot enough yetHEY has no first reading of its website to compare against yet.

Code and packages

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

Contracts

Contract creationNot enough yetHEY has not read the contract’s creation yet.
Contract activityMeasuredRead yesterday.
Verified sourceMeasuredRead 1h ago.
Contract interfaceMeasuredRead 1h ago.

Market

Current marketMeasuredRead 3m ago.
Market historyMeasuredRead yesterday.
Supply distributionMeasuredRead today.
LocksMeasuredRead 1h ago.
Market checksMeasured

Not applicable here: Package advisories, 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

Docs
https://gloam.trade/docsOfficial
Docs
https://www.gloam.trade/docs/agentsOfficial
Website
https://gloam.trade/Verified
X
https://x.com/gloamtrade@gloamtrade links back to gloam.trade — checked 2026-10-20.Official
Telegram
https://t.me/gloamhqFrom a launch or market listing
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/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/testnetOfficial
Docs
https://www.gloam.trade/docs/proofsOfficial
Docs
https://www.gloam.trade/docs/sealed-tradeOfficial

Contract

0xdcd8…724d

Build Momentum

Shipping consistently · Build Momentum 74

SHIPPING: 87
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

#14 on today’s Builder Radar

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

The three parts

Development: 74
On-chain use: 76
Research standing: 100
Overall: 78

Methodology

Public code activity

86/ 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: 30 / 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.

The token’s market, checks and locks below are context only: none of it changes activity status or Build Momentum.

Contract 0xDcD885F5c60b3aD49F6D58718696417314e8724d on Robinhood Chain

0xdcd8…724d

Token verified: The project’s own site names this contract.

Market context

Active market · FDV (fully diluted) $255K · current liquidity $80.5K · reading under an hour old (DEX Screener).

Token

Launch stage: Trading in a DEX pool
Pair age: 2mo ago

Market

24h volume: $454K
Trades 24h: 1,967 buys · 1,363 sells
Price 24h: up 3,157 percent over 24 hours· 6hdown 6.1 percent over 6 hours· 1hdown 2.4 percent over 1 hour

The tracked token has liquidity and traded in the last 24 hours.

The project’s own site names this contract.

Market history, trading and checks →

Market integrity

HEY has not seen this token hold an established market, so there is no fall to measure.

Market: Active market
Last day with trading: 2026-10-19

HEY has not seen this token hold a market of $5K or more for 3 days, so there is no level to measure a fall against.

From HEY’s own daily readings of the token’s pools and its decoded on-chain trades, and the locker’s record · checked 2026-10-20 00:52 UTC · How HEY checks this

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 ($GLOAM) — Shipping · Verified Builder · latest ship 20 Oct: Code changes this week (since Mon 19 Oct) · 23 commits · on HEY Research Lab
https://heyresearch.xyz/project/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/gloam)](https://heyresearch.xyz/project/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="gloam" variant="builder" theme="auto">
  <a href="https://heyresearch.xyz/project/gloam">Gloam on HEY Research Lab</a>
</hey-project>

Canonical page: https://heyresearch.xyz/project/gloam
API: https://heyresearch.xyz/api/projects/gloam/snapshot
Partner card (by contract): https://heyresearch.xyz/api/v1/scan?chain=4663&token=0xdcd885f5c60b3ad49f6d58718696417314e8724d
Changes feed: https://heyresearch.xyz/api/changes?project=gloam
Research receipts: An agent citing this project names it as { "subjectType": "project", "subject": { "chainId": 4663, "projectSlug": "gloam" } }. How receipts work

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

Embeddable badgeMethodology

Gloam shipped Trusted setup: final keys.

Builder activity

Questions HEY can answer about Gloam — as of 2026-10-20

Build timeline

Verified contract source: OrynthLaunchToken

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

Around a recent ship

Research notes

What changed

Research coverage

Identity

Building

Official site

Code and packages

Contracts

Market

Sources

Around a recent ship