@oracle-agent/oracle 0.10.0 → 0.12.0

package/scripts/verify-v3-venues.mjs

@@ -1,192 +0,0 @@
-#!/usr/bin/env node
-// Functionally verify Uniswap V3 venue addresses on every chain.
-//
-// Codesize alone is NOT verification -- an unrelated contract also has bytecode, and
-// on Base the canonical mainnet addresses returned 2109 bytes for two different
-// contracts, which is exactly the kind of false positive a size check waves through.
-//
-// The real test is behavioural: ask the candidate quoter to price a pair we already
-// know the answer to. A contract that returns a sane WETH->USDC quote at a standard
-// fee tier IS a working V3 quoter, regardless of what any doc claims.
-//
-// Output is a provenance record per chain, ready to paste into chains.config.mjs.
-
-import { rpcCall } from "../src/data/providers/evm-rpc.mjs";
-
-// Candidates. Most chains share the canonical deployment; Base, BSC and Avalanche
-// have their own. All of these are CANDIDATES until the probe passes.
-const CANONICAL_QUOTER = "0x61fFE014bA17989E743c5F6cB21bF9697530B21e";
-const CANONICAL_ROUTER = "0x68b3465833fb72A70ecDF485E0e4C7bD8665Fc45";
-
-const CANDIDATES = {
-  1: {
-    name: "ethereum",
-    quoter: CANONICAL_QUOTER,
-    router: CANONICAL_ROUTER,
-    tokenIn: "0xC02aaA39b223FE8D0A0e5C4F27eAD9083C756Cc2", // WETH
-    tokenOut: "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48", // USDC
-    decIn: 18,
-    decOut: 6,
-  },
-  10: {
-    name: "optimism",
-    quoter: CANONICAL_QUOTER,
-    router: CANONICAL_ROUTER,
-    tokenIn: "0x4200000000000000000000000000000000000006",
-    tokenOut: "0x0b2C639c533813f4Aa9D7837CAf62653d097Ff85",
-    decIn: 18,
-    decOut: 6,
-  },
-  56: {
-    name: "bsc",
-    quoter: "0x78D78E420Da98ad378D7799bE8f4AF69033EB077",
-    router: "0xB971eF87ede563556b2ED4b1C0b0019111Dd85d2",
-    tokenIn: "0xbb4CdB9CBd36B01bD1cBaEBF2De08d9173bc095c", // WBNB
-    tokenOut: "0x8AC76a51cc950d9822D68b83fE1Ad97B32Cd580d", // USDC (18dp on BSC)
-    decIn: 18,
-    decOut: 18,
-  },
-  137: {
-    name: "polygon",
-    quoter: CANONICAL_QUOTER,
-    router: CANONICAL_ROUTER,
-    tokenIn: "0x0d500B1d8E8eF31E21C99d1Db9A6444d3ADf1270", // WMATIC
-    tokenOut: "0x3c499c542cEF5E3811e1192ce70d8cC03d5c3359", // USDC native
-    decIn: 18,
-    decOut: 6,
-  },
-  8453: {
-    name: "base",
-    quoter: "0x3d4e44Eb1374240CE5F1B871ab261CD16335B76a",
-    router: "0x2626664c2603336E57B271c5C0b26F421741e481",
-    tokenIn: "0x4200000000000000000000000000000000000006",
-    tokenOut: "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
-    decIn: 18,
-    decOut: 6,
-  },
-  42161: {
-    name: "arbitrum",
-    quoter: CANONICAL_QUOTER,
-    router: CANONICAL_ROUTER,
-    tokenIn: "0x82aF49447D8a07e3bd95BD0d56f35241523fBab1",
-    tokenOut: "0xaf88d065e77c8cC2239327C5EDb3A432268e5831",
-    decIn: 18,
-    decOut: 6,
-  },
-  43114: {
-    name: "avalanche",
-    quoter: "0xbe0F5544EC67e9B3b2D979aaA43f18Fd87E6257F",
-    router: "0xbb00FF08d01D300023C629E8fFfFcb65A5a578cE",
-    tokenIn: "0xB31f66AA3C1e785363F0875A1B74E27b85FD66c7", // WAVAX
-    tokenOut: "0xB97EF9Ef8734C71904D8002F8b6Bc66Dd9c48a6E", // USDC
-    decIn: 18,
-    decOut: 6,
-  },
-};
-
-const FEE_TIERS = [500, 3000, 10000];
-
-const word = (v) => BigInt(v).toString(16).padStart(64, "0");
-const addrWord = (a) => a.slice(2).toLowerCase().padStart(64, "0");
-
-// QuoterV2.quoteExactInputSingle((address,address,uint256,uint24,uint160))
-// selector 0xc6a5026a -- struct is encoded inline as 5 words.
-function encodeQuote({ tokenIn, tokenOut, amountIn, fee }) {
-  return (
-    "0xc6a5026a" +
-    addrWord(tokenIn) +
-    addrWord(tokenOut) +
-    word(amountIn) +
-    word(fee) +
-    word(0) // sqrtPriceLimitX96 = 0 (no limit)
-  );
-}
-
-async function codesize(chainId, address) {
-  const r = await rpcCall(chainId, "eth_getCode", [address, "latest"]).catch(() => null);
-  const raw = r?.result ?? r;
-  return raw && raw !== "0x" ? (raw.length - 2) / 2 : 0;
-}
-
-async function probe(chainId, cfg) {
-  const result = {
-    chainId: Number(chainId),
-    name: cfg.name,
-    quoter: cfg.quoter,
-    router: cfg.router,
-    quoterCodesize: 0,
-    routerCodesize: 0,
-    workingFeeTier: null,
-    quotedOut: null,
-    humanPrice: null,
-    verdict: "FAIL",
-    reason: "",
-  };
-
-  result.quoterCodesize = await codesize(chainId, cfg.quoter);
-  result.routerCodesize = await codesize(chainId, cfg.router);
-
-  if (!result.quoterCodesize || !result.routerCodesize) {
-    result.reason = "no bytecode at candidate address on this chain";
-    return result;
-  }
-
-  // Behavioural probe: does it actually price a pair we can sanity-check?
-  const amountIn = 10n ** BigInt(cfg.decIn);
-  for (const fee of FEE_TIERS) {
-    const data = encodeQuote({
-      tokenIn: cfg.tokenIn,
-      tokenOut: cfg.tokenOut,
-      amountIn,
-      fee,
-    });
-    const r = await rpcCall(chainId, "eth_call", [{ to: cfg.quoter, data }, "latest"]).catch(
-      () => null,
-    );
-    const raw = r?.result ?? r;
-    if (!raw || raw === "0x" || raw.length < 66) continue;
-
-    const out = BigInt(`0x${raw.slice(2, 66)}`);
-    if (out === 0n) continue;
-
-    result.workingFeeTier = fee;
-    result.quotedOut = out.toString();
-    result.humanPrice = Number(out) / 10 ** cfg.decOut;
-    break;
-  }
-
-  if (result.workingFeeTier == null) {
-    result.reason = "bytecode present but no fee tier returned a quote -- not a working V3 quoter";
-    return result;
-  }
-
-  // Sanity band. A working quoter on a major pair should land in a plausible range;
-  // a wildly wrong number means we are talking to the wrong contract or decoding it
-  // wrong, and either way it must not be allowlisted.
-  if (result.humanPrice <= 0 || !Number.isFinite(result.humanPrice)) {
-    result.reason = `implausible quote ${result.humanPrice}`;
-    return result;
-  }
-
-  result.verdict = "PASS";
-  result.reason =
-    `quoteExactInputSingle at fee ${result.workingFeeTier} returned ` +
-    `${result.humanPrice} for 1 unit in -- a live, working V3 quote`;
-  return result;
-}
-
-const out = [];
-for (const [chainId, cfg] of Object.entries(CANDIDATES)) {
-  const r = await probe(chainId, cfg);
-  out.push(r);
-  const line =
-    `${r.name.padEnd(10)} ${r.verdict.padEnd(5)} ` +
-    `quoter=${String(r.quoterCodesize).padStart(6)} router=${String(r.routerCodesize).padStart(6)} ` +
-    (r.workingFeeTier ? `fee=${String(r.workingFeeTier).padStart(5)} price=${r.humanPrice}` : r.reason);
-  console.log(line);
-}
-
-console.log(`\n${out.filter((r) => r.verdict === "PASS").length}/${out.length} chains verified`);
-if (process.argv.includes("--json")) {
-  console.log(JSON.stringify(out, null, 2));
-}

package/skills/balance/SKILL.md

@@ -1,176 +0,0 @@
----
-name: balance
-description: Use when the user says balance, holdings, portfolio, wallet balance, or invokes /balance. Call the deterministic read-only multichain portfolio tool and report coverage honestly.
----
-
-# Balance
-
-Use `portfolio_snapshot` for every fresh balance request. It runs the deterministic
-multichain balance and NFT inventory reads once, then records one compact local
-observation so the user can build history without a separate tracker.
-
-Use `portfolio_history` for balance-history requests and `portfolio_value_graph`
-for charts. Use `portfolio_balance` only when the user explicitly asks for a
-non-recorded read or when local history storage is unavailable.
-
-This skill is read-only. Public addresses are identifiers, not signing rights.
-Never request a private key, seed phrase, wallet export, session key, or signature.
-
-## Trigger
-
-Run this workflow when the user:
-
-- invokes `/balance`;
-- says `balance` by itself;
-- asks for holdings, wallet balance, portfolio, net assets, or assets across chains;
-- supplies one or more public wallet addresses and asks what they hold.
-
-## Address routing
-
-Parse only public addresses supplied with the request:
-
-- `0x...` maps to `addresses.evm` and `addresses.hyperliquid` unless the user
-  explicitly assigns different addresses;
-- a Solana base58 public key maps to `addresses.solana`;
-- a Bitcoin `bc1`, `1`, or `3` address maps to `addresses.bitcoin`;
-- explicit labels such as `evm:`, `solana:`, `bitcoin:`, and `hyperliquid:` win.
-
-If no addresses are in the request, call `portfolio_snapshot` with an empty object.
-The tool uses configured public-address defaults:
-
-- `ORACLE_EVM_ADDRESS`, with legacy fallback `ORACLE_DEFAULT_ADDRESS`;
-- `ORACLE_SOLANA_ADDRESS`;
-- `ORACLE_BITCOIN_ADDRESS`;
-- `ORACLE_HYPERLIQUID_ADDRESS`, with EVM fallback.
-
-If every family returns `not-configured`, ask only for the missing public addresses.
-Do not call a zero address a user wallet and do not report missing families as zero.
-
-## Mandatory call
-
-Call `portfolio_snapshot`:
-
-```json
-{
-  "addresses": {
-    "evm": "optional public address",
-    "solana": "optional public key",
-    "bitcoin": "optional public address",
-    "hyperliquid": "optional public address"
-  },
-  "includeTokens": true,
-  "includeCollectibles": true,
-  "includePrices": true,
-  "includeNfts": true
-}
-```
-
-Omit address fields the user did not supply. Omit `evmChainIds` unless the user
-asks for a subset. The default queries every configured EVM chain. Read fungible
-and chain details from `result.balance`, NFT holdings from `result.nfts`, and the
-combined historical observation from `result.snapshot`.
-
-Never call a chain write, prepare, sign, send, submit, execute, or broadcast tool
-while answering a balance request. The compact profile-local history append made
-by `portfolio_snapshot` is allowed and contains no keys or executable payloads.
-
-## Coverage contract
-
-The current aggregator covers:
-
-- native balances on every configured EVM chain;
-- Solana SOL plus SPL Token and Token-2022 accounts;
-- Bitcoin BTC plus Runes and inscriptions when an address indexer is configured;
-- Hyperliquid HyperCore spot balances and perp account state;
-- OpenSea-supported EVM/Solana NFT inventory and Bitcoin inscriptions where the
-  configured providers expose owner data;
-- profile-local snapshots and an SVG known-value history graph.
-
-It must explicitly report unsupported or unavailable surfaces:
-
-- EVM token and NFT enumeration is unavailable without an address indexer;
-- Solana token accounts are unverified until metadata confirms symbol and spam
-  status;
-- a Solana amount of one with zero decimals is only a collectible candidate;
-- Bitcoin Runes and inscriptions require an address-indexed provider;
-- Cosmos requires a chain-specific bech32 address and LCD/RPC adapter;
-- Sui and Aptos remain unsupported until their balance adapters are installed;
-- any provider failure is `unavailable`, never a zero balance;
-- NFT prices are provider estimates, not executable bids.
-
-## History and graph
-
-For “balance history”, “portfolio history”, or a date range, call
-`portfolio_history` with the same public addresses and the requested `since`,
-`until`, and `limit`. Keep `null` values unavailable. Do not interpolate them.
-
-For “graph”, “chart”, or “show me performance”, call `portfolio_value_graph`.
-State the returned `summary.changeUsd`, `summary.changePct`, point count, and
-whether any plotted snapshots were incomplete. The image plots known priced
-value, not guaranteed liquidation value or net worth.
-
-## Response format
-
-Start with:
-
-```text
-Balance, <queriedAt>
-Known priced value: $<knownUsd>  (not a complete total)
-Coverage: <ok>/<requestedSurfaces> surfaces live
-```
-
-If `valuation.complete` is true, you may remove the parenthetical. Do not rename
-`knownUsd` to `total`, `net worth`, or `portfolio value` when coverage is partial.
-
-Then show nonzero assets first, grouped by family:
-
-```text
-EVM
-Ethereum: 0.42 ETH  $...
-Base: 18.1 ETH  $...
-
-Solana
-SOL: ...
-SPL: <mint>  <amount>  unverified
-
-Bitcoin
-BTC: ...
-Runes: ...
-Inscriptions: ...
-
-Hyperliquid
-Spot: ...
-Perps account value: $...
-Positions: ...
-```
-
-Collapse successful zero-native EVM chains into one line:
-
-```text
-Zero native: Polygon, Optimism, Arbitrum
-```
-
-End with concise exceptions:
-
-```text
-Unavailable: <failed providers or unconfigured addresses>
-Unpriced: <nonzero assets without a price>
-Warnings: <spam, stale, unknown-not-empty, or incomplete discovery warnings>
-```
-
-Do not dump raw RPC payloads unless the user asks. Keep exact public addresses in
-the response only when the user supplied multiple addresses and disambiguation is
-necessary.
-
-## Truth rules
-
-- `0` means a provider successfully returned zero.
-- `unavailable` means the provider failed or the adapter is absent.
-- `not-configured` means the public address is missing.
-- `unknownNotEmpty` means the provider cannot tell whether assets exist. Never
-  convert it to an empty portfolio.
-- Every USD figure must carry a price source and query timestamp in the tool
-  result.
-- Do not sum Stable Mainnet native USDT0 with its mirrored ERC-20 representation.
-- Do not price unverified or spam tokens by symbol alone.
-- Do not hide failed chains to make the summary look complete.

package/skills/oracle-action-semantics/SKILL.md

@@ -1,40 +0,0 @@
----
-name: oracle-action-semantics
-description: Use for watch, ping, prepare, arm, sign, send, or execution-capability questions.
----
-
-# Oracle action semantics
-
-Keep these planes distinct:
-
-1. **Public prepare plane**: reads, quotes, simulates, and prepares unsigned artifacts. It never signs or broadcasts.
-2. **Generic Oracle signer**: the unattended daemon exposes six *bounded* surfaces — `hl`, `poly`, `evm-swap`, `evm-bridge`, `btc`, `sol`. Bounded is not generic chain authority: each surface decodes and validates its own envelope shape and refuses while its allowlists are empty. Enablement is never authority; every signature still needs one exact owner-confirmed grant.
-3. **User-wallet EVM**: ordinary EVM preparations require the user's wallet signature.
-4. **Optional bounded EVM execution**: a deployment may expose a separate same-host, owner-gated EVM executor such as MAD. Verify its status and policy before saying it is available. Never infer it from the public package or the generic signer.
-
-Do not turn a deployment fact into a universal claim. If no bounded EVM executor is installed or healthy, say the current deployment cannot execute EVM. Do not say Oracle can never execute EVM.
-
-## Binding vocabulary
-
-- `watch`, `watch this`, `ping`, `ping me`, `alert`, and `notify` mean notification only.
-- Persist them as `active: true` and `actionMode: alert_only`.
-- `arm` means authorization intent for one exact bounded action.
-- Persist it as `active: true` and `actionMode: execute` only after the exact action and owner authorization are present.
-- Never convert `watch` into execution.
-- Never convert `arm` into a watch.
-- A status field such as `armed` is not action authority. Current records require explicit `active` and `actionMode` fields.
-
-Before accepting `arm`, require the exact chain, token pair, amount or fraction, trigger, recipient, router, deadline, slippage bound, and approval bound. Require the owner-gated executor to be healthy and disarmed until that exact action is authorized. Refuse global, implied, or reusable authorization.
-
-## Execution states
-
-Report each state separately:
-
-- `executionReady`
-- `requiresUserSignature`
-- `signingReady`
-- `broadcastReady`
-
-A quote is not a preparation. A preparation is not a signature. A signature is not a broadcast. A broadcast is not mined execution. Claim success only after a transaction hash, successful receipt, and expected balance delta.
-
-ERC-20 approval is a separate transaction. Use an exact bounded amount unless the user explicitly authorizes another cap. Never silently create an unlimited approval.

package/skills/oracle-best-execution/SKILL.md

@@ -1,127 +0,0 @@
----
-name: oracle-best-execution
-description: Use whenever swapping or bridging. The rule that the highest quote is not the cheapest trade, and how to compare routes honestly.
----
-
-# Best execution
-
-The biggest `amountOut` is not the best route. Rank on **net received after gas and
-fees**, every time.
-
-## Get the comparison
-
-```
-best_swap_route   { chainId, tokenIn, tokenOut, amountIn, decimalsIn, decimalsOut }
-best_bridge_route { fromChainId, toChainId, tokenIn, tokenOut, amountIn }
-```
-
-Or at a shell:
-
-```bash
-oracle-route swap   base <tokenIn> <tokenOut> [amountIn]
-oracle-route bridge arbitrum base [token] [amountIn]
-```
-
-## Read the result properly
-
-Report the winner **and** the runners-up. A user who sees only the winner cannot tell
-whether it won by 0.01% or 3%, and that difference decides whether the route is worth
-any extra risk.
-
-Three fields carry most of the meaning:
-
-- **`rankedOn`** — `net-of-cost` means gas was accounted for. `gross` means it was
-  **not**, and the ordering may be wrong.
-- **`costAccounted`** (per route) — `false` means that route's gas is unknown. It is
-  ranked on gross, which **flatters it**. Say so.
-- **`improvementBps`** — `null` means no honest spread exists, usually because the
-  top two routes measure cost differently. Do not invent one.
-
-## What to say
-
-Good: *"ParaSwap nets 1903.88 USDC after $0.01 gas. CoW is 0.01% behind but gasless,
-so on a larger size it likely wins. LI.FI quotes competitively but $4.78 of gas puts
-it 0.5% down."*
-
-Bad: *"Best route: LI.FI, 1899 USDC."* — that is the gross number, and it lost.
-
-## Preparing the winner
-
-`prepare_best_route` compares, then builds the signable artifact for the winner:
-
-```
-prepare_best_route { chainId, tokenIn, tokenOut, amountIn, taker }
-```
-
-`taker` must be the **real wallet that will sign**. Quoting is anonymous; preparing
-is not. Placeholder and burn addresses are rejected.
-
-**Check `artifactKind` before telling the user what to do.** They are not
-interchangeable:
-
-- `unsigned-transaction` (LI.FI, ParaSwap, 0x) — sign and **broadcast** it.
-- `typed-data-order` (CoW) — sign the data and **submit it to the CoW API**. There is
-  nothing to broadcast. Signing authorizes a solver to settle on your behalf.
-
-**Approval comes first, and the spender is not always the destination.** For CoW the
-approval goes to the *vault relayer*, not the settlement contract — approving the
-wrong one produces an order that silently never fills. Read `requiresApproval.spender`
-rather than assuming it equals `destination`.
-
-Some venues refuse to build calldata until the approval already exists on-chain
-(ParaSwap does). That surfaces as `failureKind: "approval-required-first"`, which is
-a real ordering constraint, not a bug: approve, then prepare again.
-
-If the winner has no prepare path, the result names an `alternative`. Say that the
-winner could not be prepared and what you used instead — do not silently substitute.
-
-**Read `driftBps`.** Prepare re-quotes, so this is how far the route moved since the
-comparison. A large negative number means the ranking may no longer hold.
-
-## Preparing a bridge
-
-`prepare_best_bridge_route` — same idea, different hazards.
-
-**`transactions` is always a list.** Some routes need an approval *and* a deposit,
-signed in order. Tell the user how many and that order matters: signing only the
-first leaves funds approved but not bridged.
-
-**Two chains are in play.** Every transaction executes on `fromChainId`; the value
-lands on `toChainId`. Report both. A prepared artifact whose transaction chain does
-not match the origin is refused outright (`failureKind: "chain-mismatch"`).
-
-**Bridging is not atomic — say so unprompted.** The origin transaction confirming does
-**not** mean funds arrived. Give the `durationSeconds` estimate and tell the user not
-to re-send while pending. This is the single most common bridging panic, and silence
-here causes double-sends.
-
-**Across quotes but cannot be prepared** in this build. It often wins on gross because
-its gas is unreported, so expect `failureKind: "no-prepare-path"` with an
-`alternative`. Say the winner could not be prepared and name what you used instead.
-
-## Rules
-
-**One answer is not a comparison.** If only one source responded, say the route is
-unbenchmarked. `sourcesAnswered` vs `sourcesTried` tells you.
-
-**Never present an unknown cost as zero.** A route missing gas data is not free; it
-is unmeasured. Those are different claims and only one of them is true.
-
-**Duration is a cost on bridges.** A route saving $2 that takes 30 minutes is not
-strictly better than one costing $2 more that lands in 20 seconds. Surface both and
-let the user choose — do not silently pick for them.
-
-**Quotes decay.** Every number here is from a past block. Re-quote immediately before
-preparing, and never carry a minOut computed from a stale quote into a signature.
-
-**A comparison is not an execution.** Ranking a route does not prepare, sign, or send
-it. Preparing is a separate step, and signing belongs to the user.
-
-## When sources fail
-
-Aggregators go down, rate-limit, and get sunset (Odos sunset its public API in
-July 2026). Individual failures are expected and appear in `failed[]`. Two things
-follow:
-
-1. Fewer sources means a weaker comparison. Report `sourcesAnswered`, do not hide it.
-2. A failing source is **not** a bad price. Never rank it last — it did not answer.

