mirror of https://github.com/luxfi/oracle.git synced 2026-10-30 15:23:21 +00:00

Files

T

History

zeekayandHanzo Dev e0e7a70130 State a version once

A version written into a manifest is written into every manifest that wants it,
which is how eslint came to exist in a hundred and four forms across this estate
and how a package came to resolve twice at run time. The catalog moves the number
out of the manifest: a manifest names the package, the workspace names the
version.

Four are held below their latest because the newer release cannot be used, and
the reason is recorded rather than the version alone: @noble/hashes 2 renamed
every subpath the web3 stack imports, @splinetool/runtime 2 depends on a package
that was never published, @dynamic-labs 5.4.1 the same, and react-resizable-panels
3 points its types condition at the bundle.

Co-authored-by: Hanzo Dev <[email protected]>

2026-09-08 02:45:57 -07:00

src

feat: change logging levels (#4514 )

2023-04-04 11:37:48 +02:00

test

feat: change logging levels (#4514 )

2023-04-04 11:37:48 +02:00

.mocharc.js

feat(monitors): remove all truffle dependencies (#3361 )

2021-09-13 14:06:24 -07:00

CHANGELOG.md

improve(common): Add test network configs (#4529 )

2023-04-18 12:50:38 -04:00

hardhat.config.js

fix: clean up a few missing and lingering dependencies in the common package (#3841 )

2022-03-18 14:25:23 -04:00

index.js

feat: rename new OO contracts (#3959 )

2022-06-10 10:55:05 +02:00

package.json

State a version once

2026-09-08 02:45:57 -07:00

README.md

feat(scripts): improve scripts for running Kovan EMP war games (#2605 )

2021-03-16 09:53:38 -07:00

README.md

@uma/monitors

This package contains four UMA monitor bot implementations: BalanceMonitor, ContractMonitor, CRMonitor, and SyntheticPegMonitor. The monitor bots are used to monitor the UMA ecosystem for key events. They have a number of monitor modules built into them that enable real time reporting on key events for a given Financial Contract.

For more information about running a monitor bot, see the docs.

Installing the package

yarn add @uma/monitors

Running the monitors

The simplest way to run the monitors is:

EMP_ADDRESS=0x1234 CUSTOM_NODE_URL=https://your.node.url.io MNEMONIC="your mnemonic (12-word seed phrase) here" MONITOR_CONFIG="{optional monitor config object}" monitors --network mainnet_mnemonic

Monitors

The four monitors available are:

The BalanceMonitor takes a specified list of addresses to monitor and sends alerts if their collateral, synthetic or Ether balance drops below defined thresholds.
The ContractMonitor sends alerts when financial contract events occur, such as liquidations and disputes.
The CRMonitor, or collateralization ratio monitor, monitors a given position's CR and sends alerts if it drops below a given threshold.
The SyntheticPegMonitor monitors a Financial Contract's synthetic and reports when the synthetic is trading off peg and there is high volatility in the synthetic price or there is high volatility in the reference price.