Currently supported features
- (CLI Only): daemon
- (CLI Only): Initialize pinza repo
- Adding IPFS files to cluster
- Removing IPFS files from cluster
- Listing pins in cluster
- Creating cluster
- Joining cluster
- Leaving cluster* - Potential data removal conflict if IPFS data belongs to multiple clusters
- Listing clusters
- List commitment
- Pins committed/allocated to local node. Calculated based off replication factor, number of nodes in network, number of pins. The mathematically closest pins by CID are the first to be stored (highest priority). Closeness is calculated via
k-bucket, which usesxor-distanceunder the hood. The local node's NodeId is compared against, meaning each unique node by nodeId has a completely different commitment/allocated pins. More information and proper explanation will be available in the future
- Pins committed/allocated to local node. Calculated based off replication factor, number of nodes in network, number of pins. The mathematically closest pins by CID are the first to be stored (highest priority). Closeness is calculated via
- Exporting cluster pinset - Exporting Pinset as a CBOR file or JSON file or raw JSON object (JS Client only)
- Import cluster pinset* - Imports pinset from CBOR file or JSON file, or raw JSON object (JS Client only)
* Not fully tested or supported in this version.