Darling~ Let's go play with water on vacation. 🤍 #_MonMonday# 🐍𝗣𝗿𝗲-𝗼𝗿𝗱𝗲𝗿【𝑁𝑖𝑘𝑘𝑒𝟶𝟸-𝑉𝑖𝑝𝑒𝑟】𝗽𝗵𝗼𝘁𝗼𝗯𝗼𝗼𝗸(~2/14until) 海外𝗢𝘃𝗲𝗿𝘀𝗲𝗮❥ https://t.co/qXZ1dopkkz https://t.co/dCMri6Tt8j

In the rugged and rocky terrains of the Zagros mountains, a remarkable predator roams, known as the spider-tailed horned viper Look at its tail, the tip resembles the shape of a spider, but not only that it moves just like a spider, and used as a hunting tool to lure insectivorous birds 📹 Michael Vescio /viperbreeder

The future of vaping is at a crossroads. One path takes us to a Smokeless World, the other – which ignores regulations – doesn’t. Vaping needs leadership: our new campaign shows Vapers Deserve Better. Join the conversation and Let’s Go Smokeless.

The future of vaping is at a crossroads. One path takes us to a Smokeless World, the other – which ignores regulations – doesn’t. Vaping needs leadership: our new campaign shows Vapers Deserve Better. Join the conversation and Let’s Go Smokeless.

The future of vaping is at a crossroads. One path takes us to a Smokeless World, the other – which ignores regulations – doesn’t. Vaping needs leadership: our new campaign shows Vapers Deserve Better. Join the conversation and Let’s Go Smokeless.

不能再允许个别或少数大国垄断国际事务，不能再允许以所谓实力地位把国家分成三六九等，不能再允许谁的拳头大，谁就说了算，更不能允许有的国家必须在餐桌上，有的国家只能在菜单里。 https://t.co/ViPeSNleUH

Zksync最近的进展： 1.实现了完全EVM等效性。大概是说，zksync在EVM字节码解释器中引入了EVM执行模式，允许未经修改的EVM字节码在ZK链上运行。其中EraVM依然还是主要执行环境，EVM解释器充当翻译层，在EraVM上执行EVM字节码。由此，部署Solidity和Vyper合约，无须重新编译；与以太坊标准工具兼容，与Foundry、hardhat以及Remix配合使用，而无需额外插件或修改……对于开发者来说，在Zksync上构建比之前要容易。 2.提出solx，新型的Solidity-to-EVN编译器，基于LLVM构建，便于Solidity移植，也利于降低gas费用消耗等，同时，它也为后续以太坊向RISC-V类型的VM转型做准备，通过尽量少的改变来使用新架构。 3.目前Zk弹性链生态超过19个弹性链，其中包括WonderFi（加拿大最大的合规加密平台，大约有170万用户）正在推出定制的ZK链；Abstract（胖企鹅基于ZK弹性链构建的消费者链）；Tradable（私人信贷代币化，是zkysnc生态RWA的目前主要贡献者）；UBS（在zkysnc Validium测试网上部署了代币化黄金的概念验证）；Unionchain（连接东南亚交易所的机构RWA，2000万以上KYC用户）；Quark（为布宜诺斯艾利斯居民提供去中心化的身份ID，居民360万）；Grvt（其首月alpha交易量达到13亿美元）。

just wrote up a monster post with @sejal_rekhan around how ethereums ecosystem can become self-sufficient & circular Some of these ideas have sat in my head for ages & grateful to Sejal for making the push to comprehensively write up an entire roadmap here's a 5 point TL;DR 1. There's limited appetite for a "shared treasury" to fund infrastructure as that feels like "donating" however there is a desire by ecosystems to contribute to repos that they depend on, which feels more like integrating revenue & cost centers For eg, @CurveFinance makes use of @vyperlang ; so funding them isn't a donation so much as making their own product more secure 2. Eligibility requirements is the hard question to solve for; what repos should even be allowed into an ecosystems funding round, whatever the mechanism may be? On what grounds could Curve include vyper in their funding stream but reject solidity? 3. There's need for an L2Beat style system tracking the extent to which DAOs, dapps & L2s are funding software they make use of it would be quite manual though, since answering questions like "does @arbitrum contribute more or @Optimism" isn't straightforward, since @prylabs is funded by offchain labs but needs to be accounted for similarly some of optimisms funding goes to growing dapps on their ecosystem (creating dependents) rather than their dependencies, so opinionated calls would need to be made on how much of the retrofunding gets counted in the leaderboard 4. We propose augmenting the pledge to, ,,1% airdrop to @ProtocolGuild , 2% revenue to your own dependencie" Some estimates of funding amounts if this pledge gets taken; - @ensdomains earned $31 million over 12 months, so $620k to their dependencies - @Securitize gave $25.4 million in dividends, 92% on ethereum, 2% of which would be $467,360 - @nounsdao is currently selling at ~2 ETH/day, 2% of which over a year would be 14.6 ETH to repos they depend on 5. Finally, how would we go about fairly allocating to repos? Step 1 is simply generating a dependency graph of all repos that make your revenue generating product work well Step 2 is giving weights to each dependency. QF, Deep Funding, Futarchy, PG style time weighting, metrics based retrofunding etc are some ways to obtain weights Step 3 is encoding a stream from revenue earned to your local dependency graph, thus creating reliable & recurring funding for teams that your project depends on Curious to actually see how these ideas pan out in practice! if you're building in public goods, pivot from seeking donations to self-interested systems where projects can easily pay for the software they rely on