> weekly rewards top 1–5 on the leaderboard → GTD top 6–10 → FCFS every week by natty points

NEW NFT COLLECTION ON RITUAL it's been quite a while since i made PFPs for various people in the @ritualfnd community I'd like to announce that preparations for an upcoming NFT collection at @ritualnet began on OCT 1 - common ~60% - rare ~25% - epic ~12% - legendary ~3% something is coming...

RITUAL MAINNET SOON i've found evidence that @ritualfnd is very similar to @monad, but there's one catch ~ 14/10/2026 > 14/10/2026 ~ community first! > community last? ~ @joshsimenhoff > @keoneHD ~ AI > L2 ~ gritual > gmonad check your boxes lmao

[ritual: why the chain runs two execution paths] hello everyone! @ritualfnd keeps getting called "an ai chain". that undersells what's actually built, so let's look under the hood the core idea ritual chain (id 1979) runs two execution paths over the same state: - replicated - every validator re-executes it, like normal evm - delegated - heavy stuff (llm inference, http calls) runs on specialized executors inside TEEs (hardware enclaves) why this matters if every validator had to re-run an llm, all of them would need gpus. ritual flips it: validators verify the executor's attestation, not the computation itself. the result is cryptographically bound to the request, so an executor can't just make an answer up precompiles, but not really 16 native precompiles are enshrined at the protocol level, for example: - 0x0801 - http calls from a smart contract - 0x0802 - llm inference - 0x0800 - onnx models - 0x0820 - agent orchestration and instead of baking them into the execution client, ritual runs them as containerized sidecars next to it. in theory anyone who can package a sidecar can get their compute onto the chain async, three flavors - sync - result comes back inline - short-running async - http/llm calls finished within ~2 sec, result lands in the receipt - two-phase async - long tasks get a task id and deliver the result later via a callback tx one detail i like: each EOA can have only one pending async job at a time. simple anti-spam for the mempool, while scheduled txs bypass it scheduler = agents that don't die the Scheduler system contract runs recurring, delayed or conditional txs. so an agent can wake up, do its job, schedule its next run, and repeat - no external server, no cron on someone's vps. block time is ~350ms, so this actually feels fast my take most "AI x crypto" projects bolt a model onto a contract via an oracle. @ritualnet changed the chain itself. whether it wins depends on adoption, but architecturally it's one of the few that isn't just a wrapper i've been in the ritual community since OCT 30, 2025 and every month the docs get deeper

hi i'm na2raaaa In the nearly 1 year i've been part of this ritual, i've done enough for the community ~ created a popular PFP collection last year that many people used ~ became a ritty in May 2026 ~ became a ploplo ambassador and the main NFT holder ~ made a bunch of edits and cards for the whole community ~ has created more than 5+ guides on the ritual ~ more than 15+ event hosts ~ 1 twitch stream with community ~ more than 10+ tournaments in various games against other projects ~ one of the first genesis roles on the server there's been some good news lately so it's worth showing what you've been up to during this time @ritualnet @ritualfnd

something is coming up very soon