---
# System prepended metadata

title: PIT Alchemy Q&A

---

# PIT Alchemy Q&A

## What Ethereum networks does PIT support
* Mainnet
* Ropsten

## What Ethereum Api does PIT use
PIT built on top of [Parity Api](https://wiki.parity.io/JSONRPC) and uses Parity specific features (i.e. [VM traces](https://wiki.parity.io/JSONRPC-trace-module.html)) which are not the part of standard [Ethereum JSON-RPC Api](https://github.com/ethereum/wiki/wiki/JSON-RPC)

## What PIT environments exists
* unstable (idle)
* staging (idle)
* production (active)

## What PIT apps exists per each environment
* blockchain-state-ethereum-mainnet
* blockchain-state-ethereum-ropsten
* ethereumd-mainnet
* ethereumd-ropsten
* ethereum-consistency-checker-mainnet
* ethereum-consistency-checker-ropsten

![Kubernetes Pods](https://i.imgur.com/qCzaua1.png)

## What Alchemy apps belongs to PIT
* Production Mainnet (active app)
* Production Ropsten (active app)
* Staging Mainnet (idle app)
* Staging Ropsten (idle app)

![Upvest ALchemy Apps](https://i.imgur.com/6EWD52y.png)

## What Alchemy apps does PIT use
* Production Mainnet
* Production Ropsten

## What Alchemy endpoints does PIT use
* `eth_blockNumber` (blockchain-state-ethereum, ethereumd)
* `eth_getBlockByNumber` (blockchain-state-ethereum, ethereumd)
* `eth_getBlockByHash` (blockchain-state-ethereum, ethereumd)
* `eth_getLogs` (blockchain-state-ethereum, ethereumd)
* `trace_replayBlockTransactions` (blockchain-state-ethereum, ethereumd)
* `eth_getTransactionReceipt` (blockchain-state-ethereum, ethereumd)
* `eth_call` (ethereum-consistency-checker)

## What fallback in-house nodes does PIT use
* 104.198.243.49 (Mainnet)
* 34.69.172.237 (Ropsten)
