Keyboard shortcuts

Press or to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Services & Infrastructure

This document outlines the internal infrastructure and services running the Satoshi Protocol.

Environments

We operate two primary environments: Staging and Mainnet.

Note on Network Usage

Both environments run on the Near Mainnet. This configuration is necessary because:

  • Near Intents, required for our liquidation logic, is unavailable on Testnet.
  • Deposit workflows can only be fully tested on Mainnet.

Developers are still encouraged to use Testnet for general Near blockchain familiarity.

Core Components

Each environment relies on the following core components:

  • Smart Contract: The deployed lending protocol logic.
  • Bots: Services that continuously monitor the protocol for liquidations.
  • Indexer: Ingests blockchain blocks and provides REST API services to the frontend.
  • Frontend: The web interface for interacting with the smart contract.

Staging Environment

Current deployment status and endpoints for the Staging environment:

We have two Slack channels to monitor the health of the applications in Staging environment:

  • sp-staging-monitoring: All crash alerts of the application from health-check go there.
  • sp-staging-notifications: Any task failures or downtime of an application goes to this channel.

Mainnet Environment

Current deployment status and endpoints for the Mainnet environment:

We have two Slack channels to monitor the health of the applications in Staging environment:

  • sp-mainnet-monitoring: All crash alerts of the application from health-check go there.
  • sp-mainnet-notifications: Any task failures or downtime of an application goes to this channel.