Prepare release

This commit is contained in:
Mark Qvist 2026-11-07 17:38:23 +01:00
parent 2960e6a41d
commit cb1260891d
No known key found for this signature in database
4 changed files with 4 additions and 4 deletions

View file

@ -39,7 +39,7 @@ While the core functionality is completely automatic, and handled by Reticulum i
The *value* of a stamp is a decimal representation of how difficult a stamp was to create, on a scale from ``0.0`` to ``100.0``. The scale is **exponential**. An increase of one point is equal to *doubling* the average compute time required. Fractional values are supported, such as ``14.125``.
Internally, the fractional part is quantized to ``256`` different values, giving an approximately ``0.4%`` difficulty increase per step. You can use any decimal number when configuring stamps, such as ``9.3691`` and you do not have to worry about "landing on" the correct step values. Reticulum will automatically handle the quantization, wire-transport representation and value comparisons.
Internally, the fractional part is quantized to ``256`` different values, giving an approximately ``0.27%`` difficulty increase per step. You can use any decimal number when configuring stamps, such as ``9.3691`` and you do not have to worry about "landing on" the correct step values. Reticulum will automatically handle the quantization, wire-transport representation and value comparisons.
The term *cost* is used everywhere a stamp value *requirement* is configured or specified. In general, *value* refers to the actual, determined value of a given stamp, *cost* refers to a value requirement.

View file

@ -291,7 +291,7 @@
<p>The amount of such computation required for a stamp to be considered valid can be configured individually by the operator of the resource being made available, whether that is network transport, a node providing information for retrieval, a shared voice room, or something else entirely.</p>
<p>While the core functionality is completely automatic, and handled by Reticulum itself, the primitives are made available at the application layer API as well, so that developers can use them to implement further protections, if required by their usage scenarios. In most cases, however, simply setting the target <em>values</em> and required <em>costs</em> for the built-in mechanisms will be sufficient.</p>
<p>The <em>value</em> of a stamp is a decimal representation of how difficult a stamp was to create, on a scale from <code class="docutils literal notranslate"><span class="pre">0.0</span></code> to <code class="docutils literal notranslate"><span class="pre">100.0</span></code>. The scale is <strong>exponential</strong>. An increase of one point is equal to <em>doubling</em> the average compute time required. Fractional values are supported, such as <code class="docutils literal notranslate"><span class="pre">14.125</span></code>.</p>
<p>Internally, the fractional part is quantized to <code class="docutils literal notranslate"><span class="pre">256</span></code> different values, giving an approximately <code class="docutils literal notranslate"><span class="pre">0.4%</span></code> difficulty increase per step. You can use any decimal number when configuring stamps, such as <code class="docutils literal notranslate"><span class="pre">9.3691</span></code> and you do not have to worry about “landing on” the correct step values. Reticulum will automatically handle the quantization, wire-transport representation and value comparisons.</p>
<p>Internally, the fractional part is quantized to <code class="docutils literal notranslate"><span class="pre">256</span></code> different values, giving an approximately <code class="docutils literal notranslate"><span class="pre">0.27%</span></code> difficulty increase per step. You can use any decimal number when configuring stamps, such as <code class="docutils literal notranslate"><span class="pre">9.3691</span></code> and you do not have to worry about “landing on” the correct step values. Reticulum will automatically handle the quantization, wire-transport representation and value comparisons.</p>
<p>The term <em>cost</em> is used everywhere a stamp value <em>requirement</em> is configured or specified. In general, <em>value</em> refers to the actual, determined value of a given stamp, <em>cost</em> refers to a value requirement.</p>
<section id="base-primitives">
<h3>Base Primitives<a class="headerlink" href="#base-primitives" title="Link to this heading"></a></h3>

File diff suppressed because one or more lines are too long

View file

@ -33,7 +33,7 @@ While the core functionality is completely automatic, and handled by Reticulum i
The *value* of a stamp is a decimal representation of how difficult a stamp was to create, on a scale from `0.0` to `100.0`. The scale is **exponential**. An increase of one point is equal to *doubling* the average compute time required. Fractional values are supported, such as `14.125`.
Internally, the fractional part is quantized to `256` different values, giving an approximately `0.4%` difficulty increase per step. You can use any decimal number when configuring stamps, such as `9.3691` and you do not have to worry about “landing on” the correct step values. Reticulum will automatically handle the quantization, wire-transport representation and value comparisons.
Internally, the fractional part is quantized to `256` different values, giving an approximately `0.27%` difficulty increase per step. You can use any decimal number when configuring stamps, such as `9.3691` and you do not have to worry about “landing on” the correct step values. Reticulum will automatically handle the quantization, wire-transport representation and value comparisons.
The term *cost* is used everywhere a stamp value *requirement* is configured or specified. In general, *value* refers to the actual, determined value of a given stamp, *cost* refers to a value requirement.