Skip to content

tacit

No narrative yet

Is this your project? Claim and verify →

smart contracts on bitcoin

What HEY knows

Building
Shipping consistentlyShipping: 8 meaningful events in 30 days; latest ship today. Evidence Source

Build Momentum 71How it is measured

Latest ship
Code changes this week (since Mon 19 Oct) · 141 commits · · Code activity

Why it matters: One of 8 meaningful events in the last 30 days: building continued, not a one-off.

This change
Code changes, read from the team’s GitHub · not a deployment
What it names
3 of 3 commits 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-10-21; HEY first knew on 2026-10-19.
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.

FollowCreate alertTerminal previewView latest ship
Share

Follow puts tacit 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 tacit’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
Shipping.
“Shipping” by the activity rule: 8 meaningful events in the last 30 days, the newest 2026-10-21.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes this week (since Mon 19 Oct) · 141 commitsCode changes, week of 2026-10-12 – 2026-10-18 · 460 commitsprover-bins-v11 (private input switch, prover whitelist)+2 moreWhat 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.
Source1 registered source, 0 of them context only.ReadRecordsCode changes this week (since Mon 19 Oct) · 141 commitsCode changes, week of 2026-10-12 – 2026-10-18 · 460 commitsprover-bins-v11 (private input switch, prover whitelist)+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

Latest ship

Checked

Code changes this week (since Mon 19 Oct) · 141 commits

Code activitySource linked

3 active days in z0r0z/tacit.

This week HEY looked inside 3 of 141 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

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

Shared change · Development spike

tacit: 3 meaningful ships were recorded in the latest 7 days, from 1 in the 7 days before.

Builder status: Shipping.

Dated 2026-10-15 by the sourceSource: hey signal

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

Questions HEY can answer about tacit — as of 2026-10-21

Is tacit still being built?
DerivedShipping: 8 meaningful events in 30 days; latest ship today. Evidence
What did tacit ship last?
FactCode changes this week (since Mon 19 Oct) · 141 commits — Code activity, today. Evidence
What does HEY not know about tacit?
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-10-12 – 2026-10-18 · 460 commits

    Code activitySource linked

    3 active days in z0r0z/tacit.

    This week HEY looked inside 5 of 460 commits to see what changed: 3 changed code, 2 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count.

  2. 2 releases in z0r0z/tacit on 15 Oct

    GitHub release

    Show all 2 releases
    1. prover-bins-v11 (private input switch, prover whitelist)

      GitHub releaseSource verified

      Confidential settle provers (exec-*) built from fa535210. Each reads PRIVATE_STDIN=1 (send the witness as a private input) and PROVER_WHITELIST (comma-separated prover addresses that may take the request); with neither set they behave as v8/v9. Same guest ELF and program vkey… Show all

      Confidential settle provers (exec-*) built from fa535210. Each reads PRIVATE_STDIN=1 (send the witness as a private input) and PROVER_WHITELIST (comma-separated prover addresses that may take the request); with neither set they behave as v8/v9. Same guest ELF and program vkey 0x006cd47f…d6e3. Pre-release until a mainnet canary passes.

    2. prover-bins-v10 (private network inputs)

      GitHub releaseSource verified

      Confidential settle provers (exec-*) built from the private-stdin branch: each Succinct network request carries its input as a private artifact (private_stdin). Same guest ELF and program vkey 0x006cd47f…d6e3; bitcoin_prove and eth_prove stay on prover-bins-v8.

  3. Code changes, week of 2026-10-05 – 2026-10-11 · 230 commits

    Code activitySource linked

    7 active days in z0r0z/tacit.

    This week HEY looked inside 4 of 230 commits to see what changed: 3 changed code, 1 documentation or maintenance only. In a burst week, enough of a sample has to change code for the week to count.

  4. Code changes, week of 2026-09-28 – 2026-10-04 · 375 commits

    Code activitySource linked

    7 active days in z0r0z/tacit.

    This week HEY looked inside 3 of 375 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

  5. prover-bins-v9

    GitHub releaseSource verified

    exec-batchtransfer built for the hosted network prover (f844d1ed). Every other binary stays on prover-bins-v8.

  6. Code changes, week of 2026-09-21 – 2026-09-27 · at least 102 commits

    Code activitySource linked

    at least 2 active days in z0r0z/tacit since 2026-09-26; the count stops at the newest 100 commits listed.

    This week HEY looked inside 3 of 102 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

  7. Code changes, week of 2026-09-14 – 2026-09-20 · at least 137 commits

    Code activitySource linked

    at least 4 active days in z0r0z/tacit since 2026-09-17; the count stops at the newest 100 commits listed.

    This week HEY looked inside 3 of 137 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

  8. prover-bins-v8 (farm/adaptor/CDP-topup/liquidate/lpbond/wrapcdpmint provers)

    GitHub releaseSource verified

    Adds the 10 previously-missing relay prover binaries: exec-farmbond, exec-farmharvest, exec-farmunbond, exec-adaptorlock, exec-adaptorclaim, exec-adaptorrefund, exec-cdpliquidate, exec-cdptopup, exec-lpbond, exec-wrapcdpmint. Full self-contained set (34 exec-* + bitcoin_prove)… Show all

    Adds the 10 previously-missing relay prover binaries: exec-farmbond, exec-farmharvest, exec-farmunbond, exec-adaptorlock, exec-adaptorclaim, exec-adaptorrefund, exec-cdpliquidate, exec-cdptopup, exec-lpbond, exec-wrapcdpmint. Full self-contained set (34 exec-* + bitcoin_prove) so the Dockerfile's single-release fetch keeps working. All verified in execute/compressed mode against the live pool's PROGRAM_VKEY before publishing; see worker/src/confidential-settle.js history for the guest-source cross-check.

  9. Code changes, week of 2026-09-07 – 2026-09-13 · at least 56 commits

    Code activitySource linked

    9 active days in z0r0z/tacit.

    This week HEY looked inside 3 of 56 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

  10. 2 releases in z0r0z/tacit on 7 Sep

    GitHub release

    Show all 2 releases
    1. v1.0.0 — Tacit

      GitHub releaseSource verified

      Tacit's first canonical mainnet release: a confidential (shielded-balance) settlement pool with native ETH/USDC/USDT wrap-unwrap, a Bitcoin-native TAC bridge, a confidential AMM (cETH/cUSDC), a cBTC/cUSD CDP suite, and a cross-chain fast lane between Bitcoin and Ethereum-side… Show all

      Tacit's first canonical mainnet release: a confidential (shielded-balance) settlement pool with native ETH/USDC/USDT wrap-unwrap, a Bitcoin-native TAC bridge, a confidential AMM (cETH/cUSDC), a cBTC/cUSD CDP suite, and a cross-chain fast lane between Bitcoin and Ethereum-side value — all settled through SP1 zero-knowledge proofs. Pool: 0x0000…f5Ba (Etherscan-verified) Prover binaries for the always-on relay are published separately under prover-bins-v7. This tag marks the deployed, live-on-mainnet state of the main branch.

    2. prover-bins-v7 (gen4 reflection guest)

      GitHub releaseSource verified

      Rebuilds bitcoin_prove against the gen4 reflection ELF (bitcoin_relay_vkey 0x0097…8c8d). All exec-* settle binaries are byte-identical to prover-bins-v6 (the settle guest is unchanged this generation).

  11. Code changes, week of 2026-08-31 – 2026-09-06 · at least 72 commits

    Code activitySource linked

    10 active days in z0r0z/tacit.

    This week HEY looked inside 3 of 72 commits to see what changed: 3 changed code. In a burst week, enough of a sample has to change code for the week to count.

  12. prover-bins-v6 (stealth lock/claim provers)

    GitHub releaseSource verified

    Adds the stealth lock/claim provers; all binaries built against the pinned confidential guest. A native note's owner is keccak(nk ‖ dom), so a sender cannot mint a spendable note for a third party: choosing nk keeps spend authority with the sender, and deriving the owner from a… Show all

    Adds the stealth lock/claim provers; all binaries built against the pinned confidential guest. A native note's owner is keccak(nk ‖ dom), so a sender cannot mint a spendable note for a third party: choosing nk keeps spend authority with the sender, and deriving the owner from a pubkey mints a note nobody can spend. The stealth path escrows to a one-time key instead, and the recipient claims it into a note under an nk only they can derive — the sound way to pay someone. New: exec-stealthlock, exec-stealthclaim, exec-stealthrefund, exec-stealthlockbatch, exec-bridgestealthmint.…

  13. prover-bins-v5 (settle harnesses rebuilt against pinned guest)

    GitHub releaseSource verified

    Settle harness binaries rebuilt against the pinned confidential guest. The v4 exec-* binaries embedded a superseded guest, so every settle proof they produced was rejected on-chain. This release rebuilds all 19 against the pinned guest ELF. Verification chain: · pinned guest ELF… Show all
    • Settle harness binaries rebuilt against the pinned confidential guest. The v4 exec-* binaries embedded a superseded guest, so every settle proof they produced was rejected on-chain. This release rebuilds all 19 against the pinned guest ELF. Verification chain:
    • pinned guest ELF sha256 170504091f44dcaff09ee844e78e446244078fef687eeacf6e61378961e5bba0
    • derives program_vkey 0x0071…c0a4
    • that vkey is present in the live pool's deployed runtime bytecode
    • all 19 binaries byte-verified to embed exactly that ELF, and each asserts…
  14. prover-bins-v4

    GitHub releaseSource verified

    Rebuilt bitcoin_prove against the current pinned reflection-prover ELF, matching the gen1 redeploy's BITCOIN_RELAY_VKEY. Other exec-* binaries carried forward unchanged from v3.

  15. SP1 prover binaries (swapbatch vkeys)

    GitHub releaseSource verified

    bitcoin_prove @ bitcoin_relay_vkey 0x00edafc6; exec-* @ program_vkey 0x0082db7e. Matches contracts/sp1/confidential/elf-vkey-pin.json.

  16. SP1 prover binaries (V2 vkeys) prover-bins-v2

    GitHub releaseSource verified

    New-vkey prover binaries: settle exec-* (program_vkey 0x00014cc4) + bitcoin_prove (bitcoin_relay_vkey 0x00580f84). For the V2 pool 0x0000…5DE1.

  17. SP1 prover binaries (settle harnesses) v1

    GitHub releaseSource verified

    Prebuilt SP1 network-prove settle binaries (exec-wrap/lp/swap/unwrap/lpremove), vkey 0x003a21ba, for worker-relay Docker build. See ops/runbooks/PROVER-BOX-SETUP.md. bitcoin_prove (reflection) added separately when rebuilt.

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

What changed

22 changes on HEY’s record for tacit: 12 releases · 2 build pace changes · 8 weeks of code pushed.

All 22 changes for tacit →

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 11m ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 6d 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 packagesMeasuredRead 1d 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