Pages:
Author

Topic: Only 900 Nodes... NVM over 7000. (Read 2194 times)

full member
Activity: 197
Merit: 100
November 10, 2014, 10:34:35 PM
#23

7000 nodes is a big or a small amount? A few month ago was more or less full nodes? Tongue

Slow and steady decline -
http://www.coinbuzz.com/2014/04/28/bitnodes-io-indicates-60-day-decline-bitcoin-nodes/

Avg 9500 early this year and 7800 avg 6 months ago.
Maybe BTC protocol should introduce something similar to PoS to encourage people to have full node opened? Tongue
Probably not a good idea. PoS coins are too easy to attack
legendary
Activity: 1722
Merit: 1004
November 10, 2014, 01:49:19 PM
#22
https://getaddr.bitnodes.io/

Blockchain.info does not connect to every node on the network.

We keep losing nodes..... :S.


Update thread title, please.
legendary
Activity: 4228
Merit: 1313
November 10, 2014, 01:25:52 PM
#21

7000 nodes is a big or a small amount? A few month ago was more or less full nodes? Tongue

Slow and steady decline -
http://www.coinbuzz.com/2014/04/28/bitnodes-io-indicates-60-day-decline-bitcoin-nodes/

Avg 9500 early this year and 7800 avg 6 months ago.
Maybe BTC protocol should introduce something similar to PoS to encourage people to have full node opened? Tongue

Go ahead, let us know when the client fork is ready, fork the blockchain and we'll see who is ready to switch to PoS.
newbie
Activity: 29
Merit: 0
November 10, 2014, 01:16:33 PM
#20

7000 nodes is a big or a small amount? A few month ago was more or less full nodes? Tongue

Slow and steady decline -
http://www.coinbuzz.com/2014/04/28/bitnodes-io-indicates-60-day-decline-bitcoin-nodes/

Avg 9500 early this year and 7800 avg 6 months ago.
Maybe BTC protocol should introduce something similar to PoS to encourage people to have full node opened? Tongue
newbie
Activity: 10
Merit: 0
November 10, 2014, 01:16:25 PM
#19
what is loosing nodes,bitcoin?
hero member
Activity: 658
Merit: 501
November 10, 2014, 01:13:12 PM
#18


I'm up to 15 connections now.  Am I right to assume that you are not actually verifying transactions on the Bitcoin network unless you are also allowing outbound traffic?

Yes.
full member
Activity: 532
Merit: 100
November 10, 2014, 01:04:24 PM
#17

Ah, ok.  I just opened up port 8333 and noticed that my number of active connections went from 8 to 10.

Congrats, you are now allowing outbound traffic and not merely a leach upon other nodes.

I'm up to 15 connections now.  Am I right to assume that you are not actually verifying transactions on the Bitcoin network unless you are also allowing outbound traffic?
hero member
Activity: 658
Merit: 501
November 10, 2014, 12:55:28 PM
#16

Ah, ok.  I just opened up port 8333 and noticed that my number of active connections went from 8 to 10.

Congrats, you are now allowing outbound traffic and not merely a leach upon other nodes.
full member
Activity: 532
Merit: 100
November 10, 2014, 12:53:19 PM
#15

So once that port is opened (port forwarded), what does it actually do for the bitcoin-qt client that's different from before?

Necessary to act as a full node, otherwise you will be limited to 8 incoming connections with no outgoing connections.

Ah, ok.  I just opened up port 8333 and noticed that my number of active connections went from 8 to 10.  I'm seeing the below entries in my debug log.  Is this normal?  (I removed my IP address in the log below)

2014-11-10 17:52:33 ProcessBlock: ACCEPTED
2014-11-10 17:52:33 ERROR: AcceptToMemoryPool : inputs already spent
2014-11-10 17:52:33 ERROR: AcceptToMemoryPool : inputs already spent
2014-11-10 17:52:57 ERROR: AcceptToMemoryPool : inputs already spent
2014-11-10 17:52:58 ERROR: AcceptToMemoryPool : inputs already spent
2014-11-10 17:53:00 receive version message: /bitcoinseeder:0.01/: version 60000, blocks=230000, us=x.x.x.x:8333, them=0.0.0.0:0, peer=178.62.20.190:43641
2014-11-10 17:53:00 Added time data, samples 17, offset +0 (+0 minutes)
2014-11-10 17:53:00 nTimeOffset = -1  (+0 minutes)
2014-11-10 17:53:03 receive version message: /bitcoinseeder:0.01/: version 60000, blocks=230000, us=x.x.x.x:8333, them=0.0.0.0:0, peer=199.127.225.232:45435
2014-11-10 17:53:03 Added time data, samples 18, offset +0 (+0 minutes)
2014-11-10 17:53:05 ERROR: AcceptToMemoryPool : nonstandard transaction: dust
2014-11-10 17:53:05 socket recv error Connection reset by peer (54)
2014-11-10 17:53:08 ERROR: AcceptToMemoryPool : nonstandard transaction: dust
hero member
Activity: 658
Merit: 501
November 10, 2014, 12:52:05 PM
#14

7000 nodes is a big or a small amount? A few month ago was more or less full nodes? Tongue

Slow and steady decline -
http://www.coinbuzz.com/2014/04/28/bitnodes-io-indicates-60-day-decline-bitcoin-nodes/

Avg 9500 early this year and 7800 avg 6 months ago.
newbie
Activity: 29
Merit: 0
November 10, 2014, 12:44:41 PM
#13
When I checked in periodically during the week we were in the 500s and 600s
900 is actually not too bad
https://getaddr.bitnodes.io/

Blockchain.info does not connect to every node on the network.

Oh, okay , thanks.

+6000, well that's more like it!!
7000 nodes is a big or a small amount? A few month ago was more or less full nodes? Tongue
newbie
Activity: 21
Merit: 0
November 10, 2014, 12:42:06 PM
#12
https://getaddr.bitnodes.io/

Blockchain.info does not connect to every node on the network.

Oh, okay , thanks.

+6000, well that's more like it!!
First post full of panic Tongue Reality isn't as bad as you think Wink
hero member
Activity: 658
Merit: 501
November 10, 2014, 12:26:39 PM
#11

So once that port is opened (port forwarded), what does it actually do for the bitcoin-qt client that's different from before?

Necessary to act as a full node, otherwise you will be limited to 8 incoming connections with no outgoing connections.
legendary
Activity: 892
Merit: 1002
1 BTC =1 BTC
November 10, 2014, 12:24:40 PM
#10
Oh, ok.  I thought I remember someone on here saying before that you weren't actually running a full node on your bitcoin-qt client unless you opened up additional ports on your firewall. Is that true?  I'm not sure why opening up more ports would make you a full node unless it's because you can process more traffic or something.

Yes, You need port 8333 open ... you can test here:

http://www.yougetsignal.com/tools/open-ports/

So once that port is opened (port forwarded), what does it actually do for the bitcoin-qt client that's different from before?

Tcp port 8333 enables communication between the bitcoin clients.
full member
Activity: 532
Merit: 100
November 10, 2014, 12:07:12 PM
#9
Oh, ok.  I thought I remember someone on here saying before that you weren't actually running a full node on your bitcoin-qt client unless you opened up additional ports on your firewall. Is that true?  I'm not sure why opening up more ports would make you a full node unless it's because you can process more traffic or something.

Yes, You need port 8333 open ... you can test here:

http://www.yougetsignal.com/tools/open-ports/

So once that port is opened (port forwarded), what does it actually do for the bitcoin-qt client that's different from before?
hero member
Activity: 658
Merit: 501
November 10, 2014, 12:05:06 PM
#8
Oh, ok.  I thought I remember someone on here saying before that you weren't actually running a full node on your bitcoin-qt client unless you opened up additional ports on your firewall. Is that true?  I'm not sure why opening up more ports would make you a full node unless it's because you can process more traffic or something.

Yes, You need port 8333 open ... you can test here:

http://www.yougetsignal.com/tools/open-ports/
full member
Activity: 532
Merit: 100
November 10, 2014, 12:02:05 PM
#7
and with future improvements it will be easier to sync and run a full node  Smiley

Please excuse my ignorance, but what is meant by running a "full node"?  How is this different than running the bitcoin-qt client?  I'm not trying to be a smart a$$ or anything, I just don't know and want to understand it better.
A full node is in fact the Bitcoin-Qt client. It relays and verifies blocks and is also capable of serving work if you are a miner.

Oh, ok.  I thought I remember someone on here saying before that you weren't actually running a full node on your bitcoin-qt client unless you opened up additional ports on your firewall. Is that true?  I'm not sure why opening up more ports would make you a full node unless it's because you can process more traffic or something.
legendary
Activity: 1862
Merit: 1011
Reverse engineer from time to time
November 10, 2014, 12:00:05 PM
#6
and with future improvements it will be easier to sync and run a full node  Smiley

Please excuse my ignorance, but what is meant by running a "full node"?  How is this different than running the bitcoin-qt client?  I'm not trying to be a smart a$$ or anything, I just don't know and want to understand it better.
A full node is in fact the Bitcoin-Qt client. It relays and verifies blocks and is also capable of serving work if you are a miner.
full member
Activity: 532
Merit: 100
November 10, 2014, 11:58:23 AM
#5
and with future improvements it will be easier to sync and run a full node  Smiley

Please excuse my ignorance, but what is meant by running a "full node"?  How is this different than running the bitcoin-qt client?  I'm not trying to be a smart a$$ or anything, I just don't know and want to understand it better.
legendary
Activity: 1148
Merit: 1014
In Satoshi I Trust
November 10, 2014, 11:25:11 AM
#4
and with future improvements it will be easier to sync and run a full node  Smiley
Pages:
Jump to: