Skip to content

d20-sdk

Dev Tools

Is this your project? Claim and verify →

Verifiable randomness (VRF) for smart contracts on Arc: Solidity consumer, ABIs, USDC fee quotes and public proof replay.

What HEY knows

Building
Shipped this weekDerivedShipping: 3 meaningful events in 30 days; latest ship 2 days ago. Evidence Source

Build Momentum 33How it is measured

Latest ship
Code changes, week of 2026-10-05 – 2026-10-11 · · Code activity

Why it matters: First week of code changes after 23 quiet days.

FollowCreate alertTerminal previewView latest ship
Share

Follow puts d20-sdk on your private watchlist and at the top of “Since you were last here” when you come back. Then pick what HEY should notify you about. Following needs an account; browsing never does.

No account? Email me d20-sdk’s changes — or read its RSS feed.

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.

Token market · context
No token tracked
Not yet known
Unknown4 gaps: Published packages (not enough yet), Official docs (no source), API description (no source), Official site changes (no source). Packages name its repository, but none is confirmed as the project’s own.

HEY can answer 6 of the 10 research questions that apply · Research coverage

What HEY checked — why it says this
Shipping.
“Shipping” by the activity rule: 3 meaningful events in the last 30 days, the newest 2026-10-09.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-10-05 – 2026-10-11SDK 0.1.1 — npm release and Arc Testnet referenceRefund consumer integration alphaWhat 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.
Source4 registered sources, 3 of them context only.ReadWhat 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

Latest ship

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

Code activitySource linked

7 active days in d20dao/d20-sdk.

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.

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

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: 10 weeks before HEY began reading this project’s sources — not yet read, not zero.

Build timeline

  1. SDK 0.1.1 — npm release and Arc Testnet reference

    GitHub releaseSource verified

    Published on npm as @d20dao/[email protected]. Install with npm install @d20dao/vrf-sdk. Includes Solidity consumer helpers, coordinator/epoch ABIs, deterministic mappings, public proof replay, AGENTS.md and packaged protocol provenance. The README now lists the Arc Testnet proxy… Show all

    Published on npm as @d20dao/[email protected]. Install with npm install @d20dao/vrf-sdk. Includes Solidity consumer helpers, coordinator/epoch ABIs, deterministic mappings, public proof replay, AGENTS.md and packaged protocol provenance. The README now lists the Arc Testnet proxy and implementation addresses from the deployment manifest. This release does not submit contract source verification to an explorer. Validated local tarball and registry installations in fresh consumers, Solidity 0.8.28 compilation, TypeScript, browser bundle, ABI parity and all four signed recipe fixtures. Registry…

  2. Refund consumer integration alpha

    GitHub releaseSource linked

    Exports the authenticated optional refund hook, notification-retry ABI, and a consumer example that tracks refunded requests separately from randomness delivery. Public protocol source is pinned to d7e785dda57499220bd37d73bc6fad9226872dcc. Validation: fresh tarball install… Show all

    Exports the authenticated optional refund hook, notification-retry ABI, and a consumer example that tracks refunded requests separately from randomness delivery. Public protocol source is pinned to d7e785dda57499220bd37d73bc6fad9226872dcc. Validation: fresh tarball install, Solidity consumer compile, TypeScript, browser bundle, ABI parity and all four signed API3 recipe fixtures passed. This GitHub prerelease remains private alpha package 0.1.0-alpha.0; npm publishing is still blocked. Confirm live implementation support before using the hook.

  3. D20DAO SDK Testnet Preview

    GitHub releaseSource linked

    Public D20DAO consumer SDK preview aligned with the deployed Arc Testnet protocol. · ESM/TypeScript replay, mapping and epoch-evidence helpers, contract ABIs and Solidity consumer sources. · Live API3 fixtures cover all four recipes and epoch-boundary replay. · The attached… Show all
    • Public D20DAO consumer SDK preview aligned with the deployed Arc Testnet protocol.
    • ESM/TypeScript replay, mapping and epoch-evidence helpers, contract ABIs and Solidity consumer sources.
    • Live API3 fixtures cover all four recipes and epoch-boundary replay.
    • The attached package archive passed fresh-consumer, browser, TypeScript and Solidity checks. The npm package remains unpublished and guarded; this is a GitHub source/package preview. Deployment addresses and reviewed runtime hashes are in the keeper repository's deployments/arc-testnet.json.

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 d20-sdk? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

Research coverage

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

6 of 10 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1d ago.

Building

  • Building activityMeasuredRead 46m ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 25d 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 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

  • Repository
  • Repository
    https://github.com/d20dao/keeperContext onlyContext only because HEY found this repository by its name and nothing the project controls links to it; it counts once the project’s own site links it or a verified owner adds it.
  • Repository
    https://github.com/d20dao/skillsContext onlyContext only because HEY found this repository by its name and nothing the project controls links to it; it counts once the project’s own site links it or a verified owner adds it.
  • Repository
    https://github.com/d20dao/watchdogContext onlyContext only because HEY found this repository by its name and nothing the project controls links to it; it counts once the project’s own site links it or a verified owner adds it.