About StarkNet Airdrop
StarkNet Airdrop is a permissionless decentralized Validity-Rollup (also known as a “ZK-Rollup”). It operates as an L2 network over Ethereum, enabling any dApp to achieve unlimited scale for its computation – without compromising Ethereum’s composability and security, thanks to The reliance on the safest and most scalable cryptographic proof system – STARK.
StarkNet has confirmed to launch an own token and 9% of the total supply has been allocated to end users and developers who’ve built dApps using StarkNet. They end users are those who used dApps built on StarkNet. dApps include dydx, Immutable, Celer, DeversiFi, Argent and many more. So early users who’ve Dapps by the snapshot date are likely to be eligible for the airdrop.
|Token Name||StarkNet Airdrop|
|Total Value||9% of the total supply|
|KYC||KYC Is Not Requirement|
|Whitepaper||Click Here To View|
|Collect Airdrop||Click Here To Collect Free Airdrop|
- StarkNet has confirmed to do an airdrop to early end users and developers.
- A total of 9% of the total supply has been allocated to the airdrop.
- The snapshot would be based on the verifiable usage of StarkEx’s technology that took place prior to June 1st, 2022. This date was given as an example, so the date could be tentative.
- They end users are those who used dApps built on StarkNet. StarkNet dApps include dydx, Immutable, Celer, DeversiFi, Argent and many more. So early users who’ve They Dapps by the snapshot date are likely to be eligible for the airdrop. For a complete list of dApps, see their website.
- Developers who’ve built dApps using are also eligible for the airdrop.
- Follow their social channels to stay updated regarding more details.
- For more information regarding the airdrop, see this Medium article.
- StarkNet Users: The users that interact with They sequencer nodes and, if necessary, with L1 contracts. These users, whether human or automated, are the agents that submit transactions to the network.
- Application Developers: The users of StarkNet that develop applications. They write and deploy and Ethereum contracts.
- StarkNet Application: A collection of contracts (L1 and L2) that, collectively, implement complete business flows.
StarkNet Contract: The program that encodes the implemented application business logic. This includes the application data structures and handling of specific transactions sent by users. Specifically, the contract encodes valid state transitions for the application.
StarkNet Account Contracts: Given account abstraction, user accounts are not implemented at the protocol level. Some contracts will, therefore, need to implement the concept of user accounts; these are called Account Contracts. The exact implementation depends on the contract; but, technically, these are StarkNet contracts that are implemented in Cairo.
StarkNet Transaction: An invocation of a specific state-transition logic that’s defined by a contract. Syntactically, a transaction has a well-defined structure that includes all the necessary metadata and an arbitrary data payload. The semantics of the transaction is defined by the invoked contract.
Blocks (previously known as batches): ordered sets of StarkNet Airdrop transactions that are run using the OS, resulting in one aggregated state change that is then committed to the L1 core contract. A block has:
… a block hash – a unique stable identifier that can be used to query and refer to the block.
… a block number – an ordinal number representing the location of the block in the sequence of accepted blocks in StarkNet. Note, a block’s number may change over time. Also, a given number may refer to different blocks at different points in time, e.g., in the event of L1 chain re-orders.