Network Overview

Goliath Network Architecture

The Goliath Network is a multi-layered, modular system designed to support decentralized applications at scale with uncompromising performance, security, and flexibility. This document provides a comprehensive overview of the network's architecture and core components.

πŸ›οΈ System Architecture

Goliath Network Architecture

🌐 Core Components

1. Core Ledger Node (ledger-core)

The Core Ledger Node is the heart of the Goliath network, responsible for:

  • Consensus Formation: Achieving distributed agreement on transaction order

  • State Management: Maintaining the authoritative ledger state

  • Transaction Processing: Validating and executing transactions

  • Event Stream Generation: Producing ordered event records

Key Features:

  • Asynchronous Byzantine Fault Tolerance (aBFT)

  • 100,000+ TPS capacity

  • 3-5 second finality

  • Fair ordering guarantees

2. EVM Gateway (evm-gateway)

The EVM Gateway provides Ethereum compatibility:

  • JSON-RPC Interface: Full Ethereum JSON-RPC API support

  • Transaction Translation: Converts EVM transactions to native format

  • Smart Contract Execution: Runs Solidity contracts on Goliath

  • Web3 Compatibility: Seamless integration with existing tools

Endpoints:

  • https://rpc.testnet.goliath.net - HTTP endpoint

  • wss://rpc.testnet.goliath.net/ws - WebSocket endpoint

3. Indexer Node Components

The Indexer Node provides data accessibility and querying:

Observer Ingestor (observer-ingestor)

  • Processes event streams from Core nodes

  • Maintains transaction history

  • Indexes smart contract events

  • Updates account balances

Stream Fetcher (stream-fetcher)

  • Downloads event stream files

  • Validates data integrity

  • Manages local buffer (record-stream-spool)

Ledger Index DB (ledger-index-db)

  • PostgreSQL-based storage

  • Optimized for complex queries

  • Maintains full transaction history

  • Stores smart contract state

Observer REST API (observer-rest)

  • RESTful interface for data queries

  • Account balance lookups

  • Transaction history

  • Network statistics

Observer gRPC API (observer-grpc)

  • High-performance streaming API

  • Real-time event subscriptions

  • Bulk data operations

EVM Indexer API (evm-indexer-api)

  • Web3-compatible query interface

  • Smart contract event logs

  • ERC token tracking

  • DeFi protocol analytics

πŸ”„ Transaction Flow

EVM Transaction Lifecycle

  1. Submission: User submits transaction via MetaMask to EVM Gateway

  2. Translation: EVM Gateway converts to native Goliath format

  3. Propagation: Transaction broadcast to Core Ledger nodes

  4. Consensus: Nodes reach agreement on ordering

  5. Execution: Smart contract code executed

  6. Recording: Results written to event stream

  7. Indexing: Observer Ingestor updates database

  8. Confirmation: User receives transaction receipt

Native Transaction Lifecycle

  1. Creation: Application creates native transaction

  2. Signing: Transaction signed with private key

  3. Submission: Sent directly to Core Ledger Node

  4. Validation: Signature and balance checks

  5. Consensus: Fair ordering established

  6. State Update: Ledger state modified

  7. Streaming: Event written to stream

  8. Indexing: Database updated for queries

🎯 Key Design Principles

1. Layered Architecture

Separation of Concerns:

  • Core layer handles consensus

  • Indexer layer provides queries

  • Gateway layer ensures compatibility

Benefits:

  • Independent scaling

  • Focused optimization

  • Clear upgrade paths

2. Event-Driven Design

Event Streams:

  • Immutable record of all activity

  • Cryptographically secured

  • Enables audit trails

  • Supports compliance

Processing Pipeline:

  • Asynchronous processing

  • Parallel indexing

  • Real-time updates

3. Dual Protocol Support

EVM Compatibility:

  • Ethereum tools work unchanged

  • Existing contracts deployable

  • Familiar developer experience

Native Performance:

  • Direct API access

  • Optimized operations

  • Advanced features

πŸ“¦ Data Management

Storage Layers

  1. Consensus State (Core Nodes)

    • Current balances

    • Smart contract state

    • Active configuration

  2. Event History (Event Streams)

    • All transactions

    • State transitions

    • Consensus proofs

  3. Indexed Data (PostgreSQL)

    • Searchable history

    • Analytics data

    • Application state

Data Retention

Component
Retention Period
Purpose

Core State

Current only

Active operations

Event Streams

7 days

Recent history

Index DB

Indefinite

Full history

File Storage

User-defined

Persistent data

🌐 Network Topology

Node Types

  1. Core Nodes (Consensus Participation)

    • Stake-weighted voting

    • Transaction validation

    • State management

    • Event generation

  2. Indexer Nodes (Data Services)

    • Read-only access

    • Query processing

    • Analytics support

    • API services

  3. Gateway Nodes (Protocol Translation)

    • EVM compatibility

    • Load balancing

    • Request routing

Network Communication

P2P Network Communication

πŸ” Security Architecture

Consensus Security

  • aBFT Protocol: Tolerates up to 1/3 malicious nodes

  • Stake-Based: Economic incentives align behavior

  • Cryptographic Proofs: Every state change verifiable

Network Security

  • TLS 1.3: All communications encrypted

  • DDoS Protection: Rate limiting and filtering

  • Node Authentication: Public key infrastructure

Application Security

  • Smart Contract Auditing: Best practices enforcement

  • Account Security: Multi-signature support

  • Key Management: Hardware wallet integration

πŸŽ‰ Performance Characteristics

Throughput

Metric
Value
Notes

TPS (Native)

100,000+

Cryptocurrency transfers

TPS (Smart Contracts)

15,000+

Complex operations

Finality Time

3-5 seconds

Time to irreversibility

Block Time

~3 seconds

New block creation

Scalability

Horizontal Scaling:

  • Add indexer nodes for read capacity

  • Deploy regional gateways

  • Implement caching layers

Vertical Scaling:

  • Increase node resources

  • Optimize database queries

  • Enhance network bandwidth

Future Sharding:

  • Parallel transaction processing

  • Cross-shard communication

  • Linear scalability improvements

πŸŽ† Advanced Features

1. Goliath Mesh

Decentralized message ordering service:

  • Fair timestamp assignment

  • Cryptographic ordering proofs

  • Off-chain application support

2. Native Token Service

Create tokens without smart contracts:

  • Lower costs than ERC-20

  • Built-in compliance features

  • Atomic operations support

3. File Storage Service

Distributed file storage:

  • Content-addressable

  • Redundant storage

  • Controlled mutability

πŸ“Š Monitoring & Analytics

Observer Monitor (observer-monitor)

  • Network health metrics

  • Performance analytics

  • Alert generation

  • Capacity planning

Key Metrics

  • Transaction throughput

  • Consensus latency

  • Node participation

  • Network utilization

  • Error rates

πŸš€ Getting Started

For Developers

For Operators

πŸ“š Additional Resources


The Goliath Network represents a breakthrough in distributed ledger technology, combining enterprise-grade performance with decentralized governance and uncompromising security. The above resources are closed-source until mainnet launch.

Last updated