{"type":"rich","version":"1.0","author_name":"npub18xqykhf26udeq2nyk98ee0a5q4w3s2f75m405a6zswpdy573lxeqmhg6zk","author_url":"https://nostr.ae/npub18xqykhf26udeq2nyk98ee0a5q4w3s2f75m405a6zswpdy573lxeqmhg6zk","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2014-03-04\n📝 Original message:Nothing is safe.\n\nTake risks.  Engage one trouble at a time.\n\nPerform unexpected actions.\n\nObserve the results.\n\nRinse and repeat.\n\nIgnore the lions.  They too shall pass.\n\n\"Do not sleep under a roof. Carry no money or food. Go alone to places\nfrightening to the common brand of men. Become a criminal of purpose. Be\nput in jail, and extricate yourself by your own wisdom.\"\n\n-- Miyamoto Musashi (Niten Ichi-ryū)\n\n\n\n\u003e Some people may have seen my service Reality Keys, which can perform a\n\u003e role\n\u003e a bit like an External State Oracle as described previously by Mike Hearn\n\u003e and others. (I like to think of it as a Certificate Authority for\n\u003e propositions, doing for facts what Verisign do for identities.) You\n\u003e register a possible outcome with us, we publish a public key for \"yes\" and\n\u003e another for \"no\", and once the outcome happens or fails to happen, we\n\u003e publish the appropriate private key.\n\u003e\n\u003e A few people have been asking for advice on the best way to use our keys\n\u003e to\n\u003e make m-of-n contracts, where each party locks up their stake in a\n\u003e transaction, then the winner gets their private key from Reality Keys and\n\u003e uses it to release the funds. Peter Todd suggested what seems like a very\n\u003e nice way to do this without needing non-standard transactions or refund\n\u003e transactions. I've had a go at implementing it and it seems to work, but I\n\u003e don't know enough about this to distinguish the ECC bit of it from magic,\n\u003e so I'm wondering if people who do understand it could comment on whether\n\u003e it's a safe thing to be doing.\n\u003e\n\u003e What I'm trying to do here is to combine the public key of each party with\n\u003e the public key of the outcome they're representing, eg I make a public key\n\u003e with:\n\u003e  \u003calice-pub\u003e + \u003creality-key-yes-pub\u003e\n\u003e ...and another with:\n\u003e  \u003cbob-pub\u003e + \u003creality-key-no-pub\u003e\n\u003e\n\u003e That goes into a 1/2 P2SH address (in the simplest possible case), which\n\u003e is\n\u003e spendable by one of Alice or Bob after the outcome occurs with either:\n\u003e  \u003calice-priv\u003e + \u003creality-key-yes-priv\u003e\n\u003e ...or\n\u003e  \u003cbob-priv\u003e + \u003creality-key-no-priv\u003e\n\u003e\n\u003e I'm making the transaction with add_pubkeys, then spending it with\n\u003e add_privkeys, both from:\n\u003e https://github.com/vbuterin/pybitcointools/blob/master/pybitcointools/main.py#L173\n\u003e\n\u003e What's worrying my superstitious mind is that knowing \u003creality-key-no-pub\u003e\n\u003e before he has to produce \u003cbob-pub\u003e, I'm wondering if there's something Bob\n\u003e could do with \u003cbob-pub\u003e to intentionally weaken the resulting (\u003cbob-pub\u003e +\n\u003e \u003creality-key-no-pub\u003e) so that he could sign a transaction with it without\n\u003e needing to know \u003creality-key-no-priv\u003e.\n\u003e\n\u003e My example script (and specifically the bit that's scaring me) is here:\n\u003e https://github.com/edmundedgar/realitykeys-examples/blob/master/realitykeysdemo.py#L247\n\u003e\n\u003e PS. I hope I'm not too far off-topic. Peter Todd suggested it might be\n\u003e worth talking about here as it potentially has implications for other\n\u003e protocols. If people prefer to respond at bitcointalk instead, we've been\n\u003e discussing it here:\n\u003e https://bitcointalk.org/index.php?topic=260898.60\n\u003e\n\u003e --\n\u003e Edmund Edgar\n\u003e Founder, Social Minds Inc (KK)\n\u003e Twitter: @edmundedgar\n\u003e Linked In: edmundedgar\n\u003e Skype: edmundedgar\n\u003e http://www.socialminds.jp\n\u003e\n\u003e Reality Keys\n\u003e @realitykeys\n\u003e ed at realitykeys.com\n\u003e https://www.realitykeys.com\n\u003e ------------------------------------------------------------------------------\n\u003e Subversion Kills Productivity. Get off Subversion \u0026 Make the Move to\n\u003e Perforce.\n\u003e With Perforce, you get hassle-free workflows. Merge that actually works.\n\u003e Faster operations. Version large binaries.  Built-in WAN optimization and\n\u003e the\n\u003e freedom to use Git, Perforce or both. Make the move to Perforce.\n\u003e http://pubads.g.doubleclick.net/gampad/clk?id=122218951\u0026iu=/4140/ostg.clktrk_______________________________________________\n\u003e Bitcoin-development mailing list\n\u003e Bitcoin-development at lists.sourceforge.net\n\u003e https://lists.sourceforge.net/lists/listinfo/bitcoin-development\n\u003e"}