Bitcoin core full node with S3 bucket #27168

issue Tharsanan1 openend this issue on February 27, 2023
  1. Tharsanan1 commented at 6:57 am on February 27, 2023: none

    Is your feature request related to a problem? Please describe. I am trying to run a bitcoin full node on a aws ec2 instance. The problem is when allocating ssd, the cost is too much. The cost for S3 storage is really low. Since bitcoin total block chain size is increasing every day it is better if we can use these kind of services. As I understand frequency for a full node to get the old data is relatively low.

    Describe the solution you’d like I suggest, we should be able to configure how we store the blocks. One possible way is storing the data and fetching the data using REST calls. In this approach bitcoin core will not worry about how blocks are stored and where. Whenever it gets a new block it will invoke a POST http call to the confgured url and save it. Whenever it needs a old block data it will do a GET call to the server using the configured url. This way individuals can develop their own version of servers that will use different type of storage services. The REST approach is just a suggestion we can implement anything that let us configure to use different type of storage mechanisms.

    One of the main argument against bitcoin is: Because of the growing blockchain size it will become impossible to run a full node by an average individual. With this kind of feature we can use very cost effective solutions for data storage.

  2. Tharsanan1 added the label Feature on Feb 27, 2023
  3. glozow commented at 8:12 am on February 27, 2023: member
    Alternatively, could you try running with -prune to reduce the amount of disk space needed for block storage?
  4. hebasto commented at 9:15 am on February 27, 2023: member

    NACK on any feature which allows to delegate a block storage to a third-party.

    It will create an opportunity for an adversary to alter block data, which being served to other peers will create a spam network traffic. That is, essentially, an attack on the Bitcoin network.


    In addition to the mentioned option, one can use -blocksdir option to manage a block storage location.

  5. fanquake closed this on Feb 27, 2023

  6. bitcoin locked this on Feb 27, 2024

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2025-01-15 06:12 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me