š
Original date posted:2019-11-17
š Original message:Mr. Lee Chiffre via bitcoin-dev wrote:
> Right now bitcoin client core supports use of tor hidden service. It
> supports v2 hidden service. I am in progress of creating a new bitcoin
> node which will use v3 hidden service instead of v2. I am looking at
> bitcoin core and btcd to use. Do any of these or current node software
> support the v3 onion addresses for the node address? What about I2P
> addresses? If not what will it take to get it to support the longer
> addresses that is used by i2p and tor v3?
>
>
Hello,
Yes, that is correct. Currently at present moment only v2 onion services
are supported. Bitcoin Core is limited at 128 bit 'addresses' in the p2p
protocol, so it requires a rework of the p2p protocol. v3 onion services
are whole ed25519 public keys, base32 encoded with .onion at the end.
Same reason applies to I2P 'address types' as well. However, I am not an
expert in I2P and don't actually know how many bitcoin full nodes might
exist in I2P.
See:
https://github.com/bitcoin/bitcoin/issues/9214
https://github.com/bitcoin/bitcoin/issues/2091
For the default `ADD_ONION` feature, the onion service key was
downgraded to explicitly RSA1024 (legacy, v2 onion services) to ensure
the feature still works out of the box:
https://github.com/bitcoin/bitcoin/pull/9234
If you want a Tor only full node, you are best to use v2 onion services
for now. Why do you need the bitcoin node to explicitly have a v3 onion
address? You can have a service that is accessible to the general public
as a v3 onion service, and in the back uses a bitcoin full node that
uses v2 onion service to talk to other nodes. The v2 onion service
bitcoin network is extended fairly.
You can use in the same torrc (Tor configuration file), implicitly same
Tor process/daemon simultaneously v2 and v3 onion services by setting
HiddenServiceVersion parameter after every HiddenServiceDir parameter.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20191117/5a13ed1e/attachment.sig>;
s7r [ARCHIVE] /
npub1j3ā¦cwg9h
2023-06-07 18:21:44
in reply to nevent1qā¦z8xt
Author Public Key
npub1j3u42vq63qzs2nyddgkf4s4t7pa85x855vas54e6yauxsvpf2wcsacwg9hPublished at
2023-06-07 18:21:44Event JSON
{
"id": "37795b5c121a4eea1a98e9adb94ff05e2427da54f877852a99eca3644eca40b0",
"pubkey": "947955301a8805054c8d6a2c9ac2abf07a7a18f4a33b0a573a277868302953b1",
"created_at": 1686162104,
"kind": 1,
"tags": [
[
"e",
"337b8070cc3375eecc444792a5976780f109f33478cf7c64cece3d6761d48b89",
"",
"root"
],
[
"e",
"0448225f70353db4eb353e838dc50c0ffe8c015193146b74c88eb122de1cc96b",
"",
"reply"
],
[
"p",
"3b49f5ff9dc155c2b07ba740b62b5ede0f30b57d85fa91a5f1d87698ed39278f"
]
],
"content": "š
Original date posted:2019-11-17\nš Original message:Mr. Lee Chiffre via bitcoin-dev wrote:\n\u003e Right now bitcoin client core supports use of tor hidden service. It\n\u003e supports v2 hidden service. I am in progress of creating a new bitcoin\n\u003e node which will use v3 hidden service instead of v2. I am looking at\n\u003e bitcoin core and btcd to use. Do any of these or current node software\n\u003e support the v3 onion addresses for the node address? What about I2P\n\u003e addresses? If not what will it take to get it to support the longer\n\u003e addresses that is used by i2p and tor v3?\n\u003e \n\u003e \n\nHello,\n\nYes, that is correct. Currently at present moment only v2 onion services\nare supported. Bitcoin Core is limited at 128 bit 'addresses' in the p2p\nprotocol, so it requires a rework of the p2p protocol. v3 onion services\nare whole ed25519 public keys, base32 encoded with .onion at the end.\n\nSame reason applies to I2P 'address types' as well. However, I am not an\nexpert in I2P and don't actually know how many bitcoin full nodes might\nexist in I2P.\n\nSee:\nhttps://github.com/bitcoin/bitcoin/issues/9214\n\nhttps://github.com/bitcoin/bitcoin/issues/2091\n\n\nFor the default `ADD_ONION` feature, the onion service key was\ndowngraded to explicitly RSA1024 (legacy, v2 onion services) to ensure\nthe feature still works out of the box:\n\nhttps://github.com/bitcoin/bitcoin/pull/9234\n\nIf you want a Tor only full node, you are best to use v2 onion services\nfor now. Why do you need the bitcoin node to explicitly have a v3 onion\naddress? You can have a service that is accessible to the general public\nas a v3 onion service, and in the back uses a bitcoin full node that\nuses v2 onion service to talk to other nodes. The v2 onion service\nbitcoin network is extended fairly.\n\nYou can use in the same torrc (Tor configuration file), implicitly same\nTor process/daemon simultaneously v2 and v3 onion services by setting\nHiddenServiceVersion parameter after every HiddenServiceDir parameter.\n\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 488 bytes\nDesc: OpenPGP digital signature\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20191117/5a13ed1e/attachment.sig\u003e",
"sig": "dd7b1875887f0b67a2f38d7e126e4754f816371c8dbe7f0ff3e2c20d93ec2662ec1e6f50f81230b9eff1a4f04ed9a56f8e1bdb7a4af7d4a33812adb2a5def38c"
}