Skip to content
Menu

mono

AI Agents

Is this your project? Claim and verify →

Safe bridge between AI agents and Web3 transactions. Open-source React kit + protocol with anti-phishing UI patterns built in.

What HEY knows

Building
Dormant: no ship for 83 daysDormant: 0 meaningful events in 30 days; latest ship on 2026-07-28. Evidence Source

Build Momentum 0How it is measured

Latest ship
Code changes, week of 2026-07-27 – 2026-08-02 · 2 commits · · Code activity

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

Latest change
Derived18 days ago: HEY reclassified the project — official source added: docs. Evidence Source
FollowCreate alertTerminal previewView latest ship
Share

Follow puts mono 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 mono’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: Published packages (not enough yet), API description (not enough yet), Official site changes (not enough yet). Packages name its repository, but none is confirmed as the project’s own.

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
Dormant.
“Dormant” by the activity rule: 0 meaningful events in the last 30 days, the newest 2026-07-28.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-07-27 – 2026-08-02 · 2 commitsv0.1.0-alpha.5 - @txkit/arbitrum-adapter joins cohortv0.1.0-alpha.4 - tx-decoder MVP+2 moreWhat HEY derivedHEY’s activity rule reads the counted events as “Dormant”.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.
Source11 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-07-27 – 2026-08-02 · 2 commitsv0.1.0-alpha.5 - @txkit/arbitrum-adapter joins cohortv0.1.0-alpha.4 - tx-decoder MVP+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
LinksWebsiteGitHubSources

Latest ship

Checked

Code changes, week of 2026-07-27 – 2026-08-02 · 2 commits

Code activitySource linked

What changed, in the repository’s own words:

1 active day in txkit/mono.

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.

Record ship:4b33f609… · 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

mono shipped a new release.

Builder status: Dormant.

Dated 2026-05-28 by the sourceSource: github

View evidence ↗Evidence receipt

Builder activity

No meaningful, source-backed updates in the 8 weeks since HEY began reading this project’s sources; earlier weeks are not yet read.

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

Is mono still being built?
DerivedDormant: 0 meaningful events in 30 days; latest ship on 2026-07-28. Evidence
What did mono ship last?
FactCode changes, week of 2026-07-27 – 2026-08-02 · 2 commits — Code activity, on 2026-07-28. Evidence
What does HEY not know about mono?
Unknown3 gaps: Published packages (not enough yet), API description (not enough yet), Official site changes (not enough yet). Packages name its repository, but none is confirmed as the project’s own. Details

