Topic: Help the bitcoin network by being a node. - page 3. (Read 20988 times)
maxconnections=512
I think one has to distinguish between nodes running on client and on a cloud server. Running bitcoind on cloud services is probably more risky as virtualization is an additional attack vector. But as these services become very cheap it is very likely that we want to run nodes on servers instead of P2P personal computers, at least for low security applications.
I'm working on a packer.io build script which can be used to deploy bitcoind servers (virtual machine images to be exact). It can be easily adapted to the various providers (or even multi-provider), as this is build into packer.
Recently there was an Digitialocean leakage reported, when you not properly remove droplets (machine images). A few years ago a Linode employee allegedly stole money (haven't investigated the claims but the possibility is always there). For AWS security see: http://awsmedia.s3.amazonaws.com/pdf/AWS_Security_Whitepaper.pdf But as the largest websites are run on the biggest providers, these should get more safe over time. It would be interesting to think about how cloud servers can be run as safely as possible. It allows people to run full nodes, basically on the click of a button. I would argue this is much better than online wallets.
I'm working on a packer.io build script which can be used to deploy bitcoind servers (virtual machine images to be exact). It can be easily adapted to the various providers (or even multi-provider), as this is build into packer.
Recently there was an Digitialocean leakage reported, when you not properly remove droplets (machine images). A few years ago a Linode employee allegedly stole money (haven't investigated the claims but the possibility is always there). For AWS security see: http://awsmedia.s3.amazonaws.com/pdf/AWS_Security_Whitepaper.pdf But as the largest websites are run on the biggest providers, these should get more safe over time. It would be interesting to think about how cloud servers can be run as safely as possible. It allows people to run full nodes, basically on the click of a button. I would argue this is much better than online wallets.
I highly suggest not storing funds on any online computer
I think one has to distinguish between nodes running on client and on a cloud server. Running bitcoind on cloud services is probably more risky as virtualization is an additional attack vector. But as these services become very cheap it is very likely that we want to run nodes on servers instead of P2P personal computers, at least for low security applications.
I'm working on a packer.io build script which can be used to deploy bitcoind servers (virtual machine images to be exact). It can be easily adapted to the various providers (or even multi-provider), as this is build into packer.
Recently there was an Digitialocean leakage reported, when you not properly remove droplets (machine images). A few years ago a Linode employee allegedly stole money (haven't investigated the claims but the possibility is always there). For AWS security see: http://awsmedia.s3.amazonaws.com/pdf/AWS_Security_Whitepaper.pdf But as the largest websites are run on the biggest providers, these should get more safe over time. It would be interesting to think about how cloud servers can be run as safely as possible. It allows people to run full nodes, basically on the click of a button. I would argue this is much better than online wallets.
I'm working on a packer.io build script which can be used to deploy bitcoind servers (virtual machine images to be exact). It can be easily adapted to the various providers (or even multi-provider), as this is build into packer.
Recently there was an Digitialocean leakage reported, when you not properly remove droplets (machine images). A few years ago a Linode employee allegedly stole money (haven't investigated the claims but the possibility is always there). For AWS security see: http://awsmedia.s3.amazonaws.com/pdf/AWS_Security_Whitepaper.pdf But as the largest websites are run on the biggest providers, these should get more safe over time. It would be interesting to think about how cloud servers can be run as safely as possible. It allows people to run full nodes, basically on the click of a button. I would argue this is much better than online wallets.
Verifying transactions absolutely DOES help the network even if you are not mining. Here's a recap of why we need nodes:
To operate, P2P wallets need to connect to P2P nodes.
Then they need to download the block chain, possibly a filtered version of it. And they need to hear about any transactions that didn't confirm yet, but which are valid and sitting in the memory pool. This is vital so someone can send you money, and you can open your wallet and see it immediately.
Storing the block chain, serving/filtering the chain, verifying and relaying transactions, all this takes resources.
When you run a node, you take some of that load onto your own shoulders. The work gets spread out, so as the number of users goes up, we need to keep adding nodes to ensure it stays relatively cheap and easy to do so.
The most important things when running a node are
1) ensuring that you are allowing inbound connections. If you run a node at home or behind a firewall, it's vital you ensure it's set up right so other nodes and wallets can connect to yours.
2) staying up to date with the latest software
Thanks to everyone who is running a node, upgrading it and accepting inbound connections! You are contributing to Bitcoin in a very direct and helpful manner.
To operate, P2P wallets need to connect to P2P nodes.
Then they need to download the block chain, possibly a filtered version of it. And they need to hear about any transactions that didn't confirm yet, but which are valid and sitting in the memory pool. This is vital so someone can send you money, and you can open your wallet and see it immediately.
Storing the block chain, serving/filtering the chain, verifying and relaying transactions, all this takes resources.
When you run a node, you take some of that load onto your own shoulders. The work gets spread out, so as the number of users goes up, we need to keep adding nodes to ensure it stays relatively cheap and easy to do so.
The most important things when running a node are
1) ensuring that you are allowing inbound connections. If you run a node at home or behind a firewall, it's vital you ensure it's set up right so other nodes and wallets can connect to yours.
2) staying up to date with the latest software
Thanks to everyone who is running a node, upgrading it and accepting inbound connections! You are contributing to Bitcoin in a very direct and helpful manner.
I am running bitcoind on my Debian personal desktop so I contribute a bit to the operation of the network. I am also running primecoin, protoshares and memorycoin. I dont think there really is a need for much more nodes, but running one never hurts the planet.
i have this program, connectifyme, allows ethernet connection to computer like a router except your laptop would be receiving/sending data through wifi...i confirmed this when trying to buy an ethernet router same deal asic miner
anyone please with knowledge contribute further
anyone please with knowledge contribute further
How do you get from a wifi router to an asic miner in your logic?
i have this program, connectifyme, allows ethernet connection to computer like a router except your laptop would be receiving/sending data through wifi...i confirmed this when trying to buy an ethernet router same deal asic miner
anyone please with knowledge contribute further
anyone please with knowledge contribute further
Helping is good!
Right, so I am helping the network in a small way?
Yes those around you to get the blockchain
and relaying transactions.
and verifying tx's.
But that doesn't matter unless you're mining.
Right, so I am helping the network in a small way?
Yes those around you to get the blockchain
and relaying transactions.
and verifying tx's.
Right, so I am helping the network in a small way?
Yes those around you to get the blockchain
and relaying transactions.
Right, so I am helping the network in a small way?
Yes those around you to get the blockchain
Right, so I am helping the network in a small way?
Yup those are nice incomings
yenomeat:8333
yenomeat:8333
Outgoing looks good
netstat incoming
netstat incoming
Something like this?
Code:
root@yenomeat:~# netstat -ap | grep bitcoind
tcp 0 0 localhost.localdom:8332 *:* LISTEN 307/bitcoind
tcp 0 0 *:8333 *:* LISTEN 307/bitcoind
tcp 0 0 yenomeat:8333 lickthesalt.com:53233 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:36494 91.84.131.109:8333 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 www.klmist.com:53816 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:38923 cust-82-99-109-35.:8333 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 host.poyomi.com:55344 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 78-21-195-6.acces:55335 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 honeycomb.charlie:43091 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 75-201.105-92.cus:52869 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 mail.blcheck.com:44184 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:45914 ks3293965.kimsufi.:8333 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 adsl-75-9-58-184.:57978 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 pppoe.178-66-13-2:59136 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 host5-81-39-130.r:59078 ESTABLISHED 307/bitcoind
tcp 0 495505 yenomeat:46040 broadband-77-37-24:8333 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 62.33.29.52:52552 ESTABLISHED 307/bitcoind
tcp 1035 11680 yenomeat:8333 202.8.246.74:61009 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 lns-c10k-ld-01-m-:63534 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 host-128.FKO.213.:59896 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 103.6.159.111:50475 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 46.39.230.82:16183 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 78-106-36-142.bro:50329 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 171.213.199.217:62130 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:46499 dmchess-unlim.vpn.:8333 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:60024 ppp-46-33-255-24.w:8333 ESTABLISHED 307/bitcoind
tcp 0 61 yenomeat:8333 187.16.56.60:60257 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 static.99.121.4.4:11835 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:53407 dynamic-vpdn-46-53:8333 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 c-68-34-134-243.h:50427 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 50-73-45-250-utah:33434 ESTABLISHED 307/bitcoind
tcp 837 42310 yenomeat:8333 CPE-124-182-179-4:62178 ESTABLISHED 307/bitcoind
tcp 1978 188240 yenomeat:8333 c-24-5-66-209.hsd:45211 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 125.71.94.138:25450 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:37257 c-75-73-129-240.hs:8333 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 cpe-67-247-18-224:49938 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 75-171-205-58.hlr:58286 ESTABLISHED 307/bitcoind
tcp6 0 0 localhost:8332 [::]:* LISTEN 307/bitcoind
tcp6 0 0 [::]:8333 [::]:* LISTEN 307/bitcoind
tcp 0 0 localhost.localdom:8332 *:* LISTEN 307/bitcoind
tcp 0 0 *:8333 *:* LISTEN 307/bitcoind
tcp 0 0 yenomeat:8333 lickthesalt.com:53233 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:36494 91.84.131.109:8333 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 www.klmist.com:53816 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:38923 cust-82-99-109-35.:8333 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 host.poyomi.com:55344 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 78-21-195-6.acces:55335 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 honeycomb.charlie:43091 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 75-201.105-92.cus:52869 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 mail.blcheck.com:44184 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:45914 ks3293965.kimsufi.:8333 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 adsl-75-9-58-184.:57978 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 pppoe.178-66-13-2:59136 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 host5-81-39-130.r:59078 ESTABLISHED 307/bitcoind
tcp 0 495505 yenomeat:46040 broadband-77-37-24:8333 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 62.33.29.52:52552 ESTABLISHED 307/bitcoind
tcp 1035 11680 yenomeat:8333 202.8.246.74:61009 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 lns-c10k-ld-01-m-:63534 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 host-128.FKO.213.:59896 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 103.6.159.111:50475 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 46.39.230.82:16183 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 78-106-36-142.bro:50329 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 171.213.199.217:62130 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:46499 dmchess-unlim.vpn.:8333 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:60024 ppp-46-33-255-24.w:8333 ESTABLISHED 307/bitcoind
tcp 0 61 yenomeat:8333 187.16.56.60:60257 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 static.99.121.4.4:11835 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:53407 dynamic-vpdn-46-53:8333 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 c-68-34-134-243.h:50427 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 50-73-45-250-utah:33434 ESTABLISHED 307/bitcoind
tcp 837 42310 yenomeat:8333 CPE-124-182-179-4:62178 ESTABLISHED 307/bitcoind
tcp 1978 188240 yenomeat:8333 c-24-5-66-209.hsd:45211 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 125.71.94.138:25450 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:37257 c-75-73-129-240.hs:8333 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 cpe-67-247-18-224:49938 ESTABLISHED 307/bitcoind
tcp 0 0 yenomeat:8333 75-171-205-58.hlr:58286 ESTABLISHED 307/bitcoind
tcp6 0 0 localhost:8332 [::]:* LISTEN 307/bitcoind
tcp6 0 0 [::]:8333 [::]:* LISTEN 307/bitcoind
Outgoing looks good
netstat incoming
netstat incoming
Do it for fun but seriously the network doesn't need it
And if you don't peer correctly, you'll actually download but never contribute
And if you don't peer correctly, you'll actually download but never contribute
I'm not doing it for fun. How can I know if I am actually making a contribution or not? I have three full nodes now, and the firewalls are open for bitcoin, but on each node I only get 5 or 6 connections at a time.
Here's the usage on one of my nodes
Quote
# bitcoind getpeerinfo|grep subver|sort|uniq -c|sort -n
1 "subver" : "",
1 "subver" : "/Satoshi:0.7.2/",
1 "subver" : "/Satoshi:0.8.0/",
2 "subver" : "/Satoshi:0.8.3/",
12 "subver" : "/Satoshi:0.8.1/",
14 "subver" : "/Satoshi:0.8.6/",
46 "subver" : "/Satoshi:0.8.5/",
1 "subver" : "",
1 "subver" : "/Satoshi:0.7.2/",
1 "subver" : "/Satoshi:0.8.0/",
2 "subver" : "/Satoshi:0.8.3/",
12 "subver" : "/Satoshi:0.8.1/",
14 "subver" : "/Satoshi:0.8.6/",
46 "subver" : "/Satoshi:0.8.5/",
The point is to become a cdn for the large blockchain
I know I can modify the config file to force outbound connections, and give priority to inbound connections, but how could a group collectively get together to leverage this feature in a manner that could bring more value to the system? Do I need to spend more time on IRC?
Nodes are so confusing Please help
https://bitcointalksearch.org/topic/ann-utc-university-of-texas-coin-a-coin-for-students-380259
https://bitcointalksearch.org/topic/ann-utc-university-of-texas-coin-a-coin-for-students-380259
Is that what your questions were about in the other thread? I think it's safe to say you have absolutely no ability to make your own alt coin. You should contract with someone to make it for you.
No one wakes up with the ability to make a coin one morning It is a process you decide to go through Even if you already knew how to code before bitcoin came out you still had to learn how to do it and practice
Yes, but it belongs in the altcoin sub forum not here.
Jump to: