Noah 🫡🦇🔊

Excited to announce that I will be interning @SinoGlobalCap, thank you @mattysino for the opportunity. No more simping only sigma octrillionaire grindset now

Booster Robotics T1 is in the lab. first job: wire up our VR remote teleoperation stack so a human operator can step in for the edge cases. then task routing. then the data flywheel.

landed in the lab

@garrytan @Hey_Amiko coded?

This is actually a good idea.

Robots get stuck. A lot. The Homebrew stack lets a remote operator take over from hundreds of km away and pilot it back to autonomy. Here's how. 👇

@daniel_chi80344 @homebrewrobots @MigrateFun Should be this one: dexscreener.com/solana/gtgc8en…

@homebrewrobots @MigrateFun Am new here how can I get the real contract address

BREW token has migrated. Holders who previously migrated can claim their new tokens here: migrate.fun/claim/mig155 Special thanks to the @MigrateFun team. See our 'how to video' below 👇

Action item for @machinedex BREW LPs. Post migration, a new pool will be re-established!

Another sprint done. We've been showing you the pieces and we connected them this sprint. A robot asks for help, gets a human operator in VR, and pays them in SOL -- without a human initiating any of it. 23 deliverables. 14 closed.👇

Here's what we've built: a payments layer, a task router, and a remote operation module. The infrastructure for handling robot deployment edge cases in the real world. Each one in action below.👇

@vedantutage03 @dhruvgera_ Happy to hop on a call ser 🫡

if you know any early stage vc’s in payments we are looking to close our round >100% MoM growth >800k+ gross volume processed we have numbers to share. cfbr

@vedantutage03 👀

these boxes have been popping up at different locations all over India 🇮🇳 beware of opening it you just might be the favoured child of the tax gods 👀

Homebrew Robotics migration page is now live. You can view the migration details here: migrate.fun/project/mig155 Migration opens March 24, 1 PM EST. More details soon.

you've probably seen screenshots of $DRV OI next to Hyperliquid and Aster from ppl shilling it as "undervalued" i dug into the numbers. here's what's actually going on first, that $1.3B OI is almost entirely options notional. Derive's own dashboard breaks it down: BTC: $528M total OI • $507M options • $21M perps ETH: $97M total OI • $94M options • $3.4M perps so actual perp OI is only ~$24M. the "$1.3B" figure comes from options notional value (which makes sense because Derive is an options protocol). but options notional and perp OI are completely different things. in perps, $70k notional = a real $70k position with collateral and liquidation risk. yes leverage inflates it, but typically by ~5–10x. in options, $70k notional just means the contract references $70k of the underlying. the premium paid might only be $200–$400. the inflation vs real capital can easily be 100x+. this is why TradFi doesn't report options OI in notional. CME and CBOE report contract count. Deribit (the largest crypto options exchange) does the same: • 483,124 contracts headline • $33.7B notional shown separately clear and transparent. Derive only shows notional OI as the headline, with no contract count on the trading UI. so i went to their stats page. Derive has roughly ~8,000 BTC options contracts across all strikes. Deribit has ~483,000. that puts Derive at ~1.7% of Deribit's size. to be clear, i actually like Derive as a project. the team is solid. but when someone puts Derive's "$1.3B OI" next to Hyperliquid and Aster and says "look how undervalued", they're comparing options notional to perp OI. it's apples to oranges. also worth noting: Derive's OI is concentrated in just two expiries (March 27 and June 26), suggesting a small number of large positions. so the real picture is: • ~8,000 options contracts • mostly one-sided call selling • concentrated in two expiries • ~1.7% of Deribit's size if someone's selling you $DRV based on "$1.3B OI at $76M mcap", they probably don't understand options. also @DefiLlama can do better here. options protocols like Derive shouldn't be ranked by notional OI alongside perp protocols. either show contract count for options or at least separate the categories. the current setup is misleading

@vedantutage03 Sched for tomo, super interested to hear more 🫡

gold mine for freelancers let’s chat about structuring your USDC/USDT freelance payments the right way drop me a dm if your company pays you in stablecoins and you are looking for a good structure to receive INR personally helping few people understand this on call and start a great tax year ahead drop a dm 👀

We gave our robot a simple OpenClaw task: find a screwdriver. Could it do it?

DEMO: Triggering real-world robot actions with Homebrew's Task Router. - Select a task (v1 tasks) - Robot prompts for an x402 payment to unlock it - Payment clears -> robot executes

tldr on @homebrewrobots entry first thought ‘build a robot’, realized real opp is commerce/end use cases…built ‘x402 action node’, now agents can pay for robot task via API. Vision too narrow, found killer use case in ‘teleoperation on demand’, help robots get unstuck, remotely…there will be factory sized centers piloting robo fleets 100s of km away…homebrew should build that! Built PoC (route+payments+teleop+platform), now we tighten latency/support more robots. All @Pumpfun support goes back to product.

We outgrew our old logo. New logo. New phase. Shipping products that turn robots into economic actors.

Robots + firecrackers + skateboard = ?

Wait...did my robot just hongbao me?