I imagine that rebuilding the database will fix this, but thats ages. Anyone have any suggestions? I have the torrent of the database that slush put up (I think it was him), so that may be easiest.
I had that happen to me too. I had to rebuild the database. |
|
|
|
New Electrum server appeared at electrum.bitcoin.cz:50000 few minutes ago. Ports 80/443 are not configured yet.
How are you doing 80/443? Are you forwarding them to 50000? I didn't see anything about this in ovidiusoft's guide. I updated the guide, should be in the main tree soon. |
|
|
|
Let's make the rule really simple: blocks are invalid if there are tx'es older than 8h not included. What do you think? I'd "time" them in blocks. What if there are too many to include in a single block?  I kind of doubt there will be a "too many tx in the same block window" problem any time soon, but sure, blocks works just as well. |
|
|
|
Now that the scammers are (at least mostly) gone and shut up... I'm offering a 50k CLC bounty to a practical, technological solution to my monopoly on CLC. If there are multiple people involved in the solution (eg, one person designs it and another implements it), I will decide how to split it up among them.
I'll say straight off, that this does not include "solutions" like the all-too-common FUDing and slander, nor special-casing to my particular blocks (that is, I should still be able to mine like everyone else after it's fixed), though fitting to the particular nature of this monopoly is acceptable.
I'm not involved in CLC and I don't have the knowledge to implement it, but I think this idea of mine might work: https://bitcointalk.org/index.php?topic=53128.0Basically, we consider miners who don't include old transactions in mined blocks are hurting the network so we invalidate their blocks. The idea was rejected because it was considered it would take away freedom from miners. In CLC context and your attack, something like that seems to be perfect - your hashing power would allow you to only delay all trasactions up to a maximum limit. Let's make the rule really simple: blocks are invalid if there are tx'es older than 8h not included. What do you think? |
|
|
|
I have another idea. It's not as high tech as yours, but it has the advantage that you can implement it now. You need: 1. a safe. 2. a friend. You don't know the password to the safe, only your friend does. He refuses to open the safe for you unless you pay him 1 BTC. There - a physical safe you can open with bitcoin  |
|
|
|
|
Also google "Rainbow Tables". It's been done for some algorithms, but their real-life usage is limited by the spread of multiple hashing, which would require exponential storage.
|
|
|
|
Do I need two P2Pool daemons? One for Bitcoin/Namecoin and another for exclusively Litecoin?!
Correct. You'll need to install the ltc_scrypt module from the litecoin_scrypt directory and then you can run p2pool for Litecoin. The other p2pool daemon will do BTC+NMC merged mining, but keep in mind that for namecoin you are actually solo mining. See options --merged-url and --merged-userpass, which need to point to namecoind rpc. Hopefully a future version of p2pool will do real p2p merged mining. |
|
|
|
Also, can p2pool talk to a remote bitcoind, or must they both be on the same box? I haven't found any sort of --connect option, but perhaps I'm doing it wrong. (also, any word on running it as a service?)
It can, use options --bitcoind-address, --bitcoind-rpc-port, --bitcoind-p2p-port. |
|
|
|
Section "ServerLayout"
Identifier "aticonfig Layout"
Screen 0 "aticonfig-Screen[0]-0" 0 0
EndSection
Does anyone know what the issue could be? Your xorg.conf doesn't look good. It also needs screens and monitor sections for the second card, and another entry in the ServerLayout section. Regenerate your xorg.conf with aticonfig --initial, you'll see the differences. You need to restart the X server after that, of course. |
|
|
|
could it be used with FPGA miners?
kind of monitoring them and making sure they're not idling
that would be a killer combination (power consumption point of view)
I think so. The whole setup could even be powered by solar power That would be very cool! |
|
|
|
Only during blockchain download/verification, right? for me, it's sitting at 0% cpu utilization. Also on transaction propagation. A dedicated node will maintain tens of connections to the other nodes (my own btcnode.novit.ro has ~150 connections all the time, I've seen as high as 400). At that point, this becomes an issue for a small device like the Pi. I'm not saying it's not doable, but someone running a dedicated node might want to use a different platform and use the Pi for something else. |
|
|
|
Since it has such a low power consumption and is essentially able to run quietly in the background, it could run bitcoind and act as a full node in the network. That would benefit everyone.
Unfortunately, parsing the blockchain is resource intensive - both CPU and I/O. Neither of these are the strong points for Raspberry Pi. However, a thin client like Electrum and a touchscreen (or 5-7 inch LCD + a small numeric keyboard) would make it a very nice POS solution. |
|
|
|
Which doesn't change the fact that hardware errors are quite rare. On 16 GPU I have never had a single HW error logged in over time 9 months.
Your high overclock likely has something to do with it.
Absolutely, I was just replying to ckolivas's assumption that hardware errors will lock the card or make it 'dead'. It's possible to overclock "just right" so the gain in mhashes is worth the few hardware errors, while keeping the uptime at 100%. |
|
|
|
Hardware Errors=0 even though one card is "DEAD" ? Hardware errors are very different to a card becoming unresponsive under load. Usually hardware errors occur if someone has unlocked the shaders in a card that has faulty shaders, or they are overclocking beyond reliable levels but below crash levels. Hitting hardware errors without a hardware hang/dead card is actually quite rare. Mmmm... no, not really: RAM: 325 CPU: 1040 Mhash/s: 337,2 Accepted: 289690 Accept/min: 4,51 Hardware: 523 Hardware %: 0,18 As you can see, a uptime of 1,5 months (since I restarted cgminer). The card never haged or went dead. |
|
|
|
Would it be possible to compile the app with the target of .NET 3.5 instead of 4.0? I'm trying to run it in Linux using Mono and some things are not supported for 4.0. System.Windows.Forms.SplitContainer doesn't implement interface System.ComponentModel.ISupportInitialize
... which is this Mono bug: https://bugzilla.novell.com/show_bug.cgi?id=648403 |
|
|
|
MtGox can do whatever they want, legal, illegal, moral, immoral, and they answer for it legally or business-wise. I wouldn't do business with someone if I believe it might get me in trouble (whatever that "trouble" might be), either. They probably considered it's more risky for their business (remember they are, but Bitcoin standards, huge) to allow the trading of those coins. What's the problem? Whether they will lose business because of it, remains to be seen. As long as we have choices of exchangers, I don't worry. What they should do, is to write an easy to read and understand TOS so customers know what are the security procedures (maybe they do have something like this, I only checked the front page, it's not there), how they do their checks, and so on. Let me be the devil's advocate: a risk-adverse customer (let's ignore for a moment the fact that Bitcoin is not for the risk-adverse people ) might consider a great advantage that someone is taking care they won't buy stolen coins. Who are we to decide that is not a reasonable thing to do? |
|
|
|
Any ideas? I have the username and password set in /etc/electrum.conf so I'm not sure why it's prompting me for them. When I put them in, it just prompts me for them again.
Any extra leading/trailing spaces in bitcoin.conf or electrum.conf ? Did you edit the files in Windows (so there might be a CR/LF there) ? |
|
|
|
I'm setting up an electrum server right now. I plan on also running it with a tor hidden service just for fun.
I would like to have these included in the HOWTO. Can you please document it? So far there have been lots of steps, but ovidiusoft's guide has helped a lot. It doesn't mention anything about dependencies, but those will vary from system to system so thats okay.
Everything was already installed on that machine (it's a test/development machine so I have a loooot of stuff there). If you're installing on a standard server distribution, let me know what packages are not installed by default so I'll include them in the HOWTO. |
|
|
|
|
Show Posts
