Knowledge submission & curation

Staging Paranet is the process of submitting a Knowledge Collection (KC) for approval before it becomes part of the paranet. Curators review and either approve or reject the KC to ensure data accuracy and quality before it's added to the network.

Knowledge collection(KC) is a collection of knowledge assets. It refers to structured data that can be stored, shared, and validated within a distributed network.

In order to maintain data integrity and prevent malicious or irrelevant information from being added, the paranet system includes permission controls that regulate who can submit and approve new data entries.

Here's the demo code for a staging paranet.

Why is KC management important?

In decentralized networks, anyone can technically contribute data, but not all data should be trusted. Without a system for validation, there is a risk of:

• Spam or false data being introduced into the network.

• Duplicate or low-quality data reducing the efficiency and reliability of the system.

• Unauthorized modifications that could disrupt the credibility of shared knowledge.

To prevent these issues, paranet uses a curator-based system, where only authorized users (curators) can decide which knowledge assets get added to the network.

How does KC submission work?

1. A miner creates a collection of knowledge assets(KC) — This is structured data (e.g., city information, scientific research, metadata, etc.) that is prepared for submission.

2. The KC is staged to the paranet — This means it is submitted for approval but is not yet officially part of the paranet.

3. A curator reviews the submission — The curator has the authority to either accept or reject the KC.

4. If approved, the KC is officially submitted and becomes part of the paranet network. If rejected, the KC does not get added, and the user must make changes or submit a different KC.

This structured approach ensures that only reliable and relevant data is added to the network while maintaining a decentralized governance model.

When creating a paranet, we can define permissions for:

• Nodes – who can join the network. (Not added yet)

• Miners – who can validate data. (Not added yet)

• KC submissions – who can add a new collection of knowledge assets.

Adding a curator

A curator is a user who decides which collection of knowledge assets (KC) are accepted or rejected. Curators are added using their address, and they control the approval of new data within the Paranet.

Add a curator:

DkgClient.paranet.addCurator(paranetUAL, PUBLIC_KEY);

Remove a curator:

DkgClient.paranet.removeCurator(paranetUAL, PUBLIC_KEY);

Check if a user is a curator:

isCurator = await DkgClient.paranet.isCurator(paranetUAL, PUBLIC_KEY);
console.log('Is user a curator?', isCurator);

Staging — Submitting KC to a paranet

When a knowledge collection (KC) is staged, it must go through the staging process before being officially added to the paranet. This means the KC is submitted for review, and the curator decides whether to accept or reject it.

Create a new knowledge collection(collection of knowledge assets):

jsCopyEditconst content = {
    public: {
        '@context': 'https://www.schema.org',
        '@id': 'urn:us-cities:info:dallas',
        '@type': 'City',
        name: 'Dallas',
        state: 'Texas',
        population: '1,343,573',
        area: '386.5 sq mi',
    }
};

const createKcResult = await DkgClient.asset.create(content, { epochsNum: 2 });
console.log('Knowledge Collection Created:', createKcResult);

Stage KC to the paranet (submit for approval):

stageToParanetResult = await DkgClient.paranet.stageKnowledgeCollection(
    createKcResult.UAL,
    paranetUAL,
);
console.log('Knowledge Collection Staged to Paranet:', stageToParanetResult);

Check if KC is staged for approval:

isStaged = await DkgClient.paranet.isKnowledgeCollectionStaged(createKcResult.UAL, paranetUAL);
console.log('Is KC staged to Paranet?', isStaged);

Reviewing and approving KC

A curator can accept or reject a knowledge collection:

Reject a KC:

DkgClient.paranet.reviewKnowledgeCollection(createKcResult.UAL, paranetUAL, false);
console.log('Knowledge Collection Rejected');

Accept a KC:

DkgClient.paranet.reviewKnowledgeCollection(createKcResult.UAL, paranetUAL, true);
console.log('Knowledge Collection Approved');

Check approval status:

approvalStatus = await DkgClient.paranet.getKnowledgeCollectionApprovalStatus(createKcResult.UAL, paranetUAL);
console.log('KC Approval Status:', approvalStatus);

Check if KC is registered:

isRegistered = await DkgClient.paranet.isKnowledgeCollectionRegistered(createKcResult.UAL, paranetUAL);
console.log('Is KC registered to Paranet?', isRegistered);

Conclusion

• Curators manage which KC entries get accepted to a paranet. Users who wish to submit data to a paranet must go through the staging process.

The curator doesn't have to be human, it can also be an AI agent.

• KC must first be submitted for approval, and then the curator can accept or reject it.

• All operations are tied to the user's public key, enabling secure and decentralized data management. 🚀