Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
  • galacteek galacteek
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 9
    • Issues 9
    • List
    • Boards
    • Service Desk
    • Milestones
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • galacteekgalacteek
  • galacteekgalacteek
  • Issues
  • #1
Closed
Open
Issue created Sep 20, 2021 by cipres@cipresOwner

Ideas to improve pronto

pronto is a new galacteek protocol that uses linked data to build a distributed RDF graph using an ontological chain system.

When a new object is recorded, it is signed and chained with URIs in what's called an ontolochain. Chains are synced via SparQL over IPFS streams. Chain sync status is also stored in the history RDF store.

The most obvious issues:

  • If an ontolochain record is lost, the synchronization of this chain is compromised (we only keep pointers to the previous object/block)

  • Scaling. Each node pulls everything it can from other nodes. While this makes content distribution almost instantaneous, this will not scale well, as rdflib (using bsddb or other backends) is really not the fastest RDF library there is.

  • Encryption. Encryption of all objects is not desirable but it will be supported. Using raw unencrypted DAGs makes things easier to study in the beginning as you can explore the raw IPLD from galacteek easily.

Will post an example of pronto's history graph so that things make more sense ..

Assignee
Assign to
Time tracking