Gora's agent testnet is live, and its demo app is an AI fund you can join

Gora¹ is a network of off-chain computers that run an app's code and sign what came back, so a smart contract or a wallet can act on an answer a majority of independent machines agreed on. Its testnet is live — the Gora developer docs² say so plainly and the endpoint they name answers — and the part of it a non-developer can use today is an AI trading fund you open in a browser, watch make decisions, and deposit testnet GORA into.

The AI fund, as a visitor sees it

The app is called Gora Trading Bot³ and it opens on numbers before prose: a fund NAV of 1.0266 GORA per share, up 2.66% over 48 steps, 25.7k GORA in assets, and 40 depositors. NAV — net asset value, the fund's price per share — is the rate a deposit would buy at. Below the figures sits the decision card: the strategy is MOMENTUM V0, the call is STAY FLAT at 55% confidence, and the reasoning is a sentence rather than a black box — 'No edge: price is oscillating around the mean. Staying flat costs nothing and keeps capital ready.' Two truncated hashes follow, one for the prompt sent to the model and one for its response, and the inference is attributed to 'Gora validators (P1)'.

A button offers to run a strategy step yourself, and clicking it added a new entry at the top of the decision log, marked attested and carrying its own pair of truncated hashes. Each entry pairs a step number and that 'attested' tag with the model's one-line rationale: the log records a depositor joining with 1,250.00 GORA and shares minted at a NAV of 1.0142, and a decision to hold a long position because the price was still above its mean and the drawdown from entry within tolerance.

Joining means depositing GORA for shares at the current NAV, with withdrawal any time and no lockup, per the page's own terms. Getting that GORA means using a faucet, and the bridge exposes one for Algorand. Twenty-five thousand GORA across forty depositors is demo scale, and the GORA in it is a test asset; assets on a testnet, the experimental copy of a blockchain, carry no monetary value.

A raffle with an on-chain prize pool

The bridge's other app is a raffle⁴, and it shows how much of the rule set can sit in a contract. 'Enter for free. Every draw period, the on-chain prize pool pays 3 random registered users in GORA,' its page reads, adding that entering opts your Algorand account into the raffle application and that your wallet approval is signed by your key and verified by the network. The Algorand application behind it stores the whole rule set as parameters rather than promises.

Sources: 6 lora.algokit.io, 6 gora.mintlify.app, 6 gora.mintlify.app, 8 lora.algokit.io +1

How an answer gets signed

None of this is a blockchain of its own. 'The Gora network is not a blockchain — it agrees on app outcomes and writes attestations to whichever chain the result targets,' the docs state¹². Validators stake GORA on Algorand, Base or Solana and sign inside rounds with a participation key, while the owner key that authorises them stays cold. A request enters, a committee is picked for that round, the committee runs the app, and the result it agrees on comes back signed; anyone holding the validators' public keys can check the signatures, and a contract can check them on-chain.

An app is off-chain code — WASM, JavaScript, TypeScript or Python — plus a manifest¹³ and a policy¹⁴. The policy is the part worth knowing about: it limits which chains the app may touch, which action types it may request, how much it may move per transaction and per day, and which recipients it may pay. The fund's own manifest states that the Gora node does not hold user keys and does not pay a user's gas, with the user or a pre-approved account paying by default. The code decides and returns an instruction; it never holds a private key or moves money itself. Randomness¹⁵ arrives as a side effect of the same machinery, since selecting a committee already requires each validator to publish a verifiable random output, and an app or a contract can request that number bound to its own request id. The docs describe it as a sealed envelope that anyone with the validator's public key can confirm was decided before the round began.

The documentation also does not oversell what is wired. It says outbound HTTP calls¹⁶ work for WASM apps only today, that the quorum-fetch mode is 'the target design and are not all wired yet', and that the whole arrangement has a 'testnet v1' trust model.

Why agents need this, and what else does it

The intended user is an agent — a program that observes, decides and acts without a person pressing a button. Gora's April 20 manifesto¹⁷ makes the operational argument: an agent that has to read from Solana, call an API, compute something and write to an Algorand contract currently gets stitched together from separate services, 'each with its own failure modes, each controlled by a different party', and the people affected by an agent's action need to know it happened correctly, 'not because someone said so, but because the execution is independently verifiable'.

