• v1.0.0-beta.97 282c9639b6

    Beta 0.97 Pre-release

    ai17z-mirror released this 2026-11-16 10:54:46 +00:00 | 1 commits to main since this release

    Install

    Copy the command for your operating system and paste it into a terminal.

    Windows 10 and 11: open Windows Terminal and paste:

    irm https://raw.githubusercontent.com/ShiftAboveCtrl/ai17z/main/install.ps1 | iex
    

    macOS 13 or newer (Apple silicon and Intel): open Terminal and paste:

    curl -fsSLO https://raw.githubusercontent.com/ShiftAboveCtrl/ai17z/main/install-ai17z-macos.sh && bash install-ai17z-macos.sh
    

    Ubuntu 22.04 or newer (amd64 and arm64): open a terminal and paste:

    curl -fsSLO https://raw.githubusercontent.com/ShiftAboveCtrl/ai17z/main/install-ai17z-ubuntu.sh && bash install-ai17z-ubuntu.sh
    

    If GitHub is down, the same installers are on AI17Z Code, AI17Z's own server:

    irm https://code.ai17z.io/AI17Z/ai17z/raw/branch/main/install.ps1 | iex
    
    curl -fsSLO https://code.ai17z.io/AI17Z/ai17z/raw/branch/main/install-ai17z-ubuntu.sh && bash install-ai17z-ubuntu.sh
    

    The installer checks your system, offers to install anything missing, then
    installs AI17Z and starts it. It downloads from GitHub, or from AI17Z Code when
    GitHub cannot provide a file, and checks every download against this
    release's SHA256SUMS.txt before it is used. AI17Z needs Docker, and
    Google Chrome for browser features. On Windows the installer also sets up
    WSL 2 and Node.js 22 or newer through Microsoft's own tools, and opens
    AI17Z when it is ready. No security setting is changed.

    Full installation guide ·
    What the installer does ·
    Uninstalling

    What's new

    Beta 0.97 teaches the token evidence card to answer more kinds of question, from screenshots to single transactions, and adds a set of opt-in Studio features.

    What changed since Beta 0.96

    Token checks read more, and say what they could not read. Every answer below keeps the card's rules: each reading carries its source and time, a reading that is missing says so and is never shown as zero, and no reply names a winner, calls anything safe or unsafe, or gives a verdict.

    • Check a token from a screenshot. A "check this" mention with no address in its text sends the attached image, or the image on the post above, to the vision role. Only a full Solana or EVM address is accepted. The reply opens with read from your image: <address> so a misread is visible. It refuses with a sentence when the image holds two addresses, when an address is shortened or unclear, or when a shortened copy disagrees with the full one. An address typed in the text always wins and the image is not read.
    • Why is it moving. A message such as "why is moving" gets then, now and change for price, volume and liquidity over 5 minutes, 1 hour (the default), 6 hours or 24 hours, each with its source, read time and pool depth. A missing earlier reading says so. The reply always ends "caused by: unknown, readings only". It reads market sources only, never X.
    • Explain this transaction. One Solana signature, bare or inside an explorer link, gets a fixed reading from the node: status, slot, block time, fee, the programs called, each instruction's decoded type and each account's SOL and token balances before and after. Anything not recorded prints "not recorded" and a section the node did not send prints "not read". It never guesses intent, never says who owns an address and never talks about profit or loss. Two signatures, a string that is not a signature, or a "whose is this" question get a one-sentence refusal and no read.
    • The deployer. The card names the account that paid to create the mint, but only when the chain proves it: the mint's oldest signature must have succeeded and carry initializeMint for that exact mint. Otherwise the deployer is reported as unavailable. A launch count appears only when the index agrees with the chain.
    • LP burn and lock. For Solana pools the card adds how much of the LP supply is burned and how much sits in a Streamflow lock that has not ended, with the unlock time. A missing pool or unreadable account prints LP status: unavailable, never 0% or "not locked". A holder that is a program or escrow account is reported as held by a contract and is not counted as locked. Streamflow escrow accounts cannot be traced to their stream within the allowed reads, so those locks read as held by a contract for now.
    • Holder map. With tools.holderMap on, a "holder map" ask about a Solana token gets a picture of its top holders, grouping accounts first funded by the same address. It reads at most 12 holders. Program-owned accounts and program funders are never grouped. The funding address never leaves the installation, and the picture carries an opaque group id only. The wording is fixed: a reading, not proof of one owner, not a verdict. It falls back to text when Studio is unlinked or slow.
    • Check A vs B and the card as a picture. Two addresses on one chain answer with both cards side by side, in the order asked and with no ranking. tools.evidenceCardImage adds an optional picture of the card from the linked Studio, and any failure sends the text card unchanged.
    • Follow up when a confirmed watch crosses. With tools.evidenceFollowUps on, the agent can reply once under the post that asked, with the before, at-card and current values. The text is fixed, no model writes it, and each crossing is answered at most once.

    The transaction explainer and the "why is it moving" reply use the existing evidence card switch, tools.evidenceCards, which is off by default. Both keep its asker limits, cooldowns and research budget, and both check the switch and permission again before sending.

    Two new posts built from what the agent already read. Both are off by default and advanced only.

    • Narrative pulse. A daily post that sets what the agent's own reading is talking about beside what people checked on AI17Z Studio. It is built only from posts already read, so it adds no read of X. Subjects are ordered by share, each with its sample size. "Rising" needs a measured snapshot 12 to 48 hours old and a 1.5 times move. Subjects the agent stays quiet about, names of accounts or people, and subjects with coordination signals are dropped. The post says it does not endorse anything and says when the checks half could not be read. Switches: studio.postNarrativePulse and studio.contributeNarrativeTerms.
    • Weekly receipts recap. A weekly post listing every signal the radar published in the last seven days with what each stated reading measured 24 hours later. Counts and readings only, small samples say "n = 4", and there is no win rate, profit or ranking. Only signals that were really published count. Switches: studio.postReceiptsRecap and an optional picture, studio.receiptsRecapImage. Any picture failure posts as text.

    Studio features.

    • Coin alerts from Studio can become the radar's universe, per agent, with an owner switch under the risk watches panel. Only token addresses are imported, at most 25, one per poll inside the usual read budget. They are noticed, never answered on their own.
    • The "most checked today" board has two opt-in settings, studio.contributeChecks and studio.postMostChecked. Only the mint, the hour and the number of distinct askers are sent, and only for checks made after the owner opted in.
    • An owner can publish the agent's paper setup to Studio as a holder playbook, after previewing the exact document.
    • A paper record post can end with the link to its proven page on the linked Studio (studio.linkPaperRecord).
    • An agent can state facts about the $AI17Z token from Studio's published document (ai17z_token.facts, off by default).
    • Activity tape receipts record which network a reply went out on.

    Telegram has two new read-only commands. radar shows what the radar is watching and what it found most recently. standing shows each agent's latest league entry and fill counts, or says there is none. Farcaster reads now have a budget of their own, 60 reads per 10 minutes by default, so they no longer draw on X's.

    A receipt claim can no longer deadlock a finishing read. The weekly claim and a read finishing the same receipt took database locks in opposite orders, and CI caught one deadlock. The two-window guarantee was never broken. The claim now takes a lock that still keeps claimers apart but no longer blocks the other side's foreign key check.

    Update check. update-ai17z -Check now reads its release source in the right order.

    This adds migrations 0138 to 0142.

    Known limits

    Several of these features need Studio routes that ship separately, and until they are live the feature reports Studio as unavailable or posts text alone: the evidence card picture, the holder map picture, the receipts recap picture, coin alerts, the check board and the narrative pulse checks half. Everything here has been exercised against mocks and test databases. No run used a live Solana node, a live vision model reading a real screenshot, or live X. The transaction reader does not yet cover address lookup tables or Token-2022 fields.

    Upgrading

    Use the updater belonging to the installation you want to update. Beta 0.97 uses the semver tag v1.0.0-beta.97. GitHub Actions builds the Windows, Ubuntu and macOS packages and verifies the published release files.


    What changed since v1.0.0-beta.96, commit by commit
    • Beta 0.97
    • Stop the receipt claim deadlocking a finishing read (#47)
    • LP burn and lock on the token evidence card (#46)
    • Holder map with same-funder grouping (#45)
    • Narrative pulse: talked about against checked, from posts already read (#44)
    • Explain this transaction: a sourced reading of one Solana signature (#43)
    • Why is it moving: a measured what-changed reply (#42)
    • Owner switch for Studio coin alerts (#41)
    • Telegram radar and standing commands, Farcaster read budget (#40)
    • Weekly signal receipts recap, with an optional picture (#39)
    • Check a token from a screenshot (#38)
    • Show the deployer on the token evidence card, proven from the chain (#36)
    • Coin alerts become the radar's universe (#35)
    • Most checked today board, core side (#37)
    • Check A vs B: two evidence cards side by side (#34)
    • Evidence card as a shareable image (#33)
    • Follow up on an evidence card when a confirmed watch crosses (opt-in) (#32)
    • Let an agent explain the AI17Z token from Studio's published facts (#31)
    • Record the publishing network on activity tape receipts (#30)
    • Close a paper record post with its proven page link (opt-in) (#29)
    • Publish an agent's setup as a holder playbook (#28)
    Which file is which

    You do not need to download anything by hand: the commands above fetch what
    they need. These are here for anybody who wants a specific file.

    File What it is
    AI17Z-Setup-1.0.0-beta.97.exe Classic Windows installer. Unsigned; the command above is the recommended route
    install-ai17z-macos.sh macOS installer script, the same file the macOS command runs
    install-ai17z-ubuntu.sh Ubuntu installer script, the same file the Ubuntu command runs
    AI17Z-macos-arm64-1.0.0-beta.97.tar.gz, AI17Z-macos-x64-1.0.0-beta.97.tar.gz macOS application, Apple silicon and Intel
    ai17z_1.0.0-beta.97_amd64.deb, ai17z_1.0.0-beta.97_arm64.deb Ubuntu packages
    SHA256SUMS.txt SHA-256 of every file
    SHA256SUMS.txt.sigstore.json Signature of SHA256SUMS.txt, verifiable against ci/cosign.pub
    install.ps1 Used by the installer: the file behind the Windows command
    Install-AI17Z-1.0.0-beta.97.ps1 Used by the installer: the Windows setup program it checks and runs
    AI17Z-App-1.0.0-beta.97.zip Used by the installer: the application the Windows setup program installs
    release-manifest.json Used by the installer: what this release is and what it needs, read before an update
    release-notes.md Used by the app: these notes, shown on its update screen

    The setup audit (AI17Z-Setup-Audit-1.0.0-beta.97.json) and a signature for every
    file are published on AI17Z Code.

    The macOS and arm64 Ubuntu packages are assembled on Linux and accepted only
    when every native file in them is byte for byte one a machine of that platform
    built and ran (ci/native-references.json).

    Verify a download
    cosign verify-blob SHA256SUMS.txt --bundle SHA256SUMS.txt.sigstore.json --key cosign.pub
    sha256sum --check --ignore-missing SHA256SUMS.txt
    
    d47efe1cd915f5e8625179d06501f62f49a3d87c9ea74e005303b3f1e6c23f2c  AI17Z-Setup-1.0.0-beta.97.exe
    27942d3a537aac05857040b9acd2b993390709738a16c22c5a3af3fe24f4a4de  install.ps1
    c4b1bbbed2ffd79bb698c2f6dbeacaa1c64e863aa370d7f160e0b5e650d9599b  Install-AI17Z-1.0.0-beta.97.ps1
    6b9c09deda77fc5e6ced9ce2205994093185396b5605dd42db73b24fd93258b0  AI17Z-App-1.0.0-beta.97.zip
    ddfa99cc627884a7004a7d04317a9f1424d9716d4a91e7b6705f6d2c782eaed6  install-ai17z-macos.sh
    d5ec40e5d07aa53cbf51ca905b0e1003e2c04d53bafe3fdcbebcb4dd64c00b5d  install-ai17z-ubuntu.sh
    b5f77c29235cd42a7db3f46c7a411b51ae4c693111a906c43f42312851c47145  ai17z_1.0.0-beta.97_amd64.deb
    ef530addf03809bdff7b2ccffc9ec13242f536e3a57183cb916c42a8e6d3408c  ai17z_1.0.0-beta.97_arm64.deb
    8f3153c16137c31d9717e373dd892e17b8673736a68895dbdb32515e3038e6cc  AI17Z-macos-arm64-1.0.0-beta.97.tar.gz
    eabb8f768054d0c989420b7b24fdb6393c6d6c54938411aa059cc4ec9f3b425c  AI17Z-macos-x64-1.0.0-beta.97.tar.gz
    

    Install AI17Z only with the commands above or from this release page.
    Nowhere else distributes it.

    Downloads