|
Crypto is notoriously hard to do right. Most privately developed systems are flawed. The best crypto systems are developed and reviewed publicly and refined until they're as good as possible. Bitcoin uses ECDSA, SHA256, and RIPEMD, and the specific implementation has been carefully reviewed as well. These are all top-tier, thoroughly reviewed systems that are unlikely to have any of the amateur mistakes they made in GMR and A5/2.
|
|
|
|
Any suggestions would be appreciated! I suggest you keep your business out of Bitcoins for now. Bitcoin's current strengths are in small transactions, international trade, and donations. If you're selling an expensive industrial product, practically no one you're doing business with will be interested in Bitcoin. What killer benefit would it have for anyone involved? It's time may come for your market too, but not yet. |
|
|
|
|
The problem is that if the customer actually did send the coins the store needs to either send them back or provide the goods.
One way to resolve it would be for the buyer to display a QR code of the signed transaction. The seller scans it and can verify it against their copy of the blockchain and transmit it to the network themselves.
|
|
|
|
|
There are also plans to prune obsolete history, but it's not implemented yet.
|
|
|
|
|
No problem! Do let me know if you (or anyone!) find another source of this data. I'd love to fill in the holes and go farther back in time.
|
|
|
|
If you make a bunch of micropayments from one wallet, they're trivially associated. If you want to use multiple nodes you'll have to source clean coins from different sources for each one. If one of the people who sells you coins gives you up (subpoena, rubber hose, whatever), you're compromised. Even if they don't it makes it much easier to associate all your previous connections together, which may compromise you. Bitcoin is pseudonymous, not anonymous, and there are many practical ways that people with resources can unveil you unless you are very careful and take a lot of precautions. https://en.bitcoin.it/wiki/Anonymityhttp://anonymity-in-bitcoin.blogspot.com/2011/07/bitcoin-is-not-anonymous.htmlTOR by comparison makes it so there are multiple nodes in different countries routing your data. Each time you start up (and any time you want) it builds a new tunnel with different nodes, leaving no connection to your prior identity. It's very strong anonymity, and it makes it very easy for anyone to get that level of security. Bitcoin's anonymity isn't anywhere near as easy and robust. |
|
|
|
|
It's highly redundant text. Most depths don't change from minute to minute, and there's lots of predictable syntax in JSON. That and 7Zip is awesome.
|
|
|
|
It's raw dumps of the JSON API (complete with occasional error messages and empty files) with PST timestamps in the filenames. It's about 5G raw, 33M compressed. Be careful extracting it: some filesystems get really slow if you put a quarter million files in one dir. http://www.mediafire.com/file/u1goocu36ng65kp/mtgox.7z |
|
|
|
Nice! It's the same idea with a little different approach that I've tried a bunch of times:  I have per-minute snapshots of the data since July. There are a bunch of gaps in the data so you have to be careful or you'll get time jumps, and it's just the public API so it's just a narrow window around the current price. If that's still good enough to be interesting to you, you're welcome to a copy of what I have. The only price is that I want to see more awesome pictures, especially around interesting events.  |
|
|
|
I don't understand the concern with just paying nodes via regular Bitcoins, or using the micropayment protocol described here: The problem is anonymity. TOR provides much stronger anonymity than Bitcoin. If you don't need that you can just use VPN services which are already available for BTC. |
|
|
|
|
As long as you save your wallet.dat you're safe.
Also check the time on your PC.
|
|
|
|
|
I would advise against it. You don't want to go down in history as the first guy to spam the blockchain, your shame on display for eternity.
|
|
|
|
|
All the nodes you got from IRC aren't accepting connections (which isn't that abnormal; most nodes are behind a firewall).
What node did you try adding? Can you try: -dns -addnode=bitcoin.es
Also, if you're behind a firewall and on a reasonably secure LAN, can you try turning off the Windows firewall briefly just to test?
|
|
|
|
|
Actually no need for -debug. Just delete your debug.log (it's probably huge), then restart Bitcoin. Let it run for a bit and post the log. That should have enough without the full debug info.
|
|
|
|
|
OK, next try running bitcoin with -debug . That will generate a debug.log file. Let it run for a bit then post the log here. Hopefully it will have some clues.
|
|
|
|
|
That sounds like a firewall - software on your PC, your home router, or your ISP - is blocking Bitcoin. Have you checked those?
|
|
|
|
|
Windows also keeps previous versions of documents if the feature is turned on. Even if it wasn't the blocks where your wallet was stored may not be overwritten yet. Stop using your computer and run cassacius's recovery tool. If they're anywhere to be found it's your best bet.
|
|
|
|
|
guiminer can run in the systray and you can set the icon hidden in the tray.
|
|
|
|
|
Show Posts
