whatisgithub

What is pulsefi?

0xr10t/pulsefi — explained in plain English

Analysis updated 2026-05-18

0RustAudience · developerComplexity · 4/5Setup · hard

In one sentence

An educational Rust project aiming to track live crypto market and onchain trade data and store it for dashboards and alerts.

Mindmap

mindmap
  root((repo))
    What it does
      Track onchain events
      Ingest market data
      Decode trade data
    Tech stack
      Rust
      ClickHouse
      Postgres
      Redis
    Use cases
      Whale alerts
      Market dashboards
    Audience
      Developers
      Researchers

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Track EVM onchain trade events in real time for analysis.

USE CASE 2

Pull in live Hyperliquid market data alongside onchain activity.

USE CASE 3

Set up alerts that flag unusually large whale trades as they happen.

What is it built with?

RustClickHousePostgresRedisGrafana

How does it compare?

0xr10t/pulsefi404-agent/codes-minerbakome-hub/bakome-crypto-quant-engine
Stars000
LanguageRustRustRust
Setup difficultyhardmoderateeasy
Complexity4/53/53/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · hard Time to first run · 1day+

Requires setting up ClickHouse, Postgres, Redis, and Grafana together, none of which the README explains how to configure.

No license information is stated in the README.

So what is it?

PulseFi is a Rust project described as a DeFi Market Intelligence Engine, built by its creator for educational purposes. It is meant to be a real time analytics engine that watches onchain events on EVM based blockchains and also pulls in market data from Hyperliquid, a trading platform. The stated goals are to ingest EVM blockchain logs using JSON-RPC calls and WebSocket subscriptions, then decode the raw smart contract events into structured trade data that is easier to work with. Alongside this, the project aims to ingest real time market data streams directly from Hyperliquid. For storage, the plan is to use ClickHouse for high volume time series data, meaning the large stream of trade and market events, while Postgres would hold metadata and alert configuration, such as rules for what should trigger a notification. Redis is intended to serve as a hot cache and to power live whale alerts, which would flag unusually large trades as they happen. The project also plans to expose the resulting data through Grafana dashboards and through its own APIs, so the information could be viewed visually or pulled into other tools. The README is organized as a Rust workspace with several separate pieces, including an EVM indexer, a Hyperliquid ingestor, an analytics worker, and an API server, each runnable with its own cargo command. Standard Rust tooling commands are listed for checking, building, running each part, testing, formatting, and linting the code. Beyond this list of goals and commands, the README does not describe how complete the project currently is, what has actually been built so far, or how to configure it. It reads as an early stage, in progress project outlining its intended architecture rather than a finished, ready to use tool.

Copy-paste prompts

Prompt 1
Explain what each cargo workspace member in pulsefi is meant to do, like evm-indexer and analytics-worker.
Prompt 2
Help me set up ClickHouse and Postgres so I can run pulsefi's storage layer locally.
Prompt 3
Show me how JSON-RPC and WebSocket subscriptions would be used to ingest EVM logs in a Rust project like pulsefi.
Prompt 4
Walk me through the cargo commands in pulsefi's README and what each one does.

Frequently asked questions

What is pulsefi?

An educational Rust project aiming to track live crypto market and onchain trade data and store it for dashboards and alerts.

What language is pulsefi written in?

Mainly Rust. The stack also includes Rust, ClickHouse, Postgres.

What license does pulsefi use?

No license information is stated in the README.

How hard is pulsefi to set up?

Setup difficulty is rated hard, with roughly 1day+ to a first successful run.

Who is pulsefi for?

Mainly developer.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.