replicatedevent: indeed, this is now sent only when the db has been (fully) replicated. in fact, the previous behaviour wasn't intended (replicated events "chunked"). however, if I understand the need described above, you want to be able to "know when some progress of replication has been made" and the
replicate.progressevent will give you that (see https://github.com/orbitdb/orbit-db-store/blob/main/src/Store.js#L100 for the callback signature and params). it's emitted for each replicated db log entry. with that, you can eg. show a nice progress bar, or hook to it to show the replicated data to the user. note though that when
replicate.progressis fired, the DB index hasn't been updated yet with the replicated data.