Pages:
Author

Topic: Do run a Bitcoin Core FULL NODE Now! (Read 8557 times)

jr. member
Activity: 53
Merit: 7
July 03, 2018, 01:47:57 AM

with a rasberrypi you have to run a pruned node, or connect an hard disk via usb2(there is no usb3)
with a bananapi you have a sata port so you can connect the hard disk directly. So with a bananapi you can run a full not pruned node. Everything else is almost equal.

I don't like pruned node because, if for some reason I have to perform a rescan I have to download the entire blockchain another time.

Also Im not sure if pruned node relays blocks.


Why would you need to run a pruned node with raspberry pi? just run a regular node. Also, pruned nodes only relay latest blocks received, but not the whole blockchain.
because the sd card is too little, I don't know if an sdcard is able to store 150gb of data. usb is very unreliable and you end up with a corrupted blockchain.

OK, now I understand your concerns. There are many sd cards with a capacity over 150 GB, it will costs just about 100€ and then you can run your full node on a raspberry.

Thanks again, I will use mine for it.
jr. member
Activity: 43
Merit: 7
July 03, 2018, 12:58:31 AM

with a rasberrypi you have to run a pruned node, or connect an hard disk via usb2(there is no usb3)
with a bananapi you have a sata port so you can connect the hard disk directly. So with a bananapi you can run a full not pruned node. Everything else is almost equal.

I don't like pruned node because, if for some reason I have to perform a rescan I have to download the entire blockchain another time.

Also Im not sure if pruned node relays blocks.


Why would you need to run a pruned node with raspberry pi? just run a regular node. Also, pruned nodes only relay latest blocks received, but not the whole blockchain.
because the sd card is too little, I don't know if an sdcard is able to store 150gb of data. usb is very unreliable and you end up with a corrupted blockchain.
jr. member
Activity: 98
Merit: 5
July 02, 2018, 08:42:34 PM

with a rasberrypi you have to run a pruned node, or connect an hard disk via usb2(there is no usb3)
with a bananapi you have a sata port so you can connect the hard disk directly. So with a bananapi you can run a full not pruned node. Everything else is almost equal.

I don't like pruned node because, if for some reason I have to perform a rescan I have to download the entire blockchain another time.

Also Im not sure if pruned node relays blocks.


Why would you need to run a pruned node with raspberry pi? just run a regular node. Also, pruned nodes only relay latest blocks received, but not the whole blockchain.
jr. member
Activity: 43
Merit: 7
July 02, 2018, 12:14:30 PM
pruned nodes sucks, you should buy a bananapi with sata port.

I don't understand your point. The performance of the raspberry and banana are similar and I don't think the disk speed will make much difference (except for the initial sync).
It was not about performances, I don't like pruned nodes, it is only a personal opinion.
better pruned nodes than no nodes at all.

I still don't know what you mean. Why would it be a pruned node? Who would notice a difference?

What's your definition of a pruned node?

with a rasberrypi you have to run a pruned node, or connect an hard disk via usb2(there is no usb3)
with a bananapi you have a sata port so you can connect the hard disk directly. So with a bananapi you can run a full not pruned node. Everything else is almost equal.

I don't like pruned node because, if for some reason I have to perform a rescan I have to download the entire blockchain another time.

Also Im not sure if pruned node relays blocks.

Moreover: Eclair needs a synchronized, segwit-ready, zeromq-enabled, wallet-enabled, non-pruning, tx-indexing Bitcoin Core node. Eclair will use any BTC it finds in the Bitcoin Core wallet to fund any channels you choose to open. Eclair will return BTC from closed channels to this wallet.
https://github.com/ACINQ/eclair/blob/master/README.md

or

c-lightning currently only works on Linux (and possibly Mac OS with some tweaking), and requires a locally running bitcoind (version 0.15 or above) that is fully caught up with the network you're testing on. Pruning (prune=n option in bitcoin.conf) is not currently supported.
https://github.com/ElementsProject/lightning/blob/master/README.md

or

You must to be running a non-pruning bitcoin daemon with:

txindex=1
set in its configuration file. If you have an existing installation of bitcoind and have not previously set this you will need to reindex the blockchain with:

bitcoind -reindex
which can take some time
https://electrumx.readthedocs.io/en/latest/HOWTO.html#prerequisites

but of course those are special usecase.

As I was saying pruned nodes are good, but non pruned ar better.
jr. member
Activity: 53
Merit: 7
July 02, 2018, 05:22:06 AM
pruned nodes sucks, you should buy a bananapi with sata port.

I don't understand your point. The performance of the raspberry and banana are similar and I don't think the disk speed will make much difference (except for the initial sync).
It was not about performances, I don't like pruned nodes, it is only a personal opinion.
better pruned nodes than no nodes at all.

I still don't know what you mean. Why would it be a pruned node? Who would notice a difference?

What's your definition of a pruned node?
jr. member
Activity: 43
Merit: 7
June 28, 2018, 08:35:45 PM
pruned nodes sucks, you should buy a bananapi with sata port.

I don't understand your point. The performance of the raspberry and banana are similar and I don't think the disk speed will make much difference (except for the initial sync).
It was not about performances, I don't like pruned nodes, it is only a personal opinion.
better pruned nodes than no nodes at all.
jr. member
Activity: 53
Merit: 7
June 28, 2018, 01:29:45 AM
pruned nodes sucks, you should buy a bananapi with sata port.

I don't understand your point. The performance of the raspberry and banana are similar and I don't think the disk speed will make much difference (except for the initial sync).

It is bettere to use a pc for initial sync, and move your copy of the blockchain on the bananapi later.
Initial synchronization on a raspberrypi will take some years.

Good suggestion, thank you.
jr. member
Activity: 43
Merit: 7
June 27, 2018, 09:15:16 AM

This are good reasons to run a full node, but are there any security concerns when running a full node? I can think of one issue, your IP would be visible to the network and therefore you are maybe a target of an attack. Is this a reasonable concern or am I too careful? Are there other concerns?

start your daemon using:
onlynet=onion
bind=127.0.0.1
listenonion=0


Thank you! I didn't know that the bitcoin core wallet supports to run over tor without much configuration.
https://en.bitcoin.it/wiki/Setting_up_a_Tor_hidden_service

Any other concers? Otherwise I will setup a full node on my raspberry  Smiley
pruned nodes sucks, you should buy a bananapi with sata port.
It is bettere to use a pc for initial sync, and move your copy of the blockchain on the bananapi later.
Initial synchronization on a raspberrypi will take some years.
jr. member
Activity: 53
Merit: 7
June 27, 2018, 08:26:03 AM

This are good reasons to run a full node, but are there any security concerns when running a full node? I can think of one issue, your IP would be visible to the network and therefore you are maybe a target of an attack. Is this a reasonable concern or am I too careful? Are there other concerns?

start your daemon using:
onlynet=onion
bind=127.0.0.1
listenonion=0


Thank you! I didn't know that the bitcoin core wallet supports to run over tor without much configuration.
https://en.bitcoin.it/wiki/Setting_up_a_Tor_hidden_service

Any other concers? Otherwise I will setup a full node on my raspberry  Smiley
jr. member
Activity: 43
Merit: 7
June 27, 2018, 07:45:34 AM

This are good reasons to run a full node, but are there any security concerns when running a full node? I can think of one issue, your IP would be visible to the network and therefore you are maybe a target of an attack. Is this a reasonable concern or am I too careful? Are there other concerns?

start your daemon using:
onlynet=onion
bind=127.0.0.1
listenonion=0
jr. member
Activity: 53
Merit: 7
June 27, 2018, 06:11:28 AM
Yes I agree I think it is unning a Bitcoin full node isn’t just for mining pools and companies. Today, we’re going to outline 6 reasons why the average user should also consider running their own Bitcoin full node. There is a list of 6 reasons to run a Bitcoin Full Node.
1)   Helps the Network
Running your own full node is the only way to have full control and to ensure that all the rules of Bitcoin are being followed. Nodes do this by rejecting blocks and transactions that don’t follow the consensus rules and by rejecting connections from peers that send them (or too many of them).
2)   Keeps you safe
Running any kind of Bitcoin wallet that does not require you to run a full node means that you have to place a certain degree of trust in the service provider, something that shouldn’t be necessary with Bitcoin.
3)   Allows you to choose
In the possible event of a hard fork where both blockchains remain active with economic activity on each side like the one in Ethereum/Ethereum Classic, running a full node is the only way you can validate the rules of the new or old blockchain, according to your preference. If you don’t run a full node, your opinion will not be considered and you will simply follow the blockchain that is given to you.
4)   Gives you a higher degree of privacy
Using a centralized, lightweight or even SPV wallet will never be as private as running a full node. Since you rely on third-party servers to broadcast your transactions for you, those servers will be aware of which addresses belong to you.
5)   It’s not that hard
To less than tech-savvy users, running a full node may seem like a challenge. However, running a Bitcoin core full node is nothing more than simply downloading the latest Bitcoin core client version and running it.
6)   It’s not that expensive
Running a node will require you to keep your computer on at all times – or at least for the majority of the day. While you can always turn your node on and off at will with this option, it is not a very practical one. Thank you.


This are good reasons to run a full node, but are there any security concerns when running a full node? I can think of one issue, your IP would be visible to the network and therefore you are maybe a target of an attack. Is this a reasonable concern or am I too careful? Are there other concerns?
newbie
Activity: 168
Merit: 0
June 26, 2018, 08:37:21 AM
Yes I agree I think it is unning a Bitcoin full node isn’t just for mining pools and companies. Today, we’re going to outline 6 reasons why the average user should also consider running their own Bitcoin full node. There is a list of 6 reasons to run a Bitcoin Full Node.
1)   Helps the Network
Running your own full node is the only way to have full control and to ensure that all the rules of Bitcoin are being followed. Nodes do this by rejecting blocks and transactions that don’t follow the consensus rules and by rejecting connections from peers that send them (or too many of them).
2)   Keeps you safe
Running any kind of Bitcoin wallet that does not require you to run a full node means that you have to place a certain degree of trust in the service provider, something that shouldn’t be necessary with Bitcoin.
3)   Allows you to choose
In the possible event of a hard fork where both blockchains remain active with economic activity on each side like the one in Ethereum/Ethereum Classic, running a full node is the only way you can validate the rules of the new or old blockchain, according to your preference. If you don’t run a full node, your opinion will not be considered and you will simply follow the blockchain that is given to you.
4)   Gives you a higher degree of privacy
Using a centralized, lightweight or even SPV wallet will never be as private as running a full node. Since you rely on third-party servers to broadcast your transactions for you, those servers will be aware of which addresses belong to you.
5)   It’s not that hard
To less than tech-savvy users, running a full node may seem like a challenge. However, running a Bitcoin core full node is nothing more than simply downloading the latest Bitcoin core client version and running it.
6)   It’s not that expensive
Running a node will require you to keep your computer on at all times – or at least for the majority of the day. While you can always turn your node on and off at will with this option, it is not a very practical one. Thank you.
legendary
Activity: 2828
Merit: 2472
https://JetCash.com
June 22, 2018, 10:18:50 AM

Have tried this and used to run the full node on my workstation.
But upon switching to a lighter laptop(which I did for my needs) I cannot do that any longer.
Also, it will take ages to download the blockchain.
And once you have started downloading the blockchain, Its almost impossible to use your computer for any of the other task you want.
An alternate approach is  that You may keep  a pruned blockchain.



What a load of tosh.

You can just copy the blockchain, no need to download it again.
You can't run a pruned blockchain unless you had a blockchain to prune.
One of my nodes is running on a netbook with a celeron processor. Is your laptop 'lighter' than that?

Was it worth bumping an old thread to post that rubbish?
I've put you on ignore, so no merits from me ever.
member
Activity: 154
Merit: 11
June 22, 2018, 09:46:38 AM

Have tried this and used to run the full node on my workstation.
But upon switching to a lighter laptop(which I did for my needs) I cannot do that any longer.
Also, it will take ages to download the blockchain.
And once you have started downloading the blockchain, Its almost impossible to use your computer for any of the other task you want.
An alternate approach is  that You may keep  a pruned blockchain.

I cannot agree with you:

1) The latest Bitcoin Core wallet app vers. 0.16.1 (I run it as my own full node) downloads the blockchain pretty fast (much faster than earlier versions)

2) I used to keep a Bitcoin Core full node wallet on an exclusively weak PC (500Mb RAM , single-core very slow old Celeron CPU) while doing all sorts of ordinary stuff , without any performance downgrade!
 I managed to achieve that by setting very low permanent process priority for the Bitcoin Core process. For that I used one of the software from this review: https://www.raymond.cc/blog/permanently-set-process-priority-in-windows-task-manager-with-prio/
member
Activity: 154
Merit: 11
November 27, 2017, 10:50:10 PM
How large is the blockchain, what is your bandwidth and how long until you synced your node?
About 160 Gb, full node may be run with any bandwidth actually (mine is 2.5Mb download/1.5 Mb upload), I had to wait about 2 weaks, but Bitcoin Core 0.15.0.1 will sync faster. You may download the whole blockchain if you have problems with syncing (see https://bitcointalksearch.org/topic/whole-bitcoin-core-015-blockchain-database-on-google-drive-2321650 ).
All necessary info may be found in the official, pretty clear docs at https://bitcoin.org/en/full-node

I installed 0.15 last week and it took just a weekend to catch up. Huge huge improvement vs last time I did this when it took
~2 weeks, as you say.

It's a very good news!  I'm very happy the great Core team has achieved such a progress in the wallet's initial syncing!


member
Activity: 64
Merit: 10
November 27, 2017, 03:30:38 PM
How large is the blockchain, what is your bandwidth and how long until you synced your node?
About 160 Gb, full node may be run with any bandwidth actually (mine is 2.5Mb download/1.5 Mb upload), I had to wait about 2 weaks, but Bitcoin Core 0.15.0.1 will sync faster. You may download the whole blockchain if you have problems with syncing (see https://bitcointalksearch.org/topic/whole-bitcoin-core-015-blockchain-database-on-google-drive-2321650 ).
All necessary info may be found in the official, pretty clear docs at https://bitcoin.org/en/full-node

I installed 0.15 last week and it took just a weekend to catch up. Huge huge improvement vs last time I did this when it took
~2 weeks, as you say.
member
Activity: 70
Merit: 10
November 27, 2017, 11:05:02 AM
The starting point of a phrase search is random, it gets a private key from the openssl rand ecdsa library and starts searching from there, simply incrementing the key. After searching many addresses for a phrase match, it will again get another random private key. The keys searched and returned with a found vanity phrase in the corresponding Bitcoin address can be from anywhere in the range of valid keys, but certainly it cannot "search the entire keyspace", as that would take somewhere just north of the age of the universe.
member
Activity: 154
Merit: 11
November 08, 2017, 02:19:50 PM
How large is the blockchain, what is your bandwidth and how long until you synced your node?
About 160 Gb, full node may be run with any bandwidth actually (mine is 2.5Mb download/1.5 Mb upload), I had to wait about 2 weaks, but Bitcoin Core 0.15.0.1 will sync faster. You may download the whole blockchain if you have problems with syncing (see https://bitcointalksearch.org/topic/whole-bitcoin-core-015-blockchain-database-on-google-drive-2321650 ).
All necessary info may be found in the official, pretty clear docs at https://bitcoin.org/en/full-node
member
Activity: 154
Merit: 11
November 08, 2017, 01:14:45 PM

I must take my words back! It has turned out that those 2x guys are not that bad! The terrible 2x chain split seems to be canceled at last!!
Everyone has the right to be mistaken, the main thing is to have the courage, honesty and wisdom to admit that they were not quite right.

sr. member
Activity: 377
Merit: 282
Finis coronat opus
November 08, 2017, 06:07:03 AM
That has nothing to do with whether "all nodes were supposed to be full nodes."

Satoshi talked about the obvious need for lightweight wallets that didn't require the entire Merkle tree database.

All nodes were supposed to be miners, without full nodes and miner nodes.
But in other argument you're right. Satoshi predicted "light" wallets.
Pages:
Jump to: