What transport layer does the Hornets use to serialize and deserialize data? Does it allow data modeling (relationship)? I know IPFS uses Protobuff (or something similar called IPLD).
Hashed tree structures have a long open-source legacy. From the invention of Merkle Trees by Ralph Merkle in the 80s, later adopted by #bitcoin , to Git’s use of hashed DAGs and IPFS's implementation of Merkle DAGs for file storage. The evolution continues: https://github.com/HORNET-Storage/scionic-merkletree
Discussion
nostr:npub1t89vhkp66hz54kga4n635jwqdc977uc2crnuyddx7maznwfrpupqwra5h9 nostr:npub1u9e887ad8pl49cxgzqkuljxcxy89dtac7jkyuajnukxg6hu2hufqdjdsp7
Please, can some of you answer this question?
H.O.R.N.E.T. Storage uses CBOR for Scionic Merkle DAG Tree encoding and decoding, just like IPFS does with Merkle DAGs.
Both JSON and CBOR enable relationships and data modeling due to their schema-less nature. CBOR is one of the only binary formats that’s schema-less like JSON.
Libp2p has options for ProtoBuffs, but IPFS doesn’t use ProtoBuffs for their Merkle DAG encoding/decoding. H.O.R.N.E.T.S avoids the use of ProtoBuffs completely.
For networking, H.O.R.N.E.T.S. will support all libp2p transport options such as: WebSockets, TCP, WebRTC, and QUIC.
H.O.R.N.E.T.S. Networking library (under development) for developers aiming to build #nostr apps that interface with Scionic Merkle DAG Trees stored on Multimedia H.O.R.N.E.T. Relays.