dGuardian

(refresh)

Statistics

These statistics are compiled from 16-01-2023, when the Guardian was first deployed.

Overall stats

Total teleports 200
Total d2o teleported 1229750
Number of deployments 4
Number of routes 4

Stats per route

Source Destination Number of Teleports Amount Teleported
evm.ethereum.hyperlane evm.astar.hyperlane 8 8
evm.ethereum.layer-zero evm.moonbeam.layer-zero 120 454966
evm.ethereum.layer-zero evm.moonbeam.layer-zero 2 19992
evm.moonbeam.layer-zero evm.ethereum.layer-zero 21 327709
evm.astar.hyperlane evm.ethereum.hyperlane 5 4
evm.moonbeam.layer-zero evm.ethereum.layer-zero 25 195716
evm.ethereum.layer-zero evm.moonbeam.layer-zero 19 231355

About dGuardian

The guardian runs an event fetching deamon for each combination of platform (e.g. EVM), network (e.g. Ethereum) and protocol (e.g. LayerZero).

The fetching deamons listen for mint and burn events pertaining to teleportation of d2o tokens between networks.

Teleportation works by burning d2o on one network and re-minting it on another network.

If the guardian sees a Mint event without a corresponding Burn event, then its possible the protocol may have been exploited. As such, the guardian will immediately freeze the d2o account in question so the protocol stewards can investigate further.

The guardian is a durable and fault tolerant process so it should never miss any events as long as it has active connections to its RPC providers.

In-process teleports

Tx Hash Protocol Account Amount Source Destination Block Hash Block Height
0x068e6d69 0xff1fc55b3b5d2cc62b82d1f77da88355e8175254 9994 evm.ethereum.layer-zero evm.moonbeam.layer-zero 0x2b094cc904d14e9185ad130019dbe0ba8beae667bd4f40b8f07e8469228e98b3 18527312

Exceptions

If the Guardian encounters an unmatched mint then it will be listed here.

The Guardian can resolve unmatched mints due to timing issues itself.

No unmatched mints.

Config

The following fetchers are live from 16-01-2023:

ethereum

moonbeam