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
Since loki 8.x we don't use the argon encryption hashing anymore because it is way too heavy even on desktop and would just kill mobile. I think it's fine for Session to not support those -- owners who registered them can simply submit an update to the blockchain to update them to the new encrypted value.
Since loki 8.x we don't use the argon encryption hashing anymore because it is way too heavy even on desktop and would just kill mobile. I think it's fine for Session to not support those -- owners who registered them can simply submit an update to the blockchain to update them to the new encrypted value.
how can you tell how the record is encrypted?
You can infer it from the length: https://github.com/oxen-io/oxen-core/blob/dev/src/cryptonote_core/oxen_name_system.cpp#L1376
Here's the high-level overview:
https://github.com/oxen-io/oxen-core/blob/dev/src/cryptonote_core/oxen_name_system.cpp#L1269-L1278
and the actual implementation is here:
https://github.com/oxen-io/oxen-core/blob/dev/src/cryptonote_core/oxen_name_system.cpp#L1401
GitHub
The text was updated successfully, but these errors were encountered: