Haad

I believe what @coyotespike writes above is the solution here. @maroodb any updates? Did you manage to get it working?

@maroodb great to hear it's now working for you! @adrprado sound like you're experiencing a different problem and I'd love to understand why it's not working. Specifically this part sounds...

Related https://github.com/orbitdb/orbit-db/issues/352.

Sorry for the delay in answering @bronger. You got it almost right! Every node maintains a chain of DB entries *per database*, ie. only the entries of the database their...

orbit-db has *strong eventual consistency*. If all nodes have all the updates (ie. the same head and they have fetched all the database entries), then yes, they all have the...

> Node A publishes a new HEAD_A first, and Node B merges it with their current head (it must merge, because both histories diverged), which results in HEAD_B. From the...

The log in orbit-db is a CmRDT. Each update to the database (state modification) is its own operation in the log. The merge is indeed commutative, associative and idempotent and...

@coyotespike this is a great idea and something I've been thinking about for long time never having the time to implement. We always needed such "bootstrappers" (always available nodes that...

@raptortech-js that's the idea, yeah! Currently all databases are in the public network and open to anyone. Obviously this is not what we want and we're working on IPFS primitives...

Thanks @dbeecham for jumping in! 😄 👍 I was thinking the UX would be, that you start the OrbitDB daemon with the CLI: ``` orbitdb daemon ``` The CLI command...