About Hop Protocol Airdrop
Hop Protocol Airdrop is a scalable rollup-to-rollup general token bridge. It allows users to send tokens from one rollup or sidechain to another almost immediately without having to wait for the networks challenge period. It currently supports bridging assets across Ethereum, Arbitrum, Optimism, Polygon, and xDai.
Hop is a scalable rollup-to-rollup general token bridge. It allows users to send tokens from one rollup to another almost immediately without having to wait for the rollup’s challenge period.
As already guessed in retroactive airdrop overview, Hop Protocol will be airdropping 8% of the total supply to early users of the platform. Users who’ve used bridge at least two times with at least $1,000 volume, liquidity providers, bonders, top 500 Hop Discord participants and 79 Twitter users who were early evangelists for Hop, external Hop contributors and past Authereum users with deployed accounts by the snapshot date are eligible to claim the airdrop. The snapshot was taken on April 1st at 12:00 am UTC.
| Platform | Total Value | Max. Participants | Website |
|---|---|---|---|
| Polygon | 50,000 SKL | Unlimited | Click Here To Visit |
Getting started
Currently Bonders must be allowed by the Hop Bridge smart contract governed by the Hop team. They are working on decentralizing the Bonder role completely. Reach out to the Hop team on discord if you are interested on becoming a bonder.
The first step is to set up a configuration file to specify which network to use and which tokens to bond.
Create a new directory under your home directory for the Hop Node configuration
The configuration file should be a JSON file under the Hop Node configuration directory
Open up this file now with your favorite editor and add the following example config
Requirements
The recommended requirements for Hop Node are:
- 100GB of storage or greater
- 8GB of memory or greater
- Intel i5 processor or newer
The minimum requirements for Hop Node are:
- 10GB of storage or greater
- 1GB of memory or greater
- Intel i3 processor or newer
Operating system
Hop runs on any operating system as long as Node.js or Docker is supported. Ubuntu is a popular choice. Using Docker is recommended.
Logging
The Hop Node does put out a lot of logs so it’s recommended to use a log managment service like CloudWatch, Loggly, Splunk, or simply rotate the logs so your node doesn’t run out of storage.
RPC Provider
It is not a requirement to run your own RPC server on chain supported chain but you can use an existing RPC provider like Infura when running the Hop node.
Becoming an authorized bonder
Currently Bonders must be allowed by the Hop Bridge smart contract governed by the Hop team. They are working on decentralizing the Bonder role completely and eventually bonders will be admitted by governance. Reach out to the Hop team on discord if you are interested on becoming a Bonder.
What are hTokens (ie hETH, hUSDC, hDAI, etc)?
The “h” tokens are a cross-network bridge token that is transferred from rollup-to-rollup and are claimed on the layer-1 for the underlying asset. It is an intermediary bridge token that allows trustless swaps.The end user doesn’t need to deal with “h” tokens directly, they only deal with the respective rollup’s canonical token.
The canonical token (also called “native token”) is the Layer-1 token that is being bridged on Layer-2. For example, DAI token on Layer-2 is the canonical token of DAI token on Layer-1. Users can send back and forth between Layer-1 token and Layer-2 representation of that token using the Layer-2’s official token bridge.
