Skip to content
HEY Research Lab
Menu

bastion

Integration record: HEY holds no Robinhood Chain evidence for this project (no token, contract or registry listing on the chain), so its ships are recorded here but it is not a Verified Builder.

Is this your project? Claim it →

A programmable Trust Runtime for autonomous AI systems. Durable execution, policy enforcement, verifiable provenance, and multi-chain trust orchestration.

What HEY knows

Development

Dormant: no ship for 74 daysDormant: 0 counted ships in 30 days; latest ship on 2026-09-01. Evidence Source

Build Momentum 0How it is measured

Latest: Code changes, week of 2026-08-31 – 2026-09-06 · 24 commits

Token

No token tracked
Follow
MoreCreate alertTerminal preview
View latest ship
Share

Get updates

Follow puts bastion on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

Sign in to follow bastion

No account? Email me bastion’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.

More detail
Not yet known
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (stale). HEY read its website and found no link to docs.
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 counted ships in the last 30 days, the newest 2026-09-01.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-08-31 – 2026-09-06 · 24 commits@zkos-labs/bastion-agentique v1.2.1@zkos-labs/mcp-server v0.2.2+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".
Research coverage: HEY can answer 8 of the 11 research questions that apply.
8 of 11 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 45d ago.

Building

  • Building activityMeasuredRead 1d ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 2mo ago.
  • TimelineMeasured

Official site

  • Official docsNo sourceHEY read its website and found no link to docs.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesStaleThe last read of its website’s files is out of date.

Code and packages

  • Repository detailsMeasuredRead 3d ago.
  • Published packagesMeasuredRead 3d ago.
  • Package advisoriesMeasuredRead 3d ago.

Not applicable here: Contract creation, Contract activity, Published source code, 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.

Market figures are context only and never change activity status. Methodology
LinksWebsite (opens in a new tab)GitHub (opens in a new tab)Sources

Latest ship

Checked

Code changes, week of 2026-08-31 – 2026-09-06 · 24 commits

Code activitySource-backed

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

What changed, in the repository’s own words:

2 active days in zkos-labs/bastion.

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

Record ship:1221ec3e… · HEY counts it as building; it does not judge the release’s quality.

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-09-01; HEY first knew on 2026-09-30.
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.

View evidence ↗ (opens in a new tab)

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.

Build timeline

  1. 3 releases in zkos-labs/bastion on 1 Sep

    GitHub release

    Show all 3 releases

    1. @zkos-labs/bastion-agentique v1.2.1

      GitHub releaseSource-backed

      Published to npm as @zkos-labs/bastion-agentique (formerly @zkos-labs/bastion-sdk). Changed · Renamed @zkos-labs/bastion-sdk → @zkos-labs/bastion-agentique, matching the project's "bastion-agentique" branding. Swept every reference across docs, CI, skill files, the SDK's own… Show all
      • Published to npm as @zkos-labs/bastion-agentique (formerly @zkos-labs/bastion-sdk). Changed
      • Renamed @zkos-labs/bastion-sdk → @zkos-labs/bastion-agentique, matching the project's "bastion-agentique" branding. Swept every reference across docs, CI, skill files, the SDK's own README/examples, and the dashboard's Integrate flow (24 files total).
      • Rewrote packages/sdk/README.md for accuracy against the actual current exports: fixed method names that never matched the real API (no simulate(); added missing…
      View evidence: @zkos-labs/bastion-agentique v1.2.1 (opens in a new tab)

    2. @zkos-labs/bastion-sdk v1.1.1

      GitHub releaseSource-backed

      Published to npm as @zkos-labs/bastion-sdk (superseded by @zkos-labs/bastion-agentique in the very next release — see v1.2.1). Added · Multichain support restored: Solana settlement via TrustAdapter · Full EVM stack: Monad support, ERC-8354 & ERC-8380 integration; Solana/Arcium… Show all
      • Published to npm as @zkos-labs/bastion-sdk (superseded by @zkos-labs/bastion-agentique in the very next release — see v1.2.1). Added
      • Multichain support restored: Solana settlement via TrustAdapter
      • Full EVM stack: Monad support, ERC-8354 & ERC-8380 integration; Solana/Arcium retired from the core path
      • Sidecar background trust scanner and policy CRUD routes
      • Settlement router integration (Epic C)
      • Durable workflow engine (Epic A)
      • trustless-ai ERC stack, CAPV ZK verdicts, WYRIWE provenance Changed
      • Removed em-dashes across the codebase
      • Docs repositioned around Bastion…
      View evidence: @zkos-labs/bastion-sdk v1.1.1 (opens in a new tab)

    3. @zkos-labs/bastion-web2 v0.3.1

      GitHub releaseSource-backed

      Published to npm as @zkos-labs/bastion-web2 (formerly @zkos-labs/web2-sdk). Changed · Renamed package @zkos-labs/web2-sdk → @zkos-labs/bastion-web2 to match project branding · Swept stale SDK name references across docs/examples · Removed em-dashes across the codebase · Docs… Show all
      • Published to npm as @zkos-labs/bastion-web2 (formerly @zkos-labs/web2-sdk). Changed
      • Renamed package @zkos-labs/web2-sdk → @zkos-labs/bastion-web2 to match project branding
      • Swept stale SDK name references across docs/examples
      • Removed em-dashes across the codebase
      • Docs repositioned around Bastion as a Programmable Trust Runtime
      View evidence: @zkos-labs/bastion-web2 v0.3.1 (opens in a new tab)

  2. 3 releases in zkos-labs/bastion on 21 Jul

    GitHub release

    Show all 3 releases

    1. @zkos-labs/mcp-server v0.2.2

      GitHub releaseSource-backed

      Updated package description to reflect Bastion repositioning as a Programmable Trust Runtime. · Description: Bastion Trust Runtime -- Model Context Protocol tools for agent trust. · Added README.md with full tool listing, pricing table, and setup instructions. · Added files… Show all
      • Updated package description to reflect Bastion repositioning as a Programmable Trust Runtime.
      • Description: Bastion Trust Runtime -- Model Context Protocol tools for agent trust.
      • Added README.md with full tool listing, pricing table, and setup instructions.
      • Added files field to package.json for clean packaging.
      View evidence: @zkos-labs/mcp-server v0.2.2 (opens in a new tab)

    2. @zkos-labs/web2-sdk v0.2.2

      GitHub releaseSource-backed

      Updated package description to reflect Bastion repositioning as a Programmable Trust Runtime. · Description: Web2 adapter for the Bastion Programmable Trust Runtime -- policy-enforced API calls for autonomous systems. · Added README.md with Quick Start, API reference, and policy… Show all
      • Updated package description to reflect Bastion repositioning as a Programmable Trust Runtime.
      • Description: Web2 adapter for the Bastion Programmable Trust Runtime -- policy-enforced API calls for autonomous systems.
      • Added README.md with Quick Start, API reference, and policy rule documentation.
      View evidence: @zkos-labs/web2-sdk v0.2.2 (opens in a new tab)

    3. @zkos-labs/sdk v0.6.2

      GitHub releaseSource-backed

      Updated package description to reflect Bastion repositioning as a Programmable Trust Runtime. · Description: TypeScript SDK for the Bastion Programmable Trust Runtime -- identity, policy, execution, and observability for autonomous systems. · README subtitle updated to match new… Show all
      • Updated package description to reflect Bastion repositioning as a Programmable Trust Runtime.
      • Description: TypeScript SDK for the Bastion Programmable Trust Runtime -- identity, policy, execution, and observability for autonomous systems.
      • README subtitle updated to match new positioning.
      View evidence: @zkos-labs/sdk v0.6.2 (opens in a new tab)

  3. v0.5.2

    GitHub releaseSource-backed

    SDK fixes and Web2 API firewall expansion begin here. SDK v0.5.2 adds simulateEvm and events methods to BastionSidecar. These expose the sidecar EVM simulation endpoint and SSE audit event stream respectively. Also adds bastion web2 firewall a new Rust crate with proxy engine… Show all

    SDK fixes and Web2 API firewall expansion begin here. SDK v0.5.2 adds simulateEvm and events methods to BastionSidecar. These expose the sidecar EVM simulation endpoint and SSE audit event stream respectively. Also adds bastion web2 firewall a new Rust crate with proxy engine policy rules OpenAPI parser and provider adapters. The TypeScript web2 SDK ships as @bastion agentique web2 sdk v0.1.0. 43 tests pass across Rust and TypeScript. All CI green. Full changelist is on the compare page below.

    View evidence: v0.5.2 (opens in a new tab)

  4. 2 releases in zkos-labs/bastion on 8 Jun

    GitHub release

    Show all 2 releases

    1. v0.5.1 — SDK fix

      GitHub releaseSource-backed

      @bastion-agentique/sdk v0.5.1 Fixes · BastionSidecar.updatePolicy now correctly hits POST /policy/full instead of PUT /policy Install npm install @bastion-agentique/sdk@0.5.1 Links · npm · GitHub release Show all
      • @bastion-agentique/sdk v0.5.1 Fixes
      • BastionSidecar.updatePolicy now correctly hits POST /policy/full instead of PUT /policy Install npm install @bastion-agentique/sdk@0.5.1 Links
      • npm
      • GitHub release
      View evidence: v0.5.1 — SDK fix (opens in a new tab)

    2. Bastion v0.5.0 — Production URL + Org Rename

      GitHub releaseSource-backed

      Default sidecar URL → (replaces localhost:3000) · GitHub org renamed to bastion-agentique · SDK published as @bastion-agentique/sdk@0.5.0 on npm Packages · @bastion-agentique/sdk — v0.5.0 (npm) Quick Start npm install @bastion-agentique/sdk import { BastionClient } from… Show all
      • What's Changed
      • Default sidecar URL → https://bastion-agentique.fly.dev/ (replaces localhost:3000)
      • GitHub org renamed to bastion-agentique
      • SDK published as @bastion-agentique/sdk@0.5.0 on npm Packages
      • @bastion-agentique/sdk — v0.5.0 (npm) Quick Start npm install @bastion-agentique/sdk import { BastionClient } from '@bastion-agentique/sdk'; const client = new BastionClient({ baseUrl: 'https://bastion-agentique.fly.dev/' });
      View evidence: Bastion v0.5.0 — Production URL + Org Rename (opens in a new tab)

  5. 2 releases in zkos-labs/bastion on 7 Jun

    GitHub release

    Show all 2 releases

    1. @bastion-agentic-defense/sdk v0.4.1

      GitHub releaseSource-backed

      Production-Ready DID Auth & Persistence What's New · Sled-backed AgentStore — agents persist across sidecar restarts (replaces in-memory HashMap) · DID keypair generation — POST /did/generate creates Ed25519 keypairs with did:bastion:solana:{pubkey} identifiers · On-chain PDA… Show all
      • Production-Ready DID Auth & Persistence What's New
      • Sled-backed AgentStore — agents persist across sidecar restarts (replaces in-memory HashMap)
      • DID keypair generation — POST /did/generate creates Ed25519 keypairs with did:bastion:solana:{pubkey} identifiers
      • On-chain PDA verification — agent registration calls getAccountInfo RPC to verify the Agent PDA exists before accepting
      • DID-signed request auth — challenge-response flow replaces API key for production use: 1. POST /auth/nonce → get challenge nonce 2. Sign nonce with Ed25519 authority key 3. Send…
      View evidence: @bastion-agentic-defense/sdk v0.4.1 (opens in a new tab)

    2. @bastion-agentic-defense/sdk v0.4.0

      GitHub releaseSource-backed

      Features · Sidecar HTTP client — typed Rust client for the Bastion sidecar REST API (/simulate, /policy, /override, /logs, /agents) · Typed SDK — full TypeScript SDK wrapping the Solana Anchor program with BastionClient class · API key auth — sidecar now supports X-Api-Key… Show all
      • What's Changed Features
      • Sidecar HTTP client — typed Rust client for the Bastion sidecar REST API (/simulate, /policy, /override, /logs, /agents)
      • Typed SDK — full TypeScript SDK wrapping the Solana Anchor program with BastionClient class
      • API key auth — sidecar now supports X-Api-Key header authentication
      • Docker — sidecar containerized via docker-compose and Dockerfile Bug Fixes
      • Resolve CI clippy + fmt failures across core and sidecar crates
      • Collapse nested if-let chains, fix unused variable warnings, auto-format all Rust files…
      View evidence: @bastion-agentic-defense/sdk v0.4.0 (opens in a new tab)

Other changes on HEY’s record

15 changes on HEY’s record for bastion: 11 releases · 1 new Verified Builder or owner proof · 1 new project on HEY · 1 build pace change · 1 other change in 1 more kind.

All 15 changes for bastion →

The full change record holds 1 more, of kinds this list leaves out — new locks, unlock reminders and HEY’s own research bookkeeping among them. Full record (JSON)

Sources

2 places HEY reads for bastion