https://github.com/blockscout/blockscout-rs
Microservices for blockscout indexer
https://github.com/blockscout/blockscout-rs
rust
Last synced: 3 months ago
JSON representation
Microservices for blockscout indexer
- Host: GitHub
- URL: https://github.com/blockscout/blockscout-rs
- Owner: blockscout
- License: mit
- Created: 2022-05-20T12:38:30.000Z (about 4 years ago)
- Default Branch: main
- Last Pushed: 2026-01-29T14:48:05.000Z (5 months ago)
- Last Synced: 2026-01-30T01:54:53.027Z (5 months ago)
- Topics: rust
- Language: Rust
- Homepage:
- Size: 11.1 MB
- Stars: 210
- Watchers: 10
- Forks: 187
- Open Issues: 225
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE-MIT
Awesome Lists containing this project
README
Blockscout Rust Services
A set of services used by [Blockscout](https://blockscout.com/) blockchain explorer, written in Rust.
## Services
1. [blockscout-ens](blockscout-ens) - indexed data of domain name service for blockscout instances.
2. [da-indexer](da-indexer) - collects blobs from different DA solutions (e.g, Celestia)
3. [eth-bytecode-db](eth-bytecode-db/) - Ethereum Bytecode Database. Cross-chain smart-contracts database used for automatic contracts verification
4. [interchain-indexer](interchain-indexer/) - Universal Bridge Indexer. A standalone service for indexing and aggregating interoperability data across multiple blockchains
5. [proxy-verifier](proxy-verifier) - backend for the standalone multi-chain verification service
6. [sig-provider](sig-provider/) - aggregator of ethereum signatures for transactions and events
7. [smart-contract-verifier](smart-contract-verifier/) - smart-contracts verification
8. [stats](stats) - service designed to calculate and present statistical information from a Blockscout instance
9. [tac-operation-lifecycle](tac-operation-lifecycle/) - indexing operations in TAC (Ton Application Chain)
10. [user-ops-indexer](user-ops-indexer) - service designed to index, decode and serve user operations as per the ERC-4337 standard
11. [visualizer](visualizer/) - service for evm visualization such as:
* Solidity contract visualization using [sol2uml](https://www.npmjs.com/package/sol2uml)
12. [multichain-aggregator](multichain-aggregator/) - service to store and index data from multiple blockscout instances. Also contains logic with [interop messages](https://docs.optimism.io/interop/message-passing)
## Running and configuring services
Services are distributed as docker images. For each service, you can find information about packages and their recent releases
inside service directories.
You can configure your app by passing the necessary environment variables when starting the container.
Configuration variables common for all services can be found [here](docs/common-envs.md).
See full list of ENVs and their description inside service directories.
```shell
docker run -p 8050:8050 --env-file ghcr.io/blockscout/{service-name}:latest
```
Alternatively, you can build your own docker images or compile them directly from sources.
Some of such options are described in [build](docs/build.md).
## Project Layouts
Most of the projects consist of 3 main parts:
1. `{service-name}-proto` - defines the gRPC proto file with all API related data.
Defines mapping HTTP/JSON requests and their parameters to those gRPC methods.
2. `{service-name}-logic` - the crate with the implementation of the main business logic.
_Note: previously the logic crate was named as `{service-name}`;
some services still use that convention_
3. `{service-name}-server` - initialize the server using the defined API.
Using the methods from “{service-name}-logic” to handle incoming requests.
The separation on "logic" and "server" crates is designed to separate functional and transport layers.
For now, "server" crates contain gRPC and HTTP as the transport layer.
It was assumed, that users may want to implement their own APIs, for which the library with functional logic might be used.
Crates that require database connection may also have additional `sea-orm`-defined crates:
1. `{service-name}-migration` - contains migrations for the database
2. `{service-name}-entity` - contains the entity files generated from the schema
## Contributing
We appreciate your support. Before writing code and submitting a pull request, please read contributing [instructions](CONTRIBUTING.md).
## License
This project is primarily distributed under the terms of the MIT license. See [LICENSE-MIT](LICENSE-MIT) for details.