|
I met the guys behind the documentary in Vienna this week. They are really doing this and they are working hard on a really tight budget.
Please consider to donate.
When I met them they had been driving since 3AM from somewhere north of Berlin (quite a trip) to do two interviews. Saving money on transportation and hotel.
|
|
|
|
Edit: As far as I can see, that bug I was talking about was fixed. It looks like I can't import the private key from another address made with Bitcoin Wallet for Android to BitcoinSpinner. Ah well.
Right, I haven't added key import yet. The good news is that it is very easy to send bitcoins from one address to another ;-) |
|
|
|
New version out 0.8.2b: -Using MtGox's new ticker located on data.mtgox.com. The old one is being deprecated. -Updating Russian translation according to O.Dima V's changes Upgrade from Google Play or alternatively you can do a direct download at: https://code.google.com/p/bitcoinspinner/downloads/listEnjoy |
|
|
|
With bloom filters on the horizon or kind of available already, will BitcoinSpinner continue to use its custom server or will this allow to turn it decentralized and independent from one particular server? Edit: All the effort that went into the server rewrite and negotiations with some BTC companies sounds like the answer is no. (I didn't follow this thread yet. Don't know why  ) It is going to be interesting to see bloom-filters integrated with wallets. I believe that we need all the diversity we can get, so BitcoinSpinner is not going the bloom-filter path. I am working full time for Bitcoincard now, and since the company regards the backend system as a strategic asset they are evaluating currently evaluating the benefits of open sourcing it. I can hopefully tell more about this after the conference. |
|
|
|
|
Thank you for your suggestions.
You are absolutely right regarding the current PIN security. It is there to avoid someone from grabbing your phone and move your coins while you look the other way.
I have been thinking along the same lines regarding encrypting keys, and didn't do it for the following reasons:
- Entering (secure) PIN/passwords on a smartphone is a real pain as it has to be long/complex
- Doing "key-stretching" on a shorter/less complex PIN (for instance hash the PIN many many times) takes long time if you want it to be secure. Using a fixed time (say 10 seconds) is not equally secure on every device as they have different CPU power and all have to compete with for instance a fast desktop computer, or maybe even an Avalon
Instead I do something else. I have two paper backups: one for my savings, and one for my daily use.
Normally I only have the wallet for daily use on my phone. Whenever I need to recharge it I:
1) Restore the savings wallet on my phone (Click the options button->Settings-> Restore wallet and scan the QR-code for your savings wallet backup)
2) Send funds to my spending wallet (I have the address in the address book, so it is really easy)
3) Restore the spending wallet (Click the options button->Settings-> Restore wallet and scan the QR-code for your spending wallet backup)
The entire process takes less than a minute
The important thing is that after step 3 the private key for the savings wallet gas been deleted from my device.
You can make this even more secure if you (as you suggest) use a dedicated device with nothing else installed.
|
|
|
|
|
S is not random. The miner can basically choose any value he wishes.
|
|
|
|
...
Can't a hash of the software version be encoded into each block?
...
But the software version of what? It is the miner who creates the block, and some miners (for instance deepbit) run on 0.3.x. |
|
|
|
The bitsofproof node sailed through the recent chain turbulences.
It was accepting the forking block in sync with 0.8 and was also able to re-org the 25 blocks as the other branch became longer.
Kudos to you. Are you happening to attend the San Jose conference? |
|
|
|
All time UTC+08:00:
08:08 – Well before I knew what later have happened, I deposited $10000-worth Bitcoins to BTC-e over OKPAY's Bitcoin payment, I paid OKPAY address 12z2n8YCJw1BEsJhhQPLCTuLqwH341nKnE 211.9093 BTC and 0.0005 BTC as transaction fee.
09:30 – The transaction was included in version 0.8's fork, block 225446
10:08 – Deposit completed, $9800 credited to my BTC-e account
12:53 – After some study, I recognized, the transaction, though included in version 0.8's fork, was never confirmed by the pre-0.8 fork, so I decided to make two double spend transactions on two of the vins of the OKPAY transaction, and broadcasted them with the raw transaction API, 0.001 BTC transaction fee included in each transaction.
13:01 – The double spend transaction was included in pre-0.8 fork block 225446
You should know what happens next...
I bet merchants would think twice before they decide to accept Bitcoins after the incident.
Ouch... |
|
|
|
If we use blockchain.info wallet, I guess we don't have to worry.
Will Multibit be affected?
MultiBit should be able to handle re-orgs of depth 50, so I guess you are fine. |
|
|
|
|
Regarding the blockchain fork currently in progress, BitcoinSpinner is on the 0.7 (winning) chain.
|
|
|
|
I personally am surprised and delighted that we move in this direction (back to the universal fork as trunk) rather than force an upgrade.
So am I. I thought only once banks or governments start cracking down on Bitcoin we will appreciate Bitcoins's capability of graceful degration [http://en.wikipedia.org/wiki/Fault-tolerant_system] but it only took a flaw to proove that it has that capability. My deep respect for the devs who took this issue on and solved it. You guys made Bitcoin and my believe in it even stronger. To blockchain eternity! Joe I think I kinda understand why this is a good thing, but can you explain like I'm five? Basically, why would it have been bad to let the 0.8 chain continue? Is the reason that it'd "force" older users to upgrade and that's a mean thing to do? I imagine that most services and many pools haven't upgraded to 0.8 yet, it is simply a safer bet to wait. (You can ask Gareth what BitInstant is running on) If we stayed on 0.8 it would take a LONG time for all services to get up to snuff. By going back to 0.7 everyone will be aligned within a few hours. |
|
|
|
We are soon going to witness the largest re-org in my time in bitcoin land. We will have thousands of computers worldwide doing a 24+ block reorg around the same time. Now I am looking for headlines saying "Mysterious power consumption spike worldwide, aliens or terrorists?"  |
|
|
|
...
The first thing to know is that all nodes will forget about transactions after a few hours
...
How long time does bitcoind remember a transaction? |
|
|
|
|
Show Posts
