forked from I2P_Developers/i2p.www
Clarify i2cp.leaseSetSecret option
This commit is contained in:
@@ -1,7 +1,7 @@
|
||||
{% extends "global/layout.html" %}
|
||||
{% block title %}I2CP{% endblock %}
|
||||
{% block lastupdated %}{% trans %}June 2019{% endtrans %}{% endblock %}
|
||||
{% block accuratefor %}0.9.41{% endblock %}
|
||||
{% block lastupdated %}2019-09{% endblock %}
|
||||
{% block accuratefor %}0.9.42{% endblock %}
|
||||
{% block content %}
|
||||
<p>{% trans -%}
|
||||
The I2P Client Protocol (I2CP) exposes a strong separation of concerns between
|
||||
@@ -254,7 +254,7 @@ Do not confuse with i2cp.leaseSetPrivateKey which is for LS1.
|
||||
<td>""
|
||||
<td>
|
||||
Base 64 encoded UTF-8
|
||||
secret used to blind the leaseset.
|
||||
secret used to blind the leaseset address.
|
||||
See proposal 123.
|
||||
</td>
|
||||
</tr>
|
||||
@@ -755,7 +755,7 @@ Do not confuse with i2cp.leaseSetPrivKey which is for LS2.
|
||||
<td>""
|
||||
<td>
|
||||
Base 64 encoded UTF-8
|
||||
secret used to blind the leaseset.
|
||||
secret used to blind the leaseset address.
|
||||
See proposal 123.
|
||||
</td>
|
||||
</tr>
|
||||
|
Reference in New Issue
Block a user