https://www.dgbwiki.com/index.php?title=Odocrypt&feed=atom&action=historyOdocrypt - Revision history2024-03-29T10:03:56ZRevision history for this page on the wikiMediaWiki 1.34.0https://www.dgbwiki.com/index.php?title=Odocrypt&diff=4281&oldid=prevJoseTrejo DGB-Noob: Changed Odocrypt blog post link to medium article link2022-12-27T20:52:50Z<p>Changed Odocrypt blog post link to medium article link</p>
<table class="diff diff-contentalign-left" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">Revision as of 20:52, 27 December 2022</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l2" >Line 2:</td>
<td colspan="2" class="diff-lineno">Line 2:</td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>[https://odocrypt.digibyteservers.io/ Odocrypt] is a unique GPU / FPGA-friendly hashing algorithm made specifically for DigiByte that changes itself every 10 days as an anti-ASIC method.</div></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>[https://odocrypt.digibyteservers.io/ Odocrypt] is a unique GPU / FPGA-friendly hashing algorithm made specifically for DigiByte that changes itself every 10 days as an anti-ASIC method.</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td></tr>
<tr><td class='diff-marker'>−</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>[https://<del class="diffchange diffchange-inline">blockchain2035</del>.com/<del class="diffchange diffchange-inline">blogs/digiassetsprotocol</del>/digibyte-v7-17-2-odocrypt-algo-fork <del class="diffchange diffchange-inline">Blog post from </del>Jared Tate (founder of DigiByte) regarding&nbsp;DigiByte v7.17.2 Odocrypt Algo Fork]</div></td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>[https://<ins class="diffchange diffchange-inline">medium</ins>.com/<ins class="diffchange diffchange-inline">digibytepublication</ins>/digibyte-v7-17-2-odocrypt-algo-fork<ins class="diffchange diffchange-inline">-bbd9c0be4d7c Article by </ins>Jared Tate (founder of DigiByte) regarding&nbsp;DigiByte v7.17.2 Odocrypt Algo Fork]</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*[[Choosing_FPGA_hardware|Choosing FPGA hardware]] </div></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*[[Choosing_FPGA_hardware|Choosing FPGA hardware]] </div></td></tr>
</table>JoseTrejo DGB-Noobhttps://www.dgbwiki.com/index.php?title=Odocrypt&diff=1748&oldid=prevNigelDigiByte at 18:48, 4 August 20192019-08-04T18:48:10Z<p></p>
<table class="diff diff-contentalign-left" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">Revision as of 18:48, 4 August 2019</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l7" >Line 7:</td>
<td colspan="2" class="diff-lineno">Line 7:</td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*[[FPGA_mining|FPGA mining]] </div></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*[[FPGA_mining|FPGA mining]] </div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td></tr>
<tr><td class='diff-marker'>−</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>=== How does Odocrypt work? <del class="diffchange diffchange-inline">=</del>==</div></td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>== <ins class="diffchange diffchange-inline">'''<span style</ins>=<ins class="diffchange diffchange-inline">"font-size:x-large;"></ins>How does Odocrypt work?<ins class="diffchange diffchange-inline"></span>''' </ins>==</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Odocrypt uses the Keccak algorithm (SHA3) for its hashing function, as it is a relatively streamlined and low-memory requirements (Perfect for all common FPGAs). It changes the hashing details every epoch (10 day time-period) based on the new seed. This change occurs at midnight UTC. When the epoch changes, the miners must compile a new .sof file (analog of a binary executable for the FPGA CPU) and program it on to the hardware. During this time, there is a 2-hour period prior to the midnight of the epoch in which the blockchain will accept the new epoch settings and / or the old epoch settings. This gives all miners a chance to re-optimize their settings and reprogram their FPGA's, without causing immediate issues in the overall hashrate for the algorithm, despite automated re-programmings taking only a matter of seconds in most instances. Once reprogrammed the FPGA uses the new seed as it's base, which is required in order to maintain the 'optimized' settings. Without this, the FPGA will be churning out invalid hashes and have an effective efficiency of zero.</div></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Odocrypt uses the Keccak algorithm (SHA3) for its hashing function, as it is a relatively streamlined and low-memory requirements (Perfect for all common FPGAs). It changes the hashing details every epoch (10 day time-period) based on the new seed. This change occurs at midnight UTC. When the epoch changes, the miners must compile a new .sof file (analog of a binary executable for the FPGA CPU) and program it on to the hardware. During this time, there is a 2-hour period prior to the midnight of the epoch in which the blockchain will accept the new epoch settings and / or the old epoch settings. This gives all miners a chance to re-optimize their settings and reprogram their FPGA's, without causing immediate issues in the overall hashrate for the algorithm, despite automated re-programmings taking only a matter of seconds in most instances. Once reprogrammed the FPGA uses the new seed as it's base, which is required in order to maintain the 'optimized' settings. Without this, the FPGA will be churning out invalid hashes and have an effective efficiency of zero.</div></td></tr>
</table>NigelDigiBytehttps://www.dgbwiki.com/index.php?title=Odocrypt&diff=1163&oldid=prevNigelDigiByte at 14:49, 18 July 20192019-07-18T14:49:16Z<p></p>
<table class="diff diff-contentalign-left" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">Revision as of 14:49, 18 July 2019</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l2" >Line 2:</td>
<td colspan="2" class="diff-lineno">Line 2:</td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>[https://odocrypt.digibyteservers.io/ Odocrypt] is a unique GPU / FPGA-friendly hashing algorithm made specifically for DigiByte that changes itself every 10 days as an anti-ASIC method.</div></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>[https://odocrypt.digibyteservers.io/ Odocrypt] is a unique GPU / FPGA-friendly hashing algorithm made specifically for DigiByte that changes itself every 10 days as an anti-ASIC method.</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td></tr>
<tr><td class='diff-marker'>−</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del class="diffchange diffchange-inline">As </del>of <del class="diffchange diffchange-inline">March 2019, </del>DigiByte <del class="diffchange diffchange-inline">is testing the algorithm and no code has been merged in to the </del>DigiByte <del class="diffchange diffchange-inline">Core code-base</del>.</div></td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">[https://blockchain2035.com/blogs/digiassetsprotocol/digibyte-v7-17-2-odocrypt-algo-fork Blog post from Jared Tate (founder </ins>of DigiByte<ins class="diffchange diffchange-inline">) regarding&nbsp;</ins>DigiByte <ins class="diffchange diffchange-inline">v7.17</ins>.<ins class="diffchange diffchange-inline">2 Odocrypt Algo Fork]</ins></div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*[[Choosing_FPGA_hardware|Choosing FPGA hardware]] </div></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>*[[Choosing_FPGA_hardware|Choosing FPGA hardware]] </div></td></tr>
</table>NigelDigiBytehttps://www.dgbwiki.com/index.php?title=Odocrypt&diff=880&oldid=prevDigiDevon at 22:30, 12 May 20192019-05-12T22:30:52Z<p></p>
<table class="diff diff-contentalign-left" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">Revision as of 22:30, 12 May 2019</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l1" >Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class='diff-marker'>−</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>Odocrypt is a unique GPU / FPGA-friendly hashing algorithm made specifically for DigiByte that changes itself every 10 days as an anti-ASIC method.</div></td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div> </div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins class="diffchange diffchange-inline">[https://odocrypt.digibyteservers.io/ </ins>Odocrypt<ins class="diffchange diffchange-inline">] </ins>is a unique GPU / FPGA-friendly hashing algorithm made specifically for DigiByte that changes itself every 10 days as an anti-ASIC method.</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>As of March 2019, DigiByte is testing the algorithm and no code has been merged in to the DigiByte Core code-base.</div></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>As of March 2019, DigiByte is testing the algorithm and no code has been merged in to the DigiByte Core code-base.</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td></tr>
<tr><td class='diff-marker'>−</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>* [[Choosing FPGA hardware]]</div></td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>*[[<ins class="diffchange diffchange-inline">Choosing_FPGA_hardware|</ins>Choosing FPGA hardware]] </div></td></tr>
<tr><td class='diff-marker'>−</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>* [[FPGA mining]]</div></td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>*[[<ins class="diffchange diffchange-inline">FPGA_mining|</ins>FPGA mining]] </div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=== How does Odocrypt work? ===</div></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=== How does Odocrypt work? ===</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Odocrypt uses the Keccak algorithm (SHA3) for its hashing function, as it is a relatively streamlined and low-memory requirements (Perfect for all common FPGAs). It changes the hashing details every epoch (10 day time-period) based on the new seed. This change occurs at midnight UTC. When the epoch changes, the miners must compile a new .sof file (analog of a binary executable for the FPGA CPU) and program it on to the hardware. During this time, there is a 2-hour period prior to the midnight of the epoch in which the blockchain will accept the new epoch settings and / or the old epoch settings. This gives all miners a chance to re-optimize their settings and reprogram their FPGA's, without causing immediate issues in the overall hashrate for the algorithm, despite automated re-programmings taking only a matter of seconds in most instances. Once reprogrammed the FPGA uses the new seed as it's base, which is required in order to maintain the 'optimized' settings. Without this, the FPGA will be churning out invalid hashes and have an effective efficiency of zero.</div></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Odocrypt uses the Keccak algorithm (SHA3) for its hashing function, as it is a relatively streamlined and low-memory requirements (Perfect for all common FPGAs). It changes the hashing details every epoch (10 day time-period) based on the new seed. This change occurs at midnight UTC. When the epoch changes, the miners must compile a new .sof file (analog of a binary executable for the FPGA CPU) and program it on to the hardware. During this time, there is a 2-hour period prior to the midnight of the epoch in which the blockchain will accept the new epoch settings and / or the old epoch settings. This gives all miners a chance to re-optimize their settings and reprogram their FPGA's, without causing immediate issues in the overall hashrate for the algorithm, despite automated re-programmings taking only a matter of seconds in most instances. Once reprogrammed the FPGA uses the new seed as it's base, which is required in order to maintain the 'optimized' settings. Without this, the FPGA will be churning out invalid hashes and have an effective efficiency of zero.</div></td></tr>
</table>DigiDevonhttps://www.dgbwiki.com/index.php?title=Odocrypt&diff=708&oldid=prevDgb chilling: Fix formatting coz I'm a monkey2019-03-27T01:12:43Z<p>Fix formatting coz I'm a monkey</p>
<table class="diff diff-contentalign-left" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">Revision as of 01:12, 27 March 2019</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l7" >Line 7:</td>
<td colspan="2" class="diff-lineno">Line 7:</td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=== How does Odocrypt work? ===</div></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>=== How does Odocrypt work? ===</div></td></tr>
<tr><td class='diff-marker'>−</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>Odocrypt uses the Keccak algorithm (SHA3) for its hashing function, as it is a relatively streamlined and low-memory requirements (Perfect for all common FPGAs). It changes the hashing details every epoch (10 day time-period) </div></td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>Odocrypt uses the Keccak algorithm (SHA3) for its hashing function, as it is a relatively streamlined and low-memory requirements (Perfect for all common FPGAs). It changes the hashing details every epoch (10 day time-period) based on the new seed. This change occurs at midnight UTC. When the epoch changes, the miners must compile a new .sof file (analog of a binary executable for the FPGA CPU) and program it on to the hardware. During this time, there is a 2-hour period prior to the midnight of the epoch in which the blockchain will accept the new epoch settings and / or the old epoch settings. This gives all miners a chance to re-optimize their settings and reprogram their FPGA's, without causing immediate issues in the overall hashrate for the algorithm, despite automated re-programmings taking only a matter of seconds in most instances. Once reprogrammed the FPGA uses the new seed as it's base, which is required in order to maintain the 'optimized' settings. Without this, the FPGA will be churning out invalid hashes and have an effective efficiency of zero.</div></td></tr>
<tr><td class='diff-marker'>−</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div><del class="diffchange diffchange-inline"> </del>based on the new seed. This change occurs at midnight UTC. When the epoch changes, the miners must compile a new .sof file (analog of a binary executable for the FPGA CPU) and program it on to the hardware. During this time, there is a 2-hour period prior to the midnight of the epoch in which the blockchain will accept the new epoch settings and / or the old epoch settings. This gives all miners a chance to re-optimize their settings and reprogram their FPGA's, without causing immediate issues in the overall hashrate for the algorithm, despite automated re-programmings taking only a matter of seconds in most instances. Once reprogrammed the FPGA uses the new seed as it's base, which is required in order to maintain the 'optimized' settings. Without this, the FPGA will be churning out invalid hashes and have an effective efficiency of zero.</div></td><td colspan="2"> </td></tr>
</table>Dgb chillinghttps://www.dgbwiki.com/index.php?title=Odocrypt&diff=707&oldid=prevDgb chilling: Added initial Odocrypt blurb2019-03-27T01:12:00Z<p>Added initial Odocrypt blurb</p>
<table class="diff diff-contentalign-left" data-mw="interface">
<col class="diff-marker" />
<col class="diff-content" />
<col class="diff-marker" />
<col class="diff-content" />
<tr class="diff-title" lang="en">
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">← Older revision</td>
<td colspan="2" style="background-color: #fff; color: #222; text-align: center;">Revision as of 01:12, 27 March 2019</td>
</tr><tr><td colspan="2" class="diff-lineno" id="mw-diff-left-l1" >Line 1:</td>
<td colspan="2" class="diff-lineno">Line 1:</td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Odocrypt is a unique GPU / FPGA-friendly hashing algorithm made specifically for DigiByte that changes itself every 10 days as an anti-ASIC method.</div></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>Odocrypt is a unique GPU / FPGA-friendly hashing algorithm made specifically for DigiByte that changes itself every 10 days as an anti-ASIC method.</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td></tr>
<tr><td class='diff-marker'>−</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;"><div>As of March 2019, DigiByte is testing the algorithm and no code has been merged in to the DigiByte Core <del class="diffchange diffchange-inline">codebase</del></div></td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div>As of March 2019, DigiByte is testing the algorithm and no code has been merged in to the DigiByte Core <ins class="diffchange diffchange-inline">code-base.</ins></div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* [[Choosing FPGA hardware]]</div></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* [[Choosing FPGA hardware]]</div></td></tr>
<tr><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* [[FPGA mining]]</div></td><td class='diff-marker'> </td><td style="background-color: #f8f9fa; color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;"><div>* [[FPGA mining]]</div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"></ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">=== How does Odocrypt work? ===</ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;">Odocrypt uses the Keccak algorithm (SHA3) for its hashing function, as it is a relatively streamlined and low-memory requirements (Perfect for all common FPGAs). It changes the hashing details every epoch (10 day time-period) </ins></div></td></tr>
<tr><td colspan="2"> </td><td class='diff-marker'>+</td><td style="color: #222; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;"><div><ins style="font-weight: bold; text-decoration: none;"> based on the new seed. This change occurs at midnight UTC. When the epoch changes, the miners must compile a new .sof file (analog of a binary executable for the FPGA CPU) and program it on to the hardware. During this time, there is a 2-hour period prior to the midnight of the epoch in which the blockchain will accept the new epoch settings and / or the old epoch settings. This gives all miners a chance to re-optimize their settings and reprogram their FPGA's, without causing immediate issues in the overall hashrate for the algorithm, despite automated re-programmings taking only a matter of seconds in most instances. Once reprogrammed the FPGA uses the new seed as it's base, which is required in order to maintain the 'optimized' settings. Without this, the FPGA will be churning out invalid hashes and have an effective efficiency of zero.</ins></div></td></tr>
</table>Dgb chillinghttps://www.dgbwiki.com/index.php?title=Odocrypt&diff=564&oldid=prevDgb chilling: Initial creation2019-03-07T08:35:37Z<p>Initial creation</p>
<p><b>New page</b></p><div>Odocrypt is a unique GPU / FPGA-friendly hashing algorithm made specifically for DigiByte that changes itself every 10 days as an anti-ASIC method.<br />
<br />
As of March 2019, DigiByte is testing the algorithm and no code has been merged in to the DigiByte Core codebase<br />
<br />
* [[Choosing FPGA hardware]]<br />
* [[FPGA mining]]</div>Dgb chilling