Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

sc-keystore: Improve docs #3334

Merged
merged 1 commit into from
Feb 15, 2024
Merged

sc-keystore: Improve docs #3334

merged 1 commit into from
Feb 15, 2024

Conversation

bkchr
Copy link
Member

@bkchr bkchr commented Feb 15, 2024

Close: #3320

@Hugo-Trentesaux are these docs better for explaining the internals?

@bkchr bkchr added the R0-silent Changes should not be mentioned in any release notes label Feb 15, 2024
@bkchr bkchr requested a review from a team February 15, 2024 09:50
@bkchr bkchr enabled auto-merge February 15, 2024 11:13
@bkchr bkchr requested a review from skunert February 15, 2024 11:14
@bkchr bkchr added this pull request to the merge queue Feb 15, 2024
Merged via the queue into master with commit 150a360 Feb 15, 2024
134 of 135 checks passed
@bkchr bkchr deleted the bkchr-keystore-docs branch February 15, 2024 11:39
bgallois pushed a commit to duniter/duniter-polkadot-sdk that referenced this pull request Mar 25, 2024
Close: paritytech#3320

@Hugo-Trentesaux are these docs better for explaining the internals?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
R0-silent Changes should not be mentioned in any release notes
Projects
None yet
Development

Successfully merging this pull request may close these issues.

password-protected keystore with sc_keystore
3 participants