HIP-3 protocol
HIP-3 is documented as a HyperCore certification surface in Mattheus. Public execution is disabled while the full-launch verdict is NO_GO.
Short answer
HIP-3 status: non-public certification and research surface. Certification state: Research-only documentation surface. HIP-3 public execution is not certified or exposed; any future write path requires exact-action certification, preview, policy checks, explicit approval, and signed lifecycle evidence.
Non-public execution
HIP-3 research and account-specific canary capabilities do not constitute public write availability while the global verdict is NO_GO.
Certification state
Research-only documentation surface. HIP-3 public execution is not certified or exposed; any future write path requires exact-action certification, preview, policy checks, explicit approval, and signed lifecycle evidence.
Who This Is For
Developers preparing HIP-3 actions through Mattheus API, SDK, MCP, or workflow surfaces.
Before You Begin
- A supported action and amount
- Preview payload hash
- Balance, allowance, liquidity, simulation, and policy checks where applicable
- Manual user approval before signing or broadcast
Answer engine brief
Mattheus overview
Mattheus is a private AI trading workspace for researching markets, testing reproducible strategies, reviewing portfolio context, and preparing governed actions. Developers can connect through REST APIs, SDKs, and MCP while account authority, policy checks, and approvals remain separate.
Does Mattheus require approval before execution?
Yes. An interactive request requires an exact short-lived one-time approval confirmed with fresh wallet reauthentication. API-key automation requires a separately activated, scoped agent session. Both paths still require wallet or signing readiness and policy checks.
Which markets are documented?
The active launch documentation covers Hyperliquid market data, paper trading, and gated Live workflows. Each page states whether an example is read-only, simulated, paper, or eligible for approval-gated Live execution.
How does policy-gated execution work?
Execution-capable requests are preview-first and must pass wallet readiness, protocol certification, feature gates, idempotency, configured policy controls, and either an exact interactive approval or a bounded API-key agent session before any live action.
Can users revoke permissions?
Users should be able to revoke supported scoped permissions and API keys. Documentation should keep stop, cancel, revoke, and policy rejection paths clear before users approve live execution.
Example
What this example does
Follow this example in order. Read the expected result below before connecting it to a live account or execution-capable workflow.
{
"protocol": "hip-3",
"venue": "HyperCore",
"aiExecutable": false,
"manualApprovalRequired": true,
"requiresPreview": true,
"requiresPolicyCheck": true,
"certification": "Research-only documentation surface. HIP-3 public execution is not certified or exposed; any future write path requires exact-action certification, preview, policy checks, explicit approval, and signed lifecycle evidence.",
"supportedActions": [
"market_research",
"deployment_context"
]
}Expected result
Common errors
- HIP-3 execution is not certified
- Market deployment context unavailable
- Action is not publicly executable
- Global launch gate is NO_GO
- Preview rejected: balances, allowance, liquidity, route, simulation, policy, or approved-address checks did not pass.
- Approval required: an interactive request has no approved, unexpired, exact one-time approval artifact, or an API-key request has no active scoped agent session.
Safety note
HIP-3 actions remain subject to market, protocol, wallet, policy, signer, and operational risk. Mattheus does not promise execution success, yield, safety, or profit.