| 00:29:48 | rusty: | Woah, I found the perfect image for sidechains: http://www.vitacost.com/Images/Products/1000/Momma/Momma-Toddler-Soft-Fork-Orange-044677710176.jpg |
| 00:33:20 | op_mul: | rusty: that has got to be the least effective fork ever. |
| 00:34:08 | rusty: | op_mul: but who could oppose such a soft fork? It's BPA free and it clearly says it's going to be 6 months + before deployment. |
| 00:34:46 | rusty: | op_mul: plus, it's "extendable"! It's the soft fork to end all soft forks :) |
| 00:35:01 | adam3us: | LOL |
| 00:35:02 | op_mul: | I'd call it a spoof. it's more spoon than fork. |
| 00:38:29 | rusty: | op_mul: True, but there are enough spoof bitcoin projects in the world already... |
| 01:23:09 | Guest87632: | Guest87632 is now known as maaku |
| 04:30:10 | rusty: | gmaxwell: I'm having a brain fade. What was the term you used for returning bitcoins from a sidechain to the main chain? |
| 05:18:03 | Pan0ram1x: | Pan0ram1x is now known as Guest19027 |
| 07:02:00 | op_mul: | I have a horrible feeling that stealth addresses are becoming a "standard" without any of the interesting stuff added to them. we'll probably end up with centralised, no payment ID mode ones for good :( |
| 07:05:21 | gmaxwell: | seems unlikely. Due to complete tonedefness they've been given an intentionally 'edgy' name that leave most wallets actively unwilling to implement them. |
| 07:06:00 | gmaxwell: | it's just as well, since the tech needs to be stronger to not have them be a net-negative for user privacy all things considered. |
| 07:11:51 | op_mul: | that comment came from a reddit post talking about a new service "supporting" them. |
| 07:17:26 | op_mul: | turns out it was just another scary "manually manage your private keys in a browser with javascript" thing. |
| 08:24:48 | Luke-Jr: | op_mul: I like the "email transaction" version better anyway. no id needed, no OP_RETURN needed. :p |
| 08:26:11 | Luke-Jr: | (that is, wrap a transaction+data in a payment protocol structure and send it via email; recipient has duty to announce to the network after telling his wallet about the key) |
| 08:28:32 | op_mul: | Luke-Jr: somehow I don't think people will latch onto that. give it a swankier name and pitch it again. |
| 08:29:37 | Luke-Jr: | op_mul: "send to person" :P |
| 08:29:53 | Luke-Jr: | "address-free bitcoin" |
| 08:29:59 | op_mul: | "AnarchySend" |
| 08:30:01 | op_mul: | ship it. |
| 08:31:49 | Luke-Jr: | "real bitcoin™" |
| 08:43:58 | execut3: | execut3 is now known as shesek |
| 08:49:11 | op_mul: | Luke-Jr: I don't like that actually. at least with HTTP it's sort of easy to tell if the page you are visiting is "secure". with email it's anybodies guess. |
| 08:49:36 | Luke-Jr: | op_mul: doesn't matter much unless you use the wrong base key with the email |
| 08:49:50 | Luke-Jr: | it's still just a signed transaction that needs a private key to redeem ;) |
| 08:51:01 | op_mul: | oh yep. I follow. I thought you meant moving BIP70 into an email form, but you meant just sending the ephemeral portion of the "stealth" address directly to the person rather than have them scan for it. |
| 08:53:07 | op_mul: | not super slick though. |
| 08:54:02 | op_mul: | if you lose the ephemeral key you either have to use a non-SPV client and scan every transaction, or outsource it. I know what most people will do. |
| 08:55:04 | Luke-Jr: | op_mul: or ask the sender to resend |
| 08:55:12 | Luke-Jr: | not sure why you'd lose it though |
| 08:56:09 | Luke-Jr: | but then, my email is stored in git <.< |
| 08:56:12 | op_mul: | I was thinking if you lost/destroyed/whatever your wallet and recovered it with a BIP32 seed. |
| 08:57:42 | Luke-Jr: | oh, hm |
| 09:05:15 | verne.freenode.net: | topic is: This channel is not about short-term Bitcoin development | http://bitcoin.ninja/ | This channel is logged. | For logs and more information, visit http://bitcoin.ninja |
| 09:05:15 | verne.freenode.net: | Users on #bitcoin-wizards: andy-logbot Aquent CoinMuncher adam3us ebfull HarusameNyanko Dizzle cbeams paveljanik Starduster_ catlasshrugged NewLiberty coiner Guest19027 d1ggy_ aburan28 ryanxcharles Elio20 jcorgan op_mul cluckj OneFixt wizkid057 e1782d11df4c9914 PaulCapestany maaku forrestv Emcy jgarzik bitbumper adlai Luke-Jr rusty grandmaster rfreeman_w epscy todays_tomorrow shesek tromp_ PRab [\\\] null_radix tacotime SubCreative otoburb c0rw1n hashtagg LarsLarsen pi07r |
| 09:05:15 | verne.freenode.net: | Users on #bitcoin-wizards: nuke1989 koshii dgenr8 optimator_ Greed Dyaheon Tjopper1 lclc_bnc sl01 nsh digitalmagus8 spinza harrow gmaxwell gavinandresen NikolaiToryzin waxwing go1111111 atgreen Cory copumpkin isis samson_ iddo s1w gnusha jaekwon sadgit brand0 eric roasbeef mr_burdell hktud0 Krellan fanquake luny berndj @ChanServ jaromil jbenet poggy_ petertodd Apocalyptic Meeh tromp DougieBot5000 helo v3Rve midnightmagic espes__ Iriez fluffypony hollandais thrasher` |
| 09:05:16 | verne.freenode.net: | Users on #bitcoin-wizards: butters nickler Logicwax lnovy ahmed_ warren fenn jchp mkarrer phantomcircuit Graet morcos michagogo mappum Muis kanzure gribble MRL-Relay Graftec bobke huseby [d__d] BananaLotus amiller artifexd kumavis coryfields BigBitz coutts BlueMatt cfields Anduck Eliel nanotube hguux_ AdrianG gwillen CryptOprah btc__ wumpus stonecoldpat dansmith_btc toddf heath bbrittain DoctorBTC EasyAt starsoccer BrainOverfl0w phedny Keefe so crescendo throughnothing |
| 09:05:16 | verne.freenode.net: | Users on #bitcoin-wizards: Taek burcin livegnik sipa harrigan sneak yoleaux azariah kinlo Guest38445 HM2 Fistful_of_Coins warptangent lechuga_ andytoshi pigeons Nightwolf btcdrak comboy a5m0 K1773R asoltys_ JonTitor Alanius mmozeiko smooth ryan-c TD-Linux catcow danneu |
| 09:20:32 | op_mul: | Luke-Jr: I suppose that's a niche issue. |
| 09:23:01 | Luke-Jr: | op_mul: not sure. half the benefit of HD wallets is a single backup |
| 09:23:45 | Luke-Jr: | I suppose the transaction could always have the OP_RETURN in it still, and only use the email so you get metadata with it |
| 12:00:47 | rusty: | rusty has left #bitcoin-wizards |
| 19:20:21 | tacotime: | w/r/t stealth addresses, i'll see if i can implement it out of band this month in btcd/btcwallet |
| 19:21:18 | tacotime: | i think that's a good way to do it for now; just export the data that's normally OP_RETURN'd with in JSON for the user to ship off to the receiver from some OOB mechanism |
| 19:22:49 | tacotime: | then users can make QR codes to put on their business cards or whatever, with [OOB_contact_info]&[stealth_address] embedded into it |
| 19:23:14 | tacotime: | then it's just a matter of forwarding the data and txhash |
| 19:23:42 | tacotime: | --> actually usable non-reusable addresses :P |
| 19:28:11 | tacotime: | i maybe derive the scan privkey from the spend privkey by hashing too, since we do that for monero and it seems relatively safe so far. |
| 20:39:49 | Elio20: | Elio20 is now known as Elio19 |
| 22:34:55 | s1w-: | s1w- is now known as s1w |
| 22:35:11 | mr_burdell_: | mr_burdell_ is now known as mr_burdell |
| 22:35:12 | s1w: | s1w is now known as Guest61341 |
| 22:35:13 | mr_burdell: | mr_burdell is now known as Guest49039 |
| 22:50:12 | roasbeef_: | roasbeef_ is now known as roasbeef |