William Swanson [ARCHIVE] on Nostr: 📅 Original date posted:2015-06-12 📝 Original message:The `n` is the curve ...
📅 Original date posted:2015-06-12
📝 Original message:The `n` is the curve order, as shown here:
https://en.bitcoin.it/wiki/Secp256k1This step is necessary to keep you on the curve. The
secp256k1_ec_privkey_tweak_add function from libsecp256k1 handles this
automatically, but if you use OpenSSL or some non-EC math library, you
probably have to do it yourself.
-William
On Fri, Jun 12, 2015 at 11:22 AM, James Poole <james at microtrx.com> wrote:
> Looking at the BIP32 definition, I hit a line that I would appreciate
> clarification on.
>
>
https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki>
> Under the section "Private parent key → private child key" there is a step:
>
> "The returned child key ki is parse256(IL) + kpar (mod n)."
>
> Can someone help me understand what "n" is in the context of this algorithm?
> I very well could be looking right at it, but wanted to double check if I am
> missing something.
>
> Thanks,
> James
Published at
2023-06-07 15:37:41Event JSON
{
"id": "8f0e373da6b4164dddfba91867710307e5c9f3a40ba09c59f6b7053da62cb264",
"pubkey": "a178a4d8dc03df766d640bbff9f4a535decb16c595ad471cabee59e7f78f439d",
"created_at": 1686152261,
"kind": 1,
"tags": [
[
"e",
"8f9a97ea716341faa59ea0dd9497c58cbd00343fa9288dedf2d8ba24a6731eeb",
"",
"root"
],
[
"e",
"1e484902de82f1cdf7c0e23cda2a6c57d381191ebaa822fa80556bfcb6ef84d7",
"",
"reply"
],
[
"p",
"be4d7066a89638c59f844815557fe728f7afaf5154cda061663f751d5b3b4e2e"
]
],
"content": "📅 Original date posted:2015-06-12\n📝 Original message:The `n` is the curve order, as shown here:\n\nhttps://en.bitcoin.it/wiki/Secp256k1\n\nThis step is necessary to keep you on the curve. The\nsecp256k1_ec_privkey_tweak_add function from libsecp256k1 handles this\nautomatically, but if you use OpenSSL or some non-EC math library, you\nprobably have to do it yourself.\n\n-William\n\nOn Fri, Jun 12, 2015 at 11:22 AM, James Poole \u003cjames at microtrx.com\u003e wrote:\n\u003e Looking at the BIP32 definition, I hit a line that I would appreciate\n\u003e clarification on.\n\u003e\n\u003e https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki\n\u003e\n\u003e Under the section \"Private parent key → private child key\" there is a step:\n\u003e\n\u003e \"The returned child key ki is parse256(IL) + kpar (mod n).\"\n\u003e\n\u003e Can someone help me understand what \"n\" is in the context of this algorithm?\n\u003e I very well could be looking right at it, but wanted to double check if I am\n\u003e missing something.\n\u003e\n\u003e Thanks,\n\u003e James",
"sig": "612d6149eca5272ae2841c328baed91d211f2e09036f83880d339df047067575c37e6885e72bd19efc2149e0e1f72550099dba6aa80f5f1445ea4f6c35246c78"
}