| ibgib is a dlt protocol i've worked on for over 20 years now. it focuses on evolving timelines in spaces, similar to a "semantic version control" system. it is most easily thought of in terms of existing technology, as a combination of git and ipfs+ceramic, but more generalized than git (no root repository, more self-similar in that data and metadata live alongside each other so no .git folder and non-object artifacts), and more of a focus on time than ipfs. note: interestingly, ibgib's design is more like ipfs than any other technology. i'm not positive on the timeline, but when i first became aware of ipfs, i had already built my first alpha of the protocol. instead of mapping to a filesystem-like internal document structure, with a token to denote a link, i had designed ibgib's interface to have the four fields it has today. this gave me both named edges (in graph terms), whereas ipfs was still using unnamed edges (thinking only hierarchically like a filesystem paradigm), as well as an intrinsic always-copy data that was a separate object. this highlights the difference between extrinsic, reference-based relationships and intrinsic value data. (i think this ultimately is a schema decision that could be swappable in the future.) |