IYInnovative You

Build record

Jara

active

An EVM NFT execution system for controlled multi-wallet minting, with policy-bound execution, durable recovery and auditable transaction handling.

Classification
Software / Onchain system
Current focus
Personal Alpha
Last updated
Jara mini-app product mockup showing the mascot, wallet readiness, active job, treasury balance and Emergency Lock interface
Locked Jara product and interface mockup.

What

Jara separates its control plane, execution and signing boundaries so mint intents can move through policy, readiness, authorization and transaction handling as durable work.

System facts

  • Control plane, execution and signing are isolated service boundaries.
  • Mint intents become durable jobs rather than executing inside Telegram handlers.
  • Multi-wallet jobs preserve an immutable execution set and enforce a shared Target Total.
  • Resolver, simulation, policy, funding readiness and Emergency Lock checks happen before transaction authority.
  • Personal Alpha connects preparation, signing, submission, monitoring and reconciliation boundaries.
  • Configured V1 chain work covers Ethereum, Ink and Robinhood Chain, with readiness differing by execution path.

Boundary

  • Production signing remains intentionally unselected.

Evidence

Log

  1. Made Telegram mint flows safer to operate.

    Active multi-step mint flows now extend while they are in use, stale or superseded actions expire, and validation failures return controlled guidance instead of raw runtime errors.

  2. Hardened the Personal Alpha execution path.

    Continued the control-plane-to-execution integration and tightened transaction lifecycle handling, including first-observation receipt reorg behavior.

  3. Turnkey signing reached the selected execution wallet.

    Bound the development signer to the execution wallet and fixed the confirmed-wallet preparation transition that had stopped the worker before execution.

  4. Built the first controlled Ink mint path.

    Added read-only Ink preflight and controlled target registration so Personal Alpha could validate a real target before execution.

  5. Personal Alpha moved into the Telegram interface.

    Added durable interactive flows so the owner path could be operated through the control plane instead of command-line-only setup.

  6. Personal Alpha got a durable execution worker.

    The owner-only worker connected durable jobs to the existing preparation, signing, submission, monitoring and reconciliation boundaries.

  7. Proved the multi-wallet execution path at 64 wallets.

    The non-production execution test prepared a 64-wallet run around a shared Target Total, with overfill protection preserved.

  8. Telegram became the control plane.

    Added access-code onboarding, wallet selection and durable mint intents. Telegram creates queued work rather than signing or broadcasting inside the handler.

Stack

  • TypeScript
  • Node.js
  • PostgreSQL
  • viem
  • Telegram
  • Turnkey