Introducing By The Deed SDK v1.0.0

Turning gameplay into verifiable Proof of Play—without putting AI, blockchain, or a hosted service in the critical path.

Games already know what players do.

They know when a player defeats a boss, completes a difficult run, discovers an area, reaches a score, collects an item, or performs a sequence of actions.

But those accomplishments usually stop at the boundary of the game.

By The Deed SDK v1.0.0 is our first step toward changing that.

@btdworks/sdk gives developers a TypeScript foundation for capturing typed gameplay events, evaluating them against deterministic game-defined rules, and turning successful verification into portable Proof-of-Play credentials. AI interpretation and Solana publication are available as optional layers rather than requirements.

Your actions are your proof.

From gameplay to proof

The core idea behind By The Deed is deliberately simple:

Play → Capture → Verify → Prove → Own

A player does something meaningful inside a game. The game captures the relevant evidence. By The Deed evaluates that evidence against rules defined by the developer. A successful result can then become a portable credential owned by the player.

For example, a game might define an achievement that requires a player to defeat a specific boss with a critical hit.

Instead of simply trusting a client-side "achievement_unlocked": true flag, the SDK can evaluate the underlying gameplay evidence:

btd.achievements.register(
  achievement("boss-breaker")
    .named("Boss Breaker")
    .when(
      event("enemy_defeated")
        .where("enemyId", "equals", "boss_01")
        .and("critical", "equals", true),
    )
    .build(),
);

The resulting verification records which rules passed, which events matched, reason codes, confidence, and a SHA-256 evidence digest. Credentials can only be issued after successful verification.

Game-defined rules come first

One of the most important decisions in v1.0.0 is that AI is not the verifier by default.

The SDK includes a deterministic rule engine supporting comparisons, AND/OR/NOT composition, counts, sequences, time windows, and aggregations. Rules are plain serializable data, so developers can version them, review them, store them, and test them independently of an AI provider.

That distinction matters.

A game developer should decide what constitutes an achievement. By The Deed provides the infrastructure to evaluate that definition against captured evidence.

Intelligence when context matters

Not every accomplishment fits neatly into score >= 50,000.

Some gameplay situations require context.

For those cases, v1.0.0 includes an optional server-side OpenAIInterpreter. It uses structured output, bounded retries and timeouts, metadata redaction, and treats supplied gameplay events as untrusted input.

Interpretation remains supplementary by default.

AI cannot independently approve a credential unless the developer explicitly configures the achievement to allow it and the interpretation satisfies the required confidence threshold.

This gives By The Deed two complementary verification layers:

Rules determine what must be true. Context helps understand what happened.

Portable Proof of Play

Once an achievement has been verified, the SDK can issue a JSON-friendly Proof-of-Play credential.

The credential packages the verified claim together with its evidence digest. Without a custom signer, v1.0.0 generates a transparent DigestProof; applications can also inject a protected signer when stronger cryptographic signing is required.

The credentials are inspired by verifiable credential models, but v1.0.0 intentionally does not claim full W3C Verifiable Credentials compliance.

The goal at this stage is straightforward:

Make meaningful gameplay accomplishments portable and independently verifiable.

Solana is optional

By The Deed can also take a verified credential and prepare its canonical digest for publication on Solana through the dedicated @btdworks/sdk/solana integration.

Raw gameplay history does not need to become public blockchain data.

The intended model is:

Gameplay evidence stays private → verification happens → canonical proof is created → only the digest is optionally published.

The included Solana adapter in v1.0.0 is a mock and does not submit real transactions; production integrations are expected to construct, sign, submit, and confirm publication through their own real adapter.

Built to live inside real games

The SDK is written in strict TypeScript and supports Node.js 20+. Its event map provides compile-time-safe gameplay payloads, while event envelopes are validated at runtime.

v1.0.0 also includes the foundations needed around the verification engine: session lifecycle management, event ordering and deduplication, payload and buffer limits, memory and browser storage, HTTP transport, typed lifecycle events, mocks, stable errors, and injectable adapters.

The architecture stays modular:

Game
  ↓
BtdClient
  ↓
Capture Events
  ↓
Deterministic Verification
  ├── Optional OpenAI Interpretation
  ↓
Verified Result
  ↓
Proof Credential
  └── Optional Solana Publication

Developers can therefore start completely offline and add external infrastructure only when their game actually needs it.

What v1.0.0 does—and doesn't—prove

Proof of Play should not be confused with proof that a game client was honest.

By The Deed verifies that supplied evidence satisfies a defined achievement rule. Authoritative telemetry, server validation, and anti-cheat remain responsibilities of the game integration.

That boundary is intentional.

By The Deed is the proof layer—not the game's anti-cheat system.

For achievements carrying competitive or economic value, v1.0.0 recommends capturing authoritative server events, keeping sensitive credentials server-side, using opaque player IDs, and publishing only canonical digests to public chains unless players explicitly consent otherwise.

This is the beginning

v1.0.0 establishes the foundation.

The roadmap currently includes dedicated Unity, Unreal Engine, and Godot integrations, hosted rule tooling, managed verification, streaming ingestion, anti-cheat and anomaly signals, cross-game reputation, credential status and revocation, wallet identity, compressed Solana credentials, additional adapters, realtime subscriptions, analytics, and schema tooling. These are planned directions rather than promised release dates.

The larger idea remains the same:

Games shouldn't have to reduce everything a player has accomplished to an isolated badge inside one database.

A deed can become evidence.

Evidence can become proof.

And proof can belong to the player.

By The Deed v1.0.0 — Your actions are your proof.

npm install @btdworks/sdk

Built by Btd Works.