to be generated by the payee in order to fulfill a transaction. The "keysend" protocol of Lightning allows payments
to be streamed to what is, essentially, an open invoice. Other cryptocurrencies may have a similar protocol that
would be used here. If not, a value of "default" should be given.
The "suggested" amount is just that. It's a suggestion, and must be changeable by the user to another value, or
to zero. The suggested amount should always be given in the smallest denomination available within the payment
protocol being used. For instance, with Lightning it is given in millisatoshis.
A single value tag can contain many `<podcast:valueRecipient>` tags as children. All of these given recipients are
sent individual payments when the payment interval triggers.
The value tag, when it exists at the `<channel>` level, designates the payment scheme for the entire podcast. When it
exists at the `<item>` level, it is intended to override the channel level tag for that episode only.
#### Example:
```
<podcast:value
type="lightning"
method="keysend"
suggested="0.00000005000"
></podcast:value>
```
<br><br>
<divclass="page"/>
### Value Recipient Element
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.
This element may only exist within a parent `<podcast:value>` element.
There is no limit on how many `valueRecipient` elements can be present in a given `<podcast:value>` element.
<br>
#### Structure:
```
<podcast:valueRecipient
name="[name of recipient(string)]"
type="[address type(string)]"
address="[the receiving address(string)]"
customKey="[optional key to pass(mixed)]"
customValue="[optional value to pass(mixed)]"
split="[share count(int)]"
/>
```
<br>
#### Attributes:
-`name` (recommended) A free-form string that designates who or what this recipient is.
-`customKey` (optional) The name of a custom record key to send along with the payment.
-`customValue` (optional) A custom value to pass along with the payment. This is considered the value that belongs to the `customKey`.
-`type` (required) A slug that represents the type of receiving address that will receive the payment.
-`address` (required) This denotes the receiving address of the payee.
-`split` (required) The number of shares of the payment this recipient will receive.
<br>
#### Explanation:
The `name` is just a human readable description of who or what this payment destination is. This could be something simple like
"Podcaster", "Co-host" or "Producer". It could also be more descriptive like "Ronald McDonald House Charity", if a podcaster
chooses to donate a percentage of their incoming funds to a charity.
The `type` denotes what type of receiving entity this is. For instance, with lightning this would typically be "node". This would
indicate that the `address` attribute for this recipient is a Lightning node that is capable of directly receiving incoming keysend payments. Valid values for
the `type` attribute are kept in the accompanying file [here](valueslugs.txt). Another option is given in examples below.
Payments must be sent to a valid destination which is given in the `address` attribute. This address format will vary depending on
the underlying currency being used.
The `split` attribute denotes an amount of "shares" of the total payment that the recipient will receive when each timed payment is made.
When a single `<podcast:valueRecipient>` is present, it should be assumed that the `split` for that recipient is 100%, and the "split" should
be ignored. When multiple recipients are present, a share calculation (see below) should be made to determine how much to send to each recipient's address.
This block designates three payment recipients. On each timed payment interval, the total payment will be split into 3 smaller
payments according to the shares listed in the split for each recipient. So, in this case, if the listener decided to pay 100 satoshis per minute for listening
to this podcast, then once per minute the "Host" would be sent 50 satoshis, the "Co-Host" would be sent 40 satoshis and the
"Producer" would be sent 10 satoshis - all to their respective lightning node addresses using the "keysend" protocol.
If, instead of a 50/40/10 (total of 100) split, the splits were given as 190/152/38 (total of 380), the respective payment amounts each minute would still
be 50 satoshis, 40 satoshis and 10 satoshis because the listener chose to pay 100 satoshis per minute, and the respective shares (as a percentage of the total) would remain the same.
On a 190/152/38 split, each minute the payment calculation would be: