FAR — Arweave Position Forecast

Personalize this dashboard

Add a wallet and a net cash target.

The target can be a mortgage, deposit, runway, or any other goal. Forecast coverage is cash after modeled tax, exit cost, and debt payoff.

Privacy: wallet balances are public. The address is sent to Arweave/AO data services for read-only lookups; the cash target is never sent with that request.

Forecast

Price the long arc.

Add a wallet and target to model position size, capital required, outcomes, financing risk, and an exit rule.

Personal inputs required

The forecast starts from your actual public AR balance.

No wallet or target is prefilled. Your target remains local to this device.

Set up forecast ↑

Research lenses

Evidence behind the forecast

Market, network, wallet and code data answer different questions. Use them to challenge the scenario above.

Thesis monitorElevated risk6 open signals · 2 critical

AR / EUR1,57 €-0.3% 24h

AR market cap103,16 Mio. €Rank unavailable

PortfolioNot loadedAdd wallet above

Network1.97M253 peers seen

Updated05 Aug, 12:00UTC

AR 24h volume3,59 Mio. €

AO / EUR1,56 €-0.5%

AO market cap9,56 Mio. €

Reward pool345.04K ARzero debt supply

Global crypto cap—unavailable

What matters now

Signal board

Facts first. Interpretation second. Every alert tells you what it does—and does not—mean.

AR market pulse

1,57 € -0.3% today

CoinGecko / DefiLlama · 30d

AR price -10.4%Market cap -10.4%Both indexed to 100

07 Jul30 days05 Aug

Market cap103,16 Mio. €

24h volume3,59 Mio. €

Implied circ. supply65.7M AR

AR regime-73.9% 1y · -98.0% ATH

AR is in a deep long-horizon drawdown

A severe drawdown changes miner, treasury, and holder economics in fiat terms. It does not by itself measure protocol usage.

AO asset-87.2%

AO remains far below its one-year reference

AO is a separate asset from AR; its liquidity and value capture must be judged separately.

Market-10.4%

AR 30-day momentum is negative

Use this as market context, not as evidence of network usage.

Code72% top share

Recent core work is contributor-concentrated

A small number of people authored most commits in the latest GitHub samples. Review quality and bus factor matter.

Your position

Public wallet

What is visible on Arweave and in the canonical AO token process. Exchange balances and cost basis are not visible.

No wallet loaded

Connect the dashboard to any public Arweave wallet.

Global market, protocol, code, and risk data remain available without a wallet.

Add wallet + target

Simple mental model

How it works

Arweave stores the record. AO computes over messages. They share settlement, but they are not the same system.

The one-line model

Pay once to add data to an ordered archive. Miners build address-bound replicas and win blocks by answering unpredictable byte challenges quickly.

data+AR fee→permanent record

Sign + seed

A wallet signs data and an AR fee. A gateway or bundler must also make the actual bytes available.

Pack replicas

Miners generate entropy and pack data into address-bound replica.2.9 partitions for local storage.

Challenge

A sequential VDF and RandomX select recall byte ranges too quickly to fetch missing data on demand.

Prove H1 / H2

A local chunk yields H1; a second full-weave challenge can yield the stronger H2 path. Peers verify the solution.

Retrieve

Gateways index and serve confirmed data. They improve UX, but a gateway is not the consensus network itself.

Why “blockweave”?

The name comes from the historical recall-block design. Current 2.9 mining challenges byte offsets and packed partitions; old two-block diagrams are now incomplete.

Why can “forever” be prepaid?

About 1/21 of a fee goes directly to miners and the rest enters an endowment, based on replicated storage and falling-cost assumptions.

What is not guaranteed?

Paying reserves data in the weave, but bytes still need seeding. Logical weave size is not proof of physical replica count or universal gateway access.

Logical weave389.3 TBnot physical replicas

1 GiB quote10.94 AR≈ 17,18 € now

Reward pool345.04K ARendowment balance

Debt supply0.00 ARlatch clear

VDF step111.41Msequential clock

720-block uploads29.9 GBLunar-derived

What the assets do

Token map

AR secures permanent storage. AO is designed for compute payments and economic security. Owning one is not equivalent to owning the other.

ARStorage layer

65.59M / ~66M normal issuance

Used to pay for data storage and reward miners. Normal issuance approaches ~66M, but current code permits extra debt issuance if the endowment cannot cover its reward obligation.

Demand pathPermanent data fees
SecurityMining + data access proofs
Supply55M genesis + ~11M curve; debt escape hatch
Market-feed implied65.7M circulating AR
Endowment now345.04K AR · 0 debt

AOCompute layer

7.23M / 21M max

Designed for service payments, staking, and flexible compute security. Issuance declines continuously as a share of the remaining supply.

1/3 issuanceDelegated AR holders
2/3 issuanceBridged yield-bearing assets
LaunchCommunity minting; no insider allocation
Market-feed circulating6.13M AO
Minted-supply value11,29 Mio. €
Max-supply value32,79 Mio. €

Value-capture test

Follow the money, not the story

Storage demand→AR fees→miners + endowment

Compute demand→AO payments / stake→operators + security

Delegated AR→1/3 AO issuance→AR holder incentive

Investment inference: adoption matters only if it produces durable fee demand, security demand, or scarcity—not merely messages, uploads, or developer announcements.

Who is building

Code + contributors

Repository activity is a useful leading signal. It is not a substitute for audits, adoption, or independent maintainers.

Arweave node

ArweaveTeam/arweave

Canonical Erlang implementation of the base protocol.

Erlang language5 authors / 90d72% top share / 90d41d ago latest push

“Core sync and release maintenance”

AO-Core / HyperBEAM

permaweb/HyperBEAM

Current Erlang reference implementation of AO-Core.

Erlang language8 authors / 90d70% top share / 90dtoday latest push

“Active protocol and device work”

AO legacy stack

permaweb/ao

Classic MU/SU/CU components and JavaScript tooling.

JavaScript language3 authors / 90d71% top share / 90d9d ago latest push

“Compatibility and maintenance work”

aos runtime + CLI

permaweb/aos

Lua process operating system and developer CLI for AO.

Lua language3 authors / 90d69% top share / 90d15d ago latest push

“aos runtime and release maintenance”

AR.IO gateway

ar-io/ar-io-node

Gateway and indexer infrastructure; access layer, not L1 consensus.

TypeScript language2 authors / 90d59% top share / 90dyesterday latest push

“Gateway and indexing maintenance”

Arweave JS SDK

ArweaveTeam/arweave-js

Browser and Node.js client for wallets, transactions, and gateways.

TypeScript language0 authors / 90d0% top share / 90d492d ago latest push

“No default-branch commits in the last year”

Developer engagement

Weekly repository activity

Community pulseCooling-47% vs prior 4w

Last 4 complete weeks133public commits

Repository breadth3/6active in 4w

Stale projects1no push in 45d

GitHub participation statistics · refreshed every six hours

Latest commit samples · tracked repos

Active contributor graph

GitHub API · live

@samcamwilliamsHyperBEAM

70commits 02

@JamesPiechotaarweave

66commits 03

@ldmbermanarweave

14commits 04

@speeddragonHyperBEAM

9commits 05

@jfrain99HyperBEAM

9commits 06

@NickJ202HyperBEAM · ao

7commits

Base protocol · 90d auditJamesPiechota · ldmberman · khetzl

92 commits across 3 authors (66 / 14 / 12). No sampled commit mapped to a public PR, and the public daily E2E history is persistently red.

AO-Core · 90d auditsamcamwilliams

339 commits across 9 authors and 87 merged PRs. Sam authored 242 commits and merged 84 PRs: strong velocity and clear key-person risk.

AO continuityTillaTheHun0 · VinceJuliano · jfrain99

Major classic AO contributors; activity is now split between compatibility work and HyperBEAM.

Method: the activity chart uses GitHub’s weekly participation statistics; contributor samples refresh from each default branch’s public Atom feed. The 90-day audit was measured on 5 Aug 2026. Merges, generated commits, pair work, mirrors, and private work can distort counts. This measures visible activity, not individual quality.

Thesis breakers

Risk register

The strongest investment process tries to disprove itself. These are the questions the dashboard should keep forcing.

01High

Token value capture

Network usage can grow while AR price does not. Track paid storage demand, fee flow, issuance, and subsidy dependence—not app counts alone.

02High

AO maturity + migration

Classic AO and the newer AO-Core/HyperBEAM model coexist. Compatibility, security assumptions, and operator economics are still moving.

03Med–high

Contributor concentration

Core development is active but concentrated. A protocol can be decentralized at runtime and centralized in maintenance.

04Medium

Gateway dependence

Consensus storage is decentralized, but most users rely on a few gateways for indexing, discovery, caching, and access.

05Medium

Endowment assumptions

“Pay once” relies on storage costs falling and the reward pool retaining enough purchasing power. If it empties, implemented debt supply can extend issuance beyond the normal constant.

06Medium

Permanent-data liability

Permanence creates legal and moderation pressure for miners and gateways. Availability can differ from retrievability through a given interface.

07High

Public assurance surface

Arweave’s daily E2E history is persistently red; sampled HyperBEAM merges had little visible review or test evidence. Shipping activity is not the same as assurance.

08Medium

License + operator adoption

HyperBEAM currently uses BSL-1.1 with a future MPL conversion. Production rights, independent operators, and practical deployment complexity affect decentralization.

Bull case

Arweave becomes the durable data layer for machines, chains, and agents; AO turns that permanent log into an open compute market.

Bear case

Usage stays subsidized or gateway-heavy, AO fragments value capture, and a concentrated team ships complexity faster than independent operators adopt it.

This is a monitoring framework, not financial advice. Price, code activity, and network health answer different questions; never let one stand in for the others.

Evidence trail

Sources

Primary protocol material first. Live APIs are labeled. Market feeds are indicative third-party data.

Primary