The latest articles on DEV Community by byze (@byze_dev). https://dev.to/byze_dev https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3953432%2F844ece57-3b6f-44b8-84ce-27854d08c5fa.png https://dev.to/byze_dev en byze Wed, 27 May 2026 02:36:49 +0000 https://dev.to/byze_dev/byze-1mgf https://dev.to/byze_dev/byze-1mgf <h1> Building Byze: An Experimental RandomX Layer-1 With Browser-Side Signing </h1> <p>Over the past months I’ve been building an experimental Layer-1 blockchain project called Byze.</p> <p>The goal is not to create “another token,” but to explore a full open-source ecosystem around:</p> <ul> <li>RandomX mining</li> <li>browser-side non-custodial signing</li> <li>mining pool infrastructure</li> <li>Qt wallet development</li> <li>self-hosted blockchain infrastructure</li> <li>quantum-signature experimentation</li> </ul> <h2> Current ecosystem status </h2> <p>The infrastructure stack is now operational:</p> <ul> <li>Qt desktop wallet</li> <li>standalone CPU miner</li> <li>mining pool</li> <li>block explorer</li> <li>browser wallet with local signing</li> <li>payout infrastructure</li> <li>nginx/Cloudflare deployment stack</li> </ul> <p>Main services:</p> <ul> <li><a href="https://byze.org" rel="noopener noreferrer">https://byze.org</a></li> <li><a href="https://wallet.byze.org" rel="noopener noreferrer">https://wallet.byze.org</a></li> <li><a href="https://explorer.byze.org" rel="noopener noreferrer">https://explorer.byze.org</a></li> <li><a href="https://pool.byze.org" rel="noopener noreferrer">https://pool.byze.org</a></li> </ul> <h2> Browser-side signing </h2> <p>One area I wanted to explore was fully browser-side transaction signing.</p> <p>The web wallet keeps:</p> <ul> <li>mnemonic generation</li> <li>HD derivation</li> <li>XMSS/SPHINCS signing</li> <li>transaction construction</li> </ul> <p>inside the browser.</p> <p>The server only:</p> <ul> <li>serves chain data</li> <li>broadcasts signed raw transactions</li> </ul> <p>No private keys or mnemonics are uploaded to the server.</p> <h2> Mining architecture </h2> <p>Byze uses RandomX and currently supports:</p> <ul> <li>in-process solo mining</li> <li>standalone pooled mining</li> <li>Stratum pool infrastructure</li> </ul> <p>I also built a standalone miner instead of depending entirely on XMRig-style integrations.</p> <p>Example:<br> </p> <p>```bash id="5h2u7x"<br> ./byze-miner \<br> --pool pool.byze.org:3333 \<br> --wallet YOUR_WALLET \<br> --worker rig01 \<br> --threads 8</p> <div class="highlight js-code-highlight"> <pre class="highlight plaintext"><code> ## Infrastructure lessons The majority of the work was not consensus code. It was: * payout reliability * wallet solvability edge cases * browser bundling * mempool parity testing * systemd deployment * nginx/static deployment * chain synchronization * explorer APIs * production restart behavior * low-memory VPS tuning Building a blockchain is easy compared to operating one reliably. ## Current focus The project is still pre-launch/private while infrastructure stabilizes. Current priorities: * release engineering * wallet UX polish * deterministic signing parity * reproducible builds * monitoring * documentation * deployment automation ## Why I’m posting I’m interested in connecting with: * blockchain infrastructure developers * mining/pool operators * wallet developers * cryptography researchers * self-hosted/open-source builders especially people working on the practical operational side of crypto systems rather than just token launches. More updates soon as the project approaches launch. </code></pre> </div> blockchain cryptocurrency showdev web3