Rough ideas after reading: https://mirror.xyz/verbsteam.eth/gnTdSqqiZC7OmqL8Dix-hEek5Sim1abC1BsZNm9_h-s

I think the key design challenge here is not requiring people to place their NOUN in a new contract.

Off the cuff ideas

- Could update governor to have an exclude list
- People who delegate to a pool, get a soulbound NFT which prevents double vote problem
- Burn soulbound NFT to get normal voting privileges again
- Governor lists known pool contracts similar to well-known Clients

(🏗️, https://lighthouse.cx)
 (🎥,  /cinema-stills) , (⬛, /textures), (🌊, /emergence)


Could you explain more on the sb NFT? My first reaction is that I don’t see why the delegator gets the nft, I’d think the pool would need it so it’s delegation of the voting power is recognized

Crypto, nouns, malleable software, interfaces, running. // working on @agora // https://0xmcg.com // /the-pond

Oh okay so the pool is a new contract? Is it just a smart account or a specific contract? 

I’m still misunderstanding

The pool contract would have a count of delegated tokens.

Which should be sufficient?