package/skills/oracle-bitcoin/SKILL.md

@@ -1,53 +0,0 @@
----
-name: oracle-bitcoin
-description: Use for Bitcoin L1, Ordinals/runes research, and inscription PSBT preparation. User-wallet signing only.
----
-
-# Bitcoin L1 / Ordinals
-
-Bitcoin is a separate signing plane. Do not route it through EVM grants, EVM
-signers, or EVM calldata policy.
-
-## What this skill owns
-
-- Bitcoin L1 reads through Esplora: tip height, fee rates, address state, UTXOs,
-  transactions.
-- Ordinals/runes reads through the Bitcoin metaprotocol data providers.
-- Satflow marketplace research and unsigned PSBT intents for ordinals/runes market
-  actions when a Satflow key is configured.
-- Inscription planning and **PSBT preparation** for user-wallet signing.
-
-## Inscription flow
-
-Default path is self-custodial:
-
-1. Collect the inscription content, MIME type, destination address, change address,
-   and fee preference.
-2. Check Bitcoin health, fee rates, and the inscription body-size cap.
-3. Estimate commit/reveal cost and UTXO needs before preparing.
-4. Prepare commit/reveal PSBTs or unsigned artifacts.
-5. User signs in Xverse, UniSat, Leather, OKX, Phantom, Magic Eden wallet, or a
-   compatible injected Bitcoin wallet.
-6. Broadcast only after explicit user confirmation.
-7. Report commit txid, reveal txid, inscription id when known, and mempool/receipt
-   status.
-
-## Hard rules
-
-- Never request or print a seed, WIF, xprv, or wallet export.
-- Operator WIF/local signing is not part of the public default. If a deployment
-  has it, it must be separately armed and still explicit-confirm gated.
-- Inscribe is Bitcoin L1 commit/reveal. Satflow is marketplace inventory/listing,
-  not the inscription path.
-- Fee facts are live facts. Re-read fees immediately before prepare.
-- If content exceeds the current cap, refuse and offer compression/splitting.
-- Never claim an inscription landed without a real reveal txid or inscription id.
-
-## Review checklist
-
-- Content hash and byte length shown before signing.
-- MIME type shown in plain language.
-- Destination and change addresses displayed and user-confirmed.
-- Fee rate, estimated vbytes, and worst-case spend shown.
-- Commit/reveal sequence explained as non-atomic.
-- Mempool status checked after broadcast.

