search

orbitdb / field-manual

The Offical User's Guide to OrbitDB
208 stars 43 forks source link

During the replication process, can I vet each entry individually before storing? #73

Closed distbit0 closed 2 years ago

distbit0 commented 5 years ago

Hi! I am interested in creating a network where nodes broadcast messages onto it and then the rest store them. I need to ensure though that a node can not just broadcast garbage messages that don't contain a POW in them.

Is there any way for nodes in orbitdb to "vet" all entries in their database before they are stored to ensure their validity?

Thanks

willemneal commented 5 years ago

By POW do you mean Proof of Work? Currently the only vetting in with write permissions (though there is work on adding to access control https://github.com/orbitdb/orbit-db/pull/383). Currently database is just a IPFS which lists the keys that have write permission to the log. Then each new entry that is not signed by the one of the keys listened is ignored by those who are synchronizing.

distbit0 commented 5 years ago

Hmm ok looks like I will need to make some modifications bto the library first for this 👍

RichardLitt commented 5 years ago

@picrypto Does that solve your question?

If you figure this out, I would love to see an example of what you've got working.

aphelionz commented 4 years ago

Moving to the Field Manual to go into more detail