Skip to content

Commit

Permalink
feat(docs): populate voyager.md
Browse files Browse the repository at this point in the history
  • Loading branch information
KaiserKarel committed Sep 27, 2023
1 parent 68bbdbd commit 8d4bb1b
Show file tree
Hide file tree
Showing 3 changed files with 30 additions and 7 deletions.
10 changes: 4 additions & 6 deletions docs/docs/01_intro.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,9 +4,7 @@ slug: /

# Union

The Union network is a hyper-efficient zero-knowledge infrastructure layer for general message passing, asset transfers, NFTs, and DeFi. It's based on consensus verification and has no dependencies on trusted third parties, oracles, multi-signatures, or [MPC](https://en.wikipedia.org/wiki/Secure_multi-party_computation). To summarize:

_Union is the most efficient, trustless bridge_
The Union network is a hyper-efficient zero-knowledge infrastructure layer for general message passing, asset transfers, NFTs, and DeFi. It's based on consensus verification and has no dependencies on trusted third parties, oracles, multi-signatures, or [MPC](https://en.wikipedia.org/wiki/Secure_multi-party_computation).

## Who is Union built for?

Expand All @@ -17,6 +15,6 @@ For those who care about decentralization and reliability, and believe that fina
Union is developed to be a scalable powerhouse:

- Fast: bridging transactions are generated and settled quickly.
- Secure: zero-knowledge consensus verification.
- Future proof: core tech is built for the next decennium
- Easy to use: high-level API usable for developers from any ecosystem
- Secure: abide by fork-choice rules.
- Future proof: core tech is built for the next decennium.
- Easy to use: high-level API usable for developers from any ecosystem.
25 changes: 25 additions & 0 deletions docs/docs/02_architecture/voyager.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,28 @@
---
title: "Voyager"
---

# Voyager

IBC relays on off-chain actors transferring packets and proofs between chains. Voyager is our in-house relayer, allowing us to support new networks without waiting for up-stream support.

## Architecture

We have opted for an event driven architecture, where the application uses an internal memory queue for observed events and I/O.

```mermaid
stateDiagram-v2
direction LR
EventListener --> Queue
Queue --> Processor
state Processor {
[*] --> Actor
Actor --> Galois
Galois --> [*]
}
Processor --> Chains
Chains --> EventListener
```

Voyager integrates over [gRPC](https://grpc.io/) with Galois to offload computation to dedicated hardware, with pending support for proving markets.
2 changes: 1 addition & 1 deletion site/src/routes/blog/the-journey-so-far/+page.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ Today, we are happy to announce the work we have done so far on Union, the trust

We spent months building in stealthmode, heads-down, as we validated our technical assumptions. The product of that is the Union testnet, [CometBLS](https://docs.union.build/architecture/cometbls), [Voyager](https://docs.union.build/architecture/voyager), and [Galois](https://docs.union.build/architecture/galois). These components allowed us to achieve **IBC to Ethereum, the endgame**.`

Union is designed around a few key principles: permissonless interopability, censorship resistance, and decentralized infrastrucutre. Anyone should be allowed to transact, with any counterparty, on any chain, and this system may not rely on massive, closed source infrastructure.
Union is designed around a few key principles: code is law and barrier to entry leads to centralization. This means that we design our products to allow anyone to run them, not just parties with massive CPU/GPU farms. Proof generation must be a fair market to avoid censorship.

With Union, we can bring any asset natively to any chain, hook into account abstraction with ICQ, and access coprocecors and storage proofs.

Expand Down

0 comments on commit 8d4bb1b

Please sign in to comment.