spec: import latest onionmessage spec, based on routeblinding.

This is from 6e99c5feaf60cb797507d181fe583224309318e9

We renamed the enctlv field to encrypted_recipient_data in the spec, and the
new onion_message is message 513.  We don't handle it until the next patch.

Two renames:
1. blinding_seed -> blinding_point.
2. enctlv -> encrypted_recipient_data.

We don't do a compat cycle for our JSON APIs for these experimental
features only used by our own plugins, we just rename.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
This commit is contained in:
Rusty Russell
2021-11-30 13:36:04 +10:30
parent 1ec6346f3d
commit b3af5f5a2c
22 changed files with 386 additions and 81 deletions

View File

@@ -269,11 +269,11 @@ int main(int argc, char **argv)
/* Look for enctlv */
if (!outer->enctlv)
errx(1, "No enctlv field");
errx(1, "No encrypted_recipient_data field");
if (tal_bytelen(outer->enctlv)
< crypto_aead_chacha20poly1305_ietf_ABYTES)
errx(1, "enctlv field too short");
errx(1, "encrypted_recipient_data field too short");
dec = tal_arr(tmpctx, u8,
tal_bytelen(outer->enctlv)
@@ -286,7 +286,7 @@ int main(int argc, char **argv)
npub,
rho.data);
if (ret != 0)
errx(1, "Failed to decrypt enctlv field");
errx(1, "Failed to decrypt encrypted_recipient_data field");
printf("Contents: %s\n", tal_hex(tmpctx, dec));