| 02:49:12 | dsnrk: | midnightmagic: that was an oversight that struck me when I read it. it's sort of the main problem with HashCash in the first place, the sort of nefarious people they are trying to keep out are exactly the ones who would have the spare computing power sitting around to do it. |
| 04:02:06 | wallet421: | wallet421 is now known as wallet42 |
| 05:40:44 | ericp7: | ericp7 is now known as ericp4 |
| 05:51:50 | jcorgan: | ;;seen wyager |
| 05:51:50 | gribble: | wyager was last seen in #bitcoin-wizards 1 week, 3 days, 3 hours, 27 minutes, and 39 seconds ago: I’ll eat my shoes if anyone invents a PoW algorithm that does “useful” work and can’t be gamed |
| 10:51:50 | pigeons: | pigeons is now known as Guest18470 |
| 11:13:54 | cym: | cym is now known as pen |
| 11:13:59 | pen: | pen is now known as pen_ |
| 11:46:02 | fanquake: | fanquake has left #bitcoin-wizards |
| 13:05:13 | skinnkavaj: | Proposal to end pooled mining |
| 13:05:16 | skinnkavaj: | http://www.mail-archive.com/bitcoin-development@lists.sourceforge.net/msg04388.html |
| 14:31:59 | amiller: | jgarzik, is dakami paying you soon |
| 14:40:11 | nsh: | -- |
| 14:40:11 | nsh: | So let's split up the transaction volume so every individual miner only |
| 14:40:11 | nsh: | needs to keep up with some portion. In a rough sense that's what |
| 14:40:11 | nsh: | alt-coins do - all the tipping microtransactions on Doge never have to |
| 14:40:11 | nsh: | hit the Bitcoin blockchain for instance, reducing pressure on the |
| 14:40:11 | nsh: | latter. But moving value between chains is inconvenient; right now |
| 14:40:13 | nsh: | moving value requires trusted third parties. Two-way atomic chain |
| 14:40:16 | nsh: | transfers does help here, but as recent discussions on the topic showed |
| 14:40:17 | nsh: | there's all sorts of edge cases with reorganizations that are tricky to |
| 14:40:20 | nsh: | handle; at worst they could lead to inflation. |
| 14:40:23 | nsh: | -- i'm having trouble imagining how a re-org in a two-way peg could lead to inflation... |
| 14:40:41 | nsh: | s/peg/atomic transfer/ |
| 15:06:51 | jgarzik: | amiller, |
| 15:06:54 | jgarzik: | "My adventure of acquiring 10BTC continues! I've got a client who's going to pay me in Bitcoin. This should be resolved in fairly short order (weeks, not months). |
| 15:06:54 | jgarzik: | Thanks for this small flexibility!" |
| 15:08:09 | nsh: | * nsh wonders what people would pay dankami for |
| 15:08:33 | amiller: | yeesh |
| 15:08:34 | nsh: | maybe he also does landscaping |
| 15:08:41 | amiller: | hope he's not actually going broke to pay you but like |
| 15:08:43 | amiller: | lol. |
| 15:30:46 | vfor: | hey guys |
| 15:30:55 | todaystomorrow: | hello :) |
| 15:30:57 | vfor: | how are privkeys encoded in bitcoind? |
| 15:31:28 | vfor: | i want to import one from another wallet but it says invalid private key |
| 15:44:32 | vfor: | 5Jn9nDNTzNQLPvuEj7SmtSQDYHVRwoYshLhzXk4dcfcA1XUM5Zr |
| 15:44:32 | vfor: | this is a key in the WIF, right? |
| 15:45:03 | michagogo: | vfor: looks like it |
| 15:45:42 | michagogo: | (don't send anything to 17mFwun2zo61KMVZcSUnX1Y4aEKJnSy9mz now... you'll lose it) |
| 15:51:53 | vfor: | lol |
| 15:52:08 | vfor: | there are some testcoins on it if somebody wants to steal them ;) |
| 15:53:39 | vfor: | so michagogo you imported the key into a bitcoin mainnet client and it worked? |
| 15:53:47 | vfor: | interesting |
| 15:54:19 | michagogo: | vfor: erm, that's a mainnet WIF |
| 15:54:30 | michagogo: | Testnet keys have a different WIF |
| 15:55:30 | dsnrk: | testnet private keys begin with 9 or c |
| 15:55:59 | vfor: | ok, i know what is going wrong now. thanks. |
| 15:56:37 | vfor: | can i import raw private keys into bitcoind? |
| 15:56:51 | vfor: | it do not like this WIF |
| 15:56:53 | dsnrk: | yes, but you shouldn't. this really is a question for #bitcoin. |
| 15:57:22 | vfor: | okay |
| 15:57:41 | vfor: | so what do you discuss here? dsnrk |
| 15:58:07 | dsnrk: | -wizards is for future things. |
| 15:58:31 | dsnrk: | it's not about bitcoin today. |
| 15:58:49 | vfor: | but #bitcoin is for trash things then |
| 15:59:46 | dsnrk: | it's where you should be asking this. -wizards is meant to be high signal, low noise. a lot of us read the entire log with this expectation. |
| 15:59:46 | vfor: | whatever… i got help. thanks! |
| 16:00:43 | vfor: | i thought wizzard means developers and not future |
| 16:01:41 | vfor: | 'Any sufficiently advanced technology is indistinguishable from magic.' |
| 16:04:40 | hearn: | that would be #bitcoin-dev |
| 16:17:17 | maaku: | "This channel is not about short-term Bitcoin development" |
| 18:24:02 | cajg_: | cajg_ is now known as cajg |
| 18:27:19 | jtimon: | I hadn't seen this video on zerocash https://www.youtube.com/watch?v=l7LSSE0bRRo |
| 18:51:32 | reipr: | I'm struggling with ideas for creating proof of assets. My user's deposit directly into cold storage. I cannot fathom publishing all of those cold storage addresses. Let's say that I generate 1 proof of solvency Merkle Tree per week, and when the coins have aged enough from the deposit addressess I move them to a smaller subset of addresses that I publish. There can seem to be alot of unaccounted for coins in the Proof of Assets because the co |
| 18:51:39 | reipr: | Sorry, long post. |
| 18:52:24 | reipr: | My idea is to provide a second merkle tree that the user's can do to account for the coins that are help in their deposit address, and a second proof of assets (they can check the balance of their own deposit address) |
| 18:52:37 | reipr: | that are held* |
| 18:52:46 | reipr: | am I way off base here? |
| 21:06:58 | todays_tomorrow: | todays_tomorrow has left #bitcoin-wizards |
| 22:00:56 | maaku: | reipr: you don't need to publish the entire ledger, just the path through it for each user |
| 22:01:09 | maaku: | and a zkp that the ledger sums to the reported balance |
| 23:40:41 | verne.freenode.net: | topic is: This channel is not about short-term Bitcoin development | "Bitcoin research, hardfork wishlist, ideas for the future - see also: https://en.bitcoin.it/wiki/Hardfork_Wishlist https://en.bitcoin.it/wiki/User:Gmaxwell/alt_ideas. This channel is logged at http://download.wpsoftware.net/bitcoin/wizards/. For questions about the logs talk to andytoshi." |
| 23:40:41 | verne.freenode.net: | Users on #bitcoin-wizards: andytoshi-logbot andytoshi dexX7 davispuh AaronvanW skinnkavaj Luke-Jr todaystomorrow paavo mappum davidlatapie Somethingx samson_ rdponticelli jctb jonpry HaltingState cajg jaekwon Vitalik_ vfor gloriusAgain d34th pigeons_ [\\\] forrestv pigeons pangpang MoALTz Burrito tjopper llllllllll CodeShark Emcy tromp mortale copumpkin wallet42 TheSeven arubi tacotime ebfull BCB mapppum c0rw1n_ shesek nshlike kazcw justanotheruser postpre catcow |
| 23:40:42 | verne.freenode.net: | Users on #bitcoin-wizards: Cory midnightmagic nsh justusranvier eristisk Kretchfoop K1773R melvster drawingthesun Krellan_ maaku [Derek] Logicwax OneFixt jchp sl01 Kawhi_desu Dyaheon abc56889 dgenr8 emsid at0mat lnovy adam3us pajarillo mr_burdell alferz spinza iddo weex reipr dansmith_btc mkarrer edulix Pan0ram1x lenticulis otoburb pi07r HM LarsLarsen Apocalyptic heakins roasbeef LaptopZZ_ @ChanServ Muis optimator quackgyver Mikalv mmozeiko zibbo Anduck crescendo |
| 23:40:42 | verne.freenode.net: | Users on #bitcoin-wizards: Krellan ryan-c dsnrk comboy Sangheili jcorgan keus DoctorBTC jaromil_ burcin nikitab helo warren phantomcircuit coyo zenojis Alanius sipa amiller kinlo flammit Graet a5m0 wumpus asoltys so BlueMatt poggy nkuttler nickler harrow realazthat stqism artifexd Adohgg stephenreed jgarzik waxwing EasyAt kiddouk ewust gribble bobke Armstrong danneu quickcoin espes [_Tristan_] kanzure nanotube michagogo moneycat rs0 lianj Eliel mhanne UukGoblin |
| 23:40:42 | verne.freenode.net: | Users on #bitcoin-wizards: Fistful_of_Coins petertodd tromp__ Hunger- lechuga_ |