Live on Robinhood Chain

Intelligence for corporate actions.

Hanx detects upcoming splits and dividends, verifies onchain state, and tells you exactly how it affects your position.

View Docs
HANX CAPending
Resolved TSLA · corporate action detected
onchain state verified
action     stock_split (3:1)
effective  2026-09-12
multiplier 1.01.0
tokens     500 (unchanged)
represents 500 → ~1,500 underlying shares
verdict    WATCH

Your token count does not change. Each token comes to represent 3 underlying shares, and the per token price stays continuous.

Split Detection State Verification Agent Callable Oracle
How it works

Three steps, from raw chain data to a clear verdict.

01
Detect

Hanx reads each token's onchain multiplier and pending action state, catching upcoming splits and dividends before their effective date.

getCorporateAction()
02
Verify

It compares what the corporate action says should be true against live onchain state — and flags any discrepancy the moment it appears.

NORMAL · WATCH · REVIEW
03
Explain

You get a plain language answer: what changes, when, and what it means for your position — or a structured verdict your agent can act on.

explainCorporateAction()

Built for holders. Ready for agents.

Split & Action Detection

Hanx reads each token's onchain multiplier state and surfaces upcoming splits and dividends before they take effect — so a 3:1 never surprises you.

Onchain State Verification

Every action is checked against live onchain state. When the expected multiplier and the actual one disagree, Hanx flags it — NORMAL, WATCH, or REVIEW.

Agent Callable Oracle

The same verdict is exposed onchain and over an API. Any wallet, bot, or AI agent can call Hanx before it trades to ask: is this asset about to change?

A corporate action oracle any agent can call.

Hanx isn't just a dashboard. The verdict that powers the UI is exposed as a callable oracle — so a wallet, bot, or AI trading agent can ask about an asset before it acts.

One call, structured answer. Ask getCorporateAction(ticker) and get the multiplier state, effective date, and a risk verdict back.

Onchain and over HTTP. The same verdict is readable from a contract or the REST API — whichever your agent speaks.

Built to gate a trade. An agent can check Hanx before executing: is this asset about to change, and is onchain state synced?

agent.ts
// before trading TSLA, check with Hanx
const action = await hanx.getCorporateAction("TSLA");
{
  action:      "stock_split",
  ratio:       "3:1",
  effective:   "2026-09-12",
  multiplier:  { current: 1.0, pending: 3.0 },
  verdict:     "WATCH",
  synced:      true
}

Not a calendar. Not a raw feed.

Three ways to tell holders about a corporate action. Only one of them checks what the chain actually says.

Rejected

A corporate action calendar

Lists dates pulled from an API. It can tell you a split is coming — but never whether the token onchain has actually caught up to it.

Rejected

A raw data feed

Surfaces multiplier values as is and stops there. Every holder is left to work out for themselves what it means for their position.

Chosen

Hanx

Compares the expected action against live onchain state, flags the gap when they disagree, and explains the impact — readable by a person or an agent.

Fair launch. Nothing reserved.

$HANX is the access token for Hanx — holding it is how you use the product. One billion supply, no presale, and nothing set aside for the team.

$HANXRobinhood Chain
Total supply1,000,000,000
Launch typeFair launch
PresaleNone
Team allocation0%
UtilityAccess to Hanx
Contract addressPending

The contract address will be published here the moment $HANX is live on Robinhood Chain.

Quickstart

Three calls. Then your agent knows.

Hanx is a read. There's nothing to deploy, no approval to sign, and no custody to hand over.

01Point at the oracle
const hanx = createClient({
  url: "https://api.hanx.xyz",
});

One base URL, or the contract address if your agent reads onchain.

02Ask about an asset
const a = await hanx.getCorporateAction(
  "TSLA"
);

// a.verdict → "NORMAL" | "WATCH" | "REVIEW"

Returns multiplier state, effective date, and a verdict.

03Gate the trade
if (a.verdict === "REVIEW") {
  hold("state not synced");
} else {
  await trade("TSLA");
}

Refuse to execute while onchain state and the action disagree.

Questions. Answered plainly.

Because that tells you what should happen, not what did. The API says a 3:1 is effective Friday; it can't tell you whether the token's onchain multiplier has actually moved. Hanx reads both and flags the gap — that gap is the entire product.

Every verdict is derived from values anyone can read: uiMultiplier, newUIMultiplier, and effectiveAt off the token, plus the Chainlink feed's last update time. No human writes a verdict. The comparison logic lives in a contract with no admin keys and no upgrade path, so it can't be quietly changed either.

No. It's read only. There's no approval to sign, no transfer, no custody, and no contract of ours ever holds your assets. If Hanx disappeared tomorrow your position would be untouched.

It's the access token for the product — holding it is how you use Hanx. Fair launch, one billion supply, no presale, and nothing allocated to the team.

Stock splits on registered tokens today, which is where the onchain representation changes most visibly. Dividends, ticker changes, mergers, and spinoffs run through the same detect-verify-explain path and are next.

Both read the same source. An agent can call getCorporateAction() onchain or over HTTP and get the identical structured verdict the dashboard renders — which is the point of shipping it as an oracle rather than a website.

Know before it lands. Not after.

Check any tokenized asset for a pending corporate action — or wire the oracle into an agent and let it check for you.