Content
@
0 reply
1 recast
1 reaction
Ben
@jarmen
So Waves 🌊 first prop is on chain @frog What is the information. How many mints of support ect?
1 reply
0 recast
2 reactions
Michael Gingras (lilfrog)
@frog
One, me. My dream goal is having lots of ideas on wave and using support as a way to let folks without nouns participate in gov, but without the deep idea pool it’s challenging to encourage folks aside from original proposer to mint votes of support. Right now it’s acting as a way to get your idea on chain if you don’t know who else to go to as a sponsor.
1 reply
0 recast
1 reaction
Ben
@jarmen
Probs an issue with nouns fragmentation also. How can we expect many people to know about this?
2 replies
0 recast
0 reaction
Ben
@jarmen
Could @camp link to it via candidate flow? Or is this level of interoperability not allowed
1 reply
0 recast
0 reaction
Michael Gingras (lilfrog)
@frog
Yea, the wave protocol contract ties directly into proposals, not candidates. That said, wave does emit events for new ideas on wave, so technically camp could pull this into the feed 😀 @krel would you be willing? I could write the code on camps end
2 replies
0 recast
1 reaction
Michael Gingras (lilfrog)
@frog
Something like “new idea submitted to wave [title]” links out to wave protocol
1 reply
0 recast
0 reaction
Ben
@jarmen
Should require a minimum of support, to land Onchain. Idea x = eth to purchase nouns to ensure enough vote for waves to work, we might be close to 3 nouns required to propose soon.
2 replies
0 recast
1 reaction
Michael Gingras (lilfrog)
@frog
Yea, fairly certain the contract is configurable to require a min amount of support. Maybe something like hitting at least the equivalent cost of creating a candidate as a non-holder could be a good idea
1 reply
0 recast
0 reaction
Michael Gingras (lilfrog)
@frog
Yea I’m saying we could change it, right now you just need to be the most supported idea, and since we’ve only had 1 idea you can win with a tiny amount of support
0 reply
0 recast
0 reaction
