Modified the voyager/README.md

[CoolatMax]

Update Voyager documentation with comprehensive architecture overview #738

---

Summary

This PR adds a clear, high-level architecture overview of Voyager, explaining how its design addresses the real-world challenges of IBC relaying, including adversarial conditions, unreliable RPCs, crash recovery, and high-throughput requirements.

The document reframes Voyager as a persistent, transactional state machine, providing readers with a conceptual model for understanding correctness, parallelism, and extensibility across heterogeneous chains.

---

Motivation

The previous Voyager documentation did not clearly explain:

• Why relaying is intrinsically difficult in production environments
• How Voyager guarantees correctness under concurrency and failure
• How crash recovery and fast startup are achieved
• How modularity enables support for new chains, light clients, and recursive (state lens) clients

This update fills that gap by documenting Voyager’s core architectural principles and execution model.

---

What’s Included

• Core relayer requirements: speed, data integrity, and crash recovery
• Voyager’s persistent finite state machine and transactional execution model
• Parallelism-by-construction using PostgreSQL-backed state
• Light client support (Tendermint, Ethereum, custom Union clients)
• Conditional / recursive Ethereum L2 clients and finality model
• Clear definitions of key abstractions:
  • Chains, consensus, client types, IBC interfaces
  • Modules vs plugins and queue-based execution
• JSON-RPC interface and developer ergonomics
• Extensibility model for new chains, rollups, and consensus mechanisms

---

Scope Notes

• Conceptual and architectural documentation only
• No implementation, API, or behavior changes
• No protocol semantics modified

---

Impact

• Makes Voyager’s design decisions explicit and reviewable
• Improves onboarding for contributors and integrators
• Provides a stable architectural reference for future feature work
• Aligns documentation with Voyager’s production-grade relayer guarantees

---

Related Context

This documentation updates and expands the Voyager docs to better reflect the current architecture and execution model.

[vercel]

@CoolatMax is attempting to deploy a commit to the unionbuild Team on Vercel.

A member of the Team first needs to authorize it.

[benluelo]

there are some good changes here, but most of this is unnecessary rewording and increased verbosity. please consider which changes are actually adding to the quality of the documentation.

[CoolatMax]

Sure @benluelo I'll go through the docs once again. And reiterate it.