Routine work,
handed off for good.
OpenHash puts software agents on the repetitive parts of your day. Give each one a remit, walk it through the routine once, then link agents end to end so everything keeps moving while you do something else.
- One remit per agent
- Taught once, repeated
- Linked end to end
- Dated claims only
Sample cards. They show the shape of the product and carry no live data.
Routine an agent could hold
Hand over the dull parts.
- Filing the daily report
- Sorting what arrives overnight
- Tidying a shared folder
- Checking a dashboard on the hour
- Copying figures between sheets
- Flagging items that need a person
- Gathering prices while you sleep
- Renaming a batch of files
- Absent draws inert
- Unconfirmed draws inert
- Every entry bears a date
- Links derive from stored URLs
- Handles are read, never typed
- Address shapes get matched
- No string is refused for looking odd
- One file holds the facts
Paste an address. It is compared, not judged.
Any string resembling a Solana address is set beside the register. The gate does not turn a string away for being unfamiliar; it reports if the string equals what has been stated.
A label, a remit, one routine.
Each agent is built around a single responsibility. You set its remit, walk it through the routine once, and from then on it repeats that routine without being asked again.
- A labelHow one agent is told from another.
- A remitA single responsibility, kept narrow.
- A routineShown once, then repeated without prompting.
- A position in the seriesIts output feeds whichever agent follows.
- A visible statusRunning, waiting or idle, readable at a glance.
- Its own paceIt keeps going behind the scenes.
- remit
- Collector
- routine
- Gather each new item
- passes to
- Bo, the Analyst
Run it. Halt it. Nothing runs unseen.
The card beside this text acts out one routine. The two buttons halt it on the spot or send it onward again. All of it happens in this tab.
From one agent to a crew.
Begin with one routine. Link the agents that follow. Previews use sample cards.
One remit, one routine.
Start small. A single agent with a clear remit pays off immediately: it picks up the routine you keep repeating and carries it out alone.
Hand the result along.
Aim one agent at another and the output of each becomes the input of whichever comes after. The sequence shows who passes what to whom.
See each member of the crew at once.
Each agent and each sequence is listed together, with a status beside every label, so a glance shows what is moving.
- AdaCollectorRunning
- BoAnalystRunning
- CyReviewerWaiting
Three moves from idea to loop.
- 1Define
Name it, narrow it
Label the agent and set its remit. A single responsibility reads better than five.
- 2Link
Point it onward
Aim its output at another agent. The sequence makes each hand-off visible.
- 3Release
Send it off
The sequence keeps moving behind the scenes while its status stays on screen.
Say only what is on record.
Facts about OpenHash that live outside the product sit in one register. Each is stated, absent or unconfirmed, and the page is drawn accordingly.
- ProductSoftware agents for repetitive jobs, linked into chainsStated
- Domainopenhash.workStated
- ChainSolanaStated
- RPC endpointapi.mainnet-beta.solana.comStated
- On-chain addressNo value on recordAbsent
- Product accessNo value on recordAbsent
- XNo value on recordAbsent
- GitHubNo value on recordAbsent
An entry with a value or stored URL and a named origin.
The slot comes alive. Links open in another tab, copy works, and the handle is read from the URL. The chip turns solid and its dot pulses.
An entry nobody has stated yet.
The slot holds its place so nothing shifts later, but it ignores clicks and prints the date it was last checked. The chip shows a hollow ring.
An entry someone mentioned and nobody has backed.
It is drawn as an absent one would be: held in place, dated, inert. The chip shows a half ring until a provenance line exists.
Solana, and one live read.
Solana and the endpoint were named in a client statement dated , recorded at batch-level. The slot below is read from that endpoint, in your browser.
Asks the stated endpoint for the current slot, then again at a calm interval. A failed read is shown as failed, with its time.
Statements arrive. The page follows.
Nothing here is edited by hand when a fact lands. The entry changes, and each reader of it changes along.
- 1On-chain addressGates everythingAbsent
The on-chain address lands
The top slot fills with the complete string and turns copyable. The gate stops reporting that it has nothing to compare against, and begins calling matches.
- 2XAbsent
The X link lands
The icon opens onto the stored URL. The handle appears in its label, read out of that URL, never typed a second time.
- 3GitHubAbsent
The GitHub link lands
Same treatment: the Octicon opens onto the stored URL, and the footer follows without any edit.
Short answers, all on record.
What is OpenHash?
Software agents that take over repetitive jobs, linked together, operated from one workspace, for Solana. That description comes from client slides and is the sum of what has been stated.
Can I download it or sign up?
Nothing of the kind has been stated yet. The register holds an open entry for product access, and this answer changes when it does.
Why are some icons and fields faded?
Their entry is absent or unconfirmed. They keep their place so the layout never jumps, they accept no clicks, and each shows the date it was last looked at.
Where is the on-chain address?
The slot at the very top of the page holds it. Today it shows not stated. As soon as a value enters the register, the slot shows the entire string and copies it on a click.
How do the X and GitHub icons get their links?
The register stores a URL. The page derives the handle from that URL when it draws the icon. With no stored URL there is nothing to follow, so the icon stays inert.
What does the gate do with an address that is not ours?
It reports the shape honestly. An address-shaped string is compared with the stated on-chain address and called a match or a difference. It is never thrown out for being unfamiliar.
Who named Solana and the endpoint?
A client statement, recorded at batch level and dated . The provenance line sits on each of those entries.
Are the agent cards real data?
No. Every card, status and progress bar on the site is a labelled sample drawn in your browser. Only the cluster slot is live.
What does the page remember about me?
Only your light or dark choice, kept in this browser. No accounts, no cookies, no analytics.
Waiting on a statement.
Items below derive from the register as the page loads. An entry drops off as soon as it is stated.
- On-chain addressabsent ·
- Product accessabsent ·
- Xabsent ·
- GitHubabsent ·