Python SDK for interacting with the OriginTrail Decentralized Knowledge Graph
OriginTrail Docs
·
View Demo
·
Report Bug
·
Request Feature
Disclaimer: Beta Version
Welcome to the beta version of our client! This software is currently in the beta testing phase, which means it is not the final release version. As a beta version, it may still contain bugs, undergo frequent updates, and have limited features. Important Points to Note:
Use at Your Own Risk: While we have made efforts to ensure the stability and reliability of the beta version, there is a possibility of encountering unexpected issues. Please use this software at your own risk.
Limited Support: As this is a beta release, our support resources may be focused on addressing critical bugs and gathering feedback from users. Therefore, support for beta versions may be limited compared to our stable releases.
Feedback Appreciated: Your feedback is invaluable to us. If you encounter any issues, have suggestions, or want to share your experiences with the beta version, please let us know. Your feedback will help us improve the software for the final release.
Not for Production Use: The beta version is intended for testing and evaluation purposes only. It is not recommended for use in a production environment where stability and reliability are crucial.
Table of Contents
OriginTrail Decentralized Knowledge Graph (DKG), hosted on the OriginTrail Decentralized Network (ODN) as trusted knowledge infrastructure, is shared global Knowledge Graph of Knowledge Assets. Running on the basis of the permissionless multi-chain OriginTrail protocol, it combines blockchains and knowledge graph technology to enable trusted AI applications based on key W3C standards.
The OriginTrail tech stack is a three layer structure, consisting of the multi-chain consensus layer (OriginTrail layer 1, running on multiple blockchains), the Decentralized Knowledge Graph layer (OriginTrail Layer 2, hosted on the ODN) and Trusted Knowledge applications in the application layer.
Further, the architecture differentiates between the public, replicated knowledge graph shared by all network nodes according to the protocol, and private Knowledge graphs hosted separately by each of the OriginTrail nodes.
Anyone can run an OriginTrail node and become part of the ODN, contributing to the network capacity and hosting the OriginTrail DKG. The OriginTrail node is the ultimate data service for data and knowledge intensive Web3 applications and is used as the key backbone for trusted AI applications (see https://chatdkg.ai)
Knowledge Asset is the new, AI‑ready resource for the Internet
Knowledge Assets are verifiable containers of structured knowledge that live on the OriginTrail DKG and provide:
- Discoverability - UAL is the new URL. Uniform Asset Locators (UALs, based on the W3C Decentralized Identifiers) are a new Web3 knowledge identifier (extensions of the Uniform Resource Locators - URLs) which identify a specific piece of knowledge and make it easy to find and connect with other Knowledge Assets.
- Ownership - NFTs enable ownership. Each Knowledge Asset contains an NFT token that enables ownership, knowledge asset administration and market mechanisms.
- Verifiability - On-chain information origin and verifiable trail. The blockchain tech increases trust, security, transparency, and the traceability of information.
By their nature, Knowledge Assets are semantic resources (following the W3C Semantic Web set of standards), and through their symbolic representations inherently AI ready. See more at https://chatdkg.ai
Discover Knowledge Assets with the DKG Explorer:
- python
>=3.10
- poetry
>=1.5.1
In order to use in the local environment, make sure to run the local DKG network.
Create virtual environment (you can choose any existing folder this command will create configurations and virtual env for python):
python3 -m venv /path/to/folder
Inside of previously generated folder you will find activate script in bin folder and run it:
source /path/to/folder/bin/activate
Install dependencies:
poetry install
Now you can run a demo example file (you need to have the local DKG network running):
python3 examples/demo.py
This roadmap outlines the goals for the first major release of the dkg.py
. Each section represents a stage in the development process and the features we plan to implement.
-
Requirement Analysis and Planning
- Define the project's scope
- Identify the core functionalities
-
Design
- Plan the library's architecture
- Establish coding standards
-
Setup Development Environment
- Setup development, testing and production environments
- Add pytest config
- Add mypy config
- Add tox config ?
- Setup Continuous Integration (CI) and Continuous Deployment (CD) pipeline
Feature | Status | Tests coverage |
---|---|---|
Get Allowance | 🟩 Completed | ❌ |
Set Allowance | 🟩 Completed | ❌ |
Increase Allowance | 🟩 Completed | ❌ |
Decrease Allowance | 🟩 Completed | ❌ |
Get Bid Suggestion | 🟩 Completed | ❌ |
Create | 🟩 Completed | ❌ |
Transfer | 🟩 Completed | ❌ |
Update | 🟩 Completed | ❌ |
Wait for finalization | 🟥 Not Started | ❌ |
Cancel update | 🟩 Completed | ❌ |
Burn | 🟩 Completed | ❌ |
Get | 🟩 Completed | ❌ |
Query | 🟩 Completed | ❌ |
Extend storing period | 🟩 Completed | ❌ |
Add tokens | 🟩 Completed | ❌ |
Add update tokens | 🟩 Completed | ❌ |
Get owner | 🟩 Completed | ❌ |
Experimental | 🟥 Not Started | ❌ |
- Write comprehensive documentation
- Provide examples and use-cases
- Review and finalize documentation
-
Beta Release
- Release a beta version for testing
- Gather and address feedback
-
Bug Fixes
- Identify and fix bugs
-
Final Testing and QA
- Perform comprehensive testing
- Ensure the library meets quality standards
Note: This roadmap is subject to changes. Each step will be accompanied by appropriate documentation, testing and code review to maintain the quality of the library.
Distributed under the Apache-2.0 License. See LICENSE
file for more information.
Contributions are what make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.
If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag "enhancement". Don't forget to give the project a star! Thanks again!
- Fork the Project
- Create your Feature Branch (
git checkout -b feature/AmazingFeature
) - Commit your Changes (
git commit -m 'Add some AmazingFeature'
) - Push to the Branch (
git push origin feature/AmazingFeature
) - Open a Pull Request
- web3.py: Basis for this project