Building Byze: An Experimental RandomX Layer-1 With Browser-Side Signing
Over the past months I’ve been building an experimental Layer-1 blockchain project called Byze.
The goal is not to create “another token,” but to explore a full open-source ecosystem around:
- RandomX mining
- browser-side non-custodial signing
- mining pool infrastructure
- Qt wallet development
- self-hosted blockchain infrastructure
- quantum-signature experimentation
Current ecosystem status
The infrastructure stack is now operational:
- Qt desktop wallet
- standalone CPU miner
- mining pool
- block explorer
- browser wallet with local signing
- payout infrastructure
- nginx/Cloudflare deployment stack
Main services:
Browser-side signing
One area I wanted to explore was fully browser-side transaction signing.
The web wallet keeps:
- mnemonic generation
- HD derivation
- XMSS/SPHINCS signing
- transaction construction
inside the browser.
The server only:
- serves chain data
- broadcasts signed raw transactions
No private keys or mnemonics are uploaded to the server.
Mining architecture
Byze uses RandomX and currently supports:
- in-process solo mining
- standalone pooled mining
- Stratum pool infrastructure
I also built a standalone miner instead of depending entirely on XMRig-style integrations.
Example:
```bash id="5h2u7x"
./byze-miner \
--pool pool.byze.org:3333 \
--wallet YOUR_WALLET \
--worker rig01 \
--threads 8
## 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.
Top comments (0)