MajorTimberWolf (@abhinav_kumar) • Hey
Blockchain | Coding in Solidity.
Publications
- 大奇迹日！
- 互关 有关必回
Follow me and I will follow back 100%
- cyber is awesome...
- another monday.hate work
- gm.Another good day
- Relax guys. Stay patient.
- **Follow me I will follow you back** 100%
- Gm! Nothing is better than the begging of weekend 🍹
- I'm saying my piece in the #futureofsocial by signing the @t2world.lens manifesto. Which values do you support?
https://manifesto-app.t2.world/share/clfybx2xv8940441fmcstqqts8j
- Nexon Finance mainnet is live on #zkSync Era 🔥
Checkout: https://app.nexon.finance
- ARB distribution model was designed by Nansen 🔵 🦅
+2,300,000 addresses bridged to Arbitrum before the snapshot.
Online 625,143 were eligible for ARB. Only around 30%!
What can we learn from their report?
5 key take-aways so you don't get excluded from airdrops ⚡
1/5
Eligibility Criteria:
- Conducted transactions: number, value, and time thresholds
- Arbitrum Nova: bridging & conducted transactions
- Dapps and Governance activity
- Liquidity providing
💡 Take-away: the more different activities, the better. Be active!
2/5
USD Value. I know this is a given, but it's important to stress out.
• The majority of wallets transact on small USD amounts
• The majority of wallets got small airdrops (USD value terms)
💡 Take-away: more volume = bigger airdrop. But you didn't need to be a whale to get it!
3/5
The number of transactions
• The majority of the wallets made 1-2 transactions (1M+ wallets)
• Only 100k wallets made 50-100 transactions
Median = 3
Average = 28
💡 Take-away: more transactions = more valuable airdrop.
Become a recurring user.
4/5
Sybil wallets:
• The Arbitrum Foundation wanted to exclude sybil wallets from getting the $ARB airdrop
• Sybil wallets = wallets with similar/fake activity, with the pure intention of hunting for an airdrop
• 172k wallets excluded
💡 Take-away: be user, not a "hunter"
5/5
Negative criteria ⚠️
This is a new concept: some actions subtracted points, i.e. they hurt the user's individual points to get ARB.
These users got less ARB:
• All transactions in a 48h period
• Interacted with only 1 smart contract
• Low ETH balance in Snapshot day
There's a lot more data in their official report.
Read the full blog post here:
🔗 nansen.ai/research/an-on-chain-distribution-model-for-the-arbitrum-community
Join alpha discord: https://earndrop.io/discord
- ZM ZM!! 💜💜
Polygon zkEVM just launched, went through the documentation and now I am here to tell you more as to how this is EXCITING for the WEB3 Community!#zkEVM #PolygonzkEVM #zkDayWatchParty #PolygonCommunity
1/ What are ZK Proofs
To understand Polygon's aim, we need to first understand ZK Proofs. In simple terms, ZK Proof is a technology which allows you to prove information without providing more details. Polygon's zkEVM does exactly this while maintaining Ethereum Compatibility
2/ What is Polygon's zkEVM trying to achieve
Polygon zkEVM uses the power of ZK Proofs to reduce transactions costs, rapidly increasing the throughput, all while maintaining the security of L1 Ethereum proving to be an attractive option for the NFTs, Gaming and DEFI markets.
3/ Now that we know what Polygon's zkEVM is trying to achieve, let's dive in deeper into it's architecture, HOW Polygon was able to develop a zkEVM. The major components of zkEVM are: Consensus Contract, zkNode, zkProver, zkEVM Bridge and more..
4/ PolygonZkEVM.sol
The consensus contract uses the concept of "Proof of Donation" and "Proof of Efficiency". In a ZK-Rollup, data storage and computation is done off-chain, a major challenge is caused when trying to ensure the correctness of the off-chain computation. Proof of Efficiency solves this challenge like this. A transaction included in the ZK-rollup is accompanied by a proof of its computational efficiency, which can then be checked on-chain. It also adds support for permissionless participation.
5/ zKNode
A ZK node is a key component of the Polygon zkEVM sidechain solution, responsible for verifying transactions using zero-knowledge proofs. It is responsible for governing the roles between Sequencers and Aggregators. A diagram shows how a zKNode works.
6/ A zKNode consists of three sub-components namely; Synchronizer, Sequencers & Aggregators, RPC. Let's try to understand why there are important, thread by thread.
7/ The synchronizer is responsible for syncing the state of the zkEVM with the state of the Ethereum mainnet. It gets all the data from the smart contracts, including the ones from Sequences & Aggregators and stores them in a database which will be fed to 3rd parties using RPC.
8/ Sequencers are responsible for user transactions and parsing them into blocks or batches. Each sequencer must pay a fee (MATIC) when publishing a series of transaction, the protocol ensures that it will be very expensive to break the chain if a sequencer shows malicious intent.
9/ An Aggregator collects the transaction information from the sequencer and forwards it to the zKProver. After receiving the proof, it is sent to the smart contract to verify the proof sent by the zKProof. A diagram below shows the working of an Aggregator.
10/ A RPC or Remote Procedure Call is a JSON-RPC interface which enables integration of zKEVM with existing tools like Metamask, Infura, etc. This means that developers can migrate their pre-existing tools without needing to make signification changes.
11/ Closing Thoughts: It's great to see Polygon build something which was thought out to be an "impractical" solution compared to other ZK L2s, but now we can see how important and beneficial it can be for the whole of web3 community. A hearty congratulations to the whole team of Polygon and @sandeep.lens , who worked endlessly and with copious amounts of energy drinks to bring us such an important scaling solution.
12/ Read more about the Polygon zKEVM Architecture: https://wiki.polygon.technology/docs/zkEVM/architecture/…
Read more about the Consensus Algorithm:
https://ethresear.ch/t/proof-of-efficiency-a-new-consensus-mechanism-for-zk-rollups/11988/12
- Here we go! Attending the @0xPolygon.lens #zkEVM Mainnet Launch with #GuildChennaii members. Let's make some waves🚀🚀🚀 #zkDayWatchParty
@vitalik21inch.lens @sandeep.lens
- Excited to be attending the #PolygonZkEVM event! It's going to be fireee 🔥🔥🚀🚀 @sandeep.lens
#Polygon #ZkEVM
- The wait is finally over! Today's the day we've been waiting for. Tune in for the launch of zkEVM MAINNET BETA with Polygon Labs and @ETHGlobal.lens. #zkEVM #zkDayWatchParty @sandeep.lens #GuildChennai #Polygon
- Excited for @0xpolygon.lens zk launch 🚀
- Everything is a hype
- 👋
- Hello Lensters!!
- Just submitted our project for Scaling Ethereum and jeez it was a hell of a ride.
More details soon.
- The activity on lens rn>>>
- AlicΞ lens wordcloud 🌿
you can create your lens wordcloud thanks to @rickydata.lens (and the awesome public lens BigQuery dataset) -> https://lenster.xyz/posts/0x0102cc-0x0110 👏👏👏
- One of the best things to do in web3 is build and connect, which is well **obvious** but some people still fail to do the obvious things.