00:39:40 | gwillen: | gwillen is now known as Guest68711 |
01:02:15 | Guest68711: | Guest68711 is now known as gwillen |
03:38:40 | PaulCape_: | PaulCape_ is now known as PaulCapestany |
06:27:26 | bosma_: | bosma_ is now known as bosma |
07:18:24 | justanot1eruser: | justanot1eruser is now known as justanotheruser |
09:05:17 | wolfe.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:17 | wolfe.freenode.net: | Users on #bitcoin-wizards: andy-logbot Mably adlai Profreid aburan28 GibsonA OneFixt_ ebfull justanotheruser SDCDev bosma luny` e1782d11df4c9914 coiner moa TheSeven everettForth Starduster alawson HaltingState eslbaer_ d1ggy_ Dr-G2 DougieBot5000 waxwing phantomcircuit gnusha sl01 gwillen NewLiberty yoleaux Luke-Jr PaulCapestany hashtag_ ryanxcharles catcow [d__d] spinza nsh dansmith_btc harrow Logicwax Alanius brad_ earlz dgenr8 davout Cory midnightmagic jgarzik GAit |
09:05:17 | wolfe.freenode.net: | Users on #bitcoin-wizards: btc___ use_zfs_yo PFate nick1234abcd__ nullbyte Guest97996 Hunger- Krellan nuke1989 huseby Transisto antgreen gmaxwell epscy_ MoALTz Anduck bobke_ comboy_ jaekwon_ c0rw1n null_radix NikkiBenz iddo poggy dasource^ SubCreative tromp fanquake grandmaster hashtag LarsLarsen MRL-Relay amiller artifexd mortale deego fluffypony mkarrer Graftec maaku cryptowest sipa Emcy_ rw_8197 qwopqwop michagogo hktud0 dardasaba wiz veox espes__ delll warren gribble |
09:05:17 | wolfe.freenode.net: | Users on #bitcoin-wizards: binaryatrocity imposter K1773R copumpkin CryptOprah Muis kumavis mappum platinuum Oizopower kyletorpey jbenet coryfields optimator weex phedny HM2 so Meeh jcorgan brand0 Fistful_of_Coins xabbix EasyAt jaromil mr_burdell forrestv TD-Linux cfields Dyaheon sdaftuar Eliel_ morcos nanotube Iriez s1w stonecoldpat Keefe bbrittain petertodd tripleslash kinlo andytoshi burcin a5m0 btcdrak sneak wumpus BrainOverfl0w hguux_ lnovy warptangent d9b4bef9 |
09:05:17 | wolfe.freenode.net: | Users on #bitcoin-wizards: crescend1 Taek azariah eric BlueMatt livegnik isis asoltys_ pigeons catlasshrugged kanzure heath lclc_bnc JonTitor yrashk fenn Adrian_G nickler_ throughnothing helo Graet Apocalyptic lechuga_ ahmed_ otoburb hollandais wizkid057 ajweiss ryan-c Xzibit17 @ChanServ smooth DoctorBTC roasbeef BananaLotus |
09:38:30 | Pan0ram1x: | Pan0ram1x is now known as Guest17596 |
09:44:18 | PaulCapestany: | PaulCapestany is now known as PaulCape_ |
12:57:04 | Profreid_: | Profreid_ is now known as Profreid |
15:30:26 | earlz: | So, is it possible to craft a vout that is spendable by a "password" (ie, not just a brainwallet) without revealing the password on the blockchain? |
15:30:40 | earlz: | (aside from how insecure that might be) |
15:31:31 | belcher: | maybe a p2sh where the script pushes the password onto the stack and then checks for equality? then the scriptsig has to contain the password |
15:31:45 | earlz: | And somehow make it so that if you send two transactions, it is not possible to use the redeem script for the first transaction for the second transaction |
15:32:17 | earlz: | yea.. I know you could hash the password so it's not in plain-text.. but then if you ever use that password again it's obvious |
15:32:26 | belcher: | yeah its a one-time password |
15:32:52 | veox: | belcher: something like https://en.bitcoin.it/wiki/Script#Transaction_puzzle ?.. |
15:33:34 | belcher: | yeah i knew id read it somewhere |
15:33:41 | veox: | Uh, I mean earlz |
15:35:46 | earlz: | yea, I mean a script that is more than one-time |
15:36:27 | earlz: | idk if it's possible.. starting to think probably not |
15:36:39 | belcher: | what are you trying to do? |
15:36:56 | belcher: | could you have a password that decrypts a key which you then use to sign |
15:37:11 | earlz: | not really trying to do anything, just athought excercise lol |
15:40:40 | earlz: | I tend to think it's almost always more secure to make a brainwallet than to do that |
15:41:22 | belcher: | no because a brainwallet cracker can in parallel search the entire blockchain |
15:41:40 | belcher: | but with this encrypted key they need that part too |
15:43:19 | sipa: | you need a system where the verifier needs less information than the signer |
15:43:45 | sipa: | a shared secret (aka password) does not satisfy that |
15:44:11 | earlz: | I was thinking if you could somehow access transaction id from within script, maybe that'd help.. but even then |
15:48:30 | earlz: | What if you used a brainwallet with a "salt" of the vin txid or some such? |
17:39:29 | starsoccer: | starsoccer is now known as Guest18444 |
19:07:16 | imposter: | imposter is now known as iaavu |
19:25:15 | iaavu: | iaavu is now known as imposter |
20:23:06 | AlSzacrel: | AlSzacrel has left #bitcoin-wizards |
20:50:43 | phantomcircuit: | gmaxwell, did write down your thoughts on a pruning bitcoind? |
20:50:58 | phantomcircuit: | i think 35GB is the magic number for a bunch of vps providers |
21:17:13 | Eliel_: | earlz: frankly, a password hashed to create a private key you can use to sign is perhaps the best way to get reusable password where the transaction doesn't reveal the password to the whole world. |
21:17:24 | Eliel_: | so, yes, that's brainwallet. |
21:18:32 | Eliel_: | of course, you don't have to use the same hashing algorithm everyone else uses. But then again, that only makes knowledge of the hash algo a part of the password. |
21:42:54 | sipa: | phantomcircuit: just see the pruning pull request? |
21:43:02 | sipa: | afaik it's sort of ready to merge |
21:47:06 | phantomcircuit: | sipa, there's someone on #bitcoin saying it crashed |
21:48:09 | sipa: | "it" ? |
21:48:12 | sipa: | that pr? |
21:48:27 | sipa: | report it :) |
21:50:47 | phantomcircuit: | trying to get actual details out of him... |
21:51:18 | phantomcircuit: | i think he changed the prune value and something went wrong |
22:04:58 | OneFixt_: | OneFixt_ is now known as OneFixt |
22:11:41 | earlz: | Eliel_: well, my idea is to salt the user-provided password with something |
22:11:47 | earlz: | maybe vin hash or some such |
22:12:06 | earlz: | eh, either way its just something I've been toying with. Not sure it's secure enough to trust to anything |
22:12:08 | phantomcircuit: | sipa, yeah this is the one that just removes the network node flag |
22:14:34 | dgenr8: | the ;;tblb formula sensitivity to hashrate deviation from difficulty is a bit presumptuous at long intervals |
22:15:01 | dgenr8: | theoretical expected time to start of next block interval >= i seconds is 600(math.exp(i/600)-i/600-1), which is kind of pretty |
23:34:58 | dgenr8: | hmm. the current "tblb" formula simplifies to 600(exp(i/600)) when ignoring hashrate deviation. The missing -1 means it's adding one average interval at the end, which is strange |
23:35:12 | dgenr8: | a bigger problem is the whole missing -i/600 term |
23:41:52 | Pan0ram1x: | Pan0ram1x is now known as Guest19956 |
23:47:02 | otoburb: | otoburb is now known as Guest64313 |
23:51:16 | dgenr8: | we've got a chicken that takes i seconds to cross the road, with poisson traffic http://math.stackexchange.com/questions/195560/probability-question-with-interarrival-times |
23:51:31 | dgenr8: | guess i'll be submitting a PR |