RE: RE: Update on BlockTrades Hive Work (Nov 25th)
You are viewing a single comment's thread from:

RE: Update on BlockTrades Hive Work (Nov 25th)

Words
72
Reading
1 min
6y

It's a known issue with hivemind. Hivemind runs two blocks behind hived to avoid microforks, because it doesn't know how to handle fork resolution properly (it never has).

Part of the change we're working on with the hived plugin mentioned above should allow us to enable hivemind to support fork resolution properly, which will allow hivemind to finally serve "real-time" data. This will also be very important for 2nd-layer apps in general.

@blocktrades: It's a known | Ecency