Changelog

All notable changes to this package are documented here. The format follows Keep a Changelog, and this package follows semantic versioning with one pre-1.0 caveat: a minor bump may change the API, a patch never does.

[Unreleased]

[0.2.3] — 2026-09-30

Added

• Additive tasra-sdk/app entry for typed slot operations, public EVM address lookup, exact-operation authorization, a registered wallet adapter and viem accounts.

• Durable prepared creation journals with known-transaction recovery and explicit refusal to retry an uncertain submission.

• Native FROST approval lifecycle, canonical approval payloads, strict IBE extraction, and operation receipt preservation/verification.

• Complete encrypted-notes, document-signing and native approval TypeScript examples, application guides and migration notes.

• committeeSignEoaDigest in tasra-sdk/committee for request-bound threshold Ethereum signing with verifier-agent compound tokens and membership proofs.

• SDK-only shared-account example that creates and provisions a tECDSA slot, confirms Alice/Bob transactions, and verifies Mallory’s server-side denial.

• Generated API reference and explicit SDK/deployment compatibility guidance.

Changed

• All 11 application-building skills lead with the current task workflow; specialized and compatibility details are available in supporting references.
• The shared-account tutorial always demonstrates durable prepared creation.
• The slot-provisioning example uses the creator’s signature instead of an admin JWT.

Fixed

• Keep recovery salts out of public tutorial evidence; select public creation references explicitly.
• Align note identity/result guidance with the API and include a complete standalone Node TypeScript configuration.
• Point skills and onboarding docs to the published Fuji deployment pointer, manifest checksum and service URLs in t3-foundry/tasra-releases; document bootstrap from a pinned repository commit.
• Narrow slot-creation results before reading the transaction hash in the skill’s direct/commit-reveal example.

Install tasra-sdk@latest from npm. Network operations require compatible contracts and services selected through a verified tasra-releases manifest.

[0.2.2] — 2026-09-23

Fixed

• Accept registered wallet Request Objects without transaction_data, while preserving operation and nonce binding checks. When transaction_data is present, continue to require exactly one entry matching the authorized operation, including its description.

[0.2.1] — 2026-09-22

Fixed

• Treat relay attempts with a consumed nonce outside the 10,000-block reconciliation window as terminal (unresolvable) and release the pending signer lock instead of retrying forever. Export the RelayReconciliation result type from tasra-sdk/chain. An unresolvable outcome does not prove that the operation failed; callers must check the resulting chain state before repeating the operation.

[0.2.0] — 2026-09-22

Added

• Per-commitment accountant seeds for faster slot creation on compatible deployments, with beacon-epoch fallback when a seed is unavailable.
• requestSlotSeed, resolveAccountantUrls, ACCOUNTANT_TAG, and the SlotSeed, SlotSeedOptions, and CommitRevealOptions types in tasra-sdk/chain.
• Seed-request options and a seeded result flag on createSlotCommitReveal.

Changed

• Commit/reveal slot creation tries a seeded reveal before waiting for the beacon. A failed seeded reveal through a relay propagates its error to preserve relay retries.
• KeyRegistry ABI includes seeded reveal methods, commitSeedDigest, and related events and errors.

[0.1.0]

Initial release of tasra-sdk: a TypeScript access layer for the Tasra network.