Build timeline

  1. v0.1.0-alpha.5 - @txkit/arbitrum-adapter joins cohort

    GitHub releaseSource verified

    Cohort tag marking the addition of @txkit/arbitrum-adapter@0.1.0-alpha.0 to the npm registry. Existing packages stay at their current versions; the release.yml idempotent guard publishes only the package whose version is not yet on npm. New… Show all
    • Cohort tag marking the addition of @txkit/arbitrum-adapter@0.1.0-alpha.0 to the npm registry. Existing packages stay at their current versions; the release.yml idempotent guard publishes only the package whose version is not yet on npm. New
    • @txkit/arbitrum-adapter@0.1.0-alpha.0
    • skeleton for the Arbitrum Open House London Buildathon Week 1 deliverable. L1->L2 bridge intents (canonical / Hop / Across / Stargate), retryable-ticket UX hints, sequencer-fee preview with L1 calldata + L2 compute split, Arbitrum-aware calldata…
    View evidence: v0.1.0-alpha.5 - @txkit/arbitrum-adapter joins cohort (opens in a new tab)

  2. v0.1.0-alpha.4 - tx-decoder MVP

    GitHub releaseSource linked

    What is new tx-decoder MVP: BUILTIN_REGISTRY ships with ERC-7730-style descriptors 20 contract / chain descriptors across 5 mainstream protocols, covering high-volume mainnet + L2 DeFi calldata: · ERC-20 standard · USDC, WETH, USDT (mainnet) with transfer / approve… Show all
    • What is new tx-decoder MVP: BUILTIN_REGISTRY ships with ERC-7730-style descriptors 20 contract / chain descriptors across 5 mainstream protocols, covering high-volume mainnet + L2 DeFi calldata:
    • ERC-20 standard
    • USDC, WETH, USDT (mainnet) with transfer / approve / transferFrom / deposit / withdraw (3 descriptors)
    • Permit2
    • mainnet + Arbitrum + Base + Optimism + Polygon (single-token permit variant, 5 descriptors)
    • Uniswap V3 SwapRouter02
    • mainnet + Arbitrum + Optimism + Polygon + Base (exactInputSingle / exactInput / exactOutputSingle / multicall, 5 descriptors)
    • Aave V3 Pool…
    View evidence: v0.1.0-alpha.4 - tx-decoder MVP (opens in a new tab)

  3. v0.1.0-alpha.3

    GitHub releaseSource linked

    Cohort release of the seven open @txkit/* packages, published to npm under the alpha dist-tag. Licensing: all open packages are now Apache-2.0 (previously MIT), per the open-core model. The monorepo root stays MIT. Already-published 0.1.0-alpha.0 and 0.1.0-alpha.1 remain MIT.… Show all
    • Cohort release of the seven open @txkit/* packages, published to npm under the alpha dist-tag. Licensing: all open packages are now Apache-2.0 (previously MIT), per the open-core model. The monorepo root stays MIT. Already-published 0.1.0-alpha.0 and 0.1.0-alpha.1 remain MIT. @txkit/tx-protocol additionally carries the spec-alignment changes drafted for 0.1.0-alpha.2 (which was never published)
    • see packages/tx-protocol/CHANGELOG.md.
    View evidence: v0.1.0-alpha.3 (opens in a new tab)

  4. v0.1.0-alpha.0

    GitHub releaseSource linked

    First public alpha of txKit. API may change before v0.1.0 stable. Packages · @txkit/core · framework-agnostic types and utilities · @txkit/react · React components: ConnectWallet, TokenBalance, TransactionButton, FlowSteps, FlowProgress, FlowToast · @txkit/themes · CSS themes… Show all
    • First public alpha of txKit. API may change before v0.1.0 stable. Packages
    • @txkit/core
    • framework-agnostic types and utilities
    • @txkit/react
    • React components: ConnectWallet, TokenBalance, TransactionButton, FlowSteps, FlowProgress, FlowToast
    • @txkit/themes
    • CSS themes (light/dark, soft/sharp/rounded variants)
    • @txkit/tx-protocol
    • PreparedTransaction envelope (CAIP-2, EIP-5792 aligned, ERC-7730 clear-signing)
    • @txkit/tx-decoder
    • calldata decoder with ERC-7730 registry support
    • @txkit/ows-adapter
    • bridge to MoonPay Open Wallet Standard
    • @txkit/x402-adapter…
    View evidence: v0.1.0-alpha.0 (opens in a new tab)

  5. @txkit/tx-protocol v0.1.0-alpha.1

    GitHub releaseSource linked

    Alpha pre-release of the PreparedEnvelope protocol. Published on the alpha npm dist-tag without provenance (repo is still private). npm install @txkit/tx-protocol@alpha See the packaged CHANGELOG.md for the full v0.1 shape (implemented kinds, reserved kinds, security… Show all

    Alpha pre-release of the PreparedEnvelope protocol. Published on the alpha npm dist-tag without provenance (repo is still private). npm install @txkit/tx-protocol@alpha See the packaged CHANGELOG.md for the full v0.1 shape (implemented kinds, reserved kinds, security invariants). 0.1.0 on the latest tag — with the provenance badge — will ship once the monorepo goes public alongside @txkit/react, @txkit/core, and @txkit/themes.

    View evidence: @txkit/tx-protocol v0.1.0-alpha.1 (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 mono? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

What changed

7 changes on HEY’s record for mono: 5 releases · 1 build pace change · 1 week of code pushed.

All 7 changes for mono →

The full change record holds 12 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 3d ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 4mo ago.
  • TimelineMeasured

Official site

  • Official docsMeasuredRead 2d 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 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

7 more sources (docs)