TASKWIRE desk 01
Connecting to the wire…

DISPATCH No. 0001//SOLANA MAINNET

Every agent request, wired to the result it produced.

Taskwire is a task ledger you keep in your browser. Each request and its outcome is hashed into a chain, signed with Ed25519, checkable by anyone with the receipt, and, when you choose, anchored to Solana mainnet with a single memo.

File a dispatch Verify a receipt
live ping dispatch slip pinging services…

    § 01

    Wire conditions

    Mainnet, read through our same-origin RPC relay. Refreshes every 20 s while this tab is open.

    Slot

    000000000

    confirmed

    Throughput

    0000

    tx / s, last 60 s

    Slot time

    000

    ms per slot

    Epoch

    0000

    progress through the current epoch

    Transactions per second, last 30 one-minute samples · getRecentPerformanceSamples

    § 02

    The method

    Four stations every task passes through. Nothing here is a promise; each step is code you can read in this page.

    1. 01 · REQUEST

      Write it down

      Name the agent, what was asked and what came back. Plain text, kept only in this browser.

    2. 02 · HASH

      Chain it

      The entry is serialised in a fixed key order and hashed with SHA-256 together with the previous entry's hash. Change one letter and every later link breaks.

    3. 03 · SIGN

      Sign the receipt

      The hash is signed with Ed25519: either a session key made in this tab, or your Solana wallet through signMessage. Same curve either way.

    4. 04 · ANCHOR

      Pin the head

      Optionally write the latest hash into an SPL Memo on mainnet. Anyone can then see your ledger existed in that state at that slot.

    § 03 · TOOL

    The task ledger

    Hash-chained and signed in your browser. Stored in this browser's local storage, nowhere else. Export it any time.

    Entries
    0
    Head
    —
    Chain
    empty
    Signer

    Session key … lives in this browser only and holds nothing.

      No dispatches yet. File one above or fill a sample.

      § 04 · TOOL

      Receipt verifier

      Paste any Taskwire receipt. We recompute its hash and check the Ed25519 signature against the signer's public key, right here, with no server.

      • Well-formed receipt
      • Hash matches the entry body
      • Ed25519 signature valid for signer
      • Links to a known previous entry

      Signer type and key are shown after checking.

      § 05 · TOOL

      Wire status directory

      The services an on-chain agent leans on, pinged from your browser. Latency is round-trip from you; each probe asks for something real and shows what came back.

      ServiceProbeAnswerLatencyLast 8

      § 06

      The life of one dispatch

      Scroll to follow your newest entry through the wire. The bytes below are the real ones from your ledger.

      1. Filedagent · request · result
      2. Serialisedfixed key order, UTF-8
      3. HashedSHA-256 with previous head
      4. SignedEd25519 over the hash
      5. AnchoredSPL Memo, optional

      § 07 · TOOL

      Anchor the ledger head

      One SPL Memo transaction, signed in your own wallet, writes your ledger head hash to mainnet. It costs a network fee and nothing else. It moves no tokens.

      Write the head

      memotaskwire:v1 head=… n=0

      Program
      MemoSq4g…fcHr
      Fee
      —
      Signer
      connect a wallet

      Check an anchor

      Anchors by address

      Memos posted by an address, read from getSignaturesForAddress (latest 100 signatures). Your wallet fills this in when connected.

        § 08

        Receipt format

        Version 1. Small enough to paste into a chat, strict enough to verify without trusting us.

        {
  "v": 1,
  "kind": "taskwire.receipt",
  "n": 4,                          // position in the chain, from 1
  "ts": "2026-11-05T10:42:13.000Z",
  "agent": "research-bot",
  "request": "…",
  "result": "…",
  "prev": "9f2c…",                 // hash of entry n-1, or 64 zeros
  "signer": "base58 Ed25519 public key",
  "scheme": "session-ed25519 | solana-wallet",
  "hash": "sha256(body)",           // body = the fields above, in this order
  "sig": "base58 Ed25519 signature of 'taskwire receipt\n' + hash"
}
        • Body is JSON.stringify of v, kind, n, ts, agent, request, result, prev, signer, scheme in that exact order.
        • Signed text is the line taskwire receipt, a newline, then the hex hash. Wallets show this text before you approve.
        • Wallet receipts verify with the wallet address itself: a Solana address is the Ed25519 public key.
        • Anchor memo reads taskwire:v1 head=<hash> n=<count>.

        § 09

        Questions on the wire

        Where is my ledger stored?

        In this browser's local storage only. Taskwire has no database and no account. Export the JSON to move it or back it up; clearing site data deletes it.

        What is the session key?

        A random 32-byte Ed25519 seed made in this tab with the browser's secure random generator and kept in local storage. It signs receipts and nothing else. It is not a wallet, holds no funds and never leaves your machine.

        Why would I sign with my wallet instead?

        So a receipt carries your public Solana identity. The wallet shows the exact text before signing. A message signature cannot move funds and is not a transaction.

        What does anchoring cost, and what can it do?

        One Memo transaction: the base network fee shown in the review sheet, usually 5,000 lamports. It writes text to the chain and moves nothing. It proves your head hash existed by that slot. It does not prove the tasks themselves were done well.

        Are the service latencies real?

        Yes. Each row is a live request from your browser to that public endpoint, and the answer column shows what it returned. They are your round trips, so they depend on your connection.

        Is there a Taskwire token or a server-side agent?

        No agent runs on our side and the site holds no funds. If a community coin is ever linked here, it will appear in the header and footer with its contract address, and nothing on this page depends on it.