1548 entries in 0.163s
artifexd: ThickAsThieves Have you heard from Danny lately? Is he ok?
artifexd: ;;rate bitcoinpete 1 Did exactly what he said he would do without delay
artifexd: ;;everify freenode:#bitcoin-otc:fe0d9a7006ac40048c49ae0e278f7f52c229fdb8b8b55499e7264c31
artifexd: <mircea_popescu> suppose someone has to be let go. << Fire the person that sucks at their job
artifexd: Ah. I was up in the north east. More north east than Dallas. Damn near Arkansas.
artifexd: "ain't" is black vernacular? I thought it was southern venacular. Source: I grew up in Texas.
artifexd: <ThickAsThieves> lemme know if you need help of any of the kinds i might be able to provide << I missed that. My response: Thanks! I will.
artifexd: I may have to just reset the genesis block and remove the checkpoints and start mining it myself.
artifexd: There's a testnet checkpoint at block 546 (or somewhere thereabouts).
artifexd: I don't want bitcoin testnet. I want altcoin testnet.
artifexd: That doesn't make it a good idea.
artifexd: I guess I get to test code in production, as it were.
artifexd: ThickAsThieves Do you know anyone running the altcoin testnet that I can connect to?
artifexd: Standard of success? No. Measurement? Sure. "Yes compile" is further along than "No compile"
artifexd: Success in communicating via code is much easier to measure than in english. "Did it compile?" vs "Did he/she understand me?"
artifexd: The audience of english is other humans, generally. The audience of code is the machine.
artifexd: It isn't about the medium. It's about the audience.
artifexd: For some people, talking is not fun. Or maybe it is, but writing code is orders of magnitude more fun than writing english.
artifexd: relevant quote "the Bitcoin network is performing enough computation to generate SHA-1 collisions every 131 minutes!"
artifexd: "Ok, so did you come up with Newman’s method or not ?"
artifexd: I did discover him in my googling. I didn't expect you to misspell his name though so I though you were talking about someone else
artifexd: That may explain why google failed me
artifexd: Change line 9 to vary the bias to your hearts content.
artifexd: True. But a generator that never generates can hardly be called a generator.
artifexd: Unless the bias is 100%, in which case there is no entropy to tap so you can't get any entropy out.
artifexd: I recoded my test for that change and the results are an even distribution regardless of flip bias. Cool.
artifexd: And if there was no bias in the coin, a straight forward flip would be good enough.
artifexd: bitcoinpete I can sell you a few ATC if you want to follow ThickAsThieves' advice
artifexd: ;;everify freenode:#bitcoin-otc:f35ce2f33ebfddb0b3e15de1380987380a2f99a0b8bb49dbbdd7e111
artifexd: Is it irony that #netsec was hacked?
artifexd: Apocalyptic Thank you for your opinion.
artifexd: I put my gpg key id on my website. Should I link it to a plain text file of the key or to its location on a key server?
artifexd: BingoBoingo Your link to bitcoinpete's blog is broken.
artifexd: There is a whole section on "Before you ask" though...
artifexd: nubbins` Interestingly, that link says that IRC is a good first place to ask.
artifexd: My wife has taken our daughter to Ecuador a couple times and no one asked me a damned thing.
artifexd: I can state with certainty that Ecuador has rules requiring notrized documentation from the not-present parent for taking a child out of the country. The US doesn't.
artifexd: Anyway, the point was that in the US, pre-18yo passports are common.
artifexd: She won't, but mom and I will.
artifexd: My daughter had a passport before she as a month old.
artifexd: loop: At the bottom of that page " Bitnodes uses Bitcoin protocol version 70001 (i.e. >= /Satoshi:0.7.x/), so nodes with older protocol version will be skipped."
artifexd: At least in the reference client.
artifexd: It is named in a comment. Variables don't contain the name.
artifexd: If you're asking about the code, then the code keeps track of amounts in satoshi. API's accept amounts in satoshi.
artifexd: There is reference to "satoshi" as the base element in the reference client code. All the code uses satoshi as the amount of accounting.
artifexd: mircea_popescu Your 1 million atc wall on x-bt.com is gone. Eaten up.
artifexd: "All email received unencrypted is automatically deleted unread." <- Should there be a comma between "deleted" and "unread"?
artifexd: nubbins` Revisit your mark-karpeles link and lol
artifexd: And if it isn't available for streaming, just about everything available via torrent is available via nntp
artifexd: Also, for the record, I think that increasing the block size right now is a dumb idea, not necessary and counter-productive to the desired result.
artifexd: I have a prior engagement that I have to attend to. I will think on this.
artifexd: Because you still have to find the birthday collision. Why would an attacker try to create a block 1 gigabyte long (which still has to be valid) in order to clash with a block 1 megabyte long?
artifexd: Your point is technically true, but practically worthless.
artifexd: However, your point that limiting the maximum length in order to limit the possible collisions is irrelevant as well because there is already a specific place for you to twiddle that will have the exact result you would want. The nonce/timestamp.
artifexd: If the hash was one letter, sure. 256 bits? "A lot" is being conservative.
artifexd: You are essentially looking at an attack that is by definition maximum difficulty.
artifexd: Because when the hash of a block is "discovered" the contents of that block are spread around the world. An attacker would have to not only find a collection of valid transactions and a sundry other pieces of data that collide with the exact same hash but also convince someone else that the replacement was the actual block.
artifexd: I don't argue with what your saying. I would instead say that this particular manner of attack would be monumentally stupid in the case of bitcoin.
artifexd: Just as much as you could claim it is mircea_popescu
artifexd: If we assume that md5 is a "good" hash function, then how much data you put into it doesn't have any bearing on what you get out of it. Thus the first character remains, essentially, random regardless of whether the input is 200 bytes or 200 megabytes.
artifexd: Making that reference harder to forge is where the security comes from. How much happens in between each reference point has no bearing on how vulnerable or reproducable each reference point is.
artifexd: Solidifying a group of tx into a block doesn't provide security in the same sense that 100 twigs in a bundle are stronger than 100 twigs seperately. It provide security in providing a stable time reference for when tx happened. Completely different domains.
artifexd: This will take a bit to type. Patience.
artifexd: I'm fairly well versed in block/transaction/hash/etc mechanics and I am trying to wrap your metaphore around that structure. It doesn't make sense. I normally have a high amount of respect for what you say. In this case though, I think you're wrong. Or, I don't understand the variety and thus need more lurking.
artifexd: mircea_popescu how does doubling the block size quadruple the work needed to get equal security? If a certain lock on a certain box provides XX amount of security, how does increasing the size of the box make the lock worth less?
artifexd: 1meg block allows for (ideally) 5000 transactions (at 200 bytes/tx). To get 12.5 btc in fees, each transaction will have to pay .0025 btc in fees. Them thar are some hefty fees.
artifexd: TAT: My wife bought that shirt for me. So many custom tshirt sites print on shitty quality shirts. This one was a good quality tshirt.
artifexd: Not that I know. I've looked and didn't find anything.
artifexd: About an hour ago someone dumped 20k+ shares and emptied the orderbook from .004 to .003.
artifexd: Then I'll sit down and shut up.