Gora is not alone in that claim. Chainlink¹⁸'s verifiable-AI material describes routing AI inference through a decentralized network of nodes to remove single points of failure, and 0G markets verified compute, persistent memory and onchain settlement for agents on a mainnet its announcement says has run since September 2025. Gora's difference is placement rather than capability: it does not ask an agent to move to a new chain, and the answer it produces is written to whichever chain the contract already lives on. On Algorand, the Foundation's AC2¹⁹ protocol, released August 25, speaks to the neighbouring problem — letting a person approve an agent's actions with a passkey while keys stay on the device — where Gora's user-facing equivalent is a signing request a phone reviews. The project's older dashboard²⁰ still lists oracle feeds, a node portal and a vesting portal next to a 'Current Rate of Return' of 10%²¹, and it routes stakers to a separate staking site²² whose validator list footer reads 'Showing page 1 / 1 (36²³ results)' beside a panel telling holders to 'Stake your $GORA on ERC-20 to your favorite validator' and marked 'Coming Soon!' — a pagination string, not a count of validators running on this network, so the agent network and the older oracle business currently sit side by side.

What the on-chain records show

Every contract in the table was created by one Algorand testnet address, which also holds the manager key of the test GORA asset. A manager key can change an asset's configuration, which is the one point of retained control in the set; that asset's freeze and clawback addresses are zeroed, so nobody can freeze a holder's balance or pull tokens back. For contrast, the mainnet GORA asset recorded with gora.io as its URL has its manager, freeze, clawback and reserve fields all unset — nothing left that can mint or seize. No audit of any of this appears in the docs or on the site, and the public GoraNetwork GitHub org²⁴ lists 15²⁵ repositories carrying 20 stars between them, its most recently pushed repo updated in April 2025, while keyword searches for the protocol-core validator code the docs describe returned no repository.

There is also a label worth reading closely. The dev bridge's broadcast log returns 31 events, and the proof object on each is typed 'mock_gora_quorum_v1', with a validator set of 'devnet-mock' and a quorum of 'mock' — these are the bridge's own mobile-signing submissions to Algorand, and the quorum behind them is a stand-in rather than the committee the docs describe. The validator list is not much sturdier: four validators are registered²⁶, every one reports its status as 'Crashed', and round summaries show uneven participation, with one validator committing seven rounds inside its last fifty log entries and another recording eleven failures. Voting power is lopsided too.

On the shared testnet, a developer's identity²⁷ is a bearer token they invent: the first token to deploy an app id owns it, and only that token can upgrade the app, manage its schedules or read its state, which makes ownership the secrecy of a string you chose. The live surfaces also sit away from the project's own domain — the docs are hosted at gora.mintlify.app, the node endpoint is a bare IP address reached through nip.io wildcard DNS, www.gora.io/docs²⁸ returns a 404 and docs.gora.io does not resolve — while the homepage still reads 'COMING 05/01' and 'Launching Soon' above a network whose endpoints already answer; a Wayback capture from May 10, 2026²⁹ carries the same wording.

Two things this pass could not confirm. The docs say³⁰ the iOS and Android apps 'ship preconfigured with the live bridge', but App Store searches for Gora Network, Goracle and Gora wallet returned only unrelated apps, so whether a phone client is installable today is unknown; the bridge's mobile-signing inbox does return four requests, including signed raffle entries, so the flow is running from somewhere. And on Algorand mainnet, the GORA asset³¹'s largest listed pool on Tinyman held about $3,100 and posted under $2 of volume in 24 hours at the time of the check.

How to start, and what to watch

A developer needs no signup and no GORA to get in: one curl command³² installs the CLI, you set a developer token of your choosing, point it at the endpoint, and deploy; deploying and invoking are free on the testnet, and an invoke draws roughly 106³³ billing units from a seeded developer balance. Node binaries for macOS and Linux sit on the endpoint's release mirror at v0.1.1, and the Algorand gateway, staking and raffle applications are already deployed for a contract to talk to.

For everyone else, the fund and the raffle are the two browser doors, both on testnet and both free to look at. Gora's Discord server³⁴, where the raffle says winners are announced, showed 19,816 members with 202 online at the time of the check, while the project's Telegram channel @goranetwork³⁵ counts 274 members and has not posted since June 2024. The thing to watch is whether the project's front page catches up to the network it now describes, and whether the four validators stop reporting 'Crashed'. The raffle's next draw is the easiest payout here to follow end to end: three registered users, paid from a pool whose rule set sits in a contract.