Dave Jones
58fc44127a
fix boost explanation
2023-10-20 11:17:27 -05:00
Alwin
867552b4f6
change reply_custom_key to int
2023-05-20 07:28:39 +02:00
Dave Jones
cf1fbd56bb
blip-10 cleanup
2023-05-11 08:56:28 -05:00
Dave Jones
2fb5b8875a
add remote references to blip-10
2023-05-10 22:34:56 -05:00
Dave Jones
29c3123fc1
lightning address wording
2023-05-01 21:03:55 -05:00
Dave Jones
4dd3adf9d8
reply payment address and routing
2023-04-28 18:48:00 -05:00
Dave Jones
4057e06139
title change
2023-04-28 17:11:16 -05:00
Dave Jones
601f65f1fc
include "signature field" and some re-wording
2023-04-28 17:09:44 -05:00
Dave Jones
145f18e123
tweak
2023-04-28 15:53:03 -05:00
Dave Jones
8bf87116e4
tweak
2023-04-25 16:58:01 -05:00
Dave Jones
f526d1e3e7
value spec - add "auto" as a payment action
2023-04-25 16:56:31 -05:00
Alwin
8b1563616c
add blip-10
2023-04-20 08:03:02 +02:00
Brian of London
4197a430f6
Remove requirement for only one Value block
...
As per the discussion: https://github.com/Podcastindex-org/podcast-namespace/issues/428
2023-01-05 13:18:51 +02:00
callebtc
ea8c8cce9d
remove nano
2022-08-20 03:10:57 +02:00
Karl Oczadly
c6b3115d32
Merge branch 'main' into patch-1
2021-11-08 17:50:45 +00:00
Dave Jones
34ac67000c
Merge pull request #307 from dellagustin/enhacement__value-spec-custom-record
...
Updated podcast:value specification for custom records
2021-11-08 11:36:43 -06:00
Brian
0aa4238ebb
The missing link
...
Signed-off-by: Brian <brian@podping.org>
2021-11-04 11:34:05 +02:00
Brian
0f40958161
Added explanation and use case for customKey/customValue
2021-11-04 11:34:05 +02:00
Guilherme Dellagustin
ebd5df5ab5
Updated podcast:value specification for custom records
...
This commit makes the usage of customKey and customValue more specific.
The change to the spec was made based on the known users for these
attributes (LNPay and HIVE gateway), but it is not necessarily backwards
compatible.
Why is this change neccessary?
Client applications that use the information on the podcast:value
tag must know what to with its content.
Imagine one receiver sets customValue to raw binary data encoded in
hex, and expects it to be sent in the payment as raw binary
data.
Imagine another receiver sets customValue to raw binary data encoded in
base64, and expects it to be sent in the payment as raw binary
data.
Imagine now that other receiver sets customerValue to a string, and
expects it to be sent in the payment as a string encoded in UTF-8 (which
currently known users do).
There is no way a client could know what do to with customValue (how to
decode it an re-encode it), without specific knowledge about how each
receiver uses this field.
Although this is possible, it is counter productive for client
development, as clients should have to know as little as possible
about different application specific protocols used by the receivers.
2021-10-16 15:21:58 +02:00
Karl Oczadly
5771efe844
Fix formatting issue
2021-10-11 20:00:58 +01:00
Karl Oczadly
8fd0def332
Add Nano to V4V specification
2021-10-11 19:51:13 +01:00
Gigi
1611d28eb6
Fix name
...
GiGi -> Gigi
2021-10-05 22:21:47 +02:00
Dave Jones
0819b3d208
credits
2021-09-02 11:14:27 -05:00
Dave Jones
a3bcc50214
credits
2021-09-02 11:13:02 -05:00
Dave Jones
a1c3442bcc
credits
2021-09-02 11:11:57 -05:00
Dave Jones
bec4837d9a
attribution @dergigi
2021-09-01 17:28:54 -05:00
Dave Jones
e9f91e5efa
formalize value tag
2021-09-01 17:22:48 -05:00
Gigi
1734f05a8e
Add "amp" to valueslugs.txt
2021-07-29 15:25:23 +02:00
Gigi
fa8364a916
Update wording; remove extra space
2021-07-29 15:17:32 +02:00
Gigi
bb350a7026
Update wording of AMP part
2021-07-29 15:16:33 +02:00
Gigi
9e2e06e4ce
Add `amp` to method
2021-07-29 15:07:29 +02:00
Gigi
238621e724
Update example to include AMP
2021-07-29 15:05:58 +02:00
Gigi
2b371676c9
Add a short description on AMP
2021-07-29 15:02:02 +02:00
Gigi
7200913bf0
Fix item-override example
2021-07-23 19:46:53 +02:00
Gigi
8a58330eb8
Update item-level override example
2021-07-23 19:43:33 +02:00
Gigi
9c93e42785
Add example description
2021-07-23 19:43:23 +02:00
Gigi
b66bc47233
Add Item-Override example
2021-07-23 19:32:26 +02:00
Gigi
224c81f5bc
Update example to make channel-level explicit
2021-07-23 18:29:36 +02:00
Dave Jones
aacd399120
Merge pull request #270 from dergigi/patch-2
...
Fix typo: crypto-currency -> cryptocurrency
2021-07-19 16:14:44 -05:00
Dave Jones
c65be328ba
Merge pull request #269 from dergigi/satoshis-sats
...
Use "sats" consistently in the value specification examples
2021-07-19 15:59:51 -05:00
Dave Jones
7afc94560b
Merge pull request #267 from dergigi/float-value-suggested
...
Update Lightning example to use `float` instead of `int`
2021-07-19 15:59:10 -05:00
Dave Jones
fd9afac233
Merge pull request #266 from dergigi/clarify-payment-interval
...
Clarify payment interval
2021-07-19 15:58:15 -05:00
Gigi
c9e7b77036
Fix typo
...
crypto-currency -> cryptocurrency
Fixed for consistency. It is written as "cryptocurrency" throughout the rest of the document.
2021-07-19 20:27:32 +02:00
Gigi
0d07f5cde1
Proper usage of one-hundred-millionth
2021-07-19 20:09:19 +02:00
Gigi
309ed95f3f
Lowercase network
2021-07-19 20:08:06 +02:00
Gigi
d34f765fcc
Add example description
...
Since sats are brought up for the first time in this example, it might be useful to explain what sats and millisats are.
2021-07-19 20:06:57 +02:00
Gigi
75b8f2ae63
satoshis -> sats
2021-07-19 19:50:21 +02:00
Gigi
13147d8dcd
Update Lightning example to float
...
Resolves #228
2021-07-19 19:25:06 +02:00
Gigi
723082422a
Clarify payment interval
...
Resolves #200
2021-07-19 16:31:26 +02:00
Gigi
ae714da434
Fix typo
...
it's percentage -> its percentage
2021-07-14 17:41:55 +02:00