|c0rw|away is now known as c0rw|zZz
|maaku is now known as Guest19249
|tdryja has left #bitcoin-wizards
|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
|Users on #bitcoin-wizards: andy-logbot gielbier ThomasV AaronvanW NewLiberty goregrind Mably nwilcox mjerr gill3s sparetire orperelman luny` d1ggy_ justanotherusr MrTratta TheSeven dc17523be3 PRab TheButterZone nessence_ Dr-G2 PaulCapestany spinza melvster mengine Guest19249 moa execut3 DougieBot5000 chmod755 jb55 jmcn_ bosma Starduster_ devrandom akstunt600 sdaftuar p15_ narwh4l adam3us cdecker Aquentin jtimon badmofo Madars c0rw|zZz mkarrer roybadami LeMiner waxwing
|Users on #bitcoin-wizards: MoALTz digitalmagus UllrSkis lnovy MRL-Relay theymos stonecoldpat epscy dgenr8 mountaingoat SDCDev pollux-bts Jaamg Tebbo rustyn forrestv espes gnusha Cory Luke-Jr tucenaber Emcy bliljerk101 elastoma ThinThread austinhill jonasschnelli huseby null_radix catcow adams__ Taek rasengan cfields btcdrak bedeho phantomcircuit kanzure sadoshi SwedFTP TD-Linux GreenIsMyPepper hulkhogan_ richardus sl01 michagogo otoburb isis ttttemp kinlo EasyAt nephyrin`
|Users on #bitcoin-wizards: Krellan nsh vonzipper larraboj_ mariorz coryfields_ sneak optimator go1111111 stevenroose BlueMatt eric afdudley warptangent ryan-c crescendo prosodyContext mappum wiz nickler_ jbenet kyuupichan livegnik pigeons davout Fistful_of_Coins mikolalysenko fluffypony amiller BananaLotus Logicwax scoria andytoshi superobserver STRML jouke Alanius_ jaromil fenn gribble nanotube Guest68586 grandmaster indolering BrainOverfl0w [ace] catlasshrugged
|Users on #bitcoin-wizards: throughnothing poggy guruvan dignork yoleaux gavinand1esen Anduck veox helo grubles heath roasbeef ggreer Iriez starsoccer binaryatrocity_ Muis Xzibit17 comboy petertodd wumpus a5m0_ jessepollak dansmith_ [d__d] AlexStraunoff sturles HM midnightmagic merlincorey warren azariah_ jrayhawk qawap Meeh_ mm_1 face tromp_ koshii _whitelogger dasource ebfull OneFixt jcorgan sundance bsm117532 CodeShark K1773R gwillen lclc wizkid057 ajweiss so s1w yrashk
|Users on #bitcoin-wizards: CryptoGoon artifexd runeks kumavis platinuum yorick Apocalyptic iddo smooth thrasher` weex berndj harrow harrigan brand0 leakypat Eliel xabbix morcos Graet @ChanServ AdrianG
|is it worth signing up for the new dev list
|aren't we being migrated?
|thats why i said new dev list
|last mail I read was that the new list was in test only, and that you could subscribe to test
|didn't read the last mail yet
|seems we do need to subscribe manually
|yes, you need to subscribe to the new dev list manually. Whether it's worth it is up to you (and off topic), the old one is defunct.
|wumpus: I'd assume ppl would get migrated, but indeed, it's offtopic to discuss the sf soap
|auto-subscribing people to mailing lists is considered bad netiquette, and this is an opportunity to get rid of inactive subscribtions. To see if you missed any messages see the archives: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/
|there was an 'emergency migration' mail to the old list, but I think no one got it because of sourceforge's mass bounce mess-up
|Is there a notation for an HD path of a public point derived from a path of hardened children? i.e. point(m/44'/0'/0')
|M/44'/0'/0' doesn't really seem right because you can't derive 44' from M
|By 'a notation' I mean something other than point(...), as that's not really a common notation for a path
|wumpus: at least I received the emergency migration mail.
|StephenM347, what's used in the HD wallet BIP?
|nsh: N(...), I think
|serP(point(kpar)) || ser32(i)).
|that's a serialized point though i think
|nsh: I'm more thinking about notation for a parseable path that can be saved and used to re-derive the key later
|Not notation that is easy to read in a paper or something
|* nsh nods
|jposner_ has left #bitcoin-wizards
|Bitcoin has some perceived decentralization problems due to the mining and mining pool thing. I just realized that this is due to the market realizing there are two separate jobs in mining that Bitcoin design tried to mix up. One job is to be a witness (mining pools) for the state of the ledger and the other is to carve the witnessed state into permanent ledger (miners).
|the witness job looks to be one that needs to be tied to an identity. So might as well make use of that and have a cryptographic identity for each witness. Then it'd become possible for witnesses to witness each other witnesseses witnessing and thus form a data structure that could be difficult to forge. Especially if we have miners cementing that structure.
|it'd create a kind of a witness network where the presence of witness loops (or cycles) in the network graph would allow verifying the entire structure as long as you trust one single witness somewhere.
|there could also be two levels of witnesses. Ledger witnesses and witness witnesses. The first ones are those who verify the ledger. The witness witnesses just witness the witnessing and record that.
|yes i believe this strategy is called "ask a friend"
|* nsh blinks
|* kanzure witnesses nsh blinking
|i'm pretty sure you can't witness things cyclically without a time machine
|* Eliel witnesses kanzure witnessing nsh blinking
|(now, if kanzure witnessed my witnessing of his witnessing, there would be the kind of cycle I talk about)
|and why would that be useful?
|proof-of-work forgeproofing works because it puts an economic floor on the cost of the probability of you being tricked
|otherwise it's just absurdly cheap
|because, everyone who's part of the cycle must cooperate to succesfully falsify the data. If it becomes possible for anyone to be part of the witnessing network...
|well, the data structure would become enormous but no-one needs all of it.
|i'm not sure it requires individuals to falsify the data- for sufficiently large networks, most users will not be able to practically meet and know each person or memorize their keys, so it's more likely that large networks are just randomly generated sybils
|each individual node can do just fine with a few verified "connections" they witness.
|i think that you might have more success narrowing the scope of which things you want to make unfalisifiable
|as long as that connects them to the network
|this is sufficient for timestamping.
|in short, it doesn't matter if falsifying the ledger is simple if anyone you want to fool then has the data they need to prove you abused your witnessing powers.
|in such a case, you don't need a lot of ledger witnesses. As long as it's possible to add more or even completely replace them in the event that the existing ones prove themselves to be completely untrustworthy.
|Eliel: I liked Joe Bonneau's paper on "Agile Tokens". It seems kind of relevant to what you were talking about -- "ledger witnesses".
|waxwing is now known as oakpac1fic
|oakpac1fic is now known as waxwing
|c0rw|zZz is now known as c0rw1n
|jps_ is now known as jps
|c0rw1n is now known as c0rw|zZz