Zk

Moonchain ZK Lite Paper

Mint of MCH

At Moonchain, once a block is produced, validated, and verified, a certain amount of new MCH tokens will be minted. These newly minted MCH tokens are then added to the staking pool, where participants in the mining process can earn them as rewards.

Participating

There are two types of participants: miner owners and those without miners who wish to join the process. Miner owners act as group leaders, forming mining groups and allowing others to participate. Group leaders must keep their miners in good condition to receive rewards. Those joining a group should choose one with a strong track record of miner performance, as any penalties imposed on a disqualified mining group will affect all associated participants.

PS: The reward distribution shown above is subject to change over time.

System Block diagram

APP

A mobile application for participants (end users).

Proxy Service

A back-end service responsible for miner registration. It also analyses miner status and forwards the results to the staking contract.

MCH-prover-service

A back-end service includes the prover manager and the Taiko-client-prover. It is responsible for SGX proof generation for miners, miner registration, and miner data analysis for penalty issuance.

sgx-prover

A service running on the miner that retrieves jobs from the back end, generates SGX proofs, and submits them back.

Contracts

The staking-related contracts have been deployed on the Arbitrum chain.

When an SGX miner is produced, the manufacturer mints an NFT for it. When a user purchases the miner, they can claim the corresponding NFT to their own wallet.

The miner owner, who also serves as the mining group leader, must first create a MiningGroupToken to establish a mining group. This allows other users to join and participate in the mining process. Once the group is formed, the miner owner can stake a designated amount of MCH into the pool and claim rewards after a set period.

Users without a miner can stake by referencing an existing group. When rewards are claimed, a portion of the earnings is allocated to the group leader as a commission.

Staking Period (a Epoch)

A staking period, known as an epoch, lasts for seven days and aligns with every Thursday at 00:00 UTC. Rewards are calculated based on the number of epochs the amount has been staked.

Penalty

Reward Reduction

If a miner’s performance falls short of expectations, a penalty will be imposed on the associated participants—namely, the owner and those who have staked on the owner. As a result, the reward for one epoch will be reduced.

Penalty Condition (at the time of checking):

• The online time has not reached 85% in the past seven days.

Slash of staked amount

When a miner performing actions that harm the network, the staked amount linked to the miner will be slash.

List of harmful actions:

• Submission of an Invalid Proof. A miner submitting an invalid proof, which will be rejected by the block proving process.
• Failure of Three Consecutive SGX Generation Jobs. [To be apply later]

Interact with Contracts

The staking process interacts with the following contracts on the Arbitrum chain:

• MCHL1 (TaikoL1.sol)

  Testnet: 0x6a5c9E342d5FB5f5EF8a799f0cAAB2678C939b0B

  Mainnet: 0x54D8864e8855A7B66eE42B8F2Eaa0F2E06bd641a

• MCHToken (MCHToken.sol)

• L1Staking (L1Staking.sol)

• ZkCenter (ZkCenter.sol)

The contract source code can be found in the MCH-mono repository and MCH-zkcenter repository.

Below are the example flows for basic staking actions.

Get contract addresses from MCHL1.

sequenceDiagram
  APP->>+MCHL1: resolve(encodeBytes32String('taiko_token'))
  MCHL1-->>-APP: Address of MCHToken Contract
  APP->>+MCHL1: resolve(encodeBytes32String('staking'))
  MCHL1-->>-APP: Address of L1Staking Contract
  APP->>+MCHL1: resolve(encodeBytes32String('zkcenter'))
  MCHL1-->>-APP: Address of ZkCenter Contract

Create a group and stake (for miner owner)

sequenceDiagram
  Note right of APP: Registered 1 or more miner(s)
  APP->>+ZkCenter: miningGroupCreate
  ZkCenter-->>-APP: success
  APP->>+MCHToken: approve(addressL1Staking, amount)
  MCHToken-->>-APP: Success
  APP->>+ZkCenter: stakeDeposit(amount)
  ZkCenter-->>-APP: Success

Stake (non miner owner)

sequenceDiagram
  Note right of APP: Select a group
  APP->>+MCHToken: approve(addressL1Staking, amount)
  MCHToken-->>-APP: Success
  APP->>+ZkCenter: stakeToGroup(groupId, amount)
  ZkCenter-->>-APP: Success

Claim Reward

sequenceDiagram
  APP->>+ZkCenter: stakeGetGrossReward()
  ZkCenter-->>-APP: Gross amount
  Note over APP,ZkCenter: Proceed if amount > 0
  APP->>+ZkCenter: stakeClaimReward()
  ZkCenter-->>-APP: Success

Withdraw

sequenceDiagram
  Note over APP,ZkCenter: Perform the request first.
  APP->>+ZkCenter: stakeRequestWithdraw(false)
  ZkCenter-->>-APP: Success
  Note over APP,ZkCenter: Wait for lock period.
  APP->>+ZkCenter: stakeClaimReward()
  ZkCenter-->>-APP: Success
  APP->>+ZkCenter: stakeWithdraw()
  ZkCenter-->>-APP: Success

Claim Commission (Group Leader)

sequenceDiagram
  APP->>+ZkCenter: stakeGetCommission()
  ZkCenter-->>-APP: Amount of commission
  Note over APP,ZkCenter: Proceed if amount > 0
  APP->>+ZkCenter: stakeClaimCommission()
  ZkCenter-->>-APP: Success

Prover Service (back-end server) APIs for APP

Mainnet base URL: https://prover-manager.moonchain.com/

Testnet base URL: https://Hudson-prover-manager.moonchain.com/

POST /app/registerMiner1

