# Venus overview

Venus is one of the implementations of Filecoin storage network, which focuses on distributed architecture and a more concise division of functionalities. Storage resources are geographically dipersed, which means as long as there is internet connection a storage cluster can be connected to the Venus storage pool.

# Architecture

The venus components/modules includes includes venus (opens new window), venus-auth (opens new window), venus-miner (opens new window), venus-messager (opens new window), venus-gateway (opens new window), venus-wallet (opens new window), venus-sealer (opens new window), and venus-market (opens new window). Based on functionalities, the components can be broken into shared components (chain services) and independent components. As a storage provider using chain services, it is no longer required to maintain chain synchronization, micro manage the sending of each message and more. As a chain services provider with hardware resources, it can build chain services for other storage providers and potentially charge service fees from them. For large storage providers, they can also take advantage of venus architecture to allow quicker expansion and easier maintenance.

The following figure demonstrates how each component interacts with each other. In this illustration, chain services is serving one storage provider and can easily scale to serve multiple storage providers.

The following shows venus components to lotus components relationship.

  • venus-auth --> token authentication service extend lotus jwt
  • venus-miner --> lotus-miner block produce part & multi miner
  • venus-sealer --> lotus-miner sealer scheduler part/wd
  • venus-worker --> lotus-worker
  • venus daemon --> lotus daemon
  • venus-wallet -> lotus wallet part
  • venus-messager --> lotus mpool
  • venus-market --> lotus-miner market part

# How venus works

For more on how each venus components work, please go through this document here (opens new window).