Kupo is fast, lightweight and configurable chain-index for the Cardano blockchain. It synchronizes data from the blockchain according to patterns matching addresses present in transaction outputs and builds a lookup table from matches to their associated output references, values and datum hashes.
See the user-manual 🕮 .
| Category | Value |
|---|---|
| Operating System | Linux 64-bit |
| RAM | 256MB |
| CPU | 2 cores |
| Disk Storage | 0 GB (in memory) - 4GB (full index) |
Kupo is well-suited for small applications which need either:
- a global chain index for resolving output references;
- a on-the-fly monitoring of an address over a short period of time.
It runs in constant memory and is blazing fast. Yet, its use-cases are limited. Here below we provide some possible alternatives with different trade-offs:
oura
Key difference(s): Oura in itself does not provide any chain-indexing, but it supports pluggable sinks where filtered data from the Cardano blockchain can be dumped into (e.g. Elastic Search or Kafka). It also supports a wider variety of events. All-in-all, a good fit for more elaborate solutions.
cardano-db-sync
Key difference(s): cardano-db-sync synchronizes ALL data from the Cardano blockchain, whereas Kupo focuses only on transaction outputs. This comes with obvious trade-offs in both on-disk storage but also runtime requirements.
plutus-chain-index
Key differences(s): the plutus-chain-index is the native component behind the PAB (Plutus Application Backend). It is however intended to be user-facing and as such, does not provide a friendly user experience for uses outside of the PAB's internals.
🕮 User Manual | 📐 Contributing | 💾 Changelog