package/skills/oracle-chain-graphs-telegram-cards/SKILL.md

@@ -1,59 +0,0 @@
----
-name: oracle-chain-graphs-telegram-cards
-description: Render per-chain market graphs and Telegram cards for Oracle alerts, including meme launches, HL HIP-3/HIP-4, and Polymarket.
----
-
-# Oracle chain graphs + Telegram cards
-
-Use when Oracle needs visual alerts: per-chain scanner cards, meme-token launch
-cards, route-comparison charts, Hyperliquid HIP-3/HIP-4 cards, or Polymarket
-cards.
-
-## Surfaces
-
-- Per-chain token charts: price, volume, liquidity, market cap, age, and venue.
-- Launch/sniper cards: token, chain, pool, route readiness, sellability, smart-wallet
-  overlap, risk status, and prepared-ticket status.
-- Hyperliquid HIP-3 builder-dex cards: dex, market, mark/oracle, funding, OI,
-  depth, liquidation/risk notes when account context is provided.
-- Hyperliquid HIP-4 outcome-market cards: event/outcome, bid/ask, depth, edge,
-  held-position context when API keys/account reads are configured.
-- Polymarket cards: event, market, Yes/No prices, volume, BBO, resolution-risk
-  notes, and prepared order intent only when user auth/API keys are configured.
-
-## Data rules
-
-- Public/keyless reads are allowed where the venue supports them.
-- API-key surfaces activate only when the user self-hosts and provides their own
-  keys. Never ship DEMI keys or assume hosted secrets.
-- A graph is evidence, not authorization. It can trigger a prepared ticket; it
-  must not bypass quote freshness, sell-sim, grant caps, or wallet signing.
-- Every card states chain/venue and confidence. Unknown data stays `UNKNOWN`.
-
-## Telegram card rules
-
-- Send text card and graph as separate messages when the card is long.
-- Avoid markdown traps: no unescaped underscore labels, avoid repeated `$` spans.
-- Keep full contracts/mints visible; never truncate the only identifier.
-- Chart rendering must soft-fail: card still sends if the image fails.
-- No buy/sell buttons unless the recipient has a valid local grant/session.
-
-## Graph schema
-
-A graph payload should include:
-
-- `chainId` / `cluster` / venue
-- token/market id
-- time window and candle interval
-- price/volume/liquidity series or order-book snapshots
-- source/provider and fetched timestamp
-- warnings for stale, sparse, or degraded data
-
-## HIP-3 / HIP-4 / Polymarket notes
-
-- HIP-3 builder perps require Hyperliquid `perpDexs` and `metaAndAssetCtxs` with
-  `dex` selected; core `meta` does not include all builder-dex markets.
-- HIP-4 outcome markets require the configured Hyperliquid/API-key path for user
-  account/order actions. Keyless cards can still show public market data.
-- Polymarket public reads work keyless; trading/order placement needs the user's
-  CLOB auth/API setup and stays prepared/user-signed.