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
In the Seraphis library there is the struct jamtis_mock_keys. It holds a number of keys, some secret, some public, including the most important of them all, "the" key k_m. The header file containing it is here.
The "mock" in the filename and its location in a folder that also contains "mocks" usually means that it's part of the testing framework and thus not part of the "production code".
I could not find another similar struct in the Seraphis library that is part of the normal code.
I see this as a possible job that somebody could pick up: Check whether we need something like that as part of normal code, e.g. as base for reading and writing keys in the wallet, and if yes, find out how that struct should look, and what relationship there would be with jamtis_mock_keys.
Is a simple copy of that struct, under a different name, in a different location, the proper way to go? Or does a wallet need a new struct for itself that maybe the Seraphis library proper hasn't even a need for?
The text was updated successfully, but these errors were encountered:
In the Seraphis library there is the struct
jamtis_mock_keys
. It holds a number of keys, some secret, some public, including the most important of them all, "the" keyk_m
. The header file containing it is here.The "mock" in the filename and its location in a folder that also contains "mocks" usually means that it's part of the testing framework and thus not part of the "production code".
I could not find another similar struct in the Seraphis library that is part of the normal code.
I see this as a possible job that somebody could pick up: Check whether we need something like that as part of normal code, e.g. as base for reading and writing keys in the wallet, and if yes, find out how that struct should look, and what relationship there would be with
jamtis_mock_keys
.Is a simple copy of that struct, under a different name, in a different location, the proper way to go? Or does a wallet need a new struct for itself that maybe the Seraphis library proper hasn't even a need for?
The text was updated successfully, but these errors were encountered: