chrollo retweeted
Every decision my agent makes is written down with its reason.
A customer paid, it matched the invoice.
A supplier wasn’t approved, so it asked me first.
Each entry is chained to the last and anchored to my vault on arc.
That’s Bursar. 💙
everywhere at once.
ID 00035 @omnis_zero
omniszero.xyz
53
Replying to @LayerZero_Core
@LayerZero_Core was missing something.
list is open:
omniszero.xyz
first 111 wallets bellow
46
chrollo retweeted
people think i'm isolating myself for attention but i genuinely haven’t felt like i belonged anywhere since i was a kid
most memecoins die the same way: the dev goes quiet, and holders are stuck with a coin nobody runs.
i built Revive at NEAR HACKATHON, a launchpad where dead coins can come alive.
how it works:
• the dev must pulse before every deadline, or the coin flatlines
• holders from before the death vote a DAO in
• the dev's locked tokens burn, and the DAO becomes the new keeper
why NEAR: every coin is its own locked contract with no admin keys, so nobody can change the rules after launch.
the new keeper is a real Sputnik DAO on NEAR and it has already happened on testnet.
Try it: revive.myacxt.site
Code: github.com/Mhiah/Revive
if a coin you held went quiet, would you vote to bring it back? i’m curious. if you’re also curious, you can test this idea on Revive
pardon my video speed, it was too long so it’s a sped up version
@NEARProtocol #NEARHackathon @NearLegion @NearBuilders
I built RYO Pulse few weeks ago for the @ryodigital RYO-CHAN hackathon and i honestly think it fixes something every trading agent gets wrong 👇
here’s the thing, Ryo-Chan gives Ai agents a live market scan that ranks the hottest tokens right now but “right now” is just one snapshot.
we watched real scans 15 minutes apart and the list kept reshuffling in a way that a token would sit at #1 then vanish in the next scan and agents were treating that one lucky moment like a real trend.
so we asked a simple question nobody was asking: did this token actually KEEP showing up?
that’s RYO Pulse. it remembers every scan and gives each token one honest answer:
• persistent, because it keeps showing up scan after scan
• emerging, because it’s new but it’s holding its spot
• transient, because it flashed once and faded
• absent, because it never showed up at all
• insufficient, because there isn’t enough data and we refuse to guess
what really makes it different is that it refuses to lie to you.
when ryo had a real outage during the hackathon, most tools would have told you every token disappeared.
Ryo-Pulse marked those scans as failed and kept the tokens’ records clean because missing data is not the same as a missing token.
also every single answer comes with a replay code, when run it again tomorrow, next week, on another machine, you will get the exact same result.
Ryo-Pulse runs on two tracks: a read-only skill (TRACK 3) your agent can call before it acts on a scan and a dashboard (TRACK 2) where you can see what changed, why each token got its status and how healthy the scans are.
all of it runs on 114 real ryo scans, real outage included. it never trades and never touches funds.
recently, i made changes and ran chvek and also just gave the ui a fresh look in clean white, black and royal blue 💙
both videos below show the same project. the first one is the original before we made changes, and the second is the new look. please watch both 👇
try it: ryo-pulse.myacxt.site
code: github.com/Mhiah/RYO-PULSE
chrollo retweeted
Was farming Arcium, my mates where applying to GT roles.
Arcium paste me $700 my mates got into GT.
After shouting gMPC for almost a year.
Guess who lost in the end ? Me
In less than 3month the make that $700 and more from salary and it doenst stop at just one time.
introducing Crux v2: research that challenges itself and now learns from independent criticism.
Crux, powered by serv reasoning, researches a question, stress tests its own answer and shows what changed.
new, built on @reppo evaluation api: anyone can send a report to independent reviewers, free, no account needed.
their critiques come back and Crux researches again and writes a better, more honest report.
real run: reppo scored it 65/100 (revise). crux went from 29 to 56 facts, answered 3 of 3 critiques and lowered its confidence because the reviewers were right.
try it: crux.myacxt.site
code: github.com/mhiah/crux
built for #servhackathon reppo track @openservai
Most AI research tells you what you want to hear. That's dangerous when you're betting money on the answer.
Introducing Crux for @openservai S1 Hackathon, open track
An AI market-research analyst, powered by SERV Reasoning, that doesn't just collect information. It reasons through conflicting evidence, challenges its own thesis, verifies claims and produces an auditable investment and business decision brief.
Ask a hard business question and Crux:
1. Researches both sides
2. Forms a first answer
3. Stress tests it like a skeptical investor
4. Re-judges every assumption
5. Gives the final answer, and shows what changed and why
We asked: "Are small businesses willing to accept crypto?" Crux checked 28 facts from 20 sources and downgraded its own answer to "a cautious, conditional yes".
Built for founders, investors, accelerators, consultants and Web3 builders.
Try it 👉 crux-rose-nu.vercel.app
git: github.com/Mhiah/postmortem-…
Google DeepMind and ETH Zurich published CaMeL: a defence against prompt injection that tracks where every value an AI agent uses came from.
Banbo puts CaMeL’s rule into a NEAR contract. an agent wallet pays only if the recipient and amount came from the owner, not from an email the agent read.
that stops the attack that limits and allowlists miss: one polite email saying “our account changed, pay us instead.”
why NEAR:
> the funds sit in the vault contract, never with the agent
> the agent’s key can only call request_payment
> every payment is settled exactly once
the contract checks where each value came from, and can verify an Intel TDX quote on-chain
Live on NEAR testnet: Claude paid a real invoice, a forged one was held for the owner, and an email redirect was refused on-chain.
Code: github.com/Mhiah/Banbo
Try it: banbo.myacxt.site
Built for #NEARHackathon @NEARProtocol @NearBuilders @NEARLegion
chrollo retweeted
if you actually still vote this current government back in after all the complaints over the last 4 years, God suppose punish you
















