AA

BASE |

[V @goodvimonly]

$liq github showing first proofs of $wstdiem thesis <20min ago

[json @json1444]

https://t.co/WSAOFXQpKe

[AA @MoonBenzi]

Back to hibernation

[AA @MoonBenzi]

@binji_x ETH CTO

[AA @MoonBenzi]

The appetite to lock in is fading

[AA @MoonBenzi]

@base B20?

[AA @MoonBenzi]

@_proxystudio Liq szn?

[AA @MoonBenzi]

@0xmikedee @ciphermobi @base Sad

[AA @MoonBenzi]

The perfect insight

[votesa ■ @votesa]

$SURPLUS is a case study in how founder ambiguity can turn a “community token” into startup runway.

the setup was simple: $SURPLUS launched on bankr, and @mac_eth was the fee receiver from day one.

every trade created volume, every trade paid fees, and those fees accrued to a wallet connected to the founder side of the story.

that matters because the entire market was trading one question: will mac accept this token or not?

early on, the answer looked like no.

he publicly distanced himself from existing community tokens, saying he was “not really planning to endorse one of those” and wanted different mechanics, including a DIEM pair.

then the answer started to move.

as the token ran, the framing changed from “not planning to endorse” to “i’ll acknowledge the token in a bit.” later, the community had “coalesced around the existing token.” then fee revenue was being discussed as something that could potentially pay for community/token management.

then the framing softened again.
SURPLUS became “just a community launched bankr token.” there was opportunity to build on top of it, but “nothing exists right now.” later, the line was: no allocations, just a bankr community token.

read that sequence carefully:

• not planning to endorse
• will acknowledge
• community coalesced around it
• maybe use fee revenue
• just a community token
• nothing exists right now
• no allocations

that is not clear founder communication. that is a moving target.

and every time the target moved, the chart repriced.

SURPLUS went from around ~$65k mcap near the early “not endorsing” stage to roughly ~$10m near the highs.

that move was not driven by clean token utility or product revenue. it was driven by founder proximity, market speculation and the question of whether this would become the accepted Surplus token.

that is where the incentive conflict starts.

the same person whose words moved the market was also the fee receiver on the volume created by those words. whether intentional or not, that is a dirty setup.

there was another thing that felt strange early on. before mac had fully acknowledged the token, i noticed he followed me even though we had never interacted before.

maybe that means nothing. but when you look at his account, he follows 3,000+ people, including a lot of base influencers, trenchers and attention nodes.

why does that matter?
because if your token narrative depends on mindshare, then surrounding yourself with the exact people who can move that mindshare is not random.

it looks like pre-positioning: build visibility, get closer to the base attention graph, keep the token unofficial enough for deniability, but visible enough for speculation.

maybe it was just networking. maybe it was not. but in the context of everything that followed, it fits the same pattern: move attention first, keep the answer unclear, then let the market trade the uncertainty.

ambiguous founder signals create speculation. speculation creates volume. volume creates fees. fees become runway.

then the chart collapsed.

after the token was already down heavily from the highs, mac posted an AMA. he said the product had $0 revenue, trading fees were the only way to afford a team, total fees were a little over 6% of supply, and he sold around 2% to get 2-3 months of runway.

that post said the quiet part out loud.

the product was not funding the token. the token was funding the product.

holders were the runway.

and the worst part was not even the first sale. it was the overhang after it. he said he planned to hold the rest unless he needed more to pay the team.

that means every future pump now has a permanent question attached to it: is this a real recovery, or just more liquidity for the next runway sale?

that is why this looked so bad. not because teams never need money. not because founders should build for free. the issue is that the funding source came from a market that had been pushed around by weeks of unclear founder signals.

the clean version would have been easy:

• this is the accepted community token
• i am the fee receiver
• fees may be sold for development
• product revenue is currently zero
• buying this means funding the team through trading volume
• expect sell pressure if more runway is needed

that would be honest. risky, but honest.

instead, the market got ambiguity first and disclosure later.

first, the token was not really endorsed. then it would be acknowledged. then the community had coalesced around it. then it was just a community bankr token. then nothing existed yet. then fees were sold for runway.

that is founder optionality.

when accountability is risky, it is just a community token. when traction is useful, it gets acknowledged. when fees accumulate, it becomes runway. when holders complain, the answer is that the alternative is zero months of funding.

you cannot have it all ways.

either the token is meaningful enough to fund the team, or it is not meaningful enough for holders to expect accountability. picking whichever framing is useful in the moment is the entire problem.

and this is where the “poor comms” excuse becomes too generous.

in a normal startup, bad communication is annoying. in a founder-adjacent bankr token, bad communication is a market mechanism. it moves price, creates volume, generates fees and funds the team.

so even if you give mac the benefit of the doubt, the outcome is still ugly: unclear signals pumped attention into the token, the fee receiver benefited from the trading activity, holders ate the drawdown, and the project walked away with runway.

the less charitable read is worse.

this looked like a volatility farming loop: keep the market guessing, let the chart run, collect fees on the volume, sell part of the stack after the hype, then leave open the possibility of selling more later.

and honestly, i would not be surprised if the next move is a burn, buyback, fee redistribution, new utility announcement or some “community alignment” patch.

not because that would fix the core problem, but because it could restart activity in the book after they had a chance to buy the bottom.

create remorse, show “alignment,” make trenchers feel like the founder learned his lesson, and hope everyone forgets the sequence that came before.

that kind of redemption arc is also a volume event.

and in this setup, volume is never neutral. volume creates fees.

the point is not that SURPLUS is fake or that the product can never work. maybe the team ships. maybe the product eventually starts generating revenue. maybe the money is spent well.

but none of that fixes the core issue: holders were pulled into a market where the founder’s framing kept changing, while the founder side collected fees from the volatility that framing created.

that is not clean fundraising.

that is not community alignment.

it is emotional whiplash engineered around maximum extraction: pull the chair back when accountability is risky, push it closer when traction is useful, let the crowd trade the uncertainty, then harvest the volume.

[AA @MoonBenzi]

meanwhile.. @_proxystudio cooking silently.

[AA @MoonBenzi]

One guy sold his bags the whole TL rioting

[AA @MoonBenzi]

LMAOOOOO

[Hunter Biden @HunterBiden]

@AngelaBelcamino

[lurks @onchainlurk]

Are you building and need funding? DMs open. Send me your github fam. 💰

[AA @MoonBenzi]

Wen

[lurks @onchainlurk]

Some may say we have entered…..dare I say….goblintown

[liquid 💧 @_proxystudio]

happy to see the head of product @ venice starting to engage with what we're cooking here at liquid

lots, LOTS coming

we've been on the outside so far, which is how I always prefer to do it. build on a protocol, make an impact and they'll support. we are not virtuals in the same way that in nov 2024 clanker was not pump. base didn't immediately support us, but when we did a billion in volume they certainly did!

step by step

[AA @MoonBenzi]

@_proxystudio @vladyy__01 So how would this fit in with Liq and Autono?

[liquid 💧 @_proxystudio]

while wstDIEM final tweaks are cooking we could ship something fun...

[AA @MoonBenzi]

@_proxystudio When do we see some launches on liquid?

[beeboop @beeboopx]

New ATHs yesterday with @AntSeedAI hitting almost 3B tokens served on the day.

On the @AskVenice side of the business, looks like things might be getting real with a wstDIEM @liquid_launcher integration 👀

[votesa ■ @votesa]

https://t.co/Sq0u8LtBlN