Skip to content

Voxelithicag

AI Agents

Is this your project? Claim and verify →

Aggregation engine — reads every venue on Robinhood Chain into one order book

What HEY knows

Building
Last shipped 40 days agoActive: 0 meaningful events in 30 days; latest ship 40 days ago. Evidence Source

Build Momentum 16How it is measured

Latest ship
Code changes, week of 2026-09-07 – 2026-09-13 · at least 3 commits · · Code activity

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

Latest change
Derived9 days ago: 0 meaningful ships this month, 4 the month before. Evidence

Follow puts Voxelithicag 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 Voxelithicag’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.

Token market · context
No token tracked
Not yet known
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record.

HEY can answer 8 of the 11 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
Active.
“Active” by the activity rule's longer window: 3 meaningful events in the last 45 days (the rule needs at least 2); the newest, 2026-09-08, 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-07 – 2026-09-13 · at least 3 commitsCode changes, week of 2026-08-31 – 2026-09-06 · 7 commitsv0.1.0+1 moreWhat 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 verified building evidence from the project's own sources.
Source9 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-09-07 – 2026-09-13 · at least 3 commitsCode changes, week of 2026-08-31 – 2026-09-06 · 7 commitsv0.1.0+6 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

Latest ship

Checked

Code changes, week of 2026-09-07 – 2026-09-13 · at least 3 commitsvoxelithicag/api

Code activitySource linked

3 active days in Voxelithicag/api.

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

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

Shared change · Release

Voxelithicag shipped v0.1.0.

Builder status: Active.

Dated 2026-09-03 by the sourceSource: github

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

Questions HEY can answer about Voxelithicag — as of 2026-10-18

Is Voxelithicag still being built?
DerivedActive: 0 meaningful events in 30 days; latest ship 40 days ago. Evidence
What did Voxelithicag ship last?
FactCode changes, week of 2026-09-07 – 2026-09-13 · at least 3 commits — Code activity, 40 days ago. Evidence
What does HEY not know about Voxelithicag?
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record. Details

Build timeline

  1. Code changes, week of 2026-09-07 – 2026-09-13 · at least 1 commitvoxelithicag/mcp

    Code activitySource linked

    3 active days in Voxelithicag/mcp.

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

  2. Code changes, week of 2026-08-31 – 2026-09-06 · 7 commitsvoxelithicag/interfaces

    Code activitySource linked

    4 active days in voxelithicag/interfaces.

    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.

  3. Code changes, week of 2026-08-31 – 2026-09-06 · 2 commitsvoxelithicag/book-engine

    Code activitySource linked

    2 active days in voxelithicag/book-engine.

    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.

  4. Code changes, week of 2026-08-31 – 2026-09-06 · at least 3 commitsvoxelithicag/docs

    Code activitySource linked

    9 active days in voxelithicag/docs.

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

  5. Code changes, week of 2026-08-31 – 2026-09-06 · at least 10 commitsvoxelithicag/api

    Code activitySource linked

    2 active days in Voxelithicag/api.

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

  6. Code changes, week of 2026-08-31 – 2026-09-06 · at least 4 commitsvoxelithicag/mcp

    Code activitySource linked

    2 active days in Voxelithicag/mcp.

    This week HEY looked inside 1 of 4 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

  7. v0.1.0voxelithicag/mcp

    GitHub releaseSource verified

    First release. { "mcpServers": { "voxelithic": { "command": "npx", "args": ["-y", "voxelithic-mcp"] } } } Six tools: health, list_tokens, list_venues, get_quote, build_swap, verify_fill. No key and no configuration. The server holds no keys and cannot sign or broadcast… Show all

    First release. { "mcpServers": { "voxelithic": { "command": "npx", "args": ["-y", "voxelithic-mcp"] } } } Six tools: health, list_tokens, list_venues, get_quote, build_swap, verify_fill. No key and no configuration. The server holds no keys and cannot sign or broadcast: build_swap returns calldata plus the approval it needs, and minOut is never chosen for the caller. Quotes come from the pools themselves through the on-chain quoter, so any number a tool returns can be reproduced with an RPC and nothing else.

  8. Code changes, week of 2026-08-31 – 2026-09-06 · 2 commitsvoxelithicag/contracts

    Code activitySource linked

    2 active days in voxelithicag/contracts.

    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.

  9. v0.4.0voxelithicag/interfaces

    GitHub releaseSource verified

    Addresses, ABIs and types for Voxelithic on Robinhood Chain (4663). npm install voxelithic-interfaces Token addresses are generated from the router's own configuration and every one is checked against mainnet before it ships: symbol() and decimals() must match, and an address… Show all

    Addresses, ABIs and types for Voxelithic on Robinhood Chain (4663). npm install voxelithic-interfaces Token addresses are generated from the router's own configuration and every one is checked against mainnet before it ships: symbol() and decimals() must match, and an address with no contract fails the build. ABIs come from the Foundry build artifacts, so they match the verified bytecode rather than being retyped. CI builds on Node 18, 20 and 22, imports the built package, and re-verifies every address against chain 4663 on each push.

  10. Code changes, week of 2026-08-31 – 2026-09-06 · 1 commitvoxelithicag/verify

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in voxelithicag/verify.

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

  11. Code changes, week of 2026-08-31 – 2026-09-06 · at least 1 commitvoxelithicag/awesome-robinhood-chain

    Code activitySource linked

    What changed, in the repository’s own words:

    3 active days in Voxelithicag/awesome-robinhood-chain.

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

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

What changed

13 changes on HEY’s record for Voxelithicag: 2 releases · 1 build pace change · 10 weeks of code pushed.

All 13 changes for Voxelithicag →

The full change record holds 7 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 11 research questions that apply.

8 of 11 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

  • Building activityMeasuredRead 10m ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 1mo 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 1h ago.
  • Published packagesMeasuredRead 49m ago.
  • Package advisoriesMeasuredRead 3h ago.

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