πŸ—„οΈAggregator Guide

This guide explains how node operators can become aggregators and allow multiple types of liquidity to be staked on their nodes in Proof-of-Liquidity.

Before starting, make sure to learn about being a collator by following Collator Guide and check out the Proof-of-Liquidity FAQ. To learn more about being a Delegator, visit the Delegator Guide.

Getting Started

In Proof-of-Liquidity v1, the node operators had to make a decision about which liquidity token to collate under. With the Proof-of-Liquidity v2 upgrade, an aggregator now has the ability to join multiple candidates, amplifying their position by utilizing multiple liquidity tokens.

If selected, the aggregator assumes the role of an author/collator, representing the collator candidates who have aggregated under them. It's still possible to be selected on the active set as a collator if a candidate chooses not to aggregate.

How to Aggregate

1. Set up an account for aggregation purposes

The aggregator account can not be a collator or delegator. Top up the account with some MGX to cover the transaction fees.

2. Select the candidates you aim to aggregate

  • go to Developer β†’ Extrinsics

  • the selected account will be the aggregator account

  • parachainStaking β†’ aggregatorUpdateMetadata

  • select the candidates (you can add more by clicking β€˜add item’ on the right)

  • submit the tx. this will set the relationship between the aggregator and the candidates.

In this example, Eve is the aggregator and proposes Alice and Charlie as candidates.

3. Confirm the aggregator from candidate accounts

  • go to Developer β†’ Extrinsics

  • the selected account will be the collator account

  • parachainStaking β†’ updateCandidateAggregator

  • turn on β€˜include option’

  • select the aggregator account

  • submit the tx. this will confirm the relationship between the candidate and the aggregator.

  • repeat the same with other candidates to aggregate under the same account.

  • from now on, the aggregator account will produce blocks instead of candidates.

In this example, Alice confirms its candidate status to be aggregated under Eve. The same transaction should also be submitted for Charlie.

The aggregator account is responsible for rotating and setting the keys in the node.

β˜‘οΈ You can check the status of your aggregator account by following

  • Developer β†’ Chain state

  • parachainStaking β†’ aggregatorMetadata

  • select the aggregator account and click the plus button on the right

  • you will see the list of candidates that are related to the aggregator account

πŸ’‘ You can check which liquidity tokens are enabled for Proof-of-Liquidity by following

  • Developer β†’ Chain state

  • parachainStaking β†’ stakingLiquidityTokens

  • click the plus button on the right

  • you will see the list of tokens that are allowed for Proof-of-Liquidity

  • to learn about token id's: How to look up Token IDs.

Last updated