I mean, if I want to store the whole block chain to do data analysis on a web site, what is the best database to use for that?
People generally wind up creating custom databases, or at least highly custom setups of standard database software. You are talking about indices containing many millions of records. It isn't as easy as just telling your SQL db to index a column. People often turn to tools like redis for such huge datasets. |
|
|
|
where do i report a bug in pushpool?
Sounds like you are using a modified version of pushpool. Report bugs to the developer who modified it. all 3 pools for ELC are having weird reporting bugs. shares are being paid out but reporting is off. no blocks since a difficulty retarget have been reported, and yet there are blocks being found according to elacoind debug log.
That's an issue outside bitcoind / pushpool, in the pool software. |
|
|
|
The fact that goto has been used badly doesn't make it a bad instrument: it's a great instrument if you know exactly when to use or not use it.
Donald Knuth and Linus Torvalds both agree with this sentiment.  Just like any other tool, you have to know when to use it, and when not to use it. |
|
|
|
Little suggestion to the dev team: when dropping the block size limit, also consider implementing "replacement code" that would give block generators the ability to control the block limit themselves through soft-limits.
Block size soft limit is already a configurable parameter inside bitcoind. |
|
|
|
Off-chain transactions offer unlimited tps. Off-chain transactions aren't Bitcoin. Not true at all. You may send a digitally signed message to anyone, by any means of digital transmission. Any number of economic incentives may exist to maintain exclusivity. |
|
|
|
This puppy ain't gonna fly with a 7 Transactions per second limit, even if it was only reserved for large transactions.
There is no 7 tps limit, even with 1MB blocksize. Off-chain transactions offer unlimited tps. |
|
|
|
Installed, so far all seems to be working fine. Amount of "ERROR: CTxMemPool::accept() : nonstandard transaction type" lines in log file is huge, no wonder datadir is almost 10 GB. The vast majority of that 10 GB is blockchain database, not debug logging. |
|
|
|
|
Disabling wifi was always a good idea.
Hard line is far more reliable in general, rather than suffer a wifi drop at a bad moment (submitting a difficulty 64 hash). It also uses less memory.
|
|
|
|
One issue that seems to persist here is the lack of a menu for Bitcoin-Qt after installation in Ubuntu unity for example in Ubuntu 12.04.
Sure this isn't a UI/Unity issue? Did you mouse over to the very, very top-left of the screen, where the panel usually lives? |
|
|
|
What is Kaminsky's deal? Saying there is a 0% chance for Proof-of-Work to survive the year? Wtf? He seems a bit misinformed about bitcoin mining. He thought GPUs couldn't currently mine bitcoin profitably, and he also thought that one entity having over 50% of hash power would result in a bitcoin price of zero, which was obviously not the case when deepbit did it. He also seems to believe that scrypt is ASIC-proof, which is not true.
He's way off. Check out @dakami and @jgarzik twitter. There is even a bet on the floor (that he's trying to back away from). |
|
|
|
Reminder: for those of you downloading a fresh copy of the blockchain, please consider using the blockchain data torrent. Testing feedback still welcome and encouraged. Post your platform/OS version in your report, as David M just did (thanks!). |
|
|
|
I wonder if FinCEN could come out with an additional "guidance" along these lines...
A) If you operate a bitcoin node, defined as any client or server software that forwards bitcoin transactions to the bitcoin network at large, regardless of whether or not you are mining said currency, then you are a "money transmitter" and need to be licensed as such.
No, because it is not possible for you to spend the money. B) The preceding paragraph applies to anyone operating a node which accepts transactions from or forwards transactions to any U.S. citizen, regardless of the location of the node.
Ditto the preceding answer. C) If you store your bitcoins on a hosted wallet, where someone else forwards your transaction to the network, then you are not a money transmitter.
In this example, you do have the ability to spend this money. You are transmitting value. |
|
|
|
it's a pity the torrent isn't 7zipped...
could the next iteration of it be compressed?
Feedback on this is welcomed. Generally, not all platforms have an easy time getting up and running with 7zip. Users in the past requested something directly usable with bitcoind. Opinions differ, and maybe if it saves a gigabyte or two, it would be worth it. Some users also complain about the doubling of disk space required -- for both compressed and uncompressed copies. |
|
|
|
|
testnet may be reset at any time.
If somebody starts making it difficult to test with, it will get a new genesis block etc.
|
|
|
|
Is OP_EVAL functional on testnet?
Pay-to-script-hash (P2SH) is functional on testnet and mainnet. OP_EVAL has long been superceded and discarded. |
|
|
|
I'd like to see how the recent Open Transactions breakthrough might allow for such an agent to come to pass.
Bitcoin itself is more decentralized, so it seems like an agent would prefer normal bitcoin transactions. But hey, get creative. This entire subject leaves wide room for experimentation and research. |
|
|
|
Any clue what this person is trying to do (93.92.198.xx)? The only thing I noticed was that the source port reported in the receive version message was always 18333.... or are these other IPs trying to connect and there's some bug causing it to think it's the 93.92.198.xx address? Netstat reported 176.9.196.xx, not the 93.92.198.xx on one of them, for example
(ed: oh, lol, it's probably some altcoin junk? ed2: hmm, 18333 port would be related to testnet... these messages started appearing after i pulled the 0.8.2.1)
2013-05-24 05:57:35 accepted connection 5.9.245.xx:59356
2013-05-24 05:57:35 send version message: version 70001, blocks=237642, us=xx.xx.xx.xx:8333, them=5.9.245.xx:59356, peer=5.9.245.xx:59356
2013-05-24 05:57:35 receive version message: version 70001, blocks=80968, us=0.0.0.0:0, them=93.92.198.xx:18333, peer=5.9.245.xx:59356
2013-05-24 05:57:35
PROCESSMESSAGE: INVALID MESSAGESTART
[...]
2013-05-24 06:09:45 disconnecting node 93.92.198.xx:39666
That seems a reasonable guess. Either a client program sending garbage, or a client program with a different pchMessageStart (network identifier), connecting on the same port. A lot of the alt-coins are so lazy, so poorly done that they fail to change the things that bitcoin nodes connect to, like network id or TCP port. |
|
|
|
Currently, the blockchain size is 7.5 GB (235.000 blocks) and it takes more than 24 hours to download and verify with an average home connection.
See Bitcoin blockchain data torrent thread. Every 4032 blocks (28 days in average) a Blockchain Block Checksum is generated by a trusted developer and included in the Bitcoin Client.
This is already done in limited form the form of checkpoints. However, because bitcoin is a zero-trust system, it is impossible to avoid validating the full blockchain. |
|
|
|
That does not hold true once the blocksize limit is removed, which will happen eventually.
There is insufficient consensus to make that prediction. |
|
|
|
|
Show Posts
