Enable PDP
This page explains how to enable PDP in Curio.
Last updated
This page explains how to enable PDP in Curio.
Last updated
Proof of Data Possession (PDP) is a new component of the Filecoin ecosystem, designed to work alongside Proof of Replication (PoRep). While PoRep ensures that data is securely stored and uniquely encoded, PDP focuses on verifying that data is accessible at specific points in time. Here’s a breakdown of what PDP does:
Periodic Accessibility: PDP checks that data is available when needed, ensuring it’s stored and accessible at regular intervals.
Efficient Retrieval: Unlike PoRep, PDP operates on unencoded data, making it faster to retrieve without the need for decoding the data.
Lightweight Verification: PDP’s proving process is computationally efficient and doesn’t require heavy resources like GPUs.
PDP is particularly useful for applications where data needs to be accessed frequently, such as in hot storage scenarios. It ensures that storage providers maintain accessible copies of data without the overhead of constant decoding. This makes PDP a valuable tool for improving retrieval efficiency on Filecoin.
It’s important to note that while PDP is a supporting element of efficient retrieval, it doesn’t guarantee retrieval; malicious storage providers could still deny service. Additionally, PDP complements, rather than replaces, PoRep, as it does not guarantee data replication or incompressibility — both essential for storage-based consensus.
You can read more about PDP .
In one of the configuration layer used by Market nodes, please enable the following tasks and restart the node.
After the service configuration is complete, please start the Curio node using the systemd and verify that GUI is accessible.
Go to Curio UI at https://<curio node IP>:4701 and click on "Configurations" in the menu. Click on the layer named "base" and update the following configurations.
Set a Domain Name:
Ensure that a valid DomainName is specified in the HTTPConfig. This is mandatory for proper HTTP server functionality and essential for enabling TLS. The domain name cannot be an IP address.
In case DelegateTLS is False , the domain name must point to the public IP address your curio node is listening on. The purpose of setting this field is to allow lets encrypt ACME protocol to automatically issue a certificate to use TLS for encrypting access to the curio api. For let's encrypt policy reasons this will only work if curio listens on port 443.
Domain name should be specified in the base layer
HTTP Configuration Details:
If TLS is managed by a reverse proxy, enable DelegateTLS in the HTTPConfig to allow the HTTP server to run without handling TLS directly.
Configure additional parameters such as ReadTimeout, IdleTimeout, and CompressionLevels to ensure the server operates efficiently.
Save the layer with the changes.
Add a new layer with name "pdp" and update the following configuration.
Enable the Deal Market:
Set EnableDealMarket to true in the CurioSubsystemsConfig for at least one node. This enables deal-making capabilities on the node.
Enable CommP:
Set EnableCommP to true. This allows the node to compute piece commitments (CommP) before publishing storage deal messages.
Enable PDP:
Set EnablePDP to true. This will allow the nodes to run PDP related tasks.
Enable ParkPiece:
Set EnableParkPieceto true. This will enable the nodes to download the remote data and save it locally.
Save the layer with changes.
Add a new layer called "http".
Enable HTTP:
To enable HTTP, set the Enable flag in the HTTPConfig to true and specify the ListenAddress for the HTTP server.
If you have more than one node in the cluster, you should enable HTTP server only on one of those nodes unless you plan to load balance with a reverse proxy.
Now, we have all the required configuration layers in place, we can start the nodes with required configuration. Update the /etc/curio.envfile and add the PDP layers.
The layer "http" should only be added to one node if cluster has multiple nodes and TLS is not delegated.
To interact with the PDP smart contracts the Curio SP must import a private key owning their PDP proof sets.
Obtain private key bytes
In the Curio web UI (localhost:4701) navigate to PDP and click "Import Key"
Paste key bytes
There are many ways to obtain key bytes. Any method of exporting an ETH private key will work. Filecoin native address private keys can be extracted with
To interact with the Curio PDP api clients need to have authentication to access a PDP API Service. PDP SPs must create PDP Services for clients to use their API. Here is the creation flow.
Client creates a local authentication token offline, they then send PEM public key to curio PDP SP
In the Curio web UI (localhost:4701) navigate to PDP and click "Add Service"
Fill out service name (i.e. clientX) and paste their public key
Curio provides a client utilty which can be used by clients to onboards the data with PDP providers.
To build the client binary, clone the Curio repo and build the PDP client.
The pdptool command contains utilities for uploading files to a curio node and interacting with the pdp contract to create proofsets, and add and remove roots from proofsets.
Once the curio node has imported the service public key you can check that you are able to connect with
Upon success you can start proving files on PDP.
Once done, please proceed with and configuration.
Get familiar with .
with a new Curio cluster.
Since, this cluster will be dedicated to PDP, you can install Curio using the when PDP feature is available as part of a release. Till then, you need to manually .
Once Curio is installed, proceed to and . This new minerID will not be used by PDP but we need to initiate it as Curio is designed to function with at least one miner ID. As part of initiating a new cluster, you will start the Curio process and the from there. Update the /etc/curio.envfile and remove the post layers.
Start the Curio nodes and to store the PDP files.
To get started using pdptool to access the curio API as a client you will need to create a service authentication secret for accessing the API. To do this run pdptool create-service-secret. This will display the public key for sending to the curio node for . Additionally it will write a file pdpservice.json that contains a PEM encoded private key for API authentication. pdptool can be used without any extra steps if run in the same directory as this file.