Skip to content

Timbagame Protocol

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 →

Shared TypeScript protocol for Timba

What HEY knows

Development

Shipping consistentlyShipping: 8 counted ships in 30 days; latest ship 6 days ago. Evidence Source

Build Momentum 59How it is measured

Latest: Code changes, week of 2026-11-02 – 2026-11-08 · 6 commits

Token

No token tracked
Follow
MoreCreate alertTerminal preview
View latest ship
Share

Get updates

Follow puts Timbagame Protocol 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 Timbagame Protocol

No account? Email me Timbagame Protocol’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 (no source). No official website on record.
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 counted ships in the last 30 days, the newest 2026-11-07.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-11-02 – 2026-11-08 · 6 commitsv0.18.3Code changes, week of 2026-10-26 – 2026-11-01 · 4 commits+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".
Research coverage: HEY can answer 7 of the 10 research questions that apply.
7 of 10 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 45d ago.

Building

  • Building activityMeasuredRead 27m 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 2d ago.
  • Published packagesMeasuredRead 2d ago.

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

Latest ship

Checked

Code changes, week of 2026-11-02 – 2026-11-08 · 6 commits

Code activitySource-backed

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

2 active days in timbagame/protocol.

This week HEY looked inside 1 of 6 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there. 6 automated commits (bot accounts or a repeating scripted message) not counted.

Record ship:9aa5303b… · 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-11-07; HEY first knew on 2026-11-02.
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.

Shared change · Published

Timbagame Protocol was published on HEY with its sources recorded.

Builder status: Shipping.

Observed by HEY on 2026-09-29Source: HEY’s research record

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.

Build timeline

A code week counts as building when a commit HEY looked inside changed code; one is enough, so HEY stops there.

  1. v0.18.3

    GitHub releaseSource-backed

    Link the oracle and bot repos in the README by @astrovm · Update dependency node to v26 · Update all dependencies · Update all dependencies · Update all dependencies · Lock file maintenance *… Show all
    • What's Changed
    • Link the oracle and bot repos in the README by @astrovm in https://github.com/timbagame/protocol/pull/74
    • Update dependency node to v26 by @renovate[bot] in https://github.com/timbagame/protocol/pull/75
    • Update all dependencies by @renovate[bot] in https://github.com/timbagame/protocol/pull/76
    • Update all dependencies by @renovate[bot] in https://github.com/timbagame/protocol/pull/77
    • Update all dependencies by @renovate[bot] in https://github.com/timbagame/protocol/pull/79
    • Lock file maintenance by @renovate[bot] in https://github.com/timbagame/protocol/pull/80 *…
  2. Code changes, week of 2026-10-26 – 2026-11-01 · 4 commits

    Code activitySource-backed

    2 active days in timbagame/protocol.

    How HEY read this week

    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. 4 automated commits (bot accounts or a repeating scripted message) not counted.

  3. 3 releases in timbagame/protocol on 26 Oct

    GitHub release

    Show all 3 releases
    1. v0.18.2

      GitHub releaseSource-backed

      Update viem, lockfiles and mise-action (0.18.2) by @astrovm Show all
      • What's Changed
      • Update viem, lockfiles and mise-action (0.18.2) by @astrovm in https://github.com/timbagame/protocol/pull/73 Full Changelog: https://github.com/timbagame/protocol/compare/v0.18.1...v0.18.2
    2. v0.18.1

      GitHub releaseSource-backed

      Accept uint48 EVM game fields as numbers (0.18.1) by @astrovm Show all
      • What's Changed
      • Accept uint48 EVM game fields as numbers (0.18.1) by @astrovm in https://github.com/timbagame/protocol/pull/72 Full Changelog: https://github.com/timbagame/protocol/compare/v0.18.0...v0.18.1
    3. v0.18.0

      GitHub releaseSource-backed

      Move renovate.json to .github by @astrovm · Remove Renovate rules that aren't needed by @astrovm · Install CI Cargo tools with mise so Renovate needs no custom manager by @astrovm · chore: sync Renovate config · Update all dependencies · Ignore RUSTSEC-2026-0387 until alloy… Show all
      • What's Changed
      • Move renovate.json to .github by @astrovm in https://github.com/timbagame/protocol/pull/62
      • Remove Renovate rules that aren't needed by @astrovm in https://github.com/timbagame/protocol/pull/63
      • Install CI Cargo tools with mise so Renovate needs no custom manager by @astrovm in https://github.com/timbagame/protocol/pull/64
      • chore: sync Renovate config by @astrovm-repo-settings[bot] in https://github.com/timbagame/protocol/pull/65
      • Update all dependencies by @renovate[bot] in https://github.com/timbagame/protocol/pull/66
      • Ignore RUSTSEC-2026-0387 until alloy moves to…
  4. Code changes, week of 2026-10-19 – 2026-10-25 · 1 commit

    Code activitySource-backed

    What changed, in the repository’s own words:

    1 active day in timbagame/protocol.

    How HEY read this week

    This week HEY looked inside 1 commit to see what changed: 1 changed code. 3 automated commits (bot accounts or a repeating scripted message) not counted.

  5. Code changes, week of 2026-10-12 – 2026-10-18 · 11 commits

    Code activitySource-backed

    5 active days in timbagame/protocol.

    How HEY read this week

    This week HEY looked inside 2 of 11 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. 8 automated commits (bot accounts or a repeating scripted message) not counted.

  6. 2 releases in timbagame/protocol on 17 Oct

    GitHub release

    Show all 2 releases
    1. v0.17.0

      GitHub releaseSource-backed

      Add period to the indexer leaderboard query by @astrovm Show all
      • What's Changed
      • Add period to the indexer leaderboard query by @astrovm in https://github.com/timbagame/protocol/pull/61 Full Changelog: https://github.com/timbagame/protocol/compare/v0.16.0...v0.17.0
    2. v0.16.0

      GitHub releaseSource-backed

      Create the GitHub release automatically after publishing by @astrovm · Document the Rust crate in the README by @astrovm · Port the HTTP schemas to Rust by @astrovm Show all
      • What's Changed
      • Create the GitHub release automatically after publishing by @astrovm in https://github.com/timbagame/protocol/pull/58
      • Document the Rust crate in the README by @astrovm in https://github.com/timbagame/protocol/pull/59
      • Port the HTTP schemas to Rust by @astrovm in https://github.com/timbagame/protocol/pull/60 Full Changelog: https://github.com/timbagame/protocol/compare/v0.15.0...v0.16.0
  7. v0.15.0

    GitHub releaseSource-backed

    Update all dependencies · Update dependency node to v24.22.0 · Update @codama/renderers-js to v2.7.0 and regenerate clients by @astrovm · Update all dependencies · Add the timba-protocol Rust crate by @astrovm · Add EVM and chain-neutral game rules to the Rust crate by @astrovm… Show all
    • What's Changed
    • Update all dependencies by @renovate[bot] in https://github.com/timbagame/protocol/pull/50
    • Update dependency node to v24.22.0 by @renovate[bot] in https://github.com/timbagame/protocol/pull/51
    • Update @codama/renderers-js to v2.7.0 and regenerate clients by @astrovm in https://github.com/timbagame/protocol/pull/53
    • Update all dependencies by @renovate[bot] in https://github.com/timbagame/protocol/pull/54
    • Add the timba-protocol Rust crate by @astrovm in https://github.com/timbagame/protocol/pull/55
    • Add EVM and chain-neutral game rules to the Rust crate by @astrovm…
  8. v0.14.2

    GitHub releaseSource-backed

    Regenerated the versioned Solana clients for Codama 2.6.0 and shipped matching package declarations. Signer objects are accepted consistently by event encoders and PDA helpers; emitted JavaScript and wire formats are unchanged. Published @timbagame/protocol@0.14.2 to GitHub… Show all

    Regenerated the versioned Solana clients for Codama 2.6.0 and shipped matching package declarations. Signer objects are accepted consistently by event encoders and PDA helpers; emitted JavaScript and wire formats are unchanged. Published @timbagame/protocol@0.14.2 to GitHub Packages. Validation: 129 tests passed, the scoped 100% line-coverage gate passed, generated clients and distribution output were checked for drift, and GitHub CI and CodeQL passed.

Earlier ships (13)
  1. Code changes, week of 2026-10-05 – 2026-10-11 · 1 commit

    Code activitySource-backed

    What changed, in the repository’s own words:

    1 active day in timbagame/protocol.

    How HEY read this week

    This week HEY looked inside 1 commit to see what changed: 1 changed code. 4 automated commits (bot accounts or a repeating scripted message) not counted.

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

    Code activitySource-backed

    3 active days in timbagame/protocol.

    How HEY read this week

    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. 1 automated commit (bot accounts or a repeating scripted message) not counted.

  3. v0.12.0

    GitHub releaseSource-backed

    Shared game workflows, EVM HTTP schemas, creation authorization checks and action eligibility for the coordinated application updates.

  4. 2 releases in timbagame/protocol on 8 Sep

    GitHub release

    Show all 2 releases
    1. Protocol 0.12.0-rc.1

      GitHub releaseSource-backed

      Adds shared creation drafts and validation, chain-qualified game URLs and identities, EVM HTTP schemas, authorization response checks and caller action eligibility. Bot, Oracle and web can reuse the same rules while retaining their chain-specific signing, persistence and RPC… Show all

      Adds shared creation drafts and validation, chain-qualified game URLs and identities, EVM HTTP schemas, authorization response checks and caller action eligibility. Bot, Oracle and web can reuse the same rules while retaining their chain-specific signing, persistence and RPC adapters. The package is bumped to 0.12.0-rc.1 for coordinated consumer testing. Existing exports remain compatible. Tests cover exact amounts, network isolation, token-policy ambiguity and recovery permissions at timeout boundaries.

    2. Protocol 0.11.0

      GitHub releaseSource-backed

      Adds versioned EVM ABI and typed transaction builders, EIP-712 authorization, winner verification, normalized game lifecycle/events, and explicit Solana import aliases. Existing Solana imports remain compatible.

  5. 3 releases in timbagame/protocol on 5 Sep

    GitHub release

    Show all 3 releases
    1. Protocol 0.10.0

      GitHub releaseSource-backed

      Update Codama generation and toolchains, add generated event codecs, and correctly derive instruction PDAs for custom program addresses. Validated with 51 tests, typechecking, generated-client and distribution drift checks, and Node imports of all package entrypoints.

    2. Protocol v0.9.0

      GitHub releaseSource-backed

      Add shared Timba event codecs and trusted program-log extraction, preserving historical unjoin layouts and bigint values. Add contract-matching winner calculation and token-policy eligibility evaluation. Validation: 51 tests, typecheck, formatting, generated-client checks, and… Show all

      Add shared Timba event codecs and trusted program-log extraction, preserving historical unjoin layouts and bigint values. Add contract-matching winner calculation and token-policy eligibility evaluation. Validation: 51 tests, typecheck, formatting, generated-client checks, and build pass. Winner vectors were also verified against the Rust contract. Released from the reviewed merge of PR #18.

    3. Protocol v0.8.0

      GitHub releaseSource-backed

      Shared behavior for Timba bot, Oracle, and web: · Exact decimal-string and bigint amount conversion, rejecting excess precision and preserving zero-decimal balances. · Contract client and IDL selection for v0.2.0 and v0.3.0. · Shared game decoding and enum normalization.… Show all
      • Shared behavior for Timba bot, Oracle, and web:
      • Exact decimal-string and bigint amount conversion, rejecting excess precision and preserving zero-decimal balances.
      • Contract client and IDL selection for v0.2.0 and v0.3.0.
      • Shared game decoding and enum normalization.
      • Preserved account-decoder overloads and address inference, with compile-time regression coverage. Validated with 42 protocol tests, typecheck, generated package checks, CI, and consumer typechecks. Consumers should replace their temporary 0.8.0 package archives with this registry release and regenerate lockfiles. Changes…
  6. 3 releases in timbagame/protocol on 3 Sep

    GitHub release

    Show all 3 releases
    1. v0.7.0

      GitHub releaseSource-backed

      feat: add versioned Solana Kit clients by @astrovm Show all
      • What's Changed
      • feat: add versioned Solana Kit clients by @astrovm in https://github.com/timbagame/protocol/pull/15 Full Changelog: https://github.com/timbagame/protocol/compare/v0.6.0...v0.7.0
    2. v0.6.0

      GitHub releaseSource-backed

      feat: publish versioned contract artifacts by @astrovm Show all
      • What's Changed
      • feat: publish versioned contract artifacts by @astrovm in https://github.com/timbagame/protocol/pull/14 Full Changelog: https://github.com/timbagame/protocol/compare/v0.5.1...v0.6.0
    3. Protocol v0.5.1

      GitHub releaseSource-backed

      Patch release updating the Protocol runtime dependency to Zod 4.5.4. No Protocol API or generated output changes.

  7. 2 releases in timbagame/protocol on 2 Sep

    GitHub release

    Show all 2 releases
    1. Protocol v0.5.0

      GitHub releaseSource-backed

      feat: expose accepted token minimum by @astrovm Show all
      • What's Changed
      • feat: expose accepted token minimum by @astrovm in https://github.com/timbagame/protocol/pull/11 Full Changelog: https://github.com/timbagame/protocol/compare/v0.4.1...v0.5.0
    2. v0.4.1

      GitHub releaseSource-backed

      Preserve operator game closure refund amounts as exact u64 decimal strings in the indexer protocol.

Other changes on HEY’s record

37 changes on HEY’s record for Timbagame Protocol: 26 releases · 1 new Verified Builder or owner proof · 1 new project on HEY · 3 build pace changes · 6 other changes in 1 more kind.

All 37 changes for Timbagame Protocol →

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

Sources

1 place HEY reads for Timbagame Protocol