Structure of Saved Policy Note about smartvaults HOT 4 CLOSED

Maybe something like this:

{
   "output_descriptor": "",
   "ui_metadata": {
          "xml": "<xml ...> </xml>",
          "keys": [key1, key2, key3, key4...]
   }
}

from smartvaults.

@yukibtc what is the structure of the policy that is saved as a note currently? Is it only the output descriptor?

Does it make sense to add something like ui_metadata which could store the above xml and key list? Then, if a client knows how to render it, like the Blockly client with the xml, or else it could ignore it.

from smartvaults.

The nostr public keys are already saved in the tags of the policy event (I can write a function to extract from tags easily).
Regarding the XML data, I don't know if is a good idea.
In general, is better to use JSON instead of XML (check here).

I think that is better to generate the blockly struct directly from the descriptor, like you have done in get policy command with termtree.
In this way, if I import the descriptor from, for example, a backup, the UI will be shown (this will not happen using the above solution).

I'll try to write a function to compose the blockly JSON from a descriptor.

https://developers.google.com/blockly/guides/get-started/web#importing_and_exporting_blocks

from smartvaults.

The one requirement that wouldn't be covered is that accounts can be added to the blockly area but not in the actual policy.

They show up in drop downs for keys but the miniscript may not contain that key. It's like for draft policies.

We also need to disable edits after the policy has received BTC, since it is needed to spend on that BTC and could be lost if edits are allowed.

from smartvaults.