In i2p documentation, it says that "the first time Bitcoin Core connects to the I2P router,
it automatically generates a persistent I2P address and its corresponding private key by
default or if -i2pacceptincoming=1 is set". This is weird, because -i2pacceptincoming=1
by itself does not have any effect. Moreover, -i2pacceptincoming is 1 by default anyway.
doc: i2p: improve `-i2pacceptincoming` mention #29813
pull brunoerg wants to merge 1 commits into bitcoin:master from brunoerg:2024-04-fix-doc-i2p changing 1 files +2 −2-
brunoerg commented at 9:22 AM on April 5, 2024: contributor
-
doc: i2p: improve `-i2pacceptincoming` mention 2179e2c320
-
DrahtBot commented at 9:22 AM on April 5, 2024: contributor
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--006a51241073e994b41acfe9ec718e94-->
Code Coverage
For detailed information about the code coverage, see the test coverage report.
<!--021abf342d371248e50ceaed478a90ca-->
Reviews
See the guideline for information on the review process.
Type Reviewers ACK laanwj, byaye, davidgumberg, achow101 If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.
- DrahtBot added the label Docs on Apr 5, 2024
-
laanwj commented at 3:14 PM on April 9, 2024: member
This documentation change is correct and makes the documentation slightly shorter, thus easier to read. ACK 2179e2c3209a41c1419f1f5ed6270a0dad68b50d
- hernanmarino approved
- byaye approved
-
byaye commented at 6:55 PM on April 12, 2024: none
ACK 2179e2c3209a41c1419f1f5ed6270a0dad68b50d
-
davidgumberg commented at 4:07 PM on April 28, 2024: contributor
ACK https://github.com/bitcoin/bitcoin/pull/29813/commits/2179e2c3209a41c1419f1f5ed6270a0dad68b50d
Checked (without testing) that behavior is as described. In
CConman::ConnectNode, unlessi2pacceptincoming == 0, a persistent I2P session (m_transient == false) with a private key stored on disk is used. Otherwise, we create a transient I2P session (m_transient == true).Relevant section of
i2p::sam::Session::CreateIfNotCreatedAlready()(called byi2p::sam::Session::Connect):if (m_transient) { // The destination (private key) is generated upon session creation and returned // in the reply in DESTINATION=. // [...] } else { // Read our persistent destination (private key) from disk or generate // one and save it to disk. Then use it when creating the session. const auto& [read_ok, data] = ReadBinaryFile(m_private_key_file); if (read_ok) { m_private_key.assign(data.begin(), data.end()); } else { GenerateAndSavePrivateKey(*sock); } // [...] } -
achow101 commented at 10:54 PM on April 30, 2024: member
ACK 2179e2c3209a41c1419f1f5ed6270a0dad68b50d
- achow101 merged this on Apr 30, 2024
- achow101 closed this on Apr 30, 2024
-
vasild commented at 1:55 PM on May 13, 2024: contributor
ACK 2179e2c3209a41c1419f1f5ed6270a0dad68b50d
- kwvg referenced this in commit 9d959d707d on Apr 14, 2025
- PastaPastaPasta referenced this in commit 272c951057 on Apr 22, 2025
- bitcoin locked this on May 14, 2025