You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On a network level promoted sign of wotstore are a disaster:
when running an accept of wotaccess and querying for promoted sign, subsequent n query reply are send to get actual peersign because promoted sign only return key to the sign.
TODO : Promoted sign should keep being stored with key of peersign only, yet when sent it should resolve and include its peersign.
This could not be achieve easyly with specific keyval serialization, (serialize would require a reference of another kvstore to encode ...), so the best things would be to have a keyval type for storage (the current one) and a keyval type for sending (with peersign included). Both keyval with the same keys obviously.
Plus rewrite promsign function to run as mutable!!!!
The text was updated successfully, but these errors were encountered:
On a network level promoted sign of wotstore are a disaster:
when running an accept of wotaccess and querying for promoted sign, subsequent n query reply are send to get actual peersign because promoted sign only return key to the sign.
TODO : Promoted sign should keep being stored with key of peersign only, yet when sent it should resolve and include its peersign.
This could not be achieve easyly with specific keyval serialization, (serialize would require a reference of another kvstore to encode ...), so the best things would be to have a keyval type for storage (the current one) and a keyval type for sending (with peersign included). Both keyval with the same keys obviously.
Plus rewrite promsign function to run as mutable!!!!
The text was updated successfully, but these errors were encountered: