Re: [Bitcoin-development] Fwd: Block Size Increase Requirements

2015-06-01 Thread Thy Shizzle
d my post. I thought it was obvious that it was sarcasm where I do not seriously believe particular participants should be excluded. On Mon, Jun 1, 2015 at 3:06 AM, Thy Shizzle wrote: > Doesn't mean you should build something that says "fuck you" to the > companies that ha

Re: [Bitcoin-development] Fwd: Block Size Increase Requirements

2015-06-01 Thread Thy Shizzle
Doesn't mean you should build something that says "fuck you" to the companies that have invested in farms of ASICS. To say "Oh yea if they can't mine it how we want stuff 'em" is naive. I get decentralisation, but don't dis incentivise mining. If miners are telling you that you're going to hurt

Re: [Bitcoin-development] Fwd: Block Size Increase Requirements

2015-06-01 Thread Thy Shizzle
WOW Way to burn your biggest adopters who put your transactions into the chain...what a douche. From: Mike Hearn Sent: ‎1/‎06/‎2015 8:15 PM To: Alex Mizrahi Cc: Bitcoin Dev

Re: [Bitcoin-development] No Bitcoin For You

2015-05-25 Thread Thy Shizzle
we can then look to bump up block size because hopefully 20mbps connections will be baseline by then etc. From: Jim Phillips<mailto:j...@ergophobia.org> Sent: ‎26/‎05/‎2015 12:53 PM To: Thy Shizzle<mailto:thyshiz...@outlook.com> Cc: Mike Hearn<ma

Re: [Bitcoin-development] No Bitcoin For You

2015-05-25 Thread Thy Shizzle
: gabe appleton<mailto:gapplet...@gmail.com> Sent: ‎26/‎05/‎2015 12:41 PM To: Thy Shizzle<mailto:thyshiz...@outlook.com> Cc: Jim Phillips<mailto:j...@ergophobia.org>; Mike Hearn<mailto:m...@plan99.net>; Bitcoin Dev<mailto:bitcoin-development@lists.sourceforge.net> Subj

Re: [Bitcoin-development] No Bitcoin For You

2015-05-25 Thread Thy Shizzle
Nah don't make blocks 20mb, then you are slowing down block propagation and blowing out conf tikes as a result. Just decrease the time it takes to make a 1mb block, then you still see the same propagation times today and just increase the transaction throughput.

Re: [Bitcoin-development] Reducing the block rate instead of increasing the maximum block size

2015-05-11 Thread Thy Shizzle
Yes This! So many people seem hung up on growing the block size! If gaining a higher tps throughput is the main aim, I think that this proposition to speed up block creation has merit! Yes it will lead to an increase in the block chain still due to 1mb ~1 minute instead of ~10 minute, but the

Re: [Bitcoin-development] Solution for Block Size Increase

