Announcing Counter Stake Stage 2 ‘The Grand Staking League’ Full Details

Counter Stake is Matic's experimental testing event for everyone wishing to participate in the Matic network, by validating, testing the network's limitations and earning mainnet MATIC tokens by showcasing technical skills. Counter Stake allows one to compete with other validators on our testnet and earn rewards.

Counter Stake is Matic's experimental testing event for everyone wishing to participate in the Matic network, by validating, testing the network's limitations and earning mainnet MATIC tokens by showcasing technical skills. Counter Stake allows one to compete with other validators on our testnet and earn rewards.

Counter Stake comprises of 3 stages:

What Happened in Stage 0?

During this stage validators were able to:

  • Understand the core components
  • Get their hands on setting up the nodes
  • Run their nodes and keeping them synced
  • Get familiar with the setup process and core components

What Happened in Stage 1?

During Stage 1, validators were able to:

  • Set up their node
  • Stake on Matic through CLI or Dashboard
  • Delegate to a validator
  • Claim and re-stake their rewards
  • Replace validators via an on-chain auction process
  • And unstake from the network

For more details on Stage 1, we released a blog post highlighting all the important points and milestones we achieved: https://blog.matic.network/counter-stake-stage-1-is-complete-the-final-stage-begins-matic-network/

During Stage 1 we ran a network which included 100 validators running their individual nodes for Matic. We then tested out all the important functionalities of Matic, such as becoming a validator, delegating to a validator, signing checkpoints, claiming rewards, etc.

And now this brings us to Stage 2!

What Will Stage 2 Involve?

Stage 2 is where we want our network to be "stress-tested" thoroughly. What this basically means is that we will be encouraging validators to:

  • Test the network for resilience against explicit exploits that take down the network
  • Try to successfully execute an economic attack and find bugs in the system/code

Important Links

Getting Started on Stage 2

In order to perform attacks correctly, we encourage validators and community members to gain an understanding of Matic's architecture and code. Without a thorough understanding of core components such as Heimdall and Bor, it would be difficult to perform attacks correctly on the network.

The Matic architecture is comprised of the following 3 layers:

  • Heimdall - Heimdall is the heart of the Matic system. It manages validators, block producer committee selection, span duration, checkpoints, the state-sync mechanism and other essential aspects of the system.
  • Bor - The block producer layer for Matic
  • Smart contracts on Ethereum - Staking, delegation and Plasma contracts

Get started by going through the Matic architecture documentation here: https://docs.matic.network/docs/validate/counter_stake#architecture

Specs can be found here:

Codebase can be found here:

In case you have an doubts or questions regarding anything, you can ask us in the Counter Stake Discord channel or you could post it on our Dev Forum here: https://forum.matic.network

Pre-requisites

You'll need to be running a node, and one that is functioning at an optimum level. This includes uptime above 95%, Heimdall and Bor nodes running correctly, as well as Bridge and Rest-server running too.

We recommend all validators to run their own Sentry Nodes in addition to the regular nodes. Running a sentry node makes you more resilient to certain attacks such as DDoS.

We will be releasing detailed information on Sentry Node setup shortly.

Objectives of Stage 2

There will be several activities to be performed by validators during Stage 2. Validators will be encouraged to conduct attacks against the network - economic attacks or those based on bugs in the code. Reporting attacks without executing them but providing an overview of how to execute them will also be considered.

There are 3 major objectives for Stage 2:

  • Network Attacks - This will include economic attacks and those based on bugs in the code. We have mentioned a list of example attacks that a validator could execute below.
  • Uptime - For running a successful network, running your node and maintaining a high uptime is of the utmost importance. For Stage 2 this will be a major objective and reward criterion.
  • Objective Tasks - There will be multiple minor tasks, not related to attacks. These tasks are optional, but by performing them validators will earn additional rewards.

Total Reward Pool for Stage 2

Network Attacks

Here is a list of example network attacks that validators could execute:

More from the Polygon Blog
Polygon Reaches First Sustainability Milestone by Achieving Network Carbon Neutrality

Polygon has made a major first step toward becoming carbon negative with the retirement of $400,000 in carbon credits representing 104,794 tonnes of greenhouse gasses, or the entirety of the network’s CO2 debt since inception.  The milestone comes after Polygon in mid-April released its Green Manifesto, part of its broader vision for sustainable development. The […]

Read More
State of Governance #2: Identity & Reputation

Clink Clank For a period of time, democracy in ancient Athens was exercised in a peculiar way.* Every eligible voter, when entering the hall, would receive a single pebble to be cast in one of two urns during assembly, signifying approval or disapproval on an issue. Athenians, understanding the significance of votes being cast anonymously, […]

Read More
Why Neobanks Will Lead TradFi’s Shift to Web3

Conventional wisdom has it that traditional finance (TradFi) and decentralized finance (DeFi) go together like vampires and garlic. But there is one area of TradFi where that black-and-white picture shades into gray. This is the case for why neobanks will be key to bridging these two worlds. Neobanks, or digital banks, are basically banks without […]

Read More
Polygon ID x Polygon DAO Integration Launches to Create New ZK-based Governance Frameworks

Today, we’re launching the first iteration of Polygon ID - a private and self-sovereign identity solution powered by zero-knowledge cryptography. To start, Polygon ID enables a whole host of features previously inaccessible to DAOs. It will be integrated with Polygon DAO beginning today, and many more DAOs to come soon.  Too often, we’re forced to […]

Read More
Announcing Polygon Pod, a Podcast From the Epicenter of Web3

What’s the future of DeFi? How can blockchain projects shake the reputation for being bad for the environment? What in the world are zero knowledge proofs? How can Web3 attract and accommodate the next billion users? When Flippening? You want to know the answers and so do we. That’s why Polygon is launching Polygon Pod […]

Read More
crossmenuchevron-down-circle