PancakeSwap关于为Cake代币提供带有VIP池的额外功能提案已获投票通过
5月25日消息,Snapshot投票页面显示,去中心化交易平台PancakeSwap关于“为Cake代币提供带有VIP池的额外功能”提案以99.6%的支持率获得通过。该提案旨在为Cake代币提供另一种用途,通过创建独家产品使其更具吸引力。
提案提议创建用于赋予用户特殊质押权力的sCake代币,功能类似于IF0,用户为了参与IF0,需要在池中质押Cake,并以此数量和质押时间确定可提交给VIP池的sCake数量。该功能将提升Cake需求、推动Cake有更多的质押,并对项目有更多的排他性。
Suiswap's Journey to Mainnet Join our Discord & connect your wallet for the testnet airdrop test & mainnet airdrop. Get: 1. Testnet & mainnet airdrops 2. 100 Suiswap Points 3. Access to on-chain events. Follow image steps to connect wallet.
at the time of writing the notification experiment post ( lenster.xyz/posts/0x0f85-0x155b ) was commented 253 times. THANK YOU SO MUCH 🙏🤍.
The notification "signal filter" sent 34 notifications. (13.44%)
(If I haven't commented your comment with sth like "✅ ..." I didn't get a notification for your comment.)
learnings:
1️⃣ tagging (e.g. @punkess.lens ) "overrules/d" the filter
2️⃣ "following" seems to be the main criteria decisive if a notification was triggered.
a few thoughts:
It's great to see steps taken to hide spam wherever the user wasn't able to act yet (comments, notifications). It's even better that both filters can be (de)activated by the user.
Configuring the filter will be very challenging and rn it's imo too strict -> new people or people with a smaller lens network get even less visibility than they got before.
I would love to see a discussion around
How can we support people starting on lens?
with tools, games, (virtual) meetups, communities, ... pls share your ideas :-). 🙏
cc @cultivatordao.lens
齐休偶然接过掌门之位,带着弱小的门派在无垠的修真世界中挣扎奋斗的故事:从一位练气底层的而立中年,到如神般俯瞰众生的睿智老者;门派在他手中发展、壮大,写下如梦如电,波澜壮阔的一生。本命由天授,同参伴我行逍遥两相对,一道诵黄庭在一个由灵根、本命、同参三者合一修行的无垠世界里,主角齐休偶然得到掌门之位,带领弱小的门派奋斗挣扎。从一位练气底层的而立中年,到如神般俯瞰众生的睿智老者。门派在他手中发展、壮大,写下如梦如电,波澜壮阔的一生
📚 Fun fact about posts on #Lens!
They can be hosted on either centralized or decentralized resources.
Decentralized ones cannot be deleted. A better name for the "Delete" button (@lenster.lens) in this case would be "Hide" because, technically, it is more accurate. Such a post can still be viewed even after deletion.
On the other side, centralized ones can be deleted if you or anyone else can access the centralized host. Or better, if a post owner can delete it, he can also change the content. So, when you see a post, you can only be sure that the content will stay the same once you know whether it is centralized or not (better not to believe in bet predictions on Lens, right?).
And since comments are technically still posts (but with a reference), we can edit them as well and make some dirty game. In general, there will be no edit tracks unless the comment's content has been uploaded to some sort of archive.
That was my first thought, but then I dug a little deeper. The trick won't work with the default Lens indexer that everyone uses nowadays because it indexes posts only once after transaction confirmation on #Polygon. So, basically, it copies your post to the indexer's DB, and later, when you use Lenster or some other client, you don't get the data from the actual post's content URL but from this DB.
I wondered why it works like that because this means the indexer's DB won't represent the actual state of the blockchain in some cases. I've written in the Lens Discord, and the answers were as follows:
discord.com/channels/918178320682733648/1080136391989669989/1080230235854864446
@cesare.lens: "To be clear the blockchain data is not changed, on-chain each post|comment has a content URI that cannot be changed. The contentURI has to point to a public location. From an immutability perspective a "purist" would argue to use an immutable data storage (e.g. IPFS) still the Lens Protocol does not stop you to use a URL you control. The indexer is driven primarily by on-chain events to determine what and when to fetch contentURI. Updating the file won't cause a chain event so simply updating the file won't work."
@wagmi.lens: "We will add a refresh endpoint soon it's on the radar"
Previous posts:
#learning #notes #dev
💰 Mirror, like, and follow to get 0.123 WMATIC; limited to the first 100 users.
Thanks to @wav3s.lens