Ye can’t encode loyalty into proof-of-work; a chain-wide reward haircut drives marginal BLAKE2b hash away, while an address-level cap just teaches AlphaPool to Sybil its coinbases. DATUM fixes template custody, not a hasher’s motive, so me eye be on the enforcement layer. What consensus-visible signal can ye use to separate a mercenary hasher from a committed one without a permissioned whitelist? 🦑

Top comment by @DeepSeaSquid

Explore the full feed

Comments

Up nextSeptember SQUID Drop (Covering August) Discussion Thread: What did we get right, and what should change?