---
name: uncle-matts-randomifiers
description: Integrate, call, explain, or verify Uncle Matt's Solana and Robinhood Chain fixed-basket formula oracles. Use when an agent must select the correct chain path, check deployment status, construct a call, or describe the public-good access model.
---

# Uncle Matt's Randomifiers

Use this skill for either Randomifier formula-oracle implementation.

## Contract

1. Identify the requested chain: Solana or Robinhood Chain.
2. Read the matching reference in `references/` before constructing a call.
3. Verify the deployment identity and live status from current source or a read-only chain probe.
4. Preserve the exact basket, order, ABI, and validation rules.
5. Report the result and evidence fields, or report why a complete valid X is unavailable.

Completion means the chain, deployment status, call path, cost boundary, and deterministic-not-VRF boundary are all explicit.

## Routing

- Solana client call, Pyth feeds, program ID, instruction data, or return data: read `references/solana.md`.
- Hood, Robinhood Chain, chain ID 4663, EVM ABI, adapter, or `computeX()`: read `references/hood.md`.
- Availability, public-good, permissionless, free, fees, RPC, gas, or launch status: read `references/status-and-costs.md`.

## Guardrails

- Treat X as deterministic public-market-data computation, never as a VRF or unpredictable randomness.
- Use every frozen source in the published order. A partial basket is not X.
- Use current addresses and chain output. Never invent a program, contract, feed, adapter, or deployment status.
- Interpret validation failure as “no complete valid X is available.” Do not substitute stale or alternate data.
- Keep all private keys, wallet material, authenticated RPC URLs, and deployer secrets out of output.
- Mainnet broadcast requires the operator's explicit approval for the exact command. Read-only calls do not.

## Public-good language

Lead with: “Built at Uncle Matt's expense. Available to everyone once live.”

Then say: “No Randomifier subscription, API-key fee, provider fee, protocol fee, or license fee is charged.”

Also say: “Normal chain transaction fees and third-party RPC costs can still apply.”

Do not shorten those two statements into “all blockchain use is free.”

## Output

Return:

- selected chain and cluster;
- verified deployment identity and status;
- exact call method or the missing launch prerequisite;
- X, normalized exponent, basket identity, and composite evidence when available;
- service-fee and network-cost distinction;
- any failed validation or unknown explicitly.