feat(cast) cast wallet new - enable default keystore

[radeksvarz]

Component

Cast

Describe the feature you would like

Currently the keystore must be explicitly declared if one wants to import new wallet key :

Usage: cast wallet new [OPTIONS] [PATH]

Arguments:
  [PATH]
          If provided, then keypair will be written to an encrypted JSON keystore

Proposal:
Add flag to import into default keystore when no PATH is given.

Additional context

No response

[kien6034]

i would like to work on this

[HenryTabima]

Tell us about your background and how it can be leveraged: *

I am a software engineer with over 8 years of experience, passionate about open-source software and Web3 development. As a member of the Dojo coding community, I am eager to begin contributing to this project.

How would you approach the problem?

To implement the feature of importing keys into a default keystore without explicitly specifying [PATH], I would:

1. Analyze Current Implementation: Understand how the cast wallet new command handles the [PATH] argument.

2. Add Default Behavior:

• Introduce a flag like --use-default to import keys into the default keystore when no [PATH] is given.
• If [PATH] is provided, keep the current behavior.
• Determine Default Location: Define a secure location for the default keystore (e.g., ~/.cast/keystore/). Ensure it's created if missing.

3. Validation and Error Handling: Handle cases like missing permissions or failed writes, with clear error messages.

4. Update Documentation: Modify help text and add examples for using the new default option.

5. Testing: Write tests to verify:

• Correct behavior with and without [PATH].
• Proper handling of default import, permissions, and edge cases.

[zerosnacks]

@kien6034 thanks! assigned this to you, let me know if you have any questions