Parex Network
Block ExplorerCommunityParex NetworkDAO
  • 🦝Parex Network Docs
  • Welcome
    • 🚩Quick Start
      • Parex Network in a nutshell
      • Connect to Mainnet and Testnet
      • Deploy and verify a contract
        • Deploy with Remix IDE
          • ERC-20 smart contract
        • Deploy with thirdweb
        • Verify with Parex Block Explorer
      • Run a Parex Chain Node
      • Become a Validator
        • Run a Validator node
        • Authorization of Other Validators
        • nametag for Validator
        • Validator slashing
        • Validator Locked
      • Parex Halving
  • How we Work
    • 📖Learn
      • About Parex Network
        • Tokenomics
        • Parex Networks Labs
      • Parex Bridge
        • How to bridge PRX PEP20 to BEP20
        • How to bridge PRX BEP20 to PEP20
      • Staking on Parex Chain
        • Locked Stake your PRX on dAPP
        • Unlocked Stake your PRX on dAPP
        • Staking Rewards
        • Staking PRX from your Ledger
      • Become a Validator
        • Run a Validator node
        • Authorization of Other Validators
        • nametag for Validator
        • Validator slashing
        • Validator Locked
      • Glossary
        • Blockchain
        • Consensus mechanisms
        • Governance
        • Validator
        • Staking
        • Wallet
        • PEP-20
        • Wrapped PRX (wPRX)
        • Dead Contract Wallet
      • Parex Halving
  • For Developers
    • 💻Develop
      • Basics
        • Use MetaMask
          • Install MetaMask
          • Link Parex Testnet to MetaMask
          • Link Parex Chain to MetaMask
        • Connect to Parex Chain
          • Connect using RPC
          • Run a Parex Chain Node
          • Use a hardware wallet
        • Block Explorer
        • Parex Testnet Faucets
          • Obtain testnet tokens
          • Obtain TPRX with Parex Testnet Faucet
        • Obtain wPRX or PRX
          • PRX to wPRX
          • wPRX to PRX
        • Deploy and verify a contract
          • Deploy with Remix IDE
            • ERC-20 smart contract
          • Deploy with thirdweb
          • Verify with Parex Block Explorer
        • Tips & Tricks
  • For Community
    • 🫂Community
  • information
    • 🗺️Roadmap
    • ♻️Doc updates
Powered by GitBook
On this page
  • Becoming a Validator on Parex Network: Earning Community Trust
  • Code Directory

Was this helpful?

  1. How we Work
  2. Learn
  3. Become a Validator

Authorization of Other Validators

Recommendation for Validators: Check the validators waiting for authorization on the node.

Becoming a Validator on Parex Network: Earning Community Trust

Becoming a validator on the Parex Network requires more than just technical proficiency—it's about earning the approval of other validators. This process serves as a testament to one's credibility and respect within the community. Once selected, validators carry the responsibility of ensuring network security and contributing to its governance. It's an opportunity for individuals to demonstrate their dedication to blockchain technology and their commitment to the long-term success of the network.


The protocol defines a voting mechanism to dynamically add new signers and remove existing ones. In Geth this can be controlled via the clique.propose(address, authorized) method (clique_propose for remote RPC calls).

To authorize a new signer, existing ones can propose it via clique.propose("0x...", true). When more than half the signers proposed it, the authorization comes into effect immediately and the new account can start signing blocks.

Similarly, existing signers can propose deauthorizing existing ones via clique.propose("0x...", false). Again if half + 1 signers deauthorize a signer, it is immediately removed from the list and blocks minted by it are rejected from that point onward.

Code Directory

With this code you can see who is waiting for approval to become a validator on the node.You can see validator wallets waiting in line.

./geth --exec 'clique.proposals' attach geth_data/geth.ipc

With this code you can authorize the validator wallet waiting in the queue.

./geth --exec 'clique.propose("wallet address", true)' attach geth_data/geth.ipc

With this code you can reject the validator wallet waiting in the queue.

./geth --exec 'clique.propose("wallet address", false)' attach geth_data/geth.ipc

With this code you can see all authorized validators.

./geth --exec 'clique.getSigners()' attach geth_data/geth.ipc
PreviousRun a Validator nodeNextnametag for Validator

Last updated 1 year ago

Was this helpful?

📖