Witch Spring Hill is a place steeped in legends and folklore. Located on the outskirts of a small, picturesque town, it is said to be home to powerful witches and magical creatures. The hill itself is shrouded in mist and mystery, adding to the allure of the stories surrounding it. According to popular belief, Witch Spring Hill was where a group of witches found refuge centuries ago. They were said to possess extraordinary powers and used their magic for both good and evil. Legend has it that the hill acted as a sanctuary, shielding the witches from the prying eyes of ordinary humans.
Legend has it that the hill acted as a sanctuary, shielding the witches from the prying eyes of ordinary humans. Over time, the witches formed a close-knit community on Witch Spring Hill, nurturing their magical abilities and sharing their knowledge. They were known to conduct secret rituals and gatherings, where they would perform spells and enchantments.
lightning-commando-rune
The commando-rune RPC command creates a base64 string called a
rune which can be used to access commands on this node. Each rune
contains a unique id (a number starting at 0), and can have
restrictions inside it. Nobody can remove restrictions from a rune: if
you try, the rune will be rejected. There is no limit on how many
runes you can issue; the node simply decodes
and checks them as they are received (we do store them for lightning-commando-listrunes(7) however).
If rune is supplied, the restrictions are simple appended to that
rune (it doesn't need to be a rune belonging to this node). If no
rune is supplied, a new one is constructed, with a new unique id.
restrictions can be the string "readonly" (creates a rune which
allows most get and list commands, and the summary command), or
an array of restrictions.
Each restriction is an array of one or more alternatives, such as "method
is listpeers", or "method is listpeers OR time is before 2023". Alternatives use a simple language to examine the command which is
being run:
- time: the current UNIX time, e.g. "time
- id: the node_id of the peer, e.g. "id=024b9a1fa8e006f1e3937f65f66c408e6da8e1ca728ea43222a7381df1cc449605".
- method: the command being run, e.g. "method=withdraw".
- rate: the rate limit, per minute, e.g. "rate=60".
- pnum: the number of parameters. e.g. "pnum
- pnameX: the parameter named X (with any punctuation like _ removed). e.g. "pnamedestination=1RustyRX2oai4EYYDpQGWvEL62BBGqN9T".
- parrN: the N'th parameter. e.g. "parr0=1RustyRX2oai4EYYDpQGWvEL62BBGqN9T".
Restrictions are one or more alternatives. Each
alternative is name operator value. The valid names are shown
above. Note that if a value contains \\ , it must be preceeded by another \\
to form valid JSON:
- = : passes if equal ie. identical. e.g. method=withdraw
- / : not equals, e.g. method/withdraw
- ^ : starts with, e.g. id^024b9a1fa8e006f1e3937f
- $ : ends with, e.g. id$381df1cc449605 .
- ~ : contains, e.g. id~006f1e3937f65f66c40 .
- < : is a decimal integer, and is less than. e.g. time
- > : is a decimal integer, and is greater than. e.g. time>1656759180
- < : preceeds in alphabetical order (or matches but is shorter), e.g. id
- > : follows in alphabetical order (or matches but is longer), e.g. id>02ff .
- # : a comment, ignored, e.g. dumb example# .
- ! : only passes if the name does not exist. e.g. pnamedestination! .
Every other operator except # fails if name does not exist!
This creates a fresh rune which can do anything:
$ lightning-cli commando-rune
We can add restrictions to that rune, like so:
$ lightning-cli commando-rune rune=KUhZzNlECC7pYsz3QVbF1TqjIUYi3oyESTI7n60hLMs9MA== restrictions=readonly
The "readonly" restriction is a short-cut for two restrictions:
- ["method^list", "method^get", "method=summary"] : You may call list, get or summary.
- ["method/listdatastore"] : But not listdatastore: that contains sensitive stuff!
We can do the same manually, like so:
$ lightning-cli commando-rune rune=KUhZzNlECC7pYsz3QVbF1TqjIUYi3oyESTI7n60hLMs9MA== restrictions='[["method^list", "method^get", "method=summary"],["method/listdatastore"]]'
Let's create a rune which lets a specific peer
(024b9a1fa8e006f1e3937f65f66c408e6da8e1ca728ea43222a7381df1cc449605)
run "listpeers" on themselves:
$ lightning-cli commando-rune restrictions='[["id=024b9a1fa8e006f1e3937f65f66c408e6da8e1ca728ea43222a7381df1cc449605"],["method=listpeers"],["pnum=1"],["pnameid=024b9a1fa8e006f1e3937f65f66c408e6da8e1ca728ea43222a7381df1cc449605","parr0=024b9a1fa8e006f1e3937f65f66c408e6da8e1ca728ea43222a7381df1cc449605"]]'
This allows listpeers with 1 argument ( pnum=1 ), which is either by name ( pnameid ), or position ( parr0 ). We could shorten this in several ways: either allowing only positional or named parameters, or by testing the start of the parameters only. Here's an example which only checks the first 9 bytes of the listpeers parameter:
$ lightning-cli commando-rune restrictions='[["id=024b9a1fa8e006f1e3937f65f66c408e6da8e1ca728ea43222a7381df1cc449605"],["method=listpeers"],["pnum=1"],["pnameid^024b9a1fa8e006f1e393", "parr0^024b9a1fa8e006f1e393"]'
Before we give this to our peer, let's add two more restrictions: that
it only be usable for 24 hours from now ( time < ), and that it can only
be used twice a minute ( rate=2 ). date +%s can give us the current
time in seconds:
$ lightning-cli commando-rune rune=fTQnfL05coEbiBO8SS0cvQwCcPLxE9c02pZCC6HRVEY9MyZpZD0wMjRiOWExZmE4ZTAwNmYxZTM5MzdmNjVmNjZjNDA4ZTZkYThlMWNhNzI4ZWE0MzIyMmE3MzgxZGYxY2M0NDk2MDUmbWV0aG9kPWxpc3RwZWVycyZwbnVtPTEmcG5hbWVpZF4wMjRiOWExZmE4ZTAwNmYxZTM5M3xwYXJyMF4wMjRiOWExZmE4ZTAwNmYxZTM5Mw== restrictions='[["time
You can also use lightning-decode(7) to examine runes you have been given:
$ .lightning-cli decode tU-RLjMiDpY2U0o3W1oFowar36RFGpWloPbW9-RuZdo9MyZpZD0wMjRiOWExZmE4ZTAwNmYxZTM5MzdmNjVmNjZjNDA4ZTZkYThlMWNhNzI4ZWE0MzIyMmE3MzgxZGYxY2M0NDk2MDUmbWV0aG9kPWxpc3RwZWVycyZwbnVtPTEmcG5hbWVpZF4wMjRiOWExZmE4ZTAwNmYxZTM5M3xwYXJyMF4wMjRiOWExZmE4ZTAwNmYxZTM5MyZ0aW1lPDE2NTY5MjA1MzgmcmF0ZT0y < "type": "rune", "unique_id": "3", "string": "b54f912e33220e9636534a375b5a05a306abdfa4451a95a5a0f6d6f7e46e65da:=3&id=024b9a1fa8e006f1e3937f65f66c408e6da8e1ca728ea43222a7381df1cc449605&method=listpeers&pnum=1&pnameid^024b9a1fa8e006f1e393|parr0^024b9a1fa8e006f1e393&time, < "alternatives": [ "method=listpeers" ], "summary": "method (of command) equal to 'listpeers'" >, < "alternatives": [ "pnum=1" ], "summary": "pnum (number of command parameters) equal to 1" >, < "alternatives": [ "pnameid^024b9a1fa8e006f1e393", "parr0^024b9a1fa8e006f1e393" ], "summary": "pnameid (object parameter 'id') starts with '024b9a1fa8e006f1e393' OR parr0 (array parameter #0) starts with '024b9a1fa8e006f1e393'" >, < "alternatives": [ "time, < "alternatives": [ "rate=2" ], "summary": "rate (max per minute) equal to 2" >], "valid": true > Because anyone can add a restriction to a rune, you can always turn a
normal rune into a read-only rune, or restrict access for 30 minutes
from the time you give it to someone. Adding restrictions before
sharing runes is best practice.
If a rune has a ratelimit, any derived rune will have the same id, and
thus will compete for that ratelimit. You might want to consider
adding a tighter ratelimit to a rune before sharing it, so you will
keep the remainder. For example, if you rune has a limit of 60 times
per minute, adding a limit of 5 times per minute and handing that rune
out means you can still use your original rune 55 times per minute.
On success, an object is returned, containing:
- rune (string): the resulting rune
- unique_id (string): the id of this rune: this is set at creation and cannot be changed (even as restrictions are added)
The following warnings may also be returned:
- warning_unrestricted_rune: A warning shown when runes are created with powers that could drain your node
Rusty Russell < [email protected] > wrote the original Python
commando.py plugin, the in-tree commando plugin, and this manual page.
Christian Decker came up with the name "commando", which almost
excuses his previous adoption of the name "Eltoo".
Each restriction is an array of one or more alternatives, such as "method
is listpeers", or "method is listpeers OR time is before 2023". Alternatives use a simple language to examine the command which is
being run:
The hill became a hub of supernatural energy, drawing in curious visitors seeking answers and blessings. As the stories go, only those with pure intentions could access the hill's magical powers. It is said that those who sought to exploit or harm the witches would face dire consequences. The hill became a symbol of protection and justice for the townsfolk, who would turn to the witches in times of need. Despite the fear and superstition surrounding Witch Spring Hill, some believed that the witches held the key to unlocking the secrets of the universe. Many scholars and researchers made pilgrimages to the hill, hoping to learn from the wisdom of the witches. These encounters resulted in the exchange of ancient knowledge, fueling the legends further. Today, Witch Spring Hill continues to captivate the imaginations of both locals and tourists. The town has embraced its mystical reputation, organizing events and tours that celebrate the folklore. Visitors can explore the hill's magical surroundings, immersing themselves in the rich history and enchanting beauty of the place. Whether you believe in the supernatural or not, Witch Spring Hill remains an intriguing destination that sparks curiosity and wonder. It serves as a reminder that there is still so much about the world that is unexplained, and that the stories we tell ourselves have the power to shape our reality..
Reviews for "Witch Spring Hill: An Artistic Haven for Witches"
1. Sam - 2/5 - I was really disappointed with Witch Spring Hill. The plot was incredibly confusing and disjointed, making it hard to follow the story. The characters were also poorly developed, lacking depth and personality. Additionally, the pacing was extremely slow, and I found myself losing interest in the game. Overall, I would not recommend Witch Spring Hill to others.
2. Emily - 1/5 - Witch Spring Hill was a complete letdown for me. The gameplay was repetitive and mundane, with very little variety in activities or quests. The graphics were also lackluster, and the game felt outdated compared to others in the genre. I had high hopes for this game, but it failed to deliver an enjoyable experience. I regret purchasing Witch Spring Hill and would advise others to steer clear of it.
3. Alex - 2/5 - I found Witch Spring Hill to be a frustrating and tedious game. The controls were clunky and unresponsive, making it difficult to navigate and perform actions. The combat system was also poorly executed, lacking the excitement and strategy that I was hoping for. The lack of customization options for the main character was disappointing as well. Overall, Witch Spring Hill fell short of my expectations and left me feeling dissatisfied.