Skip to content
This repository has been archived by the owner on Dec 18, 2024. It is now read-only.

Replication conditions #70

Open
nezzard opened this issue Sep 25, 2018 · 3 comments
Open

Replication conditions #70

nezzard opened this issue Sep 25, 2018 · 3 comments

Comments

@nezzard
Copy link

nezzard commented Sep 25, 2018

Hi, is there any possibilities for make conditions for accepting new entry?

For example
if(newEntry != true) {
return false
} ellse {
addNewEntry
}

The main idea is, if new entry has incorrect signature, then don't add entry to own copy of public db

@m00nwtchr
Copy link

m00nwtchr commented Oct 3, 2018

if the db is public you can do something even better: Prevent tampering by fixing/removing the entry. this won't work if your database is a EventStore but it should work in the case of all the others. you can do your checks in the replicated event: https://github.com/orbitdb/orbit-db/blob/master/API.md#replicated

@nezzard
Copy link
Author

nezzard commented Dec 9, 2018

checks in the replicated event

It's ok, but, how to prevent adding entry inside replicate event?
Can i break this entry? If yes how? And after that, will db continue replication?

Or i need to remove wrong entry after replication?

@aphelionz
Copy link
Collaborator

Moving this to the Field Manual so we can go into more detail

@aphelionz aphelionz transferred this issue from orbitdb/orbitdb Sep 27, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants