So I came up with this sort of distributed bitcoind, I have 2 bitcoind and I simply ask the other one to create the private key and send it (encrypted) to the first one which imports it.

But, I can't create "off chain" transactions this way. Does anyone have an idea of how you could do that with two bitcoind instances?

The only solution I have so far is to create the internal transaction system myself but I think it will lead to bugs and security problems.

I'm trying to run bitcoind pruned, the blockchain sync worked fine, and also once the sync was done bitcoind was running smoothly.

But then after a reboot, when I start bitcoind it boots up ok and does it's thing verifying some stuff but then it blocks 3 cores at 100% io-wait and the disk is frozen (if I try to cat any file bitcoind is holding the cat process freezes) and I can't kill bitcoind?!

Is anyone actually using pruned?

How should pruned be used? What is prune=<n>? MB of what, how, where?

I'm trying to reindex and run unpruned to see if pruned is the problem. Just have to wait 4 days!

So bitcoind goes from taking 3 cores to 100% io-wait and locking these files:

Code:

COMMAND           PID  TYPE SIZE MODE  M START END PATH
cron              653 FLOCK   0B WRITE 0     0   0 /run
whoopsie          640 FLOCK   0B WRITE 0     0   0 /run/lock
master            864 FLOCK   0B WRITE 0     0   0 /
master            864 FLOCK   0B WRITE 0     0   0 /
bitcoind         2014 POSIX   0B WRITE 0     0   0 /mnt/ssd/bitcoin/.lock
bitcoind         2014 POSIX   0B WRITE 0     0   0 /mnt/ssd/bitcoin/blocks/index/LOCK
bitcoind         2014 POSIX   0B WRITE 0     0   0 /mnt/ssd/bitcoin/chainstate/LOCK

to having only 1-2 cores 100% io-wait and locking this when I try kill -9:

Code:

COMMAND           PID  TYPE SIZE MODE  M START END PATH
cron              653 FLOCK   0B WRITE 0     0   0 /run
whoopsie          640 FLOCK   0B WRITE 0     0   0 /run/lock
master            864 FLOCK   0B WRITE 0     0   0 /
master            864 FLOCK   0B WRITE 0     0   0 /
bitcoind         2014 POSIX   0B WRITE 0     0   0 /mnt/ssd
bitcoind         2014 POSIX   0B WRITE 0     0   0 /mnt/ssd
bitcoind         2014 POSIX   0B WRITE 0     0   0 /mnt/ssd

I'm just curious why you would want to peg the exchange rate?

To me the scaling solution of bitcoin is altcoins!

I remember way back there was some plan to build a new forum, obviously that never happened.

Is it still interesting to the owners of bitcointalk.org?

I'm now running 3 nodes. But I only need 1 blockchain. Is there a way to point 2 of my bitcoind's to the third and only have that one download the blockchain?

Does lockunspent require vout?

Do all transactions have vout?

How can I see vout?

Is 0 the default vout?

What is vout?

In the documentation is says: (numeric) The output number -- eh, ok?

Is there some way to track unspent and notify transactions + confirmations on a public address without private key in a secure way preferably in bitcoind?

With raw transactions I can store the private keys outside of the wallet but I still need unspent tracking to be able to create the raw transaction and notifications both on transaction propagation and confirms in order for the raw API to make any sense.

Are those planned?

Edit: it seems to me the "wallet" should only contain the private keys, and some other databases (call them track and notify) should store that data.

Can you today use bitcoind with the private keys outside of the wallet without development complexity?

The only way to assure 100% uptime is to distribute your cluster and for that you need to handle private key distribution outside of the closed wallet.dat file.

What would the way to do this with the raw transactions API look like?

Where are all the old binary builds?

My fullnode was killing processes left and right for the past week until I noticed bitcoind was gobbing all 4GB... uptime was maybe 6 months.

For SSD setup's with no swap; what can be done to sustain bitcoind longer in terms of memory usage?

The web is slowly saturating with these blockchain > bitcoin statements.

https://www.youtube.com/watch?v=43e6eAAeGCs
http://www.forbes.com/sites/steveforbes/2015/04/02/how-bitcoin-will-end-world-poverty/
etc.

I would argue that the blockchain tech is really poor at doing anything else than virtual liquid functions.

The reason is simple, you don't want to put something physical and/or monolithic (like your house) in a system where; if you get hacked or loose your private key, you loose the physical goods!?

Where can I find it?

How does a private key prove it owns the private key for a public key?

Pseudocode or simple real code... I just can't seem to google it...

Got 2 predictions:

1) ARM will completely take over on servers.
2) Personal cluster hosting is happening.

Network SSD drives, hardware and power costs and last but not least development costs; it all comes together!

Time to buy a good switch.

Finns det nagon stabil pool haromkring? Typ i Sverige...

Why don't the bitcoin hardware manufacturers build custom power supplies and ASIC processor socket?

Wouldn't a standard here reduce waste from every line of new processors?

Is there any way to generate keys from a key in such a way that you can proove that the first key owns the "child" keys?

String child = generateChild("xPNmJTt8WEGufQyg");

//Where child is a potentially* unique secure pseudo random key.

boolean valid = validChild("xPNmJTt8WEGufQyg", child);

//Where valid == true...

Edit: I could solve this with a simple unique "primary key" hash:

String primary = "email | username | userid";

String child = SHA(primary + "xPNmJTt8WEGufQyg");

boolean valid = child.equals(SHA(primary + "xPNmJTt8WEGufQyg"));

Actually no I can't as the keys might collide and I need random uniqueness.

* If it collides I need to be able to just generate another.

I just added a payment solution to my GWT Wallet:

https://bitcointalk.org/index.php?topic=229355.msg6551494#msg6551494

It's in alpha, but it's free and has no transaction fees (except bitcoin built in ones).

Let me know if you have any trouble using it.

When will we get realtime transaction support in the rpc api for the official bitcoind?

Only zTex original, bare (no heatsinks, cables or power); the more, the better.