I’ve been building an experimental Layer-1 project called Byze and one of the more interesting engineering problems has been implementing a non-custodial browser wallet where signing happens entirely client-side.

The current stack includes:

• RandomX blockchain

• Qt desktop wallet

• browser wallet

• mining pool

• explorer

• standalone CPU miner

• Stratum infrastructure

The browser wallet currently:

• generates/restores mnemonics locally

• derives addresses in-browser

• constructs/signs transactions client-side

• broadcasts signed raw transactions through a lightweight API

The server never receives mnemonics or private keys.

A lot of the difficult work ended up not being consensus itself, but:

• deterministic signing parity

• mempool acceptance parity with Core

• browser bundling/runtime issues

• wallet solvability edge cases

• payout infrastructure

• low-memory VPS deployment

• explorer/pool integration

I’m interested in hearing from others who have worked on:

• browser-side cryptographic signing

• wallet infrastructure

• mining systems

• blockchain operations

• self-hosted crypto infrastructure

Project:
https://byze.org

Explorer:
https://explorer.byze.org

Wallet:
https://wallet.byze.org