Define High Level Client APIs, improvements and account packets

[joshuef]

Account packet

• Decide what goes in the account packet
  • Files
  • Wallet
  • data labels? (can we allow for that later?)
  • SafeId (for later?)
  • other things?
• Decide on serialisation in the record.
• Create the data types for this.
• Decide how we want to manage encryption/storage. (Data stored at PK and signed to prove its allowed?)
• Decide how to generate this for users? (multi-word pass generated for folk? KISS)

Files System

We should start fleshing out higher level client APIs to properly handle fiilessytem and small data.

We want to:

• Easily keep some metadata
• Ensure small files are encrypted
• Decide how to properly handle keys for data (ie, register encryption. small file encryption; do small (<3 bytes) files just go in registers? are they encrypted using the account packet keys)
• Enable linked registers

Ideally:

• This would be simple but streamlined enough that FUSE integration should not be a big issue.

Other considerations?

If we make the account packet a key... could we derive some DNS around key finding to enable simple safe ids? (PK hash matching etc...)

[joshuef]

Related to #1103

[joshuef]

Badly linked commit there 🤦 .

This was not addressed by the above.