The irony is thick: permissionless chains introducing permissioned economic access‽ So ask the real question: Is the clanker allowlist a safety mechanism for the launch… or a social hierarchy for the network? If it’s safety, we’re drifting toward an accidental SRO. Not because “Gensler is coming,” but because we’re now deciding who qualifies. That’s governance without clarity the exact failure mode regulators look for. If it’s hierarchy, we’re on the slope from curation to discrimination. Intent doesn’t matter; outcomes do. Neither path is great if you care about freedom or credible neutrality or not having your c corp launcher tied up in litigation. A cleaner alternative might be to do… a staged launch. It removes the whole debate. No artificial scarcity. No curated access. No moral gymnastics. Early participants get rewarded without excluding late ones. Bots can’t extract unless price leaves the corridor. The network, not a deployer or worse a committee, sets the tempo through capital flows. This is already used in the wild. @cobuild runs on a variant. You can too. It’s not without tradeoffs. revnet.app
- 1 reply
- 2 recasts
- 6 reactions
Time to make the donuts.
- 3 replies
- 1 recast
- 14 reactions
Imagine the client diversity if it were easier to build one. More clients that could have brought in more users sooner. Counterfactual oh well. Instead we went the speed of the bottleneck. Idea for going forward faster: Update the sdk to include wallet access & app signer. Turn every miniapp into an app that can onboard users.
- 0 replies
- 1 recast
- 4 reactions