Skip to content
Menu

vault

AI Agents

Is this your project? Claim and verify →

Agentic trading interface for RWA and tokens on Robinhood chain, with full x402 capabilities

What HEY knows

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

Build Momentum 34How it is measured

Latest ship
v0.4.2 · · GitHub release

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

FollowCreate alertTerminal previewView latest ship
Share

Follow puts vault 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 vault’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 7 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
Active.
“Active” by the activity rule: 4 meaningful events in the last 30 days, the newest 2026-10-02.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsv0.4.2Code changes, week of 2026-09-28 – 2026-10-04 · 1 commitv0.4.1+2 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.
Source1 registered source, 0 of them context only.ReadRecordsv0.4.2Code changes, week of 2026-09-28 – 2026-10-04 · 1 commitv0.4.1+3 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
LinksGitHubSources

Latest ship

Checked

v0.4.2

GitHub releaseSource verified

0.4.2 CI-only fix; no functional or behavioral changes from 0.4.1. Fixed · build.yml's release workflow was an invalid workflow file · secrets.BLOCKSCOUT_PRO_API_KEY referenced directly inside a step's if: condition, which GitHub Actions' validator rejects ("Unrecognized… Show all
  • 0.4.2 CI-only fix; no functional or behavioral changes from 0.4.1. Fixed
  • build.yml's release workflow was an invalid workflow file
  • secrets.BLOCKSCOUT_PRO_API_KEY referenced directly inside a step's if: condition, which GitHub Actions' validator rejects ("Unrecognized named-value: 'secrets'"). The whole file failed to parse, so the Build Vault workflow never ran on any tagged release since the step was added
  • 0.4.0 and 0.4.1 shipped no desktop binaries. Moved the empty-key check into the Python step itself instead of if:.

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

View evidence ↗Post this ship on X

Shared change · Release

vault shipped v0.4.2.

4 meaningful development events were recorded in the last 30 days. Builder status: Active.

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

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

Is vault still being built?
DerivedActive: 4 meaningful events in 30 days; latest ship 17 days ago. Evidence
What did vault ship last?
Factv0.4.2 — GitHub release, 17 days ago. Evidence
What does HEY not know about vault?
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-28 – 2026-10-04 · 1 commit

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in primer-systems/vault.

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

    View evidence: Code changes, week of 2026-09-28 – 2026-10-04 · 1 commit (opens in a new tab)

  2. 2 releases in primer-systems/vault on 25 Sep

    GitHub release

    Show all 2 releases

    1. v0.4.1

      GitHub releaseSource verified

      0.4.1 Lint-only fix; no functional or behavioral changes from 0.4.0. Fixed · Two unused imports (DEFAULT_NETWORK in ui/dialogs.py, timedelta in tests/test_history_time_column.py) that failed CI's ruff check. 0.4.0 Base is now a second supported network alongside Robinhood Chain… Show all
      • 0.4.1 Lint-only fix; no functional or behavioral changes from 0.4.0. Fixed
      • Two unused imports (DEFAULT_NETWORK in ui/dialogs.py, timedelta in tests/test_history_time_column.py) that failed CI's ruff check. 0.4.0 Base is now a second supported network alongside Robinhood Chain, and Vault gained a secrets/signing partner in 1Claw. x402 no longer requires a single allowlisted settlement asset, and the History view is rebuilt around having more than one chain to show. Several bugs were fixed along the way, including one security-relevant one in the signing path and every…
      View evidence: v0.4.1 (opens in a new tab)

    2. v0.4.0

      GitHub releaseSource verified

      0.4.0 Base is now a second supported network alongside Robinhood Chain, and Vault gained a secrets/signing partner in 1Claw. x402 no longer requires a single allowlisted settlement asset, and the History view is rebuilt around having more than one chain to show. Several bugs… Show all
      • 0.4.0 Base is now a second supported network alongside Robinhood Chain, and Vault gained a secrets/signing partner in 1Claw. x402 no longer requires a single allowlisted settlement asset, and the History view is rebuilt around having more than one chain to show. Several bugs were fixed along the way, including one security-relevant one in the signing path and every GUI timestamp having been shown in UTC rather than local time. Added
      • Base network support (chain 8453): Uniswap v3/v4 deployments and Morpho (Steakhouse as curator, three seed vaults), alongside the existing Robinhood…
      View evidence: v0.4.0 (opens in a new tab)

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

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in primer-systems/vault.

    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)

  4. Code changes, week of 2026-08-31 – 2026-09-06 · at least 1 commit

    Code activitySource linked

    What changed, in the repository’s own words:

    1 active day in primer-systems/vault.

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

    View evidence: Code changes, week of 2026-08-31 – 2026-09-06 · at least 1 commit (opens in a new tab)

  5. v0.3.0

    GitHub releaseSource verified

    0.3.0 Vault is now two published editions over one shared engine, and adds Morpho lending as a third policy lane alongside x402 payments and trading. Added · Morpho lending. An agent can supply USDG to a Morpho vault and withdraw it again, gated by its own policy rules — a… Show all
    • 0.3.0 Vault is now two published editions over one shared engine, and adds Morpho lending as a third policy lane alongside x402 payments and trading. Added
    • Morpho lending. An agent can supply USDG to a Morpho vault and withdraw it again, gated by its own policy rules — a per-deposit cap, a total-exposure cap as a dollar figure and/or a percent of USDG held, a daily operation ceiling, and an auto-approve threshold — through the HTTP API (POST /position, GET /position/status/{id}, POST /venues), the CLI (position pending|approve|reject, venues), and a Morpho tab in the…
    View evidence: v0.3.0 (opens in a new tab)

  6. v0.2.1

    GitHub releaseSource verified

    0.2.1 Added · An agent can read its own address and balances. /mandate now returns the agent's wallet_address (and wallet_id) in its live response, so an agent no longer has to infer the address it signs from. A new authenticated POST /balances returns that address plus its… Show all
    • 0.2.1 Added
    • An agent can read its own address and balances. /mandate now returns the agent's wallet_address (and wallet_id) in its live response, so an agent no longer has to infer the address it signs from. A new authenticated POST /balances returns that address plus its on-chain holdings (native + tokens), behind the same credential as /mandate, and degrades gracefully if the block explorer is unavailable. Read-only; no keys involved.
    View evidence: v0.2.1 (opens in a new tab)

  7. v0.2.0

    GitHub releaseSource verified

    0.2.0 Added · Ledger hardware wallet support. Derive agent addresses from a connected Ledger (Ledger Live, BIP44, Legacy MEW and custom paths), sign x402 authorizations and DEX trades on-device (including the ERC-20 approval step), and verify a stored address on the device.… Show all
    • 0.2.0 Added
    • Ledger hardware wallet support. Derive agent addresses from a connected Ledger (Ledger Live, BIP44, Legacy MEW and custom paths), sign x402 authorizations and DEX trades on-device (including the ERC-20 approval step), and verify a stored address on the device. Hardware addresses are badged and refuse private-key export; keys never touch the computer
    • Price-impact check on every trade. Vault probes the agent's chosen pool for its true rate and escalates any trade above max_price_impact_percent (default 5%) — catching a pool too thin to fill, which a slippage…
    View evidence: v0.2.0 (opens in a new tab)

  8. v0.1.0

    GitHub releaseSource verified

    v0.1.0 Initial Release

    View evidence: v0.1.0 (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 vault? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

10 changes on HEY’s record for vault: 7 releases · 3 weeks of code pushed.

All 10 changes for vault →

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

7 of 10 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

  • Building activityMeasuredRead 3h ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 17d 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, 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