made this motion clip w a stealth mode in opencode for @bagel_win
not a bad one for a first try init?
2
9
84
day 17.
#trusttheprocess30days
day 15, 16
#trusttheprocess30days
clip 1: religion ground.
clip 2: holiday is over.
unrelated, im unable to schedule video post w my acct and tried third party application, giving me issues - yesterday clip was uploaded but didn't go through, had to combine with today's own.
1
6
75
unify retweeted
I think one of the most obvious yet slept-on ways to change your life over the next year is becoming the guy people go to for objective AI model comparisons.
maybe I'm wrong, but there's still no real "Marques Brownlee" of AI models - and even if there is, there's 100% room for more.
best name I could think of for X is @AlexFinn - but that's it.
10 scrolls on Instagram as a young tech person and you'll probably find 3 videos telling you the "best AI for …", but so much of it feels like people regurgitating whatever ChatGPT or Claude told them rather than actually using these models extensively and comparing them from real user experience.
and you can niche down endlessly.
if I was a motion designer trying to understand how AI could make me better at my job, the easiest click of my life would be following someone who constantly tests the best models, workflows and tricks specifically for producing excellent motion designs.
same for developers. researchers. writers. students. designers. literally anything.
I genuinely think whoever becomes trusted for this type of work is sitting on the frontline of what could be legendary content creation over the next few years.
the reason I'm writing all of this though is because I want to try. and unfortunately, I need help.
this is probably one of the most embarrassing things I've ever written. I feel ashamed even typing it because I've experienced firsthand what it feels like to try and try and still not get the result.
after a while, you begin looking down on everything you've ever done.
my life really started falling apart after an incident where I was kidnapped and extorted N4.6M by Nigerian police officers (Sept 26 last year)
this happened roughly a day after I received money from the Plasma airdrop - money I had honestly earned being one of the biggest voices for stablecoins in my region at the time
something about me changed psychologically after that.
I entered this phase of thinking:
"if I can hustle for over a year and someone can just take half of it from me, why shouldn't I spend the rest on myself before something else takes it?"
I still invested some of what remained into MegaETH, but far less than I would have with a clearer head and more capital.
you'd think it ends there but roughly two months later, another disaster happened.
unify retweeted
one of the biggest challenges in digital hardware design is proving that you actually know how to design and build working circuits. 🧵 🖊️
imagine you’re applying for an embedded systems or digital design role. a company gives you a take-home test, you complete it, submit your work, and someone manually reviews it.
the problem is that the result stays private. there’s no easy way for another company, instructor, or reviewer to independently verify that your design works.
the same problem exists in education and within the tapeout ecosystem.
students submit simulation screenshots, developers share github repositories, and builders showcase their circuits, but verifying the actual work can still be difficult.
there’s also a problem with open competitions.
since @TapeOutWorld makes circuit designs public when they’re submitted, someone can simply wait for another person to publish a working solution and copy it.
so how do you reward the person who actually committed to solving a challenge first?
my idea as a solution: circuitcred
circuitcred is a sealed hardware design challenge and verification platform built on @TapeOutWorld and @XLayerOfficial
it allows anyone to create a hardware design challenge, invite others to solve it, and verify who submitted a working solution before the deadline.
think of it as a coding assessment platform, but for hardware and digital circuit design.
the difference is that @XLayerOfficial handles the commitment and verification process.
every successful submission gets a public, verifiable record that anyone can inspect without connecting a wallet.
how circuitcred works
the entire process has four stages.
->publish a challenge
a company, instructor, or community organizer creates a challenge.
for example:
“design an 8-bit ALU with carry and zero flags, using no more than 120 gates.”
the host defines the requirements, test cases, gate limit, submission deadline, and reveal deadline.
the challenge is published through the host’s own DeWEB container.
->commit your solution
participants read the requirements and start designing their circuits.
they can use the tapeout canvas or write their designs in Verilog and compile them using TapeSynth.
before the submission deadline, each participant submits a cryptographic hash of their design.
this is important because the actual circuit remains hidden.
nobody can see or copy another participant’s solution at this stage.
participants can update their commitment before the deadline, but only their final commitment counts.
->reveal and verify
once the commitment deadline passes, participants can reveal their designs.
they tape out their circuits and submit the information needed to match the original commitment.
the smart contract checks several things:
-does the participant own the submitted circuit?
-does the circuit match the hash they committed to earlier?
-is the circuit within the allowed gate limit?
-does it pass the required test cases?
-does the submission meet the challenge requirements?
the contract checks a sample of test cases directly on-chain.
the full test suite is then independently executed using the TAP-02 reference evaluator.
if the checks pass, the participant receives a successful on-chain record.
->public verification
this is where circuitcred becomes useful beyond the competition itself.
anyone can open a submission record without connecting a wallet or creating an account.
they can see:
>the challenge and its requirements
>the solver’s wallet address
>the circuit submitted
>the number of gates used
>the original commitment block
>the reveal block
>whether the design passed verification
the browser independently runs the full test suite and checks the result against the blockchain.
this gives reviewers a way to verify the result themselves instead of relying on screenshots or someone’s word.
Good ideas deserve to be heard.
Tweet about what you wish existed onchain, tag us and @TapeOutWorld, and stand a chance to win 2K USDT.
Ends Nov 17. Submit here: bit.ly/4eQxFIH
Check this out real quick, just saw an underrated gem on arc 👀
it's called @Aurumlend, a lending protocol built on Arc.
the main idea is simple. you supply usdc and earn yield on it. borrowers on the other side pay interest to use that liquidity, and that interest goes to suppliers.
what makes it fit arc so well, i think, is that usdc is the gas token there. the whole chain basically runs on dollars, so having a place to put idle usdc to work feels like one of the first things the ecosystem needs.
a few things i noticed:
• markets for usdc, cirbtc and weth
• supply and borrow rates shown side by side, so it's easy to compare
• staking is listed as coming soon
it's still early, so worth getting familiar with now.
as always with lending, read up on collateral and liquidation rules before you borrow anything.
take a look 👇
aurumlend.finance
🤝 Paid partnership
day 15, 16
#trusttheprocess30days
clip 1: religion ground.
clip 2: holiday is over.
unrelated, im unable to schedule video post w my acct and tried third party application, giving me issues - yesterday clip was uploaded but didn't go through, had to combine with today's own.
spendGuard is live on near testnet.
what does it do?
a coding agent that pays for API calls usually holds a key with money behind it. one poisoned readme, and it tries to spend past what you meant to give it.
SpendGuard moves the money into a contract. the agent keeps a restricted function-call key that can call request_spend on one contract and nothing else. it can ask to spend. it cannot approve itself, change the policy, or touch the treasury.
when it asks, the contract checks four things at that moment:
- is the vendor on the allowlist?
- is the amount under the per-spend cap?
- does it fit the budget for this period?
- is it inside the rate limit?
you approve or refuse the from cli. every decision leaves a receipt either way:
- approved or denied.
- the rule that passed or failed.
- the amount, the vendor, what is left in the budget.
- a receipt id anyone can read from the public RPC.
the console shows the same receipts with no backend and prints the curl commands behind every number, so you don't have to trust the page.
url: spendguard-oxunify.vercel.ap…
repo: github.com/unifyWeb3/near-bo…
if you run an agent that can spend, where should the policy be stricter?
built at NEAR HACKATHON @NEARProtocol #NEARHackathon
the project is Certalyn now, a spend limit for an agent that pays.
the console and the repository in this thread are the ones it describes: near-bound.vercel.app and github.com/unifyWeb3/near-bo…
5
introducing meridian: a hermes plugin that finds the state machines nobody wrote down and holds them to rules you write.
it reads your source, finds every status machine, and anchors each transition to a file:line. you write the rules. `hermes meridian check` enforces them: exit 1 on a forbidden edge. no model calls, no network, stdlib only.
new, built on hermes hooks: when an agent's edit touches a state machine, meridian flags the break on its next turn. advisory, it never blocks.
and every run leaves a receipt:
- the event name.
- the machine ids.
- the counts: files scanned, violations found.
- a hash that commits to the previous entry.
the chain is unkeyed, so it detects edits but anyone with write access can recompute it.
try it: hermes plugins install unifyWeb3/meridian
repo: github.com/unifyWeb3/meridia…
built for the Hermes Agent Plugin Hackathon @NousResearch #NousResearch
The Hermes Agent Plugin Hackathon starts now!
It runs for 7 days, with $20,000 in cash prizes and more.
Plugins are the most powerful way to extend Hermes Agent, and we want this hackathon to show what they can do. A plugin can change anything from the model Hermes runs on, where it stores its memory, where it runs commands, which messaging apps it works in and what Hermes Desktop shows. Plugins in the marketplace already let Hermes do things like control a phone or turn a photo into a printable 3D model.
Every kind of plugin is eligible, so build whatever functionality you want Hermes to have. We'll list accepted entries in the new Hermes Marketplace, where every Hermes user can install them.
Prizes
1st: $10,000 + neon sign + merch + $1,000 creds
2nd: $5,000 + neon sign + merch + $1,000 creds
3rd: $2,500 + neon sign + merch + $1,000 creds
4th: $1,500 + merch + $500 creds
5th: $1,000 + merch + $500 creds
Runners up (x5): merch + $250 creds
Submissions are due 5PM EST on Nov 11th. To enter:
1. Open a pull request that adds your plugin to the Hermes plugin catalog: hermes-agent.nousresearch.co…
2. Post a demo video on X and tag @NousResearch
3. Submit both links through the form: form.typeform.com/to/FwJLvOl…
Your entry is the plugin itself. Judges score it on usefulness, reliability, polish and creativity, and they favor plugins that do more than a prompt or a skill could. Keep the demo under 90 seconds and show the plugin working.
The developer guide shows how to build and test a plugin: hermes-agent.nousresearch.co…
When submissions close, we'll open a thread for every entry in the Nous Research Discord, so you can browse all the plugins and talk to the people who built them.
You can submit the form as soon as your pull request is open. The catalog checks run once a maintainer starts them, and we review entries every few days.
If you have any questions stop by the Nous Research Discord: discord.gg/nousresearch
GLHF!
now live on nous marketplace: hermes-agent.nousresearch.co…
would lub y'all feedback.
11
AI agents are starting to trade with real money. The hard part isn't the strategy. It's what happens when the agent is wrong, manipulated or compromised.
IntentRail keeps the agent's funds in a NEAR contract that enforces the owner's limits itself.
✨ website : intentrail-neon.vercel.app
✨ github repo : github.com/Onegeex/intentrai…
Built at NEAR HACKATHON for @NEARProtocol, AI Security & Defense track #NEARHackathon 🧵
off topic btw or maybe not.
why did someone seat down and built bolt when uber was already right in the market?
and even crazier after uber had completely locked down the market, why did somebody else wake up and say you what? let's build inDrive.
































