phu

payments & compliance, onchain

[phu @phulimphad]

this is the "why" under every precompile I've been shipping —
LLM calls, secrets in a TEE, sovereign agents.

they don't re-run on every validator. they run once, in a TEE,
and deliver back. 🔮 #BuildOnRitual

[phu @phulimphad]

just sat through Ritual Academy's first session and one idea reframed
how I think about blockchains entirely

why can't a normal blockchain just... run AI?

(slide credit: Ugur Sen, from the session)

[phu @phulimphad]

@ritualnet's fix: stop forcing identical results.

run heavy/non-deterministic work inside a TEE (Intel SGX / AMD SEV) —
tamper-proof hardware — and check *consistency* instead of re-running.

deterministic = light path. AI = heavy path. both on one chain.

[phu @phulimphad]

but an LLM? forward_pass(x) on different GPUs gives
0.8841 vs 0.8842 vs 0.8840

floating-point math isn't associative + GPUs schedule threads
differently → results diverge → block REJECTED ❌

[phu @phulimphad]

every validator re-runs each tx and the results MUST match.
that's what separates honest nodes from malicious ones.

transfer(10) → 0xABC on every machine ✅ block accepted

[phu @phulimphad]

@elifhilalumucu gRitual

[Elif Hilal Kara @elifhilalumucu]

Introduction to Ritual https://t.co/xrWB3IXtRI

[phu @phulimphad]

gRitual — joining Ritual Academy tomorrow 🔮

been building on @ritualnet testnet for weeks.
time to learn what's next.

#Ritual #BuildOnRitual

[phu @phulimphad]

built on @ritualnet this week

⏰ contract that wakes itself up — no cron, no backend
🔐 authenticated API call with key hidden in TEE

next: sovereign agent 🔮 #BuildOnRitual

[phu @phulimphad]

this is the part that hooked me. been shipping precompiles one by one
on testnet — last one let a contract call an authenticated API with the
key sealed in the TEE. a sovereign agent is the same idea, taken all
the way: it holds its own keys and answers to no one

[Ritual Foundation @ritualfnd]

AI agents today can act, but they can't own.

Every "autonomous" agent still routes its money through a human, a keeper, or a multisig. In each case something other than the agent has to act for the money to move.

On Ritual, your agent answers to no one ❖

[phu @phulimphad]

@okx this month?

[phu @phulimphad]

@elifhilalumucu gRitual💚

[Elif Hilal Kara @elifhilalumucu]

We're building the next generation of Ritual developers.

With 8 sessions, 3 bootcamps & Live whitepaper reads, we are building real builders.

Ritual Academy is here🧵

[phu @phulimphad]

a smart contract just called a private, API-key-gated endpoint —
and the key NEVER touched the chain. 🔮

on-chain you only see an encrypted blob + a placeholder.
the real key is decrypted & used inside the TEE. one tx.

HTTP 200 ✅ @ritualnet

[phu @phulimphad]

@arc 🦄

[phu @phulimphad]

@ritualnet that's it — a contract that reads the real internet, trustlessly.
the HTTP precompile is just the start (there's LLM, ONNX, image,
scheduler too). go build 🔮 @ritualnet

[phu @phulimphad]

you can deploy a smart contract that calls the LIVE internet
from on-chain — on @ritualnet — in about 5 minutes.
here's the whole thing, start to finish 🧵👇

[phu @phulimphad]

@ritualnet 4/ run it (1 min)
call the function → the contract hits CoinGecko from inside the
TEE and writes the price on-chain. one tx. verify on the explorer:
https://t.co/DIgLym45W2

[phu @phulimphad]

@ritualnet 3/ deploy (1 min) — forge create, NOT forge script:
forge create src/HttpOracle.sol:HttpOracle \
--rpc-url $RITUAL_RPC --private-key $PK --broadcast
→ copy the "Deployed to:" address

[phu @phulimphad]

@ritualnet 2/ the contract (2 min)
a contract that fetches a live ETH price via the HTTP precompile
(0x0801) — no oracle, no backend. the chain calls the API itself:

[phu @phulimphad]

@ritualnet 1/ setup (1 min)
• install foundry: curl -L https://t.co/sSwTC46aIR | bash
• add Ritual RPC: https://t.co/bTOkxJtqnN (chainId 1979)
• grab testnet RITUAL from the Discord faucet