#dev #cln
This morning Shahana reminded me of an idea we had earlier to create "categories" for commands, so runes can filter on that basis. But choosing the categories is a bit of a research project which we never got around to, so we sat down and did it: described using keywords of each documented command, then tried to come up with a list.
The original motivation was the "read-only" commando rune: originally it allowed all list commands, and the getinfo command, except not listdatastore because that gave you access to the master rune itself! That's no longer true, but the point stands: some commands are read-only but reveal information which could allow escalation. ,(This is why when we added the command to list runes we called itshowrunes, not listrunes!).
When plugins add commands, you want it to be intuitive. If a rune allows the pay command, that won't allow "mpay" for example: the rune probably wants to say "you can send lightning payments" and cover all the commands that are needed, or can be used, to do that.
Anyway, the exercise resulted in a first list of categories, which we will play with as we implement: they need to be in documentation, as well as accessable to runes. And Shahana suggested the term "genus" (well , genera) instead of "category".
Rusty Russell
npub179e…lz4s
2024-05-31 14:08:48
Author Public Key
npub179e9tp4yqtqx4myp35283fz64gxuzmr6n3yxnktux5pnd5t03eps0elz4sPublished at
2024-05-31 14:08:48Event JSON
{
"id": "bd851e41026d0252d1f4f971be28d20b0371d9082578b6a4976b81078173e6b5",
"pubkey": "f1725586a402c06aec818d1478a45aaa0dc16c7a9c4869d97c350336d16f8e43",
"created_at": 1717157328,
"kind": 1,
"tags": [
[
"t",
"dev"
],
[
"t",
"cln"
]
],
"content": "#dev #cln\n\nThis morning Shahana reminded me of an idea we had earlier to create \"categories\" for commands, so runes can filter on that basis. But choosing the categories is a bit of a research project which we never got around to, so we sat down and did it: described using keywords of each documented command, then tried to come up with a list. \n\nThe original motivation was the \"read-only\" commando rune: originally it allowed all list commands, and the getinfo command, except not listdatastore because that gave you access to the master rune itself! That's no longer true, but the point stands: some commands are read-only but reveal information which could allow escalation. ,(This is why when we added the command to list runes we called itshowrunes, not listrunes!).\n\nWhen plugins add commands, you want it to be intuitive. If a rune allows the pay command, that won't allow \"mpay\" for example: the rune probably wants to say \"you can send lightning payments\" and cover all the commands that are needed, or can be used, to do that.\n\nAnyway, the exercise resulted in a first list of categories, which we will play with as we implement: they need to be in documentation, as well as accessable to runes. And Shahana suggested the term \"genus\" (well , genera) instead of \"category\".",
"sig": "fc37b38e4ba8a6fbf6b411c452ffcfa5bd4b6c2c4ee19fb6d9c0d8506054fb6fd3ad76a17bd8884702734d8e307cc65e893e3dd503c602655328ef77b27686d2"
}