A production line for on-chain agents
Pons Agent Factory is being built as an open production line for blockchain missions on Robinhood Chain. It begins with a simple public function: watch the chain, collect bounded evidence, pass that evidence through six visible stations, and produce a receipt that anyone can inspect.
No hidden signer. No automatic wallet connection. No claim that a decorative animation is an autonomous agent. The public feed is the proof surface. $PAF is the planned access and coordination layer around the parts of the Factory that are scarce, private, or operator-maintained.
Public evidence should be free. ETH should settle real work. $PAF should operate and coordinate the Factory.
What is live now
The first working release is read-only. The website connects to Robinhood Chain mainnet and reads current public blocks. The terminal exposes chain ID, latest block number, transaction count, and fee context. Every fresh block automatically moves through a six-station mission; users can inspect the live findings and receipt without pressing anything.
The resulting packet contains the block number, block hash, parent hash, transaction count, freshness check, parent-link check, six agent findings, and explicit authority flags.
The open-source CLI performs the same pipeline and generates a canonical paf.receipt.v1 object with a deterministic SHA-256 digest. The current product is chain observability and evidence packaging—not trading, custody, or a promise that an agent can make money.
Six stations, one bounded mission
Scout — acquire the evidence
Scout reads the latest block and normalizes the block number, hash, transaction envelope, gas usage, and timestamp. It does not turn a sighting into a recommendation.
Sentinel — fail closed
Sentinel verifies that the network is chain 4663, the block is fresh, the hash has the expected form, and the parent link is coherent. A mismatch blocks escalation instead of being smoothed over by generated prose.
Strategist — build a bounded brief
Strategist classifies observed block activity and fee context. The brief is derived from the evidence window; it is not a prediction of token performance.
Composer — assemble the packet
Composer creates the machine-readable mission packet. In the current release, every packet is explicitly read-only and contains no transaction builder.
Scribe — bind the receipt
Scribe serializes the mission in canonical form and produces a deterministic digest. That makes a receipt portable, comparable, and resistant to silent field-order changes.
Keeper — watch freshness
Keeper tracks whether the evidence remains current and waits for the next public block. Stale data is marked stale. A fallback snapshot is never presented as a live observation.
The utility model
The public feed stays free. Utility begins where resources become scarce or where operators contribute reusable work.
1. Use the Factory
After token activation, $PAF is intended to unlock higher mission limits, private watchlists, saved policy gates, and advanced multi-agent workflows. A public observer can still inspect the chain. An operator uses $PAF because they want the Factory to monitor selected contracts, wallets, asset classes, or policies.
2. Publish to the Factory
Operators should be able to publish contract adapters, evidence collectors, policy gates, and reusable mission recipes. The planned registry uses $PAF as a publishing bond so spam and careless components carry a cost. Bonding and challenge rules are not active until their contracts and dispute boundaries are published and audited.
3. Complete operator bounties
The Factory can publish objective engineering and integration bounties: add an event adapter, support a tokenized-asset standard, improve a policy test, or verify a receipt format. Requirements and acceptance tests stay public. Operators can earn ETH or $PAF when their work is accepted.
4. Curate production
A later activation phase may use $PAF to curate registry entries and factory priorities. Governance must not bypass security invariants, seize user assets, or silently grant signing authority.
Why ETH remains important
Robinhood Chain is an EVM network, and ETH is its native economic unit. Pons Agent Factory therefore presents access prices and operator values in ETH first, with USD as a smaller reference.
- ETH covers network gas and settlement.
- Beta access and operator bounties are expressed in ETH.
- Transaction values are displayed in ETH first.
- USD remains a secondary reference.
The planned beta targets are 0.01 ETH for an Operator lane and 0.04 ETH for a Factory lane per 30 days. Those are target terms, not an active checkout. The signup page takes no payment.
$PAF and ETH have different jobs. ETH settles work. $PAF opens, extends, and coordinates the Factory.
Why would someone acquire $PAF?
The defensible answer is not “because the chart may rise.” A user acquires $PAF because they want to run more specialized missions, maintain private watchlists and policies, publish adapters and recipes, qualify for operator bounties, or curate registry components after audited activation.
If someone only wants to view the public chain feed, they do not need the token. If someone does not need the Factory’s private or operator functions, the project should not pretend otherwise.
$PAF is not designed as a holder-yield promise, revenue share, guaranteed passive-income instrument, or assurance of price appreciation. Any public token launch still requires supply, allocation, vesting, treasury, liquidity, security, and jurisdictional disclosures.
Open source is part of the proof
The core runtime is published under the MIT License at github.com/ponsagents/pons-agent-factory.
The repository contains the typed six-agent pipeline, read-only client, CLI, receipt schema, canonical digest implementation, deterministic tests, a documented CI workflow, architecture documentation, utility specification, security policy, and roadmap.
Opening code does not prove every future claim. It does make the current boundary reviewable: anyone can verify that the first release has no wallet connector, private-key parser, signing method, transaction builder, or transaction-submission method.
What happens next
- Contract-log and ERC-20 transfer adapters.
- Tokenized-asset registry support.
- Persistent content-addressed receipt archives.
- Private watchlists and alert outputs.
- A sandboxed adapter registry.
- Objective operator-bounty specifications.
- Token access only after contract publication and audit.
The Factory earns the right to launch utility by shipping each layer in public.
The boundary
Pons Agent Factory is an independent ecosystem project and is not affiliated with or endorsed by Robinhood Markets.
The $PAF contract is TBA. The only official contract announcement will come from @ponsagents. Until the contract, thresholds, and activation rules are public and verifiable, utility remains a design target rather than a deployed token claim.