03:04:59zooko:When's the next time and place that Bitcoin core devs are going to congregate at? I want to go there then.
03:11:34kanzure:i believe they rotate irc channels every 5 minutes. it's hard to keep up.
03:16:39kanzure:but you can figure out which channels by referring to your super secret decoder ring..
03:34:40gmaxwell:zooko: I think we'll all be at FC2015. Other than that, pieter and I are in mtv at the moment.
03:34:46BlueMatt:zooko: I think that has only ever happened at foundation-sponsored bitcoin conferences
03:34:51BlueMatt:that, and fc15
03:35:24zooko:gmaxwell: What are you doing in mtv?
03:35:33gmaxwell:I live here. Sipa is visiting.
03:35:51zooko:Oh yeah. :-)
03:35:52Luke-Jr:BlueMatt: he didn't say *all* <.<
03:35:55gmaxwell:(so have lots of bitcoin people recently for various reasons)
03:36:03BlueMatt:* BlueMatt lives in the city, fwiw
03:36:51gmaxwell:Probably 95% of the lines of traffic from this channel have been in the bay area at one point or another in the last month or so.
03:39:44gmaxwell:lets see recent bitcoin technical people from this channel/#bitcoin-dev I've seen in person, myself, pieter, jtimon, petertodd, maaku, adam3us, andytoshi, phantomcircuit, Luke-Jr, gavin, BlueMatt, gwillen, devrandom, plus some additional people I know less well.
03:40:30BlueMatt:thanks for tagging /everyone/
03:40:52Luke-Jr:gmaxwell: does a day go by that you don't see yourself?
03:41:16BlueMatt:Luke-Jr: mirror could be dirty...
03:41:28Luke-Jr:BlueMatt: doesn't have to be his head
03:41:29gmaxwell:may not make it as far as a mirror.
03:41:46Luke-Jr:hard to avoid seeing ones hands
03:42:47sipa:i don't think all people with bitcoin commit rights have ever been in one place together since 2011
03:43:16BlueMatt:ams conference, no?
03:43:24sipa:gmaxwell was not there
03:43:42gmaxwell:everyone with commit access has never been in one room.
03:43:43sipa:and wumpus wasn't in san jose 2013
03:43:57gmaxwell:AFAIK, unless it happened once before I did.
03:43:57BlueMatt:gmaxwell: when it was only satoshi.....
03:44:09gmaxwell:well sure, but not long after.
03:44:16sipa:or when it was just jeff gavin and tcatm
04:01:37zooko:gmaxwell: so the answer seems to be that "hang out at gmaxwell's house".
04:05:35gmaxwell:or in the area, at least. I've been conciously playing a bit of a social butterfly and bringing people togeather when they were in proximity.
04:07:57zooko:Nice. Good for you.
04:08:01zooko:How long is sipa staying?
04:08:28sipa:let's ask him
04:08:58sipa:october 24th
04:09:32zooko:Hi there. :-)
12:47:22tepper.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
12:47:22tepper.freenode.net:Users on #bitcoin-wizards: andy-logbot Aquent_ zooko Starduster pen adam3us phantomcircuit lysobit Luke-Jr Krellan p15 SDCDev rdponticelli hearn waxwing torsthaldo gloriusAgain CoinMuncher emsid mkarrer c0rw1n rfreeman_w cbeams OX3 AaronvanW HaltingState justanotheruser AlSzacrel vmatekol_ ubuntu_ austinhill TheSeven tacotime TrollsRoyce jchp Dr-G2 mortale espes__ digitalmagus Adlai devrandom Graftec wiretapped jgarzik Nightwolf copumpkin spinza dansmith_btc Happzz
12:47:22tepper.freenode.net:Users on #bitcoin-wizards: Fistful_of_coins artifexd _2539 michagogo lnovy tromp bbrittain weex gribble nanotube a5m0 irc88 EasyAt_ Transisto grishnakh__ altoz Kretchfoop Emcy jaekwon CryptOprah Muis samson_ Hunger-- wizkid057 nuke1989 BrainOverfl0w Sangheili artilectinc Guest42039 aburan28 wumpus jrayhawk_ jasx zwischenzug shesek firepacket dgenr8 arowser go1111111 zenojis LarsLarsen BigBitz Adohgg drawingthesun berndj [d__d] jcorgan yoleaux Iriez hollandais hguux
12:47:22tepper.freenode.net:Users on #bitcoin-wizards: livegnik stonecoldpat Dyaheon MRL-Relay mappum jbenet [Derek] zibbo_ kanzure petertodd optimator [\\\] warren pi07r K1773R Eliel HM gmaxwell amiller_ crescendo cfields btc_ kgk bobke iddo comboy NikolaiToryzin coryfields LaptopZZ Meeh poggy_ UukGoblin danneu catcow TD-Linux [Tristan] helo smooth otoburb gwillen ryan-c mmozeiko roasbeef pajarillo sl01 Keefe Gnosis ahmed_vegas Logicwax so epscy BlueMatt starsoccer midnightmagic Graet kinlo
12:47:22tepper.freenode.net:Users on #bitcoin-wizards: pigeons lianj Apocalyptic mr_burdell fluffypony SomeoneWeird forrestv Anduck Taek42 sipa [nsh] DoctorBTC harrow throughnothing Alanius abc56889 lechuga_ burcin phedny @ChanServ asoltys
13:10:26Aquent_:Aquent_ is now known as Aquent
13:30:43Guyver2:Guyver2 has left #bitcoin-wizards
13:40:41onefox:has someone here expierens with micropayment channels ?
13:46:53hearn:what's the question?
13:50:59hearn:onefox: poke
13:51:31onefox:ah sry in bitcoinj
13:51:36onefox:the nLockTime is set to one day but can i make it shorter, like 2 hours or so ?
13:52:18onefox:the time if a channel is not closed by the server and the client want his funds back
13:54:42hearn:yes it is configurable these days
13:54:42hearn:probably i need to update the docs
13:57:11onefox:great, and if i start this channle and the server is vanished will the client get the hole funds back or only the remaing and the other will as in the channle definited to the server ?
13:59:21Taek42:onefox using a time period of 2 hours would not be a good idea, because block times can vary a lot
13:59:46hearn:onefox: i think the docs go into this
14:00:15hearn:onefox: the client will get all the funds in the channel back if the server disappears. obviously this is supposed to be a rare event, which is why 24 hours is the default.
14:00:50hearn:onefox: the implementation imposes a minimum and i think 2 hours may be it. but it may be higher, i forgot.
14:01:23onefox:ah okey its also on the servers concern that he close the channel so he can get his part of the funds
14:01:31onefox:i guess ^^
14:02:46hearn:the server really really wants to close the channel properly. the refunds are there in case something goes wrong, that's all.
14:02:59onefox:i assume that the 2 hours can only be reduced if the block time is small like in dogecoin for example.
14:03:12onefox:or in other altcoins
14:03:21hearn:i don't know. i've never thought about that case. btw bitcoinj has a #bitcoinj irc channel if you want to discuss the details of the code there
14:03:26hearn:this channel is more meant for research
14:04:02onefox:yes i was there but i didn't got a responce in 3 hours .. so i checked some more channels out ;)
14:04:12onefox:bitcoindev pointed me here
14:04:43hearn:oh, you were?
14:04:43hearn:well normally i'm around there on weekdays CET
14:04:44hearn:usually from around noon onwards
14:05:00hearn:let's move this discussion there
14:41:01Happzz:Happzz has left #bitcoin-wizards
15:41:58kanzure:.to brisque is there a document that has a list of inaccuracies in that unmentionable book?
15:41:58yoleaux:kanzure: I'll pass your message to brisque.
16:57:30Aquent:Aquent is now known as bullwhale
17:35:49bullwhale:bullwhale is now known as Aquent
18:01:34gwillen:gwillen is now known as Guest11330
18:18:18Guest11330:Guest11330 is now known as gwillen
18:54:25skyraider7:skyraider7 has left #bitcoin-wizards
19:40:38justanotheruser:justanotheruser is now known as midoriseki
19:40:50midoriseki:midoriseki is now known as justanotheruser
20:02:09phantomcircuit:anybody have an opinion on bitgo?
20:04:22davidlatapie:davidlatapie has left #bitcoin-wizards
20:04:30hearn:it seems to have been reasonably well designed, but i only ever spent five mins playing with it. the guy who created it is an ex googler, one of the guys behind spdy
20:06:04phantomcircuit:Emcy, multisig wallet
20:06:20phantomcircuit:appear to be pushing to outsource policy enforcement essentially
20:09:26phantomcircuit:Emcy, 2/3 multisig
20:09:30phantomcircuit:they have a key
20:09:35phantomcircuit:you have a key and a backup key
20:09:47phantomcircuit:they have policy rules for their key to sign
20:10:07Emcy:such as
20:10:07phantomcircuit:a genuinely interesting project
20:10:36phantomcircuit:Emcy, business logic stuff like daily limits
20:11:00hearn:they can also do 2-factor via sms iirc
20:11:05hearn:there are a few projects like that out there now
20:11:14hearn:it makes a ton of sense. sort of half way between just a password and a trezor
20:11:35Emcy:at least someone is doing something with multisig
20:12:13phantomcircuit:hearn, it's better than a trezor for a business since you can push (some) of the business logic there
20:12:15hearn:there are people doing things with multisig
20:12:22hearn:phantomcircuit: right for online systems, yes
20:12:28phantomcircuit:otherwise you're just hoping your controller isn't stealing
21:20:40ucerron:is it possible to build a sidechain with colored coins?
21:27:39Luke-Jr:ucerron: yes
21:27:55ucerron:are there any implementations out there already?
21:28:08Luke-Jr:assuming you mean sidechain that has coloured coins, not creating a sidechain out of coloured coin constructs
21:28:18Luke-Jr:ucerron: there are no implementations of sidechains at all yet
21:28:40ucerron:what about treechains?
21:29:01Luke-Jr:you'd have to ask petertodd on that, I think
21:29:08Luke-Jr:AFAIK he's the only one working on those
21:29:15ucerron:viacoin right?
21:29:23Luke-Jr:that would be getting off-topic
21:40:21Taek42:I could be wrong, but I'm pretty sure that tree chains aren't very close to being implemented
22:36:02Taek42:tried to design a system where not every node needs to see every transaction, yet you can still make reasonable assumptions about network security if you can assume that the majority of hashing power on the network is honest
22:45:18Luke-Jr:Taek42: it seems to be built on some false premises
22:46:57Luke-Jr:Taek42: also, excluding transactions from your blocks is not dishonest
22:47:04Taek42:hmm. which ones?
22:48:20Luke-Jr:"To preserve security, child blockchains are randomly assembled from nodes, and each node is placed in exactly one child blockchain." <-- consensus systems cannot have random
22:49:42Taek42:oh. I should discuss that more then.
22:50:01Taek42:"Random" is achieved by taking the hash of the previous root block
22:50:03Luke-Jr:Taek42: I don't see how this helps scale at all
22:50:24Luke-Jr:Taek42: the hash isn't random; miners can withhold blocks with hashes they dislike
22:50:31Taek42:It's possible to manipulate that random number, but it's expensive
22:50:32Luke-Jr:and I'm not sure this system disincentivises that
22:51:40Taek42:yeah the incentive model needs to be fleshed out a bit more thoroughly as wel. It's possible that it doesn't fully disincentivize block withholding
22:52:22Luke-Jr:Taek42: anyhow, with this, every node needs to watch every child blockchain for their transactions
22:52:34Luke-Jr:and to know if those blocks are valid, they need to check every transaction in them
22:52:42Luke-Jr:otherwise they're trusting the miners
22:52:58Taek42:They only need to check the child nodes that have transactions they are interested in
22:53:07Taek42:not all of them
23:00:38sipa:how do they know that the inputs in those child nodes themselves are valid?
23:00:48sipa:by recursing further?
23:05:47Taek42:Everyone has a complete copy of the root blockchain, which is used to define who gets to mine on child blockchains
23:06:12sipa:you're not answering my question
23:06:18Taek42:child blockchains could potentially be completely internal ecosystems, not ever trading externally
23:06:22Taek42:*getting there
23:06:50Taek42:if you did want them to trade externally, you'd probably do it through the root blockchain
23:07:04Taek42:which means you would end up with with 'black' inputs, inputs that you never verify
23:07:36Taek42:but because hosts are randomly scattered throughout the network, you can believe that the inputs are honest
23:07:52Taek42:*as long as you believe that the majority of the hashing power is honest, which you can't necessarily verify
23:08:49sipa:that sounds a lot like sidechains :)
23:10:13Taek42:yeah I guess they are a lot more similar than I originally realized
23:10:57sipa:the hardest part is how to prove to the root chain that the transfers within one of the child chains were done correctly
23:11:15sipa:because if the root chain has to validate all child chains to assure itself of that, you have not gained anything
23:12:10Taek42:well, the idea is that you don't prove it at all. Instead you just rely on your random dispersion of hosts, and that a dishonest child blockchain will eventually be overtaken by an honest fork
23:12:34Taek42:Not being 100% sure is a sacrifice that you have to make if you want the scaling property
23:12:43Taek42:at least, as far as I understand
23:13:00Taek42:But I would argue that being 99.999999% sure is good enough
23:13:30Taek42:Especially if you are 100% sure about your own personal childchain that you watch.
23:16:19sipa:'eventually' is not enough
23:16:38sipa:you need to have that assurance before you accept a ttransfer from a childchain to the root chain
23:16:52sipa:or risk inflation of your currency
23:17:48Taek42:well, if you know that there are 21 million total coins, and you know that each child blockchain has X or Y, you never let the child spend more than their aggregate sum
23:18:13Taek42:so the worst thing that happens is some child builds a dishonest blockchain as the longest fork and it doesn't turn around for a very long time
23:18:41Taek42:this is sounding increasingly like sidechains though :P
23:23:10Taek42:I guess the static consensus part though would make it significantly different
23:42:14manaka:https://www.reddit.com/r/Bitcoin/comments/2is4us/whats_wrong_with_counterparty/ in this post vitalik says colorecoins p2ptrade has no way of enforcing orders. i 'm not sure what he means
23:45:25kanzure:protocol can't force bitcoin spends. so there's some "escrow period" after which if the transaction was never made, the other side of the transaction gets reverted.
23:50:58manaka:the escrow period gives a chance for all nodes to communicate. otherwise double spending could occur correct?