Loading video...

Video Failed to Load

Go Home

🚨 FRONTRUN MINT SCHEDULE🚨 In partnership with OpenSea Five years ago I minted my first ever NFT on OpenSea. Now It gives me great pleasure to come back to OS with my first fully on-chain, long-form generative art collection. FRONTRUN. 420 pieces, fully on-chain on Ethereum. The wallet that...

28,568 views • 1 month ago •via X (Twitter)

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

Someone just posted the full blueprint for an AI swarm that does the job of a 200-person quant research team. Six agents. Running 24/7. Finding brand-new alpha while you sleep. Citadel needs 100 PhDs to do this. Two Sigma needs 200. This does it with six bots and one laptop. Two ways to play this - spend a weekend building your own swarm, or copy the wallet of one that's already up $2M: Boris Cherny runs Claude Code at Anthropic. Two weeks ago he said: "I don't prompt Claude anymore. I have loops running that prompt Claude. My job is to write loops" Alpha research is just a pipeline. So instead of sitting in it, you hand each stage to its own agent: > one reads every new research paper overnight and pulls out the trade idea > one builds the features and cleans the data > one backtests it over 20 years, costs and slippage included > one runs the hard stats and kills anything overfit > one checks it still works in every market regime > one strips out plain momentum and value to see if any real edge is left Each of those six is a job a fund pays a $600,000-a-year quant to do. He runs all six for the price of an API bill. The rule that makes it work: the agent that builds a signal never gets to approve it. A separate, stronger agent tries to kill it first. Whatever survives all six by morning is real, new alpha. One trader's already running this exact swarm on Polymarket. That $2M wallet is public, every trade on-chain. The full build is in the post below - six agents, the tool that runs them, and the five mistakes that kill most people. Bookmark & read this before it's buried.

cvxv666

103,734 views • 1 month ago

Agents vs. Graphs, clearly explained! spawning more agents is great, but it has a ceiling nobody says out loud: five agents is a count. a graph is a shape. only one of them changes the answer. point five agents at the same pile with the same window and they converge. the first one writes a finding, the rest read it, and all five reports centre on the same thing. you paid five times for one opinion with four echoes. Graph engineering fixes this by moving the decision up a layer: not how many agents, but who is allowed to look at what. you need both. here's how it works: ↳ the count buys you throughput. five things happening instead of one ↳ the shape buys you coverage. five different things happening instead of the same one five times Prompts → Context → Harness → Agents → Graphs the node that does this is the splitter, and it decides more than any other node in the system. cut a repository by folder and four workers audit the same three files. cut it by blast radius and each one sees something the others cannot. the trick is being selective about what each lane is allowed to see. separate contexts are not a nice-to-have, they are the mechanism. if two agents are meant to produce different things, they must not share a window. if they are meant to produce the same thing, you did not need two agents. one thing to know before you scale it. a branch that throws does not reject the batch. it resolves to null, and that is the containment. which means your merge quietly receives a short list. ↳ filter the nulls before the merge, or one dead lane poisons the whole result ↳ never index a merge by position. eight good branches and one failure will shift everything by one, silently skip that and the run looks like it worked. the output is just missing a lane, and nothing errored. and the one that eats whole nights: multi-agent setups can use up to fifteen times the total tokens of a single chat, because every lane reloads its own core. you are trading total tokens for a clean main window. usually the right trade, always a choice. below i have quoted my full guide on graph engineering. it covers the three topologies, the verifier patterns, and where the gate should actually open. save this and read it below ↓

Hanako

92,124 views • 2 days ago

🚨 New STEPN and STEPN GO in-game challenge just dropped: The Marathon Challenge 👟 This one is simple, yet kinda brutal. Here’s the deal: you lock in a fee, you move EVERY day, and you earn GGUSD from participants who didn’t make it! Join through either the STEPN GO main menu (just tap the Marathon icon) or the STEPN pop-up when you launch your app, then: 🔐 Lock 50 $GGUSD to activate your Marathon Subscription 👉 You can join from either STEPN or STEPN GO (or both), but your participation counts as one single entry total. 🎁 Earn weekly rewards for participating, or upgrade to the Season Pass for 20 GGUSD to unlock extra rewards! 🗓️ How it works: - Each season lasts 12 weeks, made of 6 rounds (2 weeks each). - If you miss a round, you can register for the next one before it starts. 🛎️ For Round 1, you must register before October 26 at 11:59 PM UTC. Once registration closes, Round 1 begins, no late entries. From there, your one job is to use 2 Energy every day in STEPN or STEPN GO. Simple right? ⚠️ To qualify, you need to complete 2 Energy in at least one app between 00:00 and 23:59 UTC each day. ✅ If you make it to the end: You keep your fee, auto-enroll in the next round (unless you hit “unlock”), and you get a cut of the pool from everyone who didn’t make it: straight to your wallet. ❌ If you miss a day: You’re out. Your fee goes into the prize pool. GGs. That’s it: just a fun challenge that rewards consistency 💪 The first round starts on October 27! Let’s see who can really stick with it!

STEPN GO

177,866 views • 10 months ago