Pages:
Author

Topic: Do run a Bitcoin Core FULL NODE Now! - page 4. (Read 8524 times)

member
Activity: 154
Merit: 11
November 04, 2017, 12:15:22 PM
  Greetings to all good will people!

   Now, when the bunch of deceitful,  greedy,  incompetent,  irresponsible idiots from B2X (sorry for some harshness) are really endangering the Bitcoin,
 

2- Youe are talking about yoursel.

3. Shut the fuck up!

I think I am talking about YOU including.

You must be one of those 2x supporters.

2mb blocks might be discussed (though now, after the Segwit activation they are even more disputable), but they must NOT be forcefully imposed!!

sr. member
Activity: 1518
Merit: 264
November 04, 2017, 12:00:58 PM
  Greetings to all good will people!

   Now, when the bunch of deceitful,  greedy,  incompetent,  irresponsible idiots from B2X (sorry for some harshness) are really endangering the Bitcoin,
  
 

1. It is me calling.

2. You are talking about yourself.

3. Shut the fuck up!

4. Or is shall call Hitler!

Beavis and Butthead Prank Call Hitler
https://www.youtube.com/watch?v=t9laOl7cqR4
member
Activity: 154
Merit: 11
November 04, 2017, 11:56:56 AM
The method of a double computer setup is achieved by dumping the raw transaction data on the offline computer, then passing it on (with an USB stick for example) in the online computer where your node is.

This can't be done with the GUI afaik, so you would need to use the command console, so this has added risk, and you still are at risk that the text file containing your raw transaction gets compromised somehow during the process of relaying it in the network.

I have never used this method so you would need to ask someone that does for the details, but I think an encrypted Linux partition with a node used as a wallet is safe enough in most cases.
It seems,  there was a topic discussing this issue:

https://bitcointalksearch.org/topic/cold-signing-a-transaction-using-bitcoin-qt-651344
legendary
Activity: 1372
Merit: 1252
November 04, 2017, 11:47:09 AM
The method of a double computer setup is achieved by dumping the raw transaction data on the offline computer, then passing it on (with an USB stick for example) in the online computer where your node is.

This can't be done with the GUI afaik, so you would need to use the command console, so this has added risk, and you still are at risk that the text file containing your raw transaction gets compromised somehow during the process of relaying it in the network.

I have never used this method so you would need to ask someone that does for the details, but I think an encrypted Linux partition with a node used as a wallet is safe enough in most cases.
hero member
Activity: 672
Merit: 503
November 04, 2017, 11:28:48 AM
..... is there a way to create a "symbiosis" of the Electrum wallet and Bitcoin Core (or something like that), so that to sign transactions safely on ANY(doesn't matter which Linux distro, or even Windows) ALWAYS offline system, and afterwards actually broadcasting it with one's own Bitcoin Core full node.

Before I started my full node I had been doing it easily, comfortably and safely with the Electrum wallet.

All this reduces to is generating transactions off line and then inputting them into a computer with a wallet such as Bitcoin Core.

Hooking Electrum into one end and hooking "full node" into the other is two levels of specificity without any tangible benefit.

Spendulus, I've noticed if I say the Earth is round, you will say that is not quite true. You are always looking to find faults in my words Grin

The greatest benefit with the Electrum scheme is that the online system's wallet is "watch-only". The real wallet that can spend money never goes online.



The idea is to have a full bitcoin node installed in a decent system like a linux partition that you don't use for much other than to have the full node so you lower the surface attack (and not use Electrum because it's not ideal, some consider HD wallets unsafe).

Then, you would have something that's completely sealed like an airgapped laptop, and you would do the actual signature there, then you save this information in an USB or something and then relay it into the network with your full node.

The problem is I dont really know how this method works. How do you make the offline transaction, then pass it on the full node linux partition safely?

The way to lower attacks would be to have the "full node" NOT online all the time as a full node, which in and of itself invites attacks. Open ports and all that.

As for the offline machine, those methods are well documented at least for legacy Bitcoin.

But why not use a Trezor or other such hardware device? Certainly they qualify as very low hassle, high security and "off line."

I don't really trust Trezor, they keep adding unnecessary cluter specially with the new Trezor T which raises surface of attack.

I also don't trust the concept of "seeds" in general, or anything that could spawn all of your private keys thought a single passphrase.

Can't you sign transactions offline with the Bitcoin Core wallet in an airgapped computer, then move this into another computer with another Bitcoin Core and relay it to the network?

But maybe this is unnecessary and considering im not going to be running the Bitcoin Core wallet as a node 24/7 and only boot the Linux partition when I need to transact or create a new receiving address... I should be safe.

I would need to encrypt the Linux partition tho, otherwise when I boot in Windows the wallet files could be accessible if my Windows partition gets hacked.
So you don't trust the seeds or word list, but Electrum uses them. As does Trevor. Core has the HD flag today, but doesn't seem to have deterministic stuff implemented.

This explains the overall theory. There's a link at the bottom on how to do it with Electrum.

https://en.bitcoin.it/wiki/How_to_set_up_a_secure_offline_savings_wallet

Yes, that's right, I don't trust Trezor, and I certainly don't trust an SPV wallet no matter if it's called Electrum or anything else.

The HD wallet on Core cannot be generated through a seed, but since I don't know the details, I choose to stay under the old non HD format for now.
member
Activity: 154
Merit: 11
November 04, 2017, 06:09:01 AM
Is there a geographical map of where nodes are? I have a 300/300mbps connection - and a Ubuntu installation. Is running a node hard on the disk? Is 500GB disk sufficient? Sound like it. Can I install the node software and let it rebuild of the blockchain?
Now I'm up and running Bitcoin Core on my Ubuntu :-)

You're welcome :-)

Excellent, very good!

And you are welcome to the family of smart and responsible fans of the best crypto currency and currency in general - the Bitcoin!


jr. member
Activity: 57
Merit: 1
November 03, 2017, 07:12:59 PM
Is there a geographical map of where nodes are? I have a 300/300mbps connection - and a Ubuntu installation. Is running a node hard on the disk? Is 500GB disk sufficient? Sound like it. Can I install the node software and let it rebuild of the blockchain?
Now I'm up and running Bitcoin Core on my Ubuntu :-)

You're welcome :-)
staff
Activity: 3458
Merit: 6793
Just writing some code
November 03, 2017, 05:42:43 PM
Core has the HD flag today, but doesn't seem to have deterministic stuff implemented.
HD literally means Hierarchical Deterministc. Bitcoin Core allows you to make an HD wallet, so it is deterministic. What Bitcoin Core does not have is the mnemonic or seed phrase. That is completely unrelated to HD wallets; it is a totally separate BIP and not required to have an HD wallet.
legendary
Activity: 2912
Merit: 1386
November 03, 2017, 04:16:54 PM
..... is there a way to create a "symbiosis" of the Electrum wallet and Bitcoin Core (or something like that), so that to sign transactions safely on ANY(doesn't matter which Linux distro, or even Windows) ALWAYS offline system, and afterwards actually broadcasting it with one's own Bitcoin Core full node.

Before I started my full node I had been doing it easily, comfortably and safely with the Electrum wallet.

All this reduces to is generating transactions off line and then inputting them into a computer with a wallet such as Bitcoin Core.

Hooking Electrum into one end and hooking "full node" into the other is two levels of specificity without any tangible benefit.

Spendulus, I've noticed if I say the Earth is round, you will say that is not quite true. You are always looking to find faults in my words Grin

The greatest benefit with the Electrum scheme is that the online system's wallet is "watch-only". The real wallet that can spend money never goes online.



The idea is to have a full bitcoin node installed in a decent system like a linux partition that you don't use for much other than to have the full node so you lower the surface attack (and not use Electrum because it's not ideal, some consider HD wallets unsafe).

Then, you would have something that's completely sealed like an airgapped laptop, and you would do the actual signature there, then you save this information in an USB or something and then relay it into the network with your full node.

The problem is I dont really know how this method works. How do you make the offline transaction, then pass it on the full node linux partition safely?

The way to lower attacks would be to have the "full node" NOT online all the time as a full node, which in and of itself invites attacks. Open ports and all that.

As for the offline machine, those methods are well documented at least for legacy Bitcoin.

But why not use a Trezor or other such hardware device? Certainly they qualify as very low hassle, high security and "off line."

I don't really trust Trezor, they keep adding unnecessary cluter specially with the new Trezor T which raises surface of attack.

I also don't trust the concept of "seeds" in general, or anything that could spawn all of your private keys thought a single passphrase.

Can't you sign transactions offline with the Bitcoin Core wallet in an airgapped computer, then move this into another computer with another Bitcoin Core and relay it to the network?

But maybe this is unnecessary and considering im not going to be running the Bitcoin Core wallet as a node 24/7 and only boot the Linux partition when I need to transact or create a new receiving address... I should be safe.

I would need to encrypt the Linux partition tho, otherwise when I boot in Windows the wallet files could be accessible if my Windows partition gets hacked.
So you don't trust the seeds or word list, but Electrum uses them. As does Trevor. Core has the HD flag today, but doesn't seem to have deterministic stuff implemented.

This explains the overall theory. There's a link at the bottom on how to do it with Electrum.

https://en.bitcoin.it/wiki/How_to_set_up_a_secure_offline_savings_wallet
hero member
Activity: 672
Merit: 503
November 03, 2017, 03:23:18 PM
..... is there a way to create a "symbiosis" of the Electrum wallet and Bitcoin Core (or something like that), so that to sign transactions safely on ANY(doesn't matter which Linux distro, or even Windows) ALWAYS offline system, and afterwards actually broadcasting it with one's own Bitcoin Core full node.

Before I started my full node I had been doing it easily, comfortably and safely with the Electrum wallet.

All this reduces to is generating transactions off line and then inputting them into a computer with a wallet such as Bitcoin Core.

Hooking Electrum into one end and hooking "full node" into the other is two levels of specificity without any tangible benefit.

Spendulus, I've noticed if I say the Earth is round, you will say that is not quite true. You are always looking to find faults in my words Grin

The greatest benefit with the Electrum scheme is that the online system's wallet is "watch-only". The real wallet that can spend money never goes online.



The idea is to have a full bitcoin node installed in a decent system like a linux partition that you don't use for much other than to have the full node so you lower the surface attack (and not use Electrum because it's not ideal, some consider HD wallets unsafe).

Then, you would have something that's completely sealed like an airgapped laptop, and you would do the actual signature there, then you save this information in an USB or something and then relay it into the network with your full node.

The problem is I dont really know how this method works. How do you make the offline transaction, then pass it on the full node linux partition safely?

The way to lower attacks would be to have the "full node" NOT online all the time as a full node, which in and of itself invites attacks. Open ports and all that.

As for the offline machine, those methods are well documented at least for legacy Bitcoin.

But why not use a Trezor or other such hardware device? Certainly they qualify as very low hassle, high security and "off line."

I don't really trust Trezor, they keep adding unnecessary cluter specially with the new Trezor T which raises surface of attack.

I also don't trust the concept of "seeds" in general, or anything that could spawn all of your private keys thought a single passphrase.

Can't you sign transactions offline with the Bitcoin Core wallet in an airgapped computer, then move this into another computer with another Bitcoin Core and relay it to the network?

But maybe this is unnecessary and considering im not going to be running the Bitcoin Core wallet as a node 24/7 and only boot the Linux partition when I need to transact or create a new receiving address... I should be safe.

I would need to encrypt the Linux partition tho, otherwise when I boot in Windows the wallet files could be accessible if my Windows partition gets hacked.
member
Activity: 154
Merit: 11
November 03, 2017, 03:12:43 PM

The way to lower attacks would be to have the "full node" NOT online all the time as a full node, which in and of itself invites attacks. Open ports and all that.

As for the offline machine, those methods are well documented at least for legacy Bitcoin.

But why not use a Trezor or other such hardware device? Certainly they qualify as very low hassle, high security and "off line."

Electrum offline (cold storage) scheme is easy, reliable, simple and free!
Personally, I live in the poor, miserable, totalitarian country of Belarus, it is pretty expensive for me to buy any hardware, given the very high customs duties including.

Besides, it's turned out trezors may be very weak and vulnerable as well, the famous history here:
https://www.wired.com/story/i-forgot-my-pin-an-epic-tale-of-losing-dollar30000-in-bitcoin

legendary
Activity: 2912
Merit: 1386
November 03, 2017, 02:09:27 PM
..... is there a way to create a "symbiosis" of the Electrum wallet and Bitcoin Core (or something like that), so that to sign transactions safely on ANY(doesn't matter which Linux distro, or even Windows) ALWAYS offline system, and afterwards actually broadcasting it with one's own Bitcoin Core full node.

Before I started my full node I had been doing it easily, comfortably and safely with the Electrum wallet.

All this reduces to is generating transactions off line and then inputting them into a computer with a wallet such as Bitcoin Core.

Hooking Electrum into one end and hooking "full node" into the other is two levels of specificity without any tangible benefit.

Spendulus, I've noticed if I say the Earth is round, you will say that is not quite true. You are always looking to find faults in my words Grin

The greatest benefit with the Electrum scheme is that the online system's wallet is "watch-only". The real wallet that can spend money never goes online.



The idea is to have a full bitcoin node installed in a decent system like a linux partition that you don't use for much other than to have the full node so you lower the surface attack (and not use Electrum because it's not ideal, some consider HD wallets unsafe).

Then, you would have something that's completely sealed like an airgapped laptop, and you would do the actual signature there, then you save this information in an USB or something and then relay it into the network with your full node.

The problem is I dont really know how this method works. How do you make the offline transaction, then pass it on the full node linux partition safely?

The way to lower attacks would be to have the "full node" NOT online all the time as a full node, which in and of itself invites attacks. Open ports and all that.

As for the offline machine, those methods are well documented at least for legacy Bitcoin.

But why not use a Trezor or other such hardware device? Certainly they qualify as very low hassle, high security and "off line."
member
Activity: 154
Merit: 11
November 03, 2017, 02:06:45 PM

The idea is to have a full bitcoin node installed in a decent system like a linux partition that you don't use for much other than to have the full node so you lower the surface attack (and not use Electrum because it's not ideal, some consider HD wallets unsafe).

Then, you would have something that's completely sealed like an airgapped laptop, and you would do the actual signature there, then you save this information in an USB or something and then relay it into the network with your full node.

The problem is I dont really know how this method works. How do you make the offline transaction, then pass it on the full node linux partition safely?

Neurotypical,  I'm very busy right now, maybe look through this topic:

https://bitcointalksearch.org/topic/cold-signing-a-transaction-using-bitcoin-qt-651344

hero member
Activity: 672
Merit: 503
November 03, 2017, 11:54:32 AM
..... is there a way to create a "symbiosis" of the Electrum wallet and Bitcoin Core (or something like that), so that to sign transactions safely on ANY(doesn't matter which Linux distro, or even Windows) ALWAYS offline system, and afterwards actually broadcasting it with one's own Bitcoin Core full node.

Before I started my full node I had been doing it easily, comfortably and safely with the Electrum wallet.

All this reduces to is generating transactions off line and then inputting them into a computer with a wallet such as Bitcoin Core.

Hooking Electrum into one end and hooking "full node" into the other is two levels of specificity without any tangible benefit.

Spendulus, I've noticed if I say the Earth is round, you will say that is not quite true. You are always looking to find faults in my words Grin

The greatest benefit with the Electrum scheme is that the online system's wallet is "watch-only". The real wallet that can spend money never goes online.



The idea is to have a full bitcoin node installed in a decent system like a linux partition that you don't use for much other than to have the full node so you lower the surface attack (and not use Electrum because it's not ideal, some consider HD wallets unsafe).

Then, you would have something that's completely sealed like an airgapped laptop, and you would do the actual signature there, then you save this information in an USB or something and then relay it into the network with your full node.

The problem is I dont really know how this method works. How do you make the offline transaction, then pass it on the full node linux partition safely?
member
Activity: 154
Merit: 11
November 03, 2017, 11:14:04 AM
..... is there a way to create a "symbiosis" of the Electrum wallet and Bitcoin Core (or something like that), so that to sign transactions safely on ANY(doesn't matter which Linux distro, or even Windows) ALWAYS offline system, and afterwards actually broadcasting it with one's own Bitcoin Core full node.

Before I started my full node I had been doing it easily, comfortably and safely with the Electrum wallet.

All this reduces to is generating transactions off line and then inputting them into a computer with a wallet such as Bitcoin Core.

Hooking Electrum into one end and hooking "full node" into the other is two levels of specificity without any tangible benefit.

Spendulus, I've noticed if I say the Earth is round, you will say that is not quite true. You are always looking to find faults in my words Grin

The greatest benefit with the Electrum scheme is that the online system's wallet is "watch-only". The real wallet that can spend money never goes online.
legendary
Activity: 2912
Merit: 1386
November 03, 2017, 10:53:39 AM
..... is there a way to create a "symbiosis" of the Electrum wallet and Bitcoin Core (or something like that), so that to sign transactions safely on ANY(doesn't matter which Linux distro, or even Windows) ALWAYS offline system, and afterwards actually broadcasting it with one's own Bitcoin Core full node.

Before I started my full node I had been doing it easily, comfortably and safely with the Electrum wallet.



All this reduces to is generating transactions off line and then inputting them into a computer with a wallet such as Bitcoin Core.

Hooking Electrum into one end and hooking "full node" into the other is two levels of specificity without any tangible benefit.
member
Activity: 154
Merit: 11
November 03, 2017, 02:20:37 AM
I run an ESXi host as my IT training lab. I decided to run a Bitcoin full node to support the community. It will be a Linux server (no gui) virtual machine. Can you please advise what Linux distro is better and where I can find install/configure/sync the blockchain instructions?
I'd start from
https://bitcoin.org/en/full-node

I really wish I could do it on a cheap VPS, but with the 145GB blockchain and growing... the only cheap option is a rasp Pi with Harddisk?
Besides that I wonder how much up/downstream traffic does it generate (only have a 20/2 Mbit) line.
Almost all necessary info may be found here
https://bitcoin.org/en/full-node/

... very nice, the main page misses some crucial Information like how much space is needed.
i always wanted to Store my copy of the btc blockchain inside the sia chain and Keep it updated.
but ive been very busy in real life. still Hardware is the best way to Keep it safe.
The extrated archive will occupy about 160Gb
I am going to try to upload the whole blockchain to my Google drive
Of course you can do, just note I have already uploaded one as of October, 24th
newbie
Activity: 56
Merit: 0
November 02, 2017, 07:42:58 PM
I am going to try to upload the whole blockchain to my Google drive
sr. member
Activity: 546
Merit: 254
ʕʘ̅͜ʘ̅ʔ
November 02, 2017, 06:02:36 PM
Hello everyone)

As I promised, I have uploaded the whole Bitcoin Core blockchain database (0.15.0.1 version format packed into 12x10Gb 7-zip multivolume archive) as of October, 24th, 2017.

The 1-9 parts of the archive are here:
https://drive.google.com/open?id=0B1hDozqK5OhbYy1BNTFsRHE5S0U

The 10th part is here:
https://drive.google.com/open?id=0Bwp9hqEINfq7emI0TE9HSWUzT3c

And the 11-12th parts are here:
https://drive.google.com/open?id=0B04jj__m9bS6djlfc1F4RjM2RlE

I have tested the archive, so you may download safely.

To extract the Bitcoin Core blockchain database from the archive you should use any archive manager that supports 7z archives, the genuine 7z archive manager may be downloaded from here:
http://www.7-zip.org

After downloading all 12 parts launch the 7-zip manager, extract everything anywhere into your hard drive (where you are going to keep the blockchain, there must be at least 200Gb free space there).

Then launch Bitcoin Core 0.15.0.1 application, on request for the database folder point to the extracted folder.
The Core will (pretty fast) check integrity of the database, then it will start syncing the blockchain to its current state (it will start downloading and verifying blocks since October, 24th).

If you had already have your real Bitcoin  wallet before, just add into the root of the extracted folder your own 'wallet.dat' file.

If you have any questions you are welcome to ask them



very nice, the main page misses some crucial Information like how much space is needed.
i always wanted to Store my copy of the btc blockchain inside the sia chain and Keep it updated.
but ive been very busy in real life. still Hardware is the best way to Keep it safe.
sr. member
Activity: 325
Merit: 250
November 02, 2017, 05:51:07 PM
I really wish I could do it on a cheap VPS, but with the 145GB blockchain and growing... the only cheap option is a rasp Pi with Harddisk?
Besides that I wonder how much up/downstream traffic does it generate (only have a 20/2 Mbit) line.
Pages:
Jump to: