Identity can offer users more control
A Bitknowledge ID is intended to reduce dependence on a purely rented profile inside a closed platform and make more user control possible.
Bitknowledge ID is the first practical layer of the project. Its aim is to offer a more durable identity anchor and a coherent way to attach records to that identity, while separating what should be public from what should remain private.
A Bitknowledge ID is intended to reduce dependence on a purely rented profile inside a closed platform and make more user control possible.
Public records can be referenced through decentralised storage so they remain inspectable and easier to preserve beyond a single hosting provider.
The system is intended to make it clearer which records are meant for publication and which are kept private or selectively shared.
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.
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.
Collaboration, provenance, and durable records all become easier to reason about when identity is not entirely dependent on one mutable platform account.
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.