📅 Original date posted:2015-10-05
📝 Original message:
Anthony Towns <aj at erisian.com.au> writes:
> On Fri, Oct 02, 2015 at 03:18:39PM +0930, Rusty Russell wrote:
> Question:
>
> - I think this means lightning nodes are identified by the
> full 512 bit (or 257 bit?) public key used for routing -- (ie,
> knowing the HASH160 of the pubkey isn't enough, unlike in normal
> bitcoin pay2pubkey transactions).
Yes, since you need to encrypt to it, you need the full pubkey.
> - I think you can still use different keys for routing and
> anchors/commitments so far. (Using the anchor transaction to turn
> your routing id into a beacon would probably change that though)
Yes, that's still TBD.
>From the other email:
> - AES128 just uses the first half of the calculated enckey, iv and
> pad_iv
True.
> - since libsecp256k1 already sha256s the ecdh secret; the hmac/enckey/etc
> end up being sha256'ed twice (with a byte added in between). confused
> me for a minute.
I didn't notice that. Perhaps this is somewhere we should optimize?
Cheers,
Rusty.
PS. Message size of 128 bytes is completely made up, as is 20 hops. We
might want to reduce to 96 or 64 bytes.
Rusty Russell [ARCHIVE] /
npub1zw…hkhpx
2023-06-09 12:44:44
in reply to nevent1q…uzyh
Author Public Key
npub1zw7cc8z78v6s3grujfvcv3ckpvg6kr0w7nz9yzvwyglyg0qu5sjsqhkhpxPublished at
2023-06-09 12:44:44Event JSON
{
"id": "d7af8370a8cc47f206a372d0054accecd322916ed38a34390dd06c7dfa0a13bc",
"pubkey": "13bd8c1c5e3b3508a07c92598647160b11ab0deef4c452098e223e443c1ca425",
"created_at": 1686314684,
"kind": 1,
"tags": [
[
"e",
"8068f367a334368b30aff76cd525cce9c5bc6d9781f504af87639b9a503f0531",
"",
"root"
],
[
"e",
"30271d61e99f5759f161355e588126ea3fe1830fc0f8bebc0d418dd42e52c43c",
"",
"reply"
],
[
"p",
"13bd8c1c5e3b3508a07c92598647160b11ab0deef4c452098e223e443c1ca425"
]
],
"content": "📅 Original date posted:2015-10-05\n📝 Original message:\nAnthony Towns \u003caj at erisian.com.au\u003e writes:\n\u003e On Fri, Oct 02, 2015 at 03:18:39PM +0930, Rusty Russell wrote:\n\u003e Question:\n\u003e\n\u003e - I think this means lightning nodes are identified by the\n\u003e full 512 bit (or 257 bit?) public key used for routing -- (ie,\n\u003e knowing the HASH160 of the pubkey isn't enough, unlike in normal\n\u003e bitcoin pay2pubkey transactions).\n\nYes, since you need to encrypt to it, you need the full pubkey.\n\n\u003e - I think you can still use different keys for routing and\n\u003e anchors/commitments so far. (Using the anchor transaction to turn\n\u003e your routing id into a beacon would probably change that though)\n\nYes, that's still TBD.\n\n\u003eFrom the other email:\n\n\u003e - AES128 just uses the first half of the calculated enckey, iv and\n\u003e pad_iv\n\nTrue.\n\n\u003e - since libsecp256k1 already sha256s the ecdh secret; the hmac/enckey/etc\n\u003e end up being sha256'ed twice (with a byte added in between). confused\n\u003e me for a minute.\n\nI didn't notice that. Perhaps this is somewhere we should optimize?\n\nCheers,\nRusty.\nPS. Message size of 128 bytes is completely made up, as is 20 hops. We\n might want to reduce to 96 or 64 bytes.",
"sig": "ebfb88b4c10eee02c36561dc5b2e45c4b482062ecad80cbbb6b54722ce51f7063a8336b4fc418c01de96a8e3da4969ab9ae06d6435a5b9a156c7a26d5ac37c9e"
}