LogoLogo
HomeAppDiscordX/Twitter
  • Overview
    • Introduction
    • Proof-of-Stake Blockchains
    • Liquid Staking
  • Aleph Zero Network
    • About Aleph Zero
    • Liquid Staking on Aleph Zero
  • The Ike Protocol
    • How It Works
    • Staking and Unstaking with Ike
    • Earning Yield
    • Definitions
    • Architecture
      • Core Smart Contracts
      • Smart Contract Functions
      • Staking and Un-staking Mechanisms
      • Community Actions
    • DAO & Governance
      • Ike DAO
      • Protocol Management Fees
    • Official Contract Addresses
  • Community
    • Community & Social Media
    • Partnerships
      • Aleph Zero Foundation
      • AZERO.ID
    • Contribute to Open Source
    • Hackathons and Meetups
  • Development Team
    • Who We Are
    • Why We Build
  • Resources
    • FAQs
    • Bug Reports
    • Feature Requests
    • Support
Powered by GitBook
LogoLogo

Copyright Water Cooler Studios, Inc. 2024

On this page
  • The Vault Contract
  • Vault Functions
  • Vault Contract Variables
  • The Registry Contract
  • Registry Contract Variables
  • The Share Token Contract
Export as PDF
  1. The Ike Protocol
  2. Architecture

Core Smart Contracts

These are the core contracts that make up the protocol along with their uses and functions.

PreviousArchitectureNextSmart Contract Functions

Last updated 7 months ago

The Vault Contract

The Vault contract sits at the heart of the Kinstu Liquid Staking process. This contract is the user-facing entry point to the Ike Protocol, and serves a number of functions:

  1. User entry point: The Vault is the user-facing interface to the protocol. Users who want to participate in staking yield can deposit AZERO to the Vault contract and receive sA0 tokens in return. Users can also request to redeem their sA0 for staked AZERO along with their pro-rata share of the yield accrued by the protocol.

  2. Orchestrates staking delegation & redemption: The Vault delegates staking tokens to, and interfaces with, , according to the stored in the contract. This is done using Ike's .

  3. Calculates Protocol Fees: The Vault calculates and stores used to facilitate protocol . For more information, see the docs on Governance & .

Vault Functions

The Vault contract contains the and .

Vault Contract Variables

The Vault keeps track of a number of metrics. These include:

  1. Total Pooled: The total of all AZERO staked via the protocol.

  2. Total Shares: Denotes the total outstanding supply of sA0 created by the Vault

  3. Virtual Shares: Denotes the Virtual Shares allocated for .

  4. Fee Percentage: Denotes the protocol's annualized .

Note: the Redemption Ratio is not stored as a variable, however theVault contract contains methods to calculate it in both directions (from sA0 to AZERO, and vice versa).

The Registry Contract

Registry Contract Variables

Target Weights

These weights represent the target percentage of the total amount of staked AZERO allocated to each Validator. These target weights are meant to uphold decentralization of the protocol, and will be set by Governance in a decentralized way.

The Share Token Contract

The share_token contract is the core contract of the sA0 token. It is a PSP22 token contract.

The Registry smart contract maintains a list of that are actively participating in the Ike protocol, along with a set of Target Weights for allocation of staked AZERO to those Validators.

Virtual Shares
Management Fees
Management Fees
Management Fee
Management Fee
Target Weights
Registry
Staking Functions
Unstaking Functions
Validators
Validators
Page cover image
Constant Retargeting Algorithm