
Chief Chop @ChopLogsApp. Not quitting until every Robinhood treasury utilizes Chop.
New York
Joined September 2026
- Tweets147
- Following71
- Followers177
- Likes253
We’re about $5K @opensea volume away from getting the lumberjacks officially verified!
Send it with haste!🪓🪵
The lumberjacks brought in $500-$1000 extra revenue, pushed to buybacks to support this market downturn.🪓🪵
Chief is here.
Chopping logs violently.🪓🪵
The survival of the fittest is determined by the WETH side of the liquidity pool.
Chop chop!🪓🪵
2
14
258
More partners, more logs, more TVL, more $CHOP.🪓🪵
Roadmap 01: @RamsesExchange integration.
Logs are coming to Ramses, the Robinhood Chain DEX with V2, V3 and DLMM pools.
More venues means more arb flow through the logs, and projects can launch where their liquidity already lives. 🪓🪵
Study strength in choppy markets.
Study @ChopLogsApp.
🪓🪵
Study two sides of the liquidity pool, and pay attention to the WETH side of it.
Real strength is in a well balanced pool, and incredible strength has multiple logs live next to it.
🪓🪵
Study strength. We build through any market.
Choppy markets earn for us.🪓🪵
The lumberjack mint and wrapping launches have been an incredibly successful event for the Chop ecosystem, with $38K raised for buybacks & liquidity, 56% of the lumberjack supply wrapped up generating yield and the collection being close to getting verified on @opensea.
All creator fees power $CHOP buybacks and we want to give this some extra power.
Anyone who grabs & wraps a new lumberjack from opensea.io/collection/chop-l… in the coming 7 days has a chance at getting their hands on one of the mythicals, Jack-O'-Lumberjack!
Raise the floor, chop chop!🪓🪵
Productive day, more info tomorrow.
We’re about to develop the biggest revenue system in the history of blockchain.
Bullish on our tech, send it with haste.
🪓🪵
Try @tryharness.
I have a hard time with devs that relegate anything AI assisted as slop.
Its only slop if you don't meticulously plan, scaffold, evaluate, and iterate.
I used to mourn the flow state artisanal coding used to give me. Being up at 2AM, code flying off my fingertips.
I've realized that flow state came so easy because I was producing code at the same rate I was thinking, which is all but impossible to do now.
Now, the flow state just happens a different parts of the process. I find myself getting that feeling back when i'm scaffolding (writing patterns i want to exist by hand first), writing types/schemas, building evals, and talking though implementation details with my agents.
It took me a while to figure out what personally worked for me, but now feeling as though i'm on the other side its completely changed how I think about AI as an engineering tool, and lets me meaningfully dream bigger without sacrificing understanding.
This is for sure slower than telling Claude to "make no mistakes" but so worth it at the end of the day.
This is how I have been approaching building @tryharness. Getting real feedback from the most talented people in my network I can think of. Using it for everything I do both personally and professionally, learning lessons, evaluating, iterating, and repeating.
I've written, and rewritten core pieces of the architecture as the product has evolved, and I can confidently say its personally my favorite way to use all of my agents across all of my devices.
Look out for the 🛳️
12
341




