Infrastructure
This document outlines the third-party services and infrastructure components used by the protocol.
RPC Nodes
We utilize paid RPC nodes provided by FastNear.
| Usage | Details |
|---|---|
| Provider | FastNear (Paid Plan) |
| Consumers | Frontend Site, Bot |
- Status: https://status.fastnear.com/status/main
- Contact: Telegram
Near Data Server
This service is distinct from the standard RPC nodes.
- Provider: FastNear (Paid endpoint)
- Documentation: neardata-server on GitHub
- Usage: Indexer
- Status: https://status.fastnear.com/status/main
- Contact: Telegram
Hermes
We utilize a paid Hermes endpoint to fetch real-time price information.
- Type: Paid Endpoint
- Purpose: Price Feeds
- Consumers: Frontend, Bots
- Contact: Triton Pyth Levana group in Telegram, levana-pyth Slack channel
One Click
This service is utilized by our liquidation infrastructure.
- Usage: Liquidation Bots
- Purpose: Performing swaps on user collateral
- Status: https://status.near-intents.org/posts/dashboard
- Contact:
near-satoshi-portchannel in Slack
PoA Bridge
- Usage: Frontend
- Purpose: Deposits from external chains (excluding BTC)
- URL: https://bridge.chaindefuser.com/rpc
- Docs: Near Intents
- Status: https://status.near-intents.org/posts/dashboard
- Contact:
near-satoshi-portchannel in Slack
OmniBridge
- Usage: Frontend
- Purpose: External BTC deposits
- URL: https://mainnet.api.bridge.nearone.org
- Source: bridge-sdk-js on GitHub
- Status: https://status.near-intents.org/posts/dashboard
- Contact:
near-satoshi-portchannel in Slack
NowNodes API
- Usage: Frontend (through Indexer endpoints)
- Purpose: Finding information about BTC wallet address and transaction information
- Status: https://nownodes.site24x7statusiq.com/
- Contact: Telegram
Zendesk
- Usage: Frontend
- Purpose: Provides support chat
- Status: https://status.zendesk.com/
- Owner: Carla
Reown
- Usage: Frontend
- Purpose: For ethereum wallet
- Status: https://status.reown.com/
- Owner: Alejandro