Dear Bitcoin developers,
In brief, the proposal I have is to extend the protocol to allow
partial block download and upload. This is for people with
intermittent connectivity or restricted connectivity. e.g. my own
internet connection is quite slow, and my ISP routinely sends RSTs to
both sides
Check it :) https://github.com/bitcoin/bitcoin.org/pull/34
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can
Hey, looks good! I'm glad to see them sorted alphabetically :)
A couple comments: I don't think the entries for wallet security and
backups accurately describe Armory. Wallet Security should say
Encrypt/Offline or something to to that effect -- after all, offline
wallets are the holy grail
Are we looking at the same list? Because here is the order I added: Bitcoin-Qt,
Armory, Electrum and MultiBit. Maybe try CTRL-F5 to force a refresh of your
browser.
Also about the descriptions: yeah I know. I think it's better to put this up
first and then have everyone submit their own
Actually I was looking at a screenshot someone sent me because I couldn't
seem to access it even after changing the hosts file (I assumed it was
recent, but I guess not). It just looked like the regular Bitcoin page
(despite doing a ping on the command line and seeing the expected IP). Was
there
Although quite true, I actually agree though that there should be some sort of
checksum for the blocks. Bandwidth may not be a bottleneck now (or ever), but
it may be at some point. This change will help Bitcoin scale.
It stopped being just a website a long time ago.
Blocks already checksum; they hash to a low number.
Also inre: block headers, you are furnished with a previous hash in the
first 80 bytes of the block. You can always cut the connection at that
moment if you've already seen the block headers.
Peter
On Mon, Apr 30, 2012 at 1:02 PM, Zell Faze
7 matches
Mail list logo
