You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+14-97Lines changed: 14 additions & 97 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,6 +18,8 @@ Push Engine is a service that bridges off-chain data streams with on-chain smart
18
18
19
19
- Retrieves and verifies price data from Chainlink Data Streams.
20
20
- Writes verified prices to on-chain smart contracts.
21
+
-**Dual monitoring modes**: Price delta or market status monitoring.
22
+
-**V8 report support**: Full support for latest Chainlink Data Streams schema.
21
23
- Supports containerized deployment with Docker.
22
24
- Configurable through environment variables and Redis-based settings.
23
25
@@ -117,7 +119,7 @@ Before setting up the , ensure you have the required dependencies installed.
117
119
3. Update the `.env` file with your credential details (explained below) and optionally provide a `config.yml` file following the examples below.
118
120
119
121
> [!TIP]
120
-
> To ensure you won't miss any of the needed variables to be set - you can copy the provided `.env.example`and `config-example.yml`to `.env` and `config.yml`respectively and only fill in the details.
122
+
> To ensure you won't miss any of the needed variables to be set - you can copy the provided `.env.example` to `.env` and optionally use `config-v8-example.yml`as a reference for your `config.yml`.
121
123
122
124
4. Install dependencies:
123
125
```sh
@@ -153,7 +155,7 @@ To make setting environment variables easier there is a `.env.example` file in t
153
155
> [!NOTE]
154
156
> All other user configurations are stored locally using Redis file eliminating the need for separate configuration files. This ensures fast access and persistence across sessions without manual file handling. Only sensitive configurations, such as API keys and database credentials, are managed separately in the `.env` file. The application automatically loads and updates configurations in Redis as needed. Users do not need to manually edit or maintain configuration files, simplifying setup and deployment.
155
157
>
156
-
> Optional: The initial configurations can also be seeded by providing a `config.yml` file. See the `config-example.yml` and section below for more details.
158
+
> Optional: The initial configurations can also be seeded by providing a `config.yml` file. See the `config-v8-example.yml` and section below for more details.
A comprehensive example configuration file is provided at `config-v8-example.yml` that shows all available options including:
236
+
237
+
- **Price Delta Monitoring**: Traditional mode that triggers on price changes
238
+
- **Market Status Monitoring**: Mode that triggers on market open/close events
239
+
- **V3/V4 Schema**: Individual field extraction for bid/ask spreads
240
+
- **V8 Schema**: Raw report handling for advanced use cases
241
+
- **EVM and SVM**: Support for both Ethereum and Solana chains
242
+
- **Startup Sync**: Immediate data synchronization on bot startup using REST API for any report type
243
+
244
+
The example file demonstrates how to configure different monitoring modes, contract interaction patterns, and startup synchronization. You can use it as a reference when creating your own `config.yml`.
0 commit comments