Skip to content

Commit b20a774

Browse files
authored
Merge pull request #767 from ChadFarrow/main
Enhance documentation for valueRecipient tag
2 parents 5a3a638 + b41939d commit b20a774

1 file changed

Lines changed: 42 additions & 8 deletions

File tree

docs/tags/value-recipient.md

Lines changed: 42 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,4 @@
11
# Value Recipient
2-
32
`<podcast:valueRecipient>`
43

54
The `valueRecipient` tag designates various destinations for payments to be sent to during consumption of the enclosed media. Each recipient is considered to receive a "split" of the total payment according to the number of shares given in the `split` attribute.
@@ -20,13 +19,16 @@ Multiple
2019

2120
### Attributes
2221

23-
- `type` **(required)**: A slug that represents the type of receiving address that will receive the payment.
24-
- `address` **(required)**: This denotes the receiving address of the payee.
25-
- `split` **(required)**: The number of shares of the payment this recipient will receive.
26-
- `name` (recommended): A free-form string that designates who or what this recipient is.
27-
- `customKey` (optional): The name of a custom record key to send along with the payment.
28-
- `customValue` (optional): A custom value to pass along with the payment. This is considered the value that belongs to the `customKey`.
29-
- `fee` (optional) If this attribute is not specified, it is assumed to be false.
22+
* `type` **(required)**: A slug that represents the type of receiving address that will receive the payment.
23+
Known values:
24+
- `node` — a Lightning Network node public key. The `address` attribute should contain the hex-encoded pubkey.
25+
- `lnaddress` — a Lightning Address (e.g. `user@wallet.com`). The `address` attribute should contain the Lightning Address. Apps should resolve the pubkey and custom record data by calling `https://<domain>/.well-known/keysend/<username>` before sending payment. Results should be cached to minimize network requests.
26+
* `address` **(required)**: This denotes the receiving address of the payee.
27+
* `split` **(required)**: The number of shares of the payment this recipient will receive.
28+
* `name` (recommended): A free-form string that designates who or what this recipient is.
29+
* `customKey` (optional): The name of a custom record key to send along with the payment.
30+
* `customValue` (optional): A custom value to pass along with the payment. This is considered the value that belongs to the `customKey`.
31+
* `fee` (optional) If this attribute is not specified, it is assumed to be false.
3032

3133
### Examples
3234

@@ -59,3 +61,35 @@ Multiple
5961
/>
6062
</podcast:value>
6163
```
64+
65+
Lightning Address recipients can be used in place of, or mixed with, `node` recipients in the same value block:
66+
67+
```xml
68+
<podcast:value type="lightning" method="lnaddress" suggested="0.00000005000">
69+
<podcast:valueRecipient
70+
name="Alice (Podcaster)"
71+
type="lnaddress"
72+
address="alice@getalby.com"
73+
split="40"
74+
/>
75+
<podcast:valueRecipient
76+
name="Bob (Podcaster)"
77+
type="lnaddress"
78+
address="bob@fountain.fm"
79+
split="40"
80+
/>
81+
<podcast:valueRecipient
82+
name="Carol (Producer)"
83+
type="node"
84+
address="02dd306e68c46681aa21d88a436fb35355a8579dd30201581cefa17cb179fc4c15"
85+
split="15"
86+
/>
87+
<podcast:valueRecipient
88+
name="Hosting Provider"
89+
type="node"
90+
address="03ae9f91a0cb8ff43840e3c322c4c61f019d8c1c3cea15a25cfc425ac605e61a4a"
91+
split="5"
92+
fee="true"
93+
/>
94+
</podcast:value>
95+
```

0 commit comments

Comments
 (0)