This is the first step of the miner registration. Call this with the created wallet address to start the process. A agentToken will return. The APP must send the wallet address and agentToken to the miner, then the miner will use this information to verify itself with the Prover Service.

Example POST data:

{
  "instanceId": 0,
  "walletAddress": "0x0123456789ABCDEF0123456789ABCDEF01234567"
}

Example response:

{
  "ret": 0,
  "message": "",
  "result": {
    "agentToken": "VZ/NkCa4I0WCzO9SW9HCx6fzgOYLpyXMC/uTqxG+qFA="
  }
}

POST /app/registerMiner2

This is the second step of the registration. After the miner verify itself with the agentToken got from step 1, this step will be success and returned a appToken. The appToken will be used to query the miner status later on.

Example POST data:

{
  "instanceId": 0
}

Example response (miner not verify yet):

{
  "ret": 0,
  "message": "Wait for miner.",
  "result": {
    "appToken": "",
  "waitForMiner": true
  }
}

Example response (miner verified):

{
  "ret": 0,
  "message": "",
  "result": {
    "appToken": "K6P1QE7Az6Qh8JmPFjgR1XhG9bbzWviO1zKMhWN2FyU",
  "waitForMiner": false
  }
}

GET /app/minerList/<WALLET_ADDRESS>

Get the list of miners.

Auth header:

"Authorization" : "Bearer <APP_TOKEN>"

Example response:

{
  "ret": 0,
  "message": "",
  "result": {
    "count": 4
    "minerList": [
      {"instanceId": 1, "lastPing": "2025-02-10T15:01:34.000Z", "online": 1},
      {"instanceId": 3, "lastPing": "2025-02-10T15:03:14.000Z", "online": 1},
      {"instanceId": 5, "lastPing": "2025-02-10T15:05:24.000Z", "online": 1},
      {"instanceId": 7, "lastPing": "2025-02-10T15:07:44.000Z", "online": 1}
    ]
  }
}

GET /app/minerStatus/<INSTANCE_ID>

Get the status of a miner.

Auth header:

"Authorization" : "Bearer <APP_TOKEN>"

Example response:

{
  "ret": 0,
  "message": "",
  "result": {
    "lastPing": "2025-02-10T15:01:34.000Z",
    "online": {"value": 1, "timestamp": "2025-02-10T15:00:00Z"},
    "proofReceived": {"value": 22, "timestamp": "2025-02-10T15:00:00Z"},
    "proofRejected": {"value": 15, "timestamp": "2025-02-10T15:00:00Z"}
  }
}

“online”, “proofReceived”, “proofRejected” are statistic result of past 1 hour data.

GET /app/minerStatistic/<INSTANCE_ID>/<ITEM>/[daily]

Retrieve a miner’s statistical data. The ITEM parameter can be one of the following: "online", "proofReceived", or "proofRejected". Additionally, the optional daily parameter returns data aggregated on a daily basis; if omitted, the data will be aggregated on a 7 days (1 epoch) basis.

Auth header:

"Authorization" : "Bearer <APP_TOKEN>"

Example response:

{
  "ret": 0,
  "message": "",
  "result": {
    "item": "proofReceived",
    "data": [
      {"value": 0, "timestamp": "2024-12-05T00:00:00Z"},
      {"value": 0, "timestamp": "2024-12-12T00:00:00Z"},
      {"value": 0, "timestamp": "2024-12-19T00:00:00Z"},
      {"value": 0, "timestamp": "2024-12-26T00:00:00Z"},
      {"value": 0, "timestamp": "2025-01-02T00:00:00Z"},
      {"value": 0, "timestamp": "2025-01-09T00:00:00Z"},
      {"value": 0, "timestamp": "2025-01-16T00:00:00Z"},
      {"value": 0, "timestamp": "2025-01-23T00:00:00Z"},
      {"value": 0, "timestamp": "2025-01-30T00:00:00Z"},
      {"value": 0, "timestamp": "2025-02-06T00:00:00Z"},
      {"value": 114,"timestamp": "2025-02-13T00:00:00Z"}
    ]
  }
}

Miner Registration Flow

Here’s an example flow for registering a miner.

1. Purchase a miner.
2. Use the APP to create a wallet.
3. Connect to the miner via Bluetooth using the app.
4. The APP getting the instance ID via Bluetooth.
5. Perform first registration step with Prover Service with the wallet address and instance ID.
6. Save the wallet address and the received agent token to the miner. Then restart the service at miner.
7. Perform second registration step with Prover Service.
8. Claim the SGX miner NFT.

sequenceDiagram
  loop Not registered
    Miner->>+ProverService: ping
    ProverService-->>-Miner: Auth failed
  end
  Note over ZkCenter,Miner: Start of registration
  APP->>+Miner: Get miner's instance ID
  Miner-->>-APP: Instance ID
  APP->>+ProverService: registerMiner1
  ProverService-->>-APP: agentToken
  APP->>+Miner: Save walletAddress and agentToken
  Miner-->>-APP: success
  Miner->>Miner: Restart agent service
  Miner->>+ProverService: ping with correct agentToken
  ProverService-->>-Miner: success
  APP->>+ProverService: registerMiner2
  ProverService->>+ZkCenter: minerRegister
  ZkCenter-->>-ProverService: success
  ProverService-->>-APP: appToken
  APP->>+ZkCenter: minerClaim
  ZkCenter-->>-APP: success
  Note over APP,Miner: End of registration
  opt APP operations
    APP->>+ProverService: minerStatus
    ProverService-->>-APP: status
  end
  loop Registered
    Miner->>+ProverService: fetch/submit proof jobs
    ProverService-->>-Miner: success
  end