2015-05-07 Thread Thy Shizzle
Nicolas, can you think if there would be a problem with allowing blocks to be created faster instead of increasing block size? So say if difficulty was reduced to allow block creation every 2 minutes instead of 10 minutes, can you think of any bad outcome from this (I know this is different to w

Re: [Bitcoin-development] Where do I start?

2015-04-15 Thread Thy Shizzle
Zero conf :D From: gabe appleton Sent: ‎16/‎04/‎2015 12:15 PM To: bitcoin-development@lists.sourceforge.net Subject: [Bitcoin-development] Where do I start? Background: I'm a CS student

Re: [Bitcoin-development] "network disruption as a service" and proof of local storage

2015-03-27 Thread Thy Shizzle
If the IP discovery is your main motivation, why don't you introduce some onion routing into transactions? That would solve this problem easily, of course there is an overhead which will slightly slow down the relay of transactions but not significantly, also make it an option not enforced, for

Re: [Bitcoin-development] Address Expiration to Prevent Reuse

2015-03-26 Thread Thy Shizzle
companies-51183 From: Gregory Maxwell<mailto:gmaxw...@gmail.com> Sent: ‎27/‎03/‎2015 2:13 PM To: Thy Shizzle<mailto:thyshiz...@outlook.com> Cc: s...@sky-ip.org<mailto:s...@sky-ip.org>; Tom Harding<mailto:t...@thinlink.com>; Bitcoin Development<mailto

Re: [Bitcoin-development] Address Expiration to Prevent Reuse

2015-03-26 Thread Thy Shizzle
Yes I agree, also there is talks about a government body I know of warming to bitcoin by issuing addresses for use by a business and then all transactions can be tracked for that business entity. This is one proposal I saw put forward by a country specific bitcoin group to their government and s

Re: [Bitcoin-development] "network disruption as a service" and proof of local storage

2015-03-23 Thread Thy Shizzle
Wow, that's quite impressive. But what comes to my mind is if such an extravagant solution really need to be implemented regarding proof of storage? I mean, my idea whilst building my node was to do something along the lines of "tell me what you got" i.e get block height from the version message

Re: [Bitcoin-development] Criminal complaints against "network disruption as a service" startups

2015-03-22 Thread Thy Shizzle
From: odinn<mailto:odinn.cyberguerri...@riseup.net> Sent: ‎23/‎03/‎2015 4:50 PM To: Thy Shizzle<mailto:thyshiz...@outlook.com> Cc: bitcoin-development@lists.sourceforge.net<mailto:bitcoin-development@lists.sourceforge.net> Subject: Re: [Bitcoin-development] Criminal compla

Re: [Bitcoin-development] Criminal complaints against "network disruption as a service" startups

2015-03-22 Thread Thy Shizzle
I don't believe that at all. Analyzing information publicly available is not illegal. Chainalysis or whatever you call it would be likened to observing who comes and feeds birds at the park everyday. You can sit in the park and observe who feeds the birds, just as you can connect to the Bitcoin

Re: [Bitcoin-development] Electrum 2.0 has been tagged

2015-03-12 Thread Thy Shizzle
still don't allow completely > arbitrary words to be used because I don't see the word lists changing > too often, nor implementations storing word lists of all words and > languages. > > Thanks for clarifying, > -Neill. > > On Thu, Mar 12, 2015 at 04:21:59AM +

[Bitcoin-development] Broken Threading

2015-03-12 Thread Thy Shizzle
Yes apologies for the broken threading, it was the result of me auto forwarding between mail providers etc. To fix this issue I have created this new dedicated outlook account (thyshiz...@outlook.com) that I shall use for all my subscriptions here and I am unsubscribing the yahoo address. This

Re: [Bitcoin-development] Testnet3

2015-03-11 Thread Thy Shizzle
Strangely enough, it has started to work properly and I didn't even touch my code just had it sitting there in the loop/ping circuit it was performing and capturing with wireshark.that is quite odd! "Hi, so I have my .NET node communicating on the P2P network just fine, so I figured as I'll

Re: [Bitcoin-development] Electrum 2.0 has been tagged

2015-03-11 Thread Thy Shizzle
  Why on earth would you want to derive the mnemonic from the wallet seed? Ever? Remembering that as an attacker doesn't actually have to do any key stretching, they can just keep trying (what is it 64 bytes from memory?) at a time without any PBKDF2 to attack a seed, it seems that the PBKDF2 is

Re: [Bitcoin-development] Electrum 2.0 has been tagged

2015-03-11 Thread Thy Shizzle
Yes I agree with this sentiment. As for the version, don't forget we can kinda "brute force" our way to determine a version, because lets say there is 10 versions, we can generate the seed for all 10 versions and then check to see which seed was in use (has transacted) and then use that seed. If

Re: [Bitcoin-development] Electrum 2.0 has been tagged

2015-03-11 Thread Thy Shizzle
nemonics. On Thu, Mar 12, 2015 at 02:16:38AM +, Thy Shizzle wrote: > That's disappointing the Electrum 2.0 doesn't use BIP39. Agreed, but I don't know the full background on this. > Changing the wordlist in the future has ZERO effect on derived seed, whatever > mnemo

[Bitcoin-development] Testnet3

2015-03-11 Thread Thy Shizzle
Hi, so I have my .NET node communicating on the P2P network just fine, so I figured as I'll now start looking at making and validating transactions etc I should probably migrate to test net. Now I see that we are up to the third generation testnet testnet3, and I am sending my messages now usin

Re: [Bitcoin-development] Electrum 2.0 has been tagged

2015-03-11 Thread Thy Shizzle
Also as I've shown, you can work a version into it, I was going to actually propose it to the BIP39 authors but didn't think it was an issue. I think BIP39 is fantastic. I think Electrum 2.0 (And everyone) should use BIP39  On 2015-03-11 06:21 PM, Thy Shizzle wrote: > H I don&#x

Re: [Bitcoin-development] Electrum 2.0 has been tagged

2015-03-11 Thread Thy Shizzle
That's disappointing the Electrum 2.0 doesn't use BIP39. >From my interpretation of BIP39, wordlists DO NOT REQUIRE to be fixed between >wallet providers. There is some recommendations regarding the wordlists to >help with things such as predictive text, so mobile apps can easily predict >the wo

Re: [Bitcoin-development] Useless Address attack?

2015-03-04 Thread Thy Shizzle
s. *    * Several indexes are kept for high performance. Defining DEBUG_ADDRMAN will introduce frequent (and expensive) *      consistency checks for the entire data structure. */ On Wed, Mar 4, 2015 at 5:40 PM, Thy Shizzle wrote: Hi, so just a thought as my node relays addresses etc. If I wan

[Bitcoin-development] Useless Address attack?

2015-03-04 Thread Thy Shizzle
Hi, so just a thought as my node relays addresses etc. If I wanted to really slow down communication over the P2P network, what's stopping me from popping up a heap of dummy nodes that do nothing more than exchange version and relay addresses, except I send addr messages with all 1000 addresses

Re: [Bitcoin-development] What's what with addr relaying?

2015-02-19 Thread Thy Shizzle
relay because the if it hadn't been seen for 60 minutes previously it now becomes 3 hours and we use but don't relay makes sense. On Thursday, 19 February 2015, 22:33, Thy Shizzle wrote: Hi, plugging away at my C# Bitcoin node "Lego.NET" Thashiznets/Lego.NET

[Bitcoin-development] What's what with addr relaying?

2015-02-19 Thread Thy Shizzle
Hi, plugging away at my C# Bitcoin node "Lego.NET" Thashiznets/Lego.NET now I am currently working on addr relaying. I am as we speak wiring up my DB in Azure, and ready to start plopping net_addrs in my DB, all good however I'm reading two different specification docs that seem to be wildly va