📅 Original date posted:2013-09-05 📝 Original message:On Sep 5, 2013, at 12:14 PM, Mike Hearn wrote: > On Thu, Sep 5, 2013 at 12:04 PM, Wendell <w at grabhive.com> wrote: >> Funny you should mention it! I just mocked this idea up last week, though I assumed a cruder system of "voting" to an address that corresponds to a feature -- literally, voting with your wallet (for your wallet, ad infinitum). I watched your talk about assurance contracts and other "hidden" features, but am not entirely sure that I understood it enough to know how it would work in this context. Sorry for the persistent hand-holding requests, but some advice would be very welcome. > > Well, it's a bit complicated and needs some software development to do well. The best way to fund a complex project would be to raise the money using an assurance contr.... oh wait ;) Well, let's assume that our "public good" is based on the 5-step model described here: en.bitcoin.it/wiki/Contracts#Example_3:_Assurance_contracts This good corresponds to something like "Facebook contact synchronization" and has a target of 50 BTC, though we also want to be able to take more if people are willing to give it. From here, it is unfortunately a little over our collective heads; we have as of yet no experience with the scripting language. I suppose I'm trying to twist your arm for an example, and maybe an anecdote. How would we do it? Does it require the donors to do anything esoteric? I saw "but they do not broadcast it" -- does this happen automatically when coins are sent to that address, for example? Confused but enthusiastic, -wendell grabhive.com | twitter.com/grabhive | gpg: 6C0C9411