Initial Product

Bitknowledge ID

Bitknowledge ID is the first practical layer of the project. Its aim is to give a person or organisation a durable identity anchor and a coherent way to attach records to that identity, while separating what should be public from what should remain private.

Ownership

Identity should belong to the user

A Bitknowledge ID is intended to be controlled by the person or entity it represents, not treated as a purely rented profile inside a closed platform.

Storage

Records can be linked through IPFS

Public records can be referenced through decentralised storage so they remain inspectable and easier to preserve beyond a single hosting provider.

Control

Public and private records stay distinct

The system should make it clear which records are intended for publication and which are kept private or selectively shared.

Plain-English Summary

What Bitknowledge ID is meant to do

  • Give users an identity base that is not reducible to a social media account or one vendor database.
  • Attach records to that identity so credentials, references, documents, and other materials can be organised coherently.
  • Support publication choices so some records can be openly referenced while others remain private.
Progressive Detail

How the model is intended to work

Public records

These are records meant to be referenced, inspected, or shared more widely. IPFS is relevant here because it provides a way to address content directly and preserve access paths more independently.

Private records

These are records a user may want attached to identity context without publishing openly. The distinction matters because privacy should be designed into the structure, not added as an afterthought.

Why identity comes first

Collaboration, provenance, and durable records all become easier to reason about when identity is not entirely dependent on one mutable platform account.

How this connects to the broader project

Bitknowledge ID is an entry point. It creates a practical base on top of which richer knowledge, archival, and federated interaction systems can later be built.