description:
Surfpool is a command-line tool for working with Solana-based deployments and other blockchain runtimes. It integrates with the Solana CLI ecosystem and relies on shared configuration and keypair files managed by Solana tooling.
upstream-relation: I am the upstream developer and publisher of the snap.
interfaces:
personal-files:
request-type: auto-connection
reasoning: surfpool is a CLI tool that interoperates with the Solana CLI and requires access to the user’s Solana keypair stored in ~/.config/solana/id.json. This file is essential for signing blockchain transactions, and users expect this to work without extra manual steps.
I previously asked for access to classic confinement, but was instead directed to setup the personal-files plug and request auto-connection.
The default case will be for ~/.config/solana/id.json, but users will often have multiple id’s. For example a ~/.config/solana/devnet_id.json, ~/.config/solana/mainnet_id.json. They really can configure this to be wherever they want, but the most common case will be in the ~/.config/solana/* folder
@txtx_svc - So the snap never needs to write anything to this ~/.config/solana/* dir and just needs to be able to read from it automatically? #askForInfo
@txtx_svc - Please let me know once you upload a revision of the snap that contains the personal-files interface requested and I’ll go ahead and make the changes live! Thanks