Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Secure keybase via hardware-backed encryption (iOS Secure Enclave / Android Keystore)
Summary
This PR secures the Gno keybase by encrypting keys using a hardware-backed private key that lives in the platform keystore:
To enable this, the
gnonativeframework now implements thegnoDB interface.Only the primitive DB operations are bridged to native code (Swift/Kotlin) via a
NativeDBManager, which talks to the Keychain/Keystore forget/set/delete...of raw byte keys and values. Higher-level logic stays in Go.Design
DB interface split:
[]bytein/out).Iterator protocol:
Because the Go↔native bridge can only exchange primitive values, iteration is done in chunks.
Go calls
scanChunk(...)repeatedly; native returns a single blob that aggregates multiple key/value pairs.scanChunknative functions return this blob format: