Skip to content

Applications#

Check out sigmaverse.io - your portal to the Ergo Universe

Core Components#

Autolykos

The underlying Memory-hard ASIC-resistant Proof of Work (PoW) algorithm oriented towards GPUs.

eUTXO

Ergo uses a so-called extended-UTXO model, which implies UTXOs with the ability to contain arbitrary data and sophisticated scripts.

NIPoPoWs

Enable extended support of light nodes which makes Ergo friendly for end-users, allowing them to run contracts on common devices such as mobile phones without centralised intermediaries.

Privacy

Ergo provides superior access to discrete log-based zero-knowledge proofs

Scaling

Explore the various scaling solutions being explored on Ergo.

Storage Rent

Storage Rent is a nominal fee incurred by unmoved boxes after four years.

ErgoScript

A simple high-level language enabling clear descriptions of contractual logic.

Oracles

The messengers in and out of blockchains. Ergo Blockchain’s design allows Oracle Pools, protected by trust heirarchies.

Parachains/Sidechains

Main Use Cases of Ergo#

  • Multi-Sig: Multi-Sig or Multi Provers are helpful for the reliability of smart contracts. This kind of implementation is vital for security. So that smart contracts aren’t in control of one person but rather governed by multiple accounts. Multi-stage contracts can also be designed for punishing malicious actors trying to take control of smart contracts.
  • NIPoPoWs: Non-interactive proofs of proof of works can be used to build an interoperable blockchain ecosystem. With NIPoPoW implementation, Ergo Blockchain can interact with the smart contracts on proof of stake networks. This would open up an integrated use case between different dApps on different blockchains. Cardano is already planning to implement side chains with NIPoPoWs in collaboration with EMURGO.
  • Oracles: Oracles are the messengers in and out of blockchains. They contain valuable data (e.g. price feed) so that applications work seamlessly. Ergo Blockchain’s design allows Oracle Pools, and this would help to create data hierarchies. A system of oracles that can be scored regarding their trust level is a significant phenomenon.
  • Time Epoch: Ergo Blockchain can be designed to have timed operations. For example, during an ICO (or IDO), a code in a smart contract can provide timed-release so that investors have a protective layer if the project owner isn’t delivering his/her promises. In Ethereum, programming such a kind of timed operation isn’t possible.
  • Parachain/Sidechains: This is a yet-to-develop area for Ergo Blockchain. It’s certainly possible, and we know that the implementation of parachains has a significant impact on scalability. Our core developer Alex Chepurnoy is about to release a paper on it, so stay tuned!