Bitcoin Forum
June 23, 2021, 12:04:54 AM *
News: Latest Bitcoin Core release: 0.21.1 [Torrent]
  Home Help Search Login Register More  
  Show Posts
Pages: [1] 2 3 »
1  Bitcoin / Bitcoin Technical Support / Distributed Bitcoind on: May 13, 2016, 08:24:18 AM
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.
2  Bitcoin / Bitcoin Technical Support / Bitcoind 0.12 pruned locks file system on: April 06, 2016, 08:02:34 AM
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:

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:

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
3  Bitcoin / Development & Technical Discussion / Why LN when we have altcoins and exchanges? on: February 25, 2016, 10:29:43 PM
I'm just curious why you would want to peg the exchange rate?

To me the scaling solution of bitcoin is altcoins!
4  Other / New forum software / New Forum on: January 17, 2016, 11:57:49 PM
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
5  Bitcoin / Bitcoin Technical Support / Use blockchain of another bitcoind on: August 08, 2015, 11:30:00 PM
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?
6  Bitcoin / Development & Technical Discussion / lock and vout on: August 03, 2015, 07:46:23 AM
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?
7  Bitcoin / Development & Technical Discussion / Distributed bitcoind on: August 02, 2015, 11:21:38 AM
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.
8  Bitcoin / Development & Technical Discussion / Distibuted bitcoind on: July 16, 2015, 09:33:40 AM
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?
9  Bitcoin / Bitcoin Technical Support / Last official release with static build on: July 07, 2015, 05:18:44 PM
Where are all the old binary builds?
10  Bitcoin / Bitcoin Technical Support / Memory on: June 25, 2015, 06:12:52 PM

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?
11  Bitcoin / Bitcoin Discussion / Blockchain Rant on: April 03, 2015, 10:23:36 AM
The web is slowly saturating with these blockchain > bitcoin statements.

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!?
12  Bitcoin / Development & Technical Discussion / Changelog for bitcoind? on: March 19, 2015, 05:47:46 PM
Where can I find it?
13  Bitcoin / Development & Technical Discussion / public/private key on: February 09, 2015, 09:24:00 PM
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...
14  Other / Off-topic / Raspberry Pi 2 on: February 02, 2015, 03:23:28 PM
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.
15  Local / Skandinavisk / Bitcoin Pool on: January 23, 2015, 06:45:07 PM
Finns det nagon stabil pool haromkring? Typ i Sverige...
16  Bitcoin / Hardware / Power Supply and ASIC socket standard on: January 03, 2015, 06:37:18 PM
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?
17  Bitcoin / Development & Technical Discussion / Child key derivation function on: November 11, 2014, 05:45:52 PM
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. Undecided

* If it collides I need to be able to just generate another.
18  Economy / Service Discussion / New BTC only payment provider on: May 10, 2014, 08:26:21 PM
I just added a payment solution to my GWT Wallet:

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.
19  Bitcoin / Development & Technical Discussion / longpoll listtransactions on: May 02, 2014, 01:33:30 PM
When will we get realtime transaction support in the rpc api for the official bitcoind?
20  Economy / Computer hardware / [WTB] zTex 1.15x on: February 19, 2014, 08:24:57 PM
Only zTex original, bare (no heatsinks, cables or power); the more, the better.
Pages: [1] 2 3 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!