Skip to content
snjroPublic

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

Digu

If you want to use Digu right away, open this site:

https://snjro.github.io/Digu/

Digu is a user interface to view smart contracts for Augur. You can browse contract data such as ABI, creation info, functions, events in detail. Digu can import the event logs emitted by the contracts from a snapshot published with this site (warp sync, for Ethereum now; it can be turned off for each chain in the sync panel, which opens from the sync progress in the header). If you have a RPC endpoint URL, Digu retrieves the event logs after the snapshot, or all of them. To get a URL, see RPC endpoint URL.

  • Semi-Serverless:
    Digu is a standalone application, basically it runs without a server. It connects to a remote environment only to get event logs: the snapshot of the warp sync, which it reads from this same site (GitHub Pages), and the RPC endpoint you set. These event logs are all stored on your local database.
  • Zero personal data collection:
    Digu does NOT collect any personal information. All data that requires preservation such as preference, settings, RPC endpoint URL you set are stored locally.

without a connection to the RPC endpoint, Digu has fundamental data about blockchains and contracts. So even if you don't have an RPC endpoint, you can still browse those information. When you open a chain that has a snapshot, Digu imports the event logs of the snapshot (warp sync). The owner of Digu makes the snapshot with scripts/warp-sync/build-snapshot.mjs and publishes it with this site. The logs come from an RPC endpoint with a key; the first logs of Ethereum were fetched without the script (see its README). The snapshot has the logs decoded with the ABIs of the contracts, in the same way as Digu decodes the logs it retrieves itself, so Digu saves them in your browser without decoding them again. If you provide Digu with an RPC endpoint, Digu will use it to retrieve and list event logs emitted by the contracts, after the end of the snapshot. These logs are stored in your local browser database called IndexedDB.

The main libraries that are used to achieve this are:

how it works

For example, the contracts of a version look like this:

Getting started

About

No description, website, or topics provided.

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages