| Repository | Description |
|---|---|
| mono-chain | LythiumBFT chain node (monod) |
| mono-commander | TUI-first CLI for node operators (monoctl) |
| networks | Network configurations and genesis files |
| validators | Validator dashboard and performance tracking |
| mono-core-peers | Peer registry for network bootstrapping |
| mono-chain-registry | Chain metadata registry (chain IDs, RPCs, assets) |
| Repository | Description |
|---|---|
| browser-wallet | Browser extension wallet (Chrome, Firefox, Edge) |
| desktop-wallet | Desktop wallet (macOS, Windows, Linux) |
| mobile-wallet | Mobile wallet (iOS, Android) |
| monoscan | Block explorer with EVM and Cosmos support |
| guardian | Automated security scanner |
| api-utils | Shared TypeScript utilities for Monolythium apps |
| Network | Chain ID | EVM Chain ID | Hex |
|---|---|---|---|
| Localnet | mono-local-1 |
262145 | 0x40001 |
| Sprintnet | mono-sprint-1 |
262146 | 0x40002 |
| Testnet | mono_6940-1 |
6940 | 0x1B1C |
| Mainnet | mono_6941-1 |
6941 | 0x1B1D |
Important: All networks require the official
genesis.json. Do not start your own chain.
DNS-based seed discovery is available for all public networks:
seed1.<network>.mononodes.xyz
seed2.<network>.mononodes.xyz
seed3.<network>.mononodes.xyz
Replace <network> with sprintnet, testnet, or mainnet.
The peer registry (peers.json) provides bootstrap peers for each network. Each entry includes:
chain_idfor network identificationgenesis_sha256for genesis verification
Peer registries are for operator convenience only and do not affect consensus.
# Install Mono Commander
go install github.com/monolythium/mono-commander/cmd/monoctl@latest
# Launch the interactive TUI
monoctl
# Or join a network via CLI
monoctl join --network Sprintnet --home ~/.monod- MetaMask / Web3 wallets: Connect using the EVM JSON-RPC endpoint
- Chain ID: Use the EVM Chain ID from the networks table above
- RPC endpoints: See network-specific documentation
- Keplr / Leap: Native Cosmos wallet support for staking and governance
- CLI: Use
monodfor direct chain interaction
If you discover a security vulnerability in any Monolythium product:
- Report it at issues.monolythium.com (preferred) or via GitHub Security Advisories
- Do NOT open a public issue
- Test on testnet only — all contracts are deployed 1:1 on testnet and mainnet
We provide safe harbor for good-faith security researchers under CFAA and equivalent laws. Valid findings are eligible for LYTH token rewards.
See our Bug Bounty Program and Security Policy for full details.
We welcome contributions! Please review:
- Follow Go conventions and formatting (
gofmt) - Add tests for new functionality
- Keep commits focused and atomic
- Update documentation as needed
No rollback. Emergency response: HALT → PATCH → UPGRADE → RESTART
- Sprintnet: Active development network
- Testnet: Coming soon (mainnet-mirror configuration)
- Mainnet: Planned