Thanks!

That fixed it for me, too.

I had a similar crash, on MacOS, though. It happened right after validating the previous blockchain, and as the GUI loaded.

The final logging line was "GUI: TransactionTablePriv::refreshWallet", right after loading the root certificates.

Ran it again with -resetguisettings and it's fixed! I got the welcome screen again, that's OK, it was happy to re-use my existing blockchain download (re-indexing for 0.15 had already completed by this point).

Josh

Wow.  I knew he had ALS and was becoming increasingly paralyzed, but didn't know he had passed on until just now.  What a frustrating and imprisoning feeling that must be: to have a brilliant mind trapped in a failing body that can no longer communicate to the outside world.

I hope the 0.0001 BTC unit can be named in his honor (the "Finney").

Nice!  I thought about "Bitcoin over radio" as well.  Didn't get to the point of deciding exactly which frequencies or modes would be best for the task, though.  Just thought about the general idea, using the model of a ham radio repeater that serves a given geographical region.

The idea is to have some way of ensuring Bitcoin transactions can still be made, even if the Internet is down/unavailable/suppressed in the region.  It would work similar to a ham radio repeater, many of which already support various digital modes.

The repeater (good radio station on a mountaintop or something like that, so it has good reach) would be the only node that would require Internet connectivity.  It would have an output frequency (always transmitting), and an input frequency (always receiving).

The repeater would broadcast the blockchain as it came in, on its output frequency.  The repeater would also broadcast local transactions that have not yet been confirmed, to acknowledge them.

Individual users would transmit to the repeater, on its input frequency, the transaction they wish to make.  Only the repeater needs to receive the transmission, other individual users don't need to, as long as everybody remains within range of the repeater.  As with traditional ham radio, this lowers the cost dramatically and makes it easier to use, as only the repeaters need to have really good antenna locations, as users can reach other users through the repeater.

If the Bitcoin node at the repeater deemed that transaction to be acceptable (stored it in mempool and relayed it to other nodes over the Internet), then that transaction would be rebroadcast on the output of the repeater, so that all within radio range would know it, as well as over the Internet.  Thus, the sender of the transaction would get acknowledgement that it had been accepted.

If there is enough downtime between blocks, the repeater would rebroadcast historical blocks, so that anybody who missed a block due to static/interference or whatever could have another chance to stay fully synchronized.

An additional sophistication could be to add the ability to subscribe to addresses of interest (using filters for privacy), so that unconfirmed transactions matching those filters would also be broadcast on the radio, not just blocks.  This would provide faster notification of incoming transactions, without having to wait for them to appear in a block, similar to outgoing transactions.

The idea is to have the ability to transact by Bitcoin be very survivable.  If the traditional Internet connections are knocked out, either by disaster or intentionally by government trying to do suppression/censorship, the ability to do Bitcoin by radio could be very useful.

Josh

Nice!

I got pywallet running, and it helped me to scrub out an old 0/unconfirmed transaction that I hadn't paid enough transaction fee to clear.

Had to make a small change, to get it to run on Gentoo Linux.

Unfortunately, Gentoo packaged the bsddb library under the name "bsddb3" which is incorrect, and breaks pywallet.  This works around that breakage, by trying to import from bsddb3 if bsddb fails.  Exactly the same library, but different name.

Here's the pull request for this: https://github.com/jackjack-jj/pywallet/pull/6

Josh

Sorry for the necropost, but I have to agree with Foxpup.

I would love the ability to set the minimum fee for transactions that my local node creates, independently of the minimum fee that will be required in order to accept transactions from others.

(earlier question removed, it seems not to be necessary anymore)

Nice, on IRC sipa told me of a third setting!  Simply use the -txfee command line option.  So, we do have 3 knobs to turn:

"mintxfee" in bitcoin.conf = Affects mined blocks that my node solves (I should be so lucky!)

"minrelaytxfee" in bitcoin.conf = Affects relayed transactions that my node receives from others

-txfee on command line (not bitcoin.conf) = Affects wallet transactions that my node originates

Is this right?

Josh

I think the FBI will keep it, especially if the trial leads to a conviction ("drug money" and other seized assets are kept by the government upon conviction, providing a nice revenue stream that many say leads to overzealous enforcement of drug laws when the local police agency is feeling a little poor).

It could provide the USA with a storehouse of Bitcoin, in much the same way as Fort Knox provides a storehouse of physical gold.  If Bitcoin takes off in the future and becomes more widely accepted, this could prove quite useful to the government as an asset.

I'm up and running on Linux.  Also using the modified cgminer from bitmaintech.  Thanks for posting your patch to GitHub.

https://github.com/bitmaintech/cgminer/pull/1

It compiles and runs perfectly.  I made the same fix independently before finding your pull request

There's lots of good documentation from AntMiner here:

https://github.com/AntMiner/AntGen1

The cgminer command line I'm using is:


If you aren't using P2Pool replace username, password, and pool URL with whatever your other pool requires, of course.

All my AntMiner USB devices autodetected cleanly, and I'm getting a clean 1.5 GH/s from each miner.

I rather like the idea of grouping Bitcoin units by 10,000 as others have said.

It fits in well with Bitcoin's design of 8 decimal places in total.

Grouping by 4 decimal places makes sense here, because 8 decimal places fits cleanly into two groups of 4.

Japanese culture already uses grouping by 4 decimal places: man, oku, chou, kei.  (Maybe this is why Satoshi chose to divide Bitcoin into 8 decimal places, and not 6 or 9, as a Western designer might have done?)

Chinese culture also groups by 4, and we all know how important China is to Bitcoin.

And, we already have a unit for 10,000 BTC, the Pizza (named after the first successful real-world transaction), so this is a smooth progression of units.

10,000 Satoshi = 1 ?

10,000 ? = 1 BTC

10,000 BTC = 1 Pizza

OK, enough rambling, here are my nominations for the "?" unit:

Nakamoto (goes with Satoshi)

Finney (memorable, and a tribute)

Others have already mentioned these, but I agree with them.

Josh

Nice, thanks!  Paid for 14 miners just now.  Sent PM with the details.

Nice, thanks for making the list!

Was wondering how much should be refunded, out of what I got out of mining that block (what little there was, I'm a small-time miner).

Just sent my refund now.  I wonder how much he ended up getting back?

Josh

Nice!!  Good to know you got control of that page.

Josh

Another "good" block was found recently by P2Pool:

https://blockchain.info/block/00000000000000000df911554881a518a0d1a0f4adeafb6b2e1136866c9a67b3

I calculated this would be good for a difficulty up to 78,688,747,242 (not sure the math was right, though).

I had that happen to me, too, but not nearly that bad.  Caught it in time.

The fuse did not blow, but the plastic of the fuse melted away and glued itself to the board.

I couldn't remove the fuse without using Vice-Grips to grab what's left of the plastic and carefully work it free.  Then I was left with bare metal tabs sticking out of the fuse holder.  Removed these carefully, with needlenose pliers.

The lid on the USB hub comes off easily by turning those little screws.  An Allen wrench, 3 mm size, worked perfectly for me.  It is much easier to access the fuse holder, and ATX power supply connector, this way.  Don't try removing the fuse (or whatever's left of it) without removing the lid first.

Reason is, when you're working on removing the fuse, be sure not to move or otherwise put stress on the fuse holder block!  It's soldered there with some very thin solder joints (probably too thin, that also causes it to overheat even more).  It's a fragile, weak area.  Might be a good idea to support the fuse holder block so that it can't move, perhaps with another pair of pliers, while you work at digging out the burned fuse.

Although my power supply claims to be "500 watts", it is only rated for 30 amps on the 5 volt rail (150 watts).  With 49 Erupters installed, I'm right on the edge.

I replaced the 40 amp fuse, that melted away, with a 30 amp fuse.  It has less capacity, but all 49 Erupters have been mining for several days now, and it has not blown yet.  I recommend doing this.  It also matches what my power supply is rated at, which will help keep it from accidentally becoming overloaded.

The fuse plastic is also a bit thinner, so it will stand away from the board a little bit, and hopefully make for an easier job of removing it later, if necessary.  The supplied 40 amp fuse that comes with the USB hub might be made out of a weak plastic that melts easily, it would seem.  My new fuse is nowhere near melting.

I also concentrated my fan cooling on blowing directly on the fuse area!  That area is a critical weakness and it gets hot.

Also the ATX power supply connector.  Feel it, and one of the wires will be warm to the touch.  That's the 5 volt wire.  The 24-pin Molex connector also doesn't like heat.  Molex is known to blacken easily, as anybody who has owned a pinball machine will tell you

When Molex blackens, it doesn't feed power as easily, so it blackens more, etc. and eventually you get thermal runaway and it burns.

On the other hand, the Erupters themselves don't really mind getting hot.  They still work fine.  Before I got this big hub, I just had the Erupters sitting on my desk in ordinary little consumer USB hubs, without cooling, and they seem to be OK (although very wam to the touch).

I re-aimed my big fan at this side of the USB hub, so it's blowing full blast on the fuse connector and ATX connector!  The wind also has the nice side effect of blowing across the Erupters as well, from this angle, helping them stay cool.  I recommend doing that, as you've seen, it's obviously most important to cool that area of the USB hub, with as much air as you can get blowing directly on that fuse.

And definitely a smoke detector in the room

Aye, you're right.  I have that in already, but only for pong.  Don't have it for ping.  Should be easy enough to add.

Josh

Strange!

I worked on a recent patch for Bitcoin that added ping time measurement (using ping/pong).  During development, I ran into some strange nodes out there that were doing something similar.

https://github.com/bitcoin/bitcoin/pull/2937#issuecomment-23457819

Here's the referenced IRC chat:

http://bitcoinstats.com/irc/bitcoin-dev/logs/2013/08/28#l1377673880

Many of these IP addresses match!!

Only thing is, this was for the *pong* message, not ping.  They were sending me pong messages of zero size.  I now check the size before doing any processing, and just throw it out if it's too small, to avoid the spam messages you get about the exception.  I don't remember ever getting any undersized *ping* messages from them.

I remember the version also, it was 0.8.99.  I think this just means you're running the latest Bitcoin from GitHub, compiled yourself, and thus not an official release?  Not sure about that, though.

Didn't think this had anything to do with p2pool, though.  Interesting.

Josh

Not sure if this text is still needed, but:

Krellan; 100; 3.5; 12JXrgup9NJdwp5rWqnqXJ57RN4hYHY8i6

Great!

Sent email with the shipping label PDF to the email address in your first post, just now.

Ordered 100 USB Erupters (should include 2 of the 49-port USB hubs).

OK, thanks.  Sorry I'm a little unclear on the new ordering process.  Ship date should be Monday, correct?

Thanks.  Will pay soon, getting 100.

Am I correct in that "Medium Priority Box" is the size to pick, for 100?  This includes room to fit the hubs also, right?

Nice!

Hoping you still have some in stock.  If still there, please reserve for me 70 USB Erupters, and 2 of those 49-port USB hubs.

I know that the USB hubs aren't free unless there's an even lot of 50 Erupters that are ordered at the same time to go with each.  With that in mind, what is the price on an individual USB hub?  Maybe I should just increase my order to 100 USB Erupters, to get 2 hubs?  Let me know which would be more cost effective, then I'll send in payment.

Thanks!