Archive legacy status docs and canonicalize genesis entrypoints
This commit is contained in:
@@ -49,7 +49,7 @@
|
||||
|
||||
## Overview
|
||||
|
||||
The DeFi Oracle Meta Mainnet (ChainID 138) is a production-ready blockchain network built on Hyperledger Besu with QBFT (Quorum Byzantine Fault Tolerance) consensus. The network is designed as a read network with public RPC endpoints and internal oracle publishers.
|
||||
The DeFi Oracle Meta Mainnet (ChainID 138) is an operator-focused blockchain network built on Hyperledger Besu with QBFT (Quorum Byzantine Fault Tolerance) consensus. The network is designed as a read network with public RPC endpoints and internal oracle publishers.
|
||||
|
||||
## Network Architecture
|
||||
|
||||
@@ -276,4 +276,3 @@ The network is organized into three tiers:
|
||||
- DeFi protocol integrations
|
||||
- Layer 2 solutions
|
||||
- Privacy features (Tessera)
|
||||
|
||||
|
||||
@@ -236,7 +236,7 @@ Diagrams are tracked in Git:
|
||||
|
||||
## References
|
||||
|
||||
- [Assets Guide](ASSETS_GUIDE.md)
|
||||
- [Assets Guide](../guides/ASSETS_GUIDE.md)
|
||||
- [Azure Architecture Center](https://docs.microsoft.com/azure/architecture/)
|
||||
- [Azure Architecture Icons](https://docs.microsoft.com/azure/architecture/icons/)
|
||||
- [Azure Architecture Patterns](https://docs.microsoft.com/azure/architecture/patterns/)
|
||||
@@ -267,4 +267,3 @@ make -f Makefile.assets download-icons
|
||||
- Network: `assets/diagrams/network/`
|
||||
- Deployment: `assets/diagrams/deployment/`
|
||||
- Templates: `assets/diagrams/templates/`
|
||||
|
||||
|
||||
@@ -38,9 +38,10 @@ This document explains the directory structure of the project, particularly the
|
||||
#### `scripts/` - Shell Scripts
|
||||
- **Purpose**: Contains utility shell scripts for deployment, key management, etc.
|
||||
- **File Pattern**: `*.sh`
|
||||
- **Usage**: `./scripts/generate-genesis.sh`
|
||||
- **Usage**: `./scripts/generate-genesis-proper.sh 4`
|
||||
- **Contents**:
|
||||
- `generate-genesis.sh` - Genesis file generation script
|
||||
- `generate-genesis-proper.sh` - Canonical QBFT genesis file generation script
|
||||
- `generate-genesis.sh` - Compatibility wrapper for the canonical generator
|
||||
- `deployment/` - Deployment scripts
|
||||
- `deploy-weth.sh` - WETH deployment script
|
||||
- `deploy-multicall.sh` - Multicall deployment script
|
||||
@@ -104,7 +105,7 @@ RPC_URL=https://rpc.d-bis.org ./tests/health-check.sh
|
||||
### Running Shell Scripts
|
||||
```bash
|
||||
# Generate genesis
|
||||
./scripts/generate-genesis.sh
|
||||
./scripts/generate-genesis-proper.sh 4
|
||||
|
||||
# Generate validator keys
|
||||
./scripts/key-management/generate-validator-keys.sh 4
|
||||
|
||||
@@ -9,7 +9,7 @@ The DeFi Oracle Meta Mainnet uses a tiered architecture with validators, sentrie
|
||||
- **Count**: 4+ validators
|
||||
- **Location**: Private subnets, no public IPs
|
||||
- **Peering**: Only to sentries (via static-nodes.json)
|
||||
- **Consensus**: IBFT 2.0
|
||||
- **Consensus**: QBFT
|
||||
- **RPC**: Disabled for security
|
||||
|
||||
### Sentries
|
||||
@@ -86,7 +86,7 @@ accounts-allowlist=[
|
||||
]
|
||||
```
|
||||
|
||||
## IBFT 2.0 Configuration
|
||||
## QBFT Configuration
|
||||
|
||||
### Genesis Parameters
|
||||
|
||||
@@ -98,7 +98,7 @@ accounts-allowlist=[
|
||||
|
||||
### Validator Set
|
||||
|
||||
Validators are specified in the genesis `extraData` field. The validator set can be updated via IBFT transitions.
|
||||
Validators are specified in the genesis `extraData` field. The validator set can be updated via QBFT transitions.
|
||||
|
||||
### Consensus Parameters
|
||||
|
||||
@@ -170,7 +170,7 @@ Monitor network topology to ensure proper peering:
|
||||
|
||||
### Updating Consensus Parameters
|
||||
|
||||
1. Create IBFT transition block
|
||||
1. Create QBFT transition block
|
||||
2. Update block period, epoch length, or request timeout
|
||||
3. All validators must accept the transition
|
||||
|
||||
@@ -189,4 +189,3 @@ Monitor network topology to ensure proper peering:
|
||||
- Validator failure: Remove failed validator
|
||||
- Chain stall: Restart validators
|
||||
- Security incident: Isolate affected nodes
|
||||
|
||||
|
||||
Reference in New Issue
Block a user