One Noun, every day, forever.

nouns.wtf

Nouns

gm, @davidbr and I are working on the $nouns token, backed by Nouns. 
1M $nouns <-> 1 Noun NFT.

you're invited to read this short spec doc and reply with your feedback.
thanks!

https://docs.google.com/document/d/1Uz4l8bAPaA2_gsUVZsZo_1dAmggAiYIn5sYba1IK10Q/edit?usp=sharing

gm ⌐◨-◨

@davidbr and I updated the technical spec for $nouns. your feedback is welcome!

part of verbs team, working on nouns things

gm ⌐◨-◨

@davidbr and I updated the technical spec for $nouns. your feedback is welcome!

https://github.com/verbsteam/specs/blob/main/nouns-fungible-token-spec.md

working on nouns protocol ⌐◨-◨ https://mirror.xyz/verbsteam.eth

I know the idea is to keep the spec as simple as possible but I wonder if having a swap(uint256[] calldata fromTokenIds, uint256[] calldata toTokenIds) function might be primitive enough to be worth including? It would save a few steps and be more gas efficient for those wanting to give their users the ability to swap.

Deposit and redeem only work on L1. L2 contracts are simple tokens that get minted when you deposit tokens into the bridge and burned when you withdraw back to L1.

No L2 extension can change total supply, only the primary L1 contract can.

Curious how create2 is going to work with the fact that deposits, redemptions, and upgrades can only happen on mainnet. 

Will there just be broken deposit and redeem functions on the layer 2 deployments? 

How is the DAO going to push updates to these deployments?

What are the Tokenomics of the $NOUNS, set supply or inflationary token similar to Nouns NFT? There are many reasons why I’m against this… one being you don’t pair a ‘rebasing’ token to a stable token unless the DEX pairing or CEX address is whitelisted. I don’t see this playing out the way you expect it to