If you just want to run a node, then... just download the client and let it finish syncing. Maybe even enable listening connections by setting listen=1 in your configuration file; that'd be the maximum contribution to the network in terms of bandwidth.
But, in practice, people run a node for their own interest. It's more secure and private for your own sake. The incentive which comes from individual gains is what keeps the network resilient and decentralized, not altruism.
Topic: BitCore Implementation For Support To community (Read 88 times)
Just a small query: Why do we need it behind the webserver? From the document, I understand that the Bitcoin core full node works for syncing the blockchain with other nodes and provides one more medium for confirmation, which the Bitcoin network can use. And yes this will not be for any kind of wallet services.
Also, can you please throw some light on some documents which can make me more aware of RPC?
Also, can you please throw some light on some documents which can make me more aware of RPC?
Among other things, Bitcoin Core does not use HTTPS, so all of the communication is, by default, exposed to third-parties. Although that part is not a big deal, there are some other reasons:
- Rate limiting, as I mentioned
- For security reasons, as a web server like Nginx or Apache is more hardened against security bugs so it can catch some of the exploits that might compromise Bitcoin Cora via the RPC port
- If you want to forward traffic to port 80
It makes it all very simple, really.
Yup, that I understood, my friend. What I am not able to understand is what RPC port you are talking about for the Bitcoin core full node server that needs to be open. As I can read on Bitcoin core documents, there is only one port that is required, which is 8333, to be open to sync and service other nodes for confirmation and transactions.
Just a small query: Why do we need it behind the webserver? From the document, I understand that the Bitcoin core full node works for syncing the blockchain with other nodes and provides one more medium for confirmation, which the Bitcoin network can use. And yes this will not be for any kind of wallet services.
Also, can you please throw some light on some documents which can make me more aware of RPC?
Also, can you please throw some light on some documents which can make me more aware of RPC?
Among other things, Bitcoin Core does not use HTTPS, so all of the communication is, by default, exposed to third-parties. Although that part is not a big deal, there are some other reasons:
- Rate limiting, as I mentioned
- For security reasons, as a web server like Nginx or Apache is more hardened against security bugs so it can catch some of the exploits that might compromise Bitcoin Cora via the RPC port
- If you want to forward traffic to port 80
It makes it all very simple, really.
Hello
Thanks for your reply.
Just a small query: Why do we need it behind the webserver? From the document, I understand that the Bitcoin core full node works for syncing the blockchain with other nodes and provides one more medium for confirmation, which the Bitcoin network can use. And yes this will not be for any kind of wallet services.
Also, can you please throw some light on some documents which can make me more aware of RPC?
Thanks for your reply.
From my understanding of what you said, I'm guessing you want to run a Bitcoin Core node, not program one from scratch.
Well, basically, you'd need to open the RPC port and make it public (with no username/password). Then, use the command-line option to disable the wallet subsystem so people don't use it, and that's about it.
But you may want to put it behind a web server and use some rate-limiting inside so that it doesn't get overloaded.
Well, basically, you'd need to open the RPC port and make it public (with no username/password). Then, use the command-line option to disable the wallet subsystem so people don't use it, and that's about it.
But you may want to put it behind a web server and use some rate-limiting inside so that it doesn't get overloaded.
Just a small query: Why do we need it behind the webserver? From the document, I understand that the Bitcoin core full node works for syncing the blockchain with other nodes and provides one more medium for confirmation, which the Bitcoin network can use. And yes this will not be for any kind of wallet services.
Also, can you please throw some light on some documents which can make me more aware of RPC?
I'm guessing you want to run a Bitcoin Core node, not program one from scratch, form my understanding of what you said.
Well basically, you'd need to open the RPC port and make it public (with no username/password). And use the command-line option to disable the wallet subsystem so people don't use it, and that's about it.
But you may want to put it behind a web server and use some rate-limiting inside so that it doesn't get overloaded.
Well basically, you'd need to open the RPC port and make it public (with no username/password). And use the command-line option to disable the wallet subsystem so people don't use it, and that's about it.
But you may want to put it behind a web server and use some rate-limiting inside so that it doesn't get overloaded.
Hello
Thanks for your reply.
I am in no hurry. I will wait for appropriate answers from whoever helps.
In terms of services, this full node would be available for all kinds of blockchain services for the network and community. I plan to keep this online 24/7, and connectivity would be 1 GBPS, so there would be no network issues. The network would be open to all as Bitcore, so other Bitcore full nodes can sync. Yes, as of now, as planned, this will be only the Bitcore node's full node. But you can help add more features if required, as I am sure the set of hardware is powerful enough to provide those services.
Thanks for your reply.
I am in no hurry. I will wait for appropriate answers from whoever helps.
In terms of services, this full node would be available for all kinds of blockchain services for the network and community. I plan to keep this online 24/7, and connectivity would be 1 GBPS, so there would be no network issues. The network would be open to all as Bitcore, so other Bitcore full nodes can sync. Yes, as of now, as planned, this will be only the Bitcore node's full node. But you can help add more features if required, as I am sure the set of hardware is powerful enough to provide those services.
Hi, welcome to the forum.
First of all, there aren't many programmer or people who use full node software besides Bitcoin Core in this forum. So don't expect detailed reply soon.
What kind of support you're going to provide? Just running "Bitcore Node" feature where you run Bitcoin full node?
First of all, there aren't many programmer or people who use full node software besides Bitcoin Core in this forum. So don't expect detailed reply soon.
I am Bhavin Patel from India. I wanted to implement a Full Bit Core node to support the Bitcoin community. This node will be hosted on the cloud and will be available to the community for use in Bitcoin processes.
What kind of support you're going to provide? Just running "Bitcore Node" feature where you run Bitcoin full node?
Hello To Bitcoin Family,
I am Bhavin Patel from India. I wanted to implement a Full Bit Core node to support the Bitcoin community. This node will be hosted on the cloud and will be available to the community for use in Bitcoin processes.
While reviewing resources and articles on Bitcore implementation and tech details, it was advised to seek ideas and tech information from respected community members on 1. security advice, 2. security implementation, 3. do's and don'ts about implementation, 4. server specification, and 5. Are there any other guidelines that will help implement and make robots secure Bitcore on the cloud?
I am a tech guy, so I can understand all aspects of implementation, security, hardware, software, etc. As a tech enthusiast and supporter of cryptocurrencies, I want to do this to support the community.
I will bear the cost of implementation operations and ongoing maintenance.
So, I request all family members of the Bitcoin community to please advise on the above points.
Thanks in advance to all my Bitcoin family members.
Regards,
Bhavin Patel
I am Bhavin Patel from India. I wanted to implement a Full Bit Core node to support the Bitcoin community. This node will be hosted on the cloud and will be available to the community for use in Bitcoin processes.
While reviewing resources and articles on Bitcore implementation and tech details, it was advised to seek ideas and tech information from respected community members on 1. security advice, 2. security implementation, 3. do's and don'ts about implementation, 4. server specification, and 5. Are there any other guidelines that will help implement and make robots secure Bitcore on the cloud?
I am a tech guy, so I can understand all aspects of implementation, security, hardware, software, etc. As a tech enthusiast and supporter of cryptocurrencies, I want to do this to support the community.
I will bear the cost of implementation operations and ongoing maintenance.
So, I request all family members of the Bitcoin community to please advise on the above points.
Thanks in advance to all my Bitcoin family members.
Regards,
Bhavin Patel
Jump to: