Upgrading IPFS for Enterprise with SHA3 Encryption
GhostDrive, our innovative Layer 2 solution, is geared to enhance the IPFS and Filecoin networks by offering a high-level digital asset management system. It harnesses the strength of four major blockchains - Ethereum (ETH), Filecoin (FIL), and Polygon (Matic), ensuring a thorough and efficient platform for users to manage their digital assets, files, and objects.
At present, we are offering full support for installation within Docker and limited support for installation on a Linux machine (including RHEL, CentOS, Debian, Ubuntu). We're actively working on automating the Linux installation process and broadening our support to include both Windows and macOS.
IPFS requires 512MiB of memory and can run an IPFS node on a Raspberry Pi. However, how much disk space your IPFS installation takes up depends on how much data you're sharing. A base installation takes up about 12MB of disk space, and the default maximum disk storage is set to 10GB. IPFS can run on most Linux, macOS, and Windows systems. We recommend running it on a machine with at least 2 GB of RAM and 2 CPU cores (go-ipfs is highly parallel). On systems with less memory, it may not be completely stable. We also highly recommend running it on an SSD, preferably on Gen4+ NVMe SSD of any vendor.
If your system is resource-constrained, we recommend initializing your daemon with ipfs init --profile=lowpower
.
For this, you'll need to replace the line 7 of setup.sh
with the command above.
• CPU 12 cores / 24 threads, or more, 2.8GHz, or faster AVX2 instruction support (to use official release binaries, self-compile otherwise) Support for AVX512f and/or SHA-NI instructions is helpful The AMD Zen3 series is popular with the validator community
• RAM 128GB, or more
• Motherboard with 256GB capacity suggested
• Disk PCIe Gen3/4 NVME SSD Accounts: 500GB, or larger. High TBW (Total Bytes Written) Ledger: 64TB or larger. High TBW suggested
• OS: (Optional) 10GB, or larger. SATA OK The Samsung 970 and 980 Pro series SSDs are popular with the validator community
• GPUs Not strictly necessary at this time Motherboard and power supply speed to add one or more high-end GPUs in the future suggested
bash <(curl -s https://raw.githubusercontent.com/docker/docker-install/master/install.sh) && \
bash <(curl -s https://raw.githubusercontent.com/Ghost-Drive/ghost-node/main/get-gxd-docker.sh)
OR
bash <(wget -qO - https://raw.githubusercontent.com/docker/docker-install/master/install.sh) && \
bash <(wget -qO - https://raw.githubusercontent.com/Ghost-Drive/ghost-node/main/get-gxd-docker.sh)
You will be prompted for a node name in the middle of the setup process. If no name is provided, the hostname of the machine the script is launched on will be taken.
A precompiled docker image is available for download at https://hub.docker.com/r/ghost/ghost-ipfs-node
Alternatively, if you wish to manually build the Docker file, clone the project and simply run:
docker build -t ghost-ipfs-gen4-node ./docker
...
...
IPFS has an updating tool that can be accessed through ipfs update
. The tool is
not installed alongside IPFS in order to keep that logic independent of the main
codebase. To install ipfs update
, download it here.
List the available versions of go-ipfs:
$ ipfs cat /ipns/dist.ipfs.io/go-ipfs/versions
Then, to view available builds for a version from the previous command ($VERSION):
$ ipfs ls /ipns/dist.ipfs.io/go-ipfs/$VERSION
To download a given build of a version:
$ ipfs get /ipns/dist.ipfs.io/go-ipfs/$VERSION/go-ipfs_$VERSION_darwin-386.tar.gz # darwin 32-bit build
$ ipfs get /ipns/dist.ipfs.io/go-ipfs/$VERSION/go-ipfs_$VERSION_darwin-amd64.tar.gz # darwin 64-bit build
$ ipfs get /ipns/dist.ipfs.io/go-ipfs/$VERSION/go-ipfs_$VERSION_freebsd-amd64.tar.gz # freebsd 64-bit build
$ ipfs get /ipns/dist.ipfs.io/go-ipfs/$VERSION/go-ipfs_$VERSION_linux-386.tar.gz # linux 32-bit build
$ ipfs get /ipns/dist.ipfs.io/go-ipfs/$VERSION/go-ipfs_$VERSION_linux-amd64.tar.gz # linux 64-bit build
$ ipfs get /ipns/dist.ipfs.io/go-ipfs/$VERSION/go-ipfs_$VERSION_linux-arm.tar.gz # linux arm build
$ ipfs get /ipns/dist.ipfs.io/go-ipfs/$VERSION/go-ipfs_$VERSION_windows-amd64.zip # windows 64-bit build
- As IPFS default WebUI is shipped via the public IPFS network, it is not available out-of-the-box in our GhostCloud private IPFS network. If you need to use it, it can be separately installed from the https://github.com/ipfs/ipfs-webui
FOR SP PROVIDERS // KYC is required, please email us directly: [email protected]
Typical 4-node NVM + GPU installation
- Rack 24U 1x
- Supermicro 2U GPU Lines server 4x
- Intel Xeon LGA-4189 16-core processor 4x
- NVMe SSD 4Tb Gen 3/4 2.5” hot swap drive 16x
- GPU PNY NVIDIA A40 48GB – 4x
- HPE FlexNetwork 5130 HI Switch Series 1x
- Accessories