API Restructure

[n8maninger]

• Adds a bit more structure to wallets and wallet addresses with the goal of making usage between implementations more consistent.
  • Wallets now have a unique ID, friendly name, and description for easier updating.
  • Addresses (optionally) support storing their spend policy
• Splits the SC and SF utxo endpoints
• Adds pagination to the SC and SF utxo endpoints
• Returns 404 errors on all the wallet endpoints if the wallet does not exist

[lukechampine]

Good stuff. What's the motivation for names->IDs, especially int64? Is it a sqlite thing?

[n8maninger]

Good stuff. What's the motivation for names->IDs, especially int64? Is it a sqlite thing?

name -> ID makes it possible to later change the name and keep the other wallet data consistent. The UI currently generates a UUID as the name and adds an additional friendlyName to metadata. This enforces that flow for all consumers.

I don’t really have a preference on the type. Int64 is easy and supported by every db I’m aware of. We could also use a UUID or frand.Entry128().String(). As long as it’s unique and set by walletd

[lukechampine]

Ok. Let's at least define a distinct WalletID type for it.