Skip to content

Conversation

bznein
Copy link
Collaborator

@bznein bznein commented Aug 29, 2025

Before asking for reviews, here is a check list of the most common things you might need to consider:

  • updating the Changelog
  • writing unit tests
  • checking if your changes affect other coins or tokens in unintended ways
  • testing on multiple environments (Qt, Android, ...)
  • having an AI review your changes

@bznein bznein requested a review from Beerosagos August 29, 2025 12:44
bznein added 2 commits August 29, 2025 13:48
In order to have a single type of receiver for the struct, we need to
either have every method with a pointer receiver, or a value one. A
value one is not possible since GetOrAddKeystore needs to modify the
config.
A pointer one is also troublesome because AccountsConfig() returns a
value, so calls like b.AccountsConfig().Derive() or similar wouldn't be
possible.
At the same time AccountsConfig() can't be changed to return a pointer
because it needs to lock the accountsConfigLock and returning a pointer
would cause data races.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant