Pages:
Author

Topic: Bitcoin Full Node (Read 2473 times)

legendary
Activity: 1008
Merit: 1001
Let the chips fall where they may.
January 28, 2015, 11:00:44 PM
#34
Wrong. You must allow traffic across port 8333 which is going to be blocked by most hardware firewalls.  See here.  https://bitcointalksearch.org/topic/setting-up-a-bitcoin-node-128122

You need to do that if you want to contribute to the network. If you simply want a full node to relay and verify your own transactions, you don't have to.
legendary
Activity: 4228
Merit: 1313
January 28, 2015, 02:22:37 PM
#33
Can anyone tell me of the advantages of running a Bitcoin full node?

When someone is running Bitcoin Core in his machine, is not he running a full node as long as he is connected to the internet ?

Often, but not always, it depends on the configuration of things.  Particularly your router.  If you only have 8 connections, you may need to investigate if port 8333 is available from the outside of your network.  Some router and other firewalls need a bit of configuration.

You can see if port 8333 is open so that you are accepting incoming connections using a tool like this:
http://www.yougetsignal.com/tools/open-ports/
legendary
Activity: 4228
Merit: 1313
January 28, 2015, 02:18:20 PM
#32
You should run a full node onnly for support the bitcoin network, you don't have any other advantage.

I'm confused, don't you receive the tx fees?  Huh

No only the mining pool received the TX fees , it is a PoW coin not a PoS coin .

For p2pool, it is slightly different - the pool operator doesn't receive the fees, they are paid directly.  (Another advantage of p2pool - you don't have to worry about a pool operator stealing coins if they are not reputable.  Likewise, p2pool makes it difficult to attack the network unlike non p2p pools. )
full member
Activity: 532
Merit: 100
January 28, 2015, 02:10:38 PM
#31
Also, see here from Bitcoin.org:  "If you have a good Internet connection, you can strengthen the Bitcoin network by keeping full node software running on your computer or server with port 8333 open. Full nodes are securing and relaying all transactions.

https://bitcoin.org/en/support-bitcoin

This might help too:

"While you’re waiting for the torrent to finish, you should configure your home’s router (assuming that you have one.) It’s critical that you forward port 8333 on your router to the IP address of the computer that is running your node. If you don’t do this, you will not be contributing your bandwidth to the network and should not run the node. You can check that your port forwarding works using the “check node” tool on Bitnodes.io when your node is running. If you’re running a software firewall on the machine running the node, you’ll also want to ensure that you create a rule to open up port 8333."  https://medium.com/@lopp/how-to-set-up-a-bitcoin-full-node-2dd1c09763d3
full member
Activity: 532
Merit: 100
January 28, 2015, 02:06:47 PM
#30
....
Wrong. You must allow traffic across port 8333 which is going to be blocked by most hardware firewalls.  See here.  https://bitcointalksearch.org/topic/setting-up-a-bitcoin-node-128122

So , you have to use "bitcoin-qt or bitcoind" and  open the tcp port 8333,



Just download the bitcoin-qt or bitcoind and you will be a full node

Make sure to open TCP port 8333.






I edited my post slightly.  I don't know what bitcoind is unless that is the daemon running the bitcoin-qt client, but with with bitcoin-qt, you need to open up port 8333 to allow for more than 8 connections to the Bitcoin network.
legendary
Activity: 1778
Merit: 1043
#Free market
January 28, 2015, 02:05:05 PM
#29
....
Wrong. You must allow traffic across port 8333 which is going to be blocked by most hardware firewalls.  See here.  https://bitcointalksearch.org/topic/setting-up-a-bitcoin-node-128122

So , you have to use "bitcoin-qt or bitcoind" and  open the tcp port 8333,



Just download the bitcoin-qt or bitcoind and you will be a full node

Make sure to open TCP port 8333.



I edited my post slightly.  I don't know what bitcoind is, but with with bitcoin-qt, you need to open up port 8333 to allow for more than 8 connections to the Bitcoin network.


Bitcoind :

Bitcoind is a program that implements the Bitcoin protocol for command line and remote procedure call (RPC) use. It is also the first Bitcoin client in the network's history. It is available under the MIT license in 32-bit and 64-bit versions for Windows, GNU/Linux-based OSes, and Mac OS X.



https://en.bitcoin.it/wiki/Bitcoind
full member
Activity: 532
Merit: 100
January 28, 2015, 02:03:41 PM
#28
....
Wrong. You must allow traffic across port 8333 which is going to be blocked by most hardware firewalls.  See here.  https://bitcointalksearch.org/topic/setting-up-a-bitcoin-node-128122

So , you have to use "bitcoin-qt or bitcoind" and  open the tcp port 8333,



Just download the bitcoin-qt or bitcoind and you will be a full node

Make sure to open TCP port 8333.



I edited my post slightly.  I don't know what bitcoind is, but with with bitcoin-qt, you need to open up port 8333 to allow for more than 8 connections to the Bitcoin network.
legendary
Activity: 1778
Merit: 1043
#Free market
January 28, 2015, 02:02:37 PM
#27
....
Wrong. You must allow traffic across port 8333 which is going to be blocked by most hardware firewalls.  See here.  https://bitcointalksearch.org/topic/setting-up-a-bitcoin-node-128122

So , you have to use "bitcoin-qt or bitcoind" and  open the tcp port 8333,



Just download the bitcoin-qt or bitcoind and you will be a full node

Make sure to open TCP port 8333.


full member
Activity: 532
Merit: 100
January 28, 2015, 02:02:18 PM
#26
Can anyone tell me of the advantages of running a Bitcoin full node?

When someone is running Bitcoin Core in his machine, is not he running a full node as long as he is connected to the internet ?

No, you have to open up additional ports on your firewall and have them forwarded to the machine running Bitcoin Core to become a full node. This would take you from being connected to around 7 nodes or less to 30 nodes or more and it also allows bidirectional traffic to/from those nodes as well.

The number of connected nodes has nothing to do with a machine beeing/hosting a full node or not.

Anyone running bitcoin core/qt is running a full node. The traffic is bidirectional regardless of the firewall settings as long as the node can access the internet. Once a connection has been established, data can be transfered in both directions.

The node might not be available for light clients (like multibit) because the firewall does not allow connections from the outside. The node might also be unable handle more than 1 connection and thus relay no new transactions but the ones that originated from it. This node might not be very helpfull, but it is still a full node.

Edit: spelling, additions to clarify

 

You must allow traffic across port 8333 which is going to be blocked by most hardware firewalls to allow for more than 8 connections though.  See here.  https://bitcointalksearch.org/topic/setting-up-a-bitcoin-node-128122
full member
Activity: 532
Merit: 100
January 28, 2015, 01:59:26 PM
#25
Can anyone tell me of the advantages of running a Bitcoin full node?

When someone is running Bitcoin Core in his machine, is not he running a full node as long as he is connected to the internet ?

No, you have to open up additional ports on your firewall and have them forwarded to the machine running Bitcoin Core to become a full node. This would take you from being connected to around 7 nodes or less to 30 nodes or more and it also allows bidirectional traffic to/from those nodes as well.

The number of connected nodes has nothing to do with a machine beeing/hosting a full node or not.

Anyone running bitcoin core/qt is running a full node. The traffic is bidirectional regardless of the firewall settings as long as the node can access the internet. Once a connection has been established, data can be transfered in both directions.

The node might not be available for light clients (like multibit) because the firewall does not allow connections from the outside. The node might also be unable handle more than 1 connection and thus relay no new transactions but the ones that originated from it. This node might not be very helpfull, but it is still a full node.

Edit: spelling, additions to clarify

Wrong. You must allow traffic across port 8333 which is going to be blocked by most hardware firewalls.  See here.  https://bitcointalksearch.org/topic/setting-up-a-bitcoin-node-128122
legendary
Activity: 1778
Merit: 1043
#Free market
January 28, 2015, 01:51:52 PM
#24
To clarify: a full node stores (and verifies) the entire block-chain (now around 30GB).

so, all the users that are using the bitcoin core "client" are  full nodes?
legendary
Activity: 1008
Merit: 1001
Let the chips fall where they may.
January 28, 2015, 01:49:32 PM
#23
To clarify: a full node stores (and verifies) the entire block-chain (now around 30GB).
copper member
Activity: 1498
Merit: 1528
No I dont escrow anymore.
January 28, 2015, 01:13:15 PM
#22
Can anyone tell me of the advantages of running a Bitcoin full node?

When someone is running Bitcoin Core in his machine, is not he running a full node as long as he is connected to the internet ?

No, you have to open up additional ports on your firewall and have them forwarded to the machine running Bitcoin Core to become a full node. This would take you from being connected to around 7 nodes or less to 30 nodes or more and it also allows bidirectional traffic to/from those nodes as well.

The number of connected nodes has nothing to do with a machine beeing/hosting a full node or not.

Anyone running bitcoin core/qt is running a full node. The traffic is bidirectional regardless of the firewall settings as long as the node can access the internet. Once a connection has been established, data can be transfered in both directions.

The node might not be available for light clients (like multibit) because the firewall does not allow connections from the outside. The node might also be unable handle more than 1 connection and thus relay no new transactions but the ones that originated from it. This node might not be very helpfull, but it is still a full node.

Edit: spelling, additions to clarify
full member
Activity: 532
Merit: 100
January 28, 2015, 12:48:58 PM
#21
Can anyone tell me of the advantages of running a Bitcoin full node?

When someone is running Bitcoin Core in his machine, is not he running a full node as long as he is connected to the internet ?

No, you have to open up additional ports on your firewall and have them forwarded to the machine running Bitcoin Core to become a full node. This would take you from being connected to around 7 nodes or less to 30 nodes or more and it also allows bidirectional traffic to/from those nodes as well.
sr. member
Activity: 350
Merit: 250
Honest 80s business!
January 28, 2015, 10:58:56 AM
#20
Well actually, it (only) makes the network more stable. You help distributing new transactions and keeping a copy of the latest blockchain available. You become a part of the whole Bitcoin ecosystem and thus help making it better! Smiley
legendary
Activity: 1662
Merit: 1050
January 28, 2015, 10:39:30 AM
#19
Can anyone tell me of the advantages of running a Bitcoin full node?

When someone is running Bitcoin Core in his machine, is not he running a full node as long as he is connected to the internet ?
legendary
Activity: 1358
Merit: 1001
https://gliph.me/hUF
January 28, 2015, 10:34:39 AM
#18
[...] but nowadays nobody does solo-mining I guess?

Of course they do. If you have enough equipment it is still possible. There are also solo mining pools by which the pool op takes care of the blockchain etc., but the hashing is not pooled together as on a regular pool. For example: https://bitcointalksearch.org/topic/yh-solockpoolorg-2-fee-solo-mining-usade-255-blocks-solved-763510 and http://bitsolo.net/
legendary
Activity: 1316
Merit: 1000
Si vis pacem, para bellum
January 28, 2015, 10:33:13 AM
#17
You should run a full node onnly for support the bitcoin network, you don't have any other advantage.

I'm confused, don't you receive the tx fees?  Huh

No only the mining pool received the TX fees , it is a PoW coin not a PoS coin .

I thought only lightweight nodes and asic miners need a central server or pool. Full nodes should connect directly to other nodes.

 Huh

OK, I've looked it up:
transaction fees of a transaction can only be collected by including it into a valid block. And to be able to include a transaction in a valid block you have to mine a valid block. If you would mine one block, you could collect the fees, but nowadays nobody does solo-mining I guess?

it is worth running a full node to keep the network strong if you can leave your computer on 24/7 and connected to internet

plenty of people still mine at home but you need decent hardware to make it worthwhile and cheap electric ,a cpu or gpu mining  would be losing you money thesedays i would imagine unless your power is free
legendary
Activity: 2044
Merit: 1055
January 28, 2015, 09:59:28 AM
#16
You should run a full node onnly for support the bitcoin network, you don't have any other advantage.

I'm confused, don't you receive the tx fees?  Huh

No only the mining pool received the TX fees , it is a PoW coin not a PoS coin .

I thought only lightweight nodes and asic miners need a central server or pool. Full nodes should connect directly to other nodes.

 Huh

OK, I've looked it up:
transaction fees of a transaction can only be collected by including it into a valid block. And to be able to include a transaction in a valid block you have to mine a valid block. If you would mine one block, you could collect the fees, but nowadays nobody does solo-mining I guess?
legendary
Activity: 2044
Merit: 1055
January 28, 2015, 09:56:04 AM
#15
You should run a full node onnly for support the bitcoin network, you don't have any other advantage.

I'm confused, don't you receive the tx fees?  Huh

No only the mining pool received the TX fees , it is a PoW coin not a PoS coin .

I thought only lightweight nodes and asic miners need a central server or pool. Full nodes should connect directly to other nodes.

 Huh
Pages:
Jump to: