So I thought a bit of how the governments could try to break bitcoin:

- Make bitcoin specific hardware illegal while they build their own.
- Break SHA256.

Both of these suggest a modular hashing algo for FPGA fork would be good to have in preparation.

An Spartan 6 FPGA specific hard fork option might come in handy?

I would like to make an altcoin for all those FPGA's out there. = with a modular hashing algo.

Unfortunately I'm only versed in Java.

Another feature that I would like to highlight is blockchain delete of obsolete transactions to save disc space and be able to match Visa cards transaction rates in a P2P system.

Thank you SIR!

My understanding of BTC is now almost complete!

That the miner who solves the block can just bump your transaction to the next block if it's too cheap is so cool!

Let's cross our fingers that this fee model will hold as block revenues go down to 12.5 after the next drop...

I think the limit for fee-less transactions should be higher until the value of BTC rises, in order to keep the chain as small as possible until the chain purging is built into the Satoshi client.

BTW, one last question, so about that merkle-root chain cleanup thing, is it on it's way?

Yeah, I know I should have invested in bitcoins "all-in" (more FPGA's as buying bitcoins and hoarding outright is all greed and not supporting the ideology at all = just like any wallstreet coorporate drone), back when I bought my FPGA's in december 2011. Oh well, at least I'm not totally BTC-less. Also it feels strange to have a large amount of "wealth" in a small easily misplace/erase/forgetpassword-able file.

Edit: Actually I don't need anyone that gives a crap!

Ah, can somebody explain how transaction fees work? I understand you can add fees if you wan't the network to process the transaction with high priority right? So that means IF there was a shitload of transactions you would get ahead...

But it's always optional right?

Ok,

2 things strike me when visiting blockchain.info:

- How does blockchain.info track IP numbers? And why do they track IP numbers = really bad for anonymity!

- The block chain is getting spammed with tiny transactions of < 1 BTC by services like SatoshiDice etc. these are REALLY bad for the network, why don't they have internal accounting?!

So FPGA's are not that bad after all (If you only look on electricity consumption):

	W/GH
zTEX	40
Avalon	9
BFL	7

On purchase price they are aweful though:

	$/GH
zTEX	1450
Avalon	110
BFL	22

But if you look how many BTC they will give, I think buying FPGA's around christmas 2011 kicks all ASIC's in the butt!

Edit: Just need a timemachine and someone that gives a crap!

So this was expected, if they had 1GH/W we would have known already. But if they deliver 60GH in two singles that draw 60W each, that's ok! 2W per GH is still x20 better than 40W of my FPGA's! Alot better than Avalons x6!

If they need 3 singles to give 60GH at 60W that's still twice as good as Avalon.

Not to mention design, size and noise!

Now it's just a question of delivery dates, nobody will wait for fixed power electronics, but for us that ordered in 2013 we'll get those anyhow.

Good news all around! Now we're just waiting for proof (and maybe proof of delivery) until we release a shitstorm of orders...

Exactly! In an expanding world (resources and people) infinite value helps you exploit nature and grow population as fast as possible. But now finite is on the table, and decreasing population. Only gold and bitcoins work in that environment.

Ah, thx big time!

How about:

You ask for the password every time you generate new addresses (instead of pregenerating 100 without knowing AT ALL how many will be ever needed) and at that time say "we will ask you for your password to encrypt this/these address(es), this also means you have to backup your wallet.dat file IMMEDIATELY AFTER before ANY payment is made to the new address(es)".

BEFORE encryption occurs so the user can CHOOSE what to do with a NO/CANCEL button!!!

Also again, why didn't the old wallet work? If it should still work, it should still work. I'm a grownup and I know that if I don't delete my old unencrypted wallets and someone steals them from me I can only blame myself. I mean I'm the one pressing "encrypt", I know that means I'm encrypting.

The ONLY thing in the whole world that matters is that I don't loose my coins, ONLY in a far away second place comes the fear of someone stealing them!!!

So in retrospect wallets should NOT include any other information than I told the software to store there. IE private keys, no history, no pregenerated keys, no nothing else but the private keys I want to be there. PERIOD

Since the size of the wallet grows with each transaction now, noobs will think they need to rebackup after each transaction, that has to stop. So lets keep the transaction history somewhere else ok?

It's REALLY REALLY crucial to get this right for future user adoption since loosing your wallet is the only real "flaw" of BTC.

This is unacceptable user experience if you want anyone other but hardcore linux nerds to use BTC.

Ok, why does the client pregenerate addresses?

And still why does the dialogue say "your old wallet won't work anymore" if that's false?

Yes I would like to run a silent 20GH module outside any case on a fanless 150W PSU...

Ok, so old wallet should still work?!

But why does the warning window say: YOUR OLD WALLET WILL STOP TO WORK!!

And when I tried to use the old wallet it really didn't work... so probably the client stores some state as "locked" locally?

My god I hate software that treats users as morons and hides the real inner workings!

So I encrypted my wallet and I tried to remove the new wallet before starting the client again (since the client doesn't warn you BEFORE encrypting) and rollback to old wallet, but it was then empty.

So I got really scared! and then put the new encrypted back and that worked fine.

Just had to backup REALLY REALLY fast... since if something happened during those few seconds; poof all BTC gone = NOT COOL!!! hello devs get you heads out of your asses!!!

You need to make this process a 2 phase commit!!!

Ok, but what I wan't to know is HOW does the encryption disable the old wallet? If I install a new client on another computer and use the old unencrypted wallet will it work?

Hi, what would be needed to run a Avalon module standalone?

And can you underclock it so it can be passively cooled unsealed?

Don't saw me down at the ankles if I'm wrong but isn't this just proof of the difficulty/price coupling?

We know for sure that if the price goes down the difficulty goes down (GPU miners stop mining)...

What if the price is decided by the miners that only sell to a high price point to be able to continue mining?!

If this is true, ASIC's will lower stabilize the price once they kick out GPU's because the electricity bill will be lower for miners.

What do you say?

Edit: I think the rush is ASIC fueled = raising the price to what it needs to be in order for ASIC to be barely profitable keeping the mining going...

Basically making this a reward drop + ASIC effect

Moser.

Ok, FYI rolling updates is the solution; or tumbleweed for SuSE... the linux community has fixed the problem!

Too bad its only for 11.4 and above though... works great on my laptop! Incredible!

So when will ripple give away ripples? I mean when will the system be usable?

Then this sounds like more like a scam... so what happens when all billion XRP run out since thay are destroyed upon every transaction? Also how does giving free XRP prevent flooding the system with bogus 0.00000000000001XXX transactions?