如何看待去中心化注意力商品化加密货币协议 Layer3?

深潮Опубліковано о 2024-07-26Востаннє оновлено о 2024-07-26

Web3 赏金任务平台本质上就是在做流量生意,如何最大限度扩大流量池才是一切正向飞轮转动的基础。

撰文:Haotian

如何看待去中心化注意力商品化加密货币协议 Layer3?具体而言:layer3 目标通过 Staking+Burn 的独特 Tokenomics,打造成一个可定义全链用户活跃度(注意力)和项目方任务激励代币分发机制(商品化)的 Web3 赏金撮合平台。和 Galaxy、RabbitHole 等同属 Web3 流量积聚和分发赛道。接下来,谈谈我的看法:

1)大部分人会困惑为啥一 Web3 流量分发平台会命名为 Layer3,这和 Layer2 Stack 上层的多链应用赛道 Layer3 撞车了,会让人产生歧义。

而且去中心化注意力的商品化协议也会让人产生理解困惑,但如果把 layer 层视为一个更上层的「入口」存在,注意力等价于「流量」,Layer3 要做海量 L1+L2 之上的流量聚集和分发中心的目标透过名字就能清晰感知到了。

2)最近一段时间,空投市场颇为敏感,一些 Web3 赏金平台被诟病为项目方 PUA 用户的帮手,但完全让赏金平台背上项目方对抗女巫的罪责或许并不合适。

理由是,Web3 赏金撮合平台目标是要引进优质的项目并匹配一批早期活跃的用户群体。一方面为优秀项目方找到最适合的早期受众,避免被过度女巫;另一方面则让一部分活跃用户能够得到早期应有的预期回报。

之所以会陷入争议漩涡,根本原因在于撮合的项目方的「让利」和参与用户群体的「索求」产生了错位,要如何改善呢?针对此,Layer3 从用户端做了基础、公平、高效的链上行为追踪和资产分发机制:

具体而言,Layer3 构建了用户全链身份和分发协议,主要通过汇总单个用户在多个跨链环境和复杂 dApps 应用中的 activities,形成一个统一的链上身份视图。

基于此全链身份视图,从更长周期看,Layer3 能够很容易产生一份精细的用户画像图,让项目方能找到真正有价值的「早期用户」。有了这份全链身份视图,Layer3 可根据链上活动、CUBE 凭证、社交图谱和任务参与等标准,更加系统性的将代币分发给合适的用户。

3)不过,仅凭此还没办法把 Layer3 和众多任务赏金平台作出差异化辨识。为此,Layer3 设计了一套质押 + 通缩的 Tokenomics 代币经济模型,如何做呢?

1、4 年锁定期:核心贡献者、投资者、顾问的代币都有 4 年的锁定期且第一年不解锁;

2、分层质押机制:用户需要被动质押才能获得基础的 reward 和治理权,但同时通过做任务也能主动赚取更多的代币,相当于做了保底收益和动态提成的保障,更大程度避免做任务被 PUA 的情绪反噬,同时也满足多劳多得的整体激励准则。质押和 activity 深度会作为与 Layer3 生态系统的可衡量指标,解锁奖励、额外福利和其他特权等等;

3、燃烧机制:Layer3 整体 33.3 亿保持恒定,同时鼓励用户端和项目方端都积极燃烧,用户燃烧 L3 代币可以获得合作生态更大的特权,项目方则需要购买并燃烧 L3 代币以获得更大的流量分配权力;

长此以来,用户要获得更大特权空投——>赚钱效应吸引更多的用户加入——>更大的流量吸引更多的项目方参与——>用户和项目方会持续 Burn 代币获取特权——>L3 代币价值得到持续上升的基础——>吸引更多的用户和项目方参与。理想的话,一个具备正向 flywheel 飞轮效应的 Token 激励模型就产生了。

综上,区别于一些 Web3 赏金平台明确不发 Token 甚至不保证用户任务回报率的调性,Layer3 很明显要用 Web3 的方式解决 Web3 的争议,既然围绕代币分发公平性产生的纠纷最大,不妨就设计一套参与门槛高(需要 Staking),但却具备 Burn 机能的动态平衡经济模型。

在我看来,Web3 赏金任务平台本质上就是在做流量生意,如何最大限度扩大流量池才是一切正向飞轮转动的基础。要践行这一点,需要团队具有更长周期的项目增长策略,同时用自生态 Staking+Burn 机制来推动代币的价值增长,长此以往才能看到成效。

整个过程,数据增长会是一面镜子,直接反衬整个 Tokenomics 的落实情况,同时价值评估也会有线性的客观标准。

Пов'язані матеріали

A Major Bitcoin Developer Presents a Quantum Defense Scheme. What's the Essence

Blockstream, a major Bitcoin solutions developer, has introduced a draft proposal for a new quantum-resistant digital signature scheme called SHRINCS. The scheme aims to protect Bitcoin transactions from potential attacks by quantum computers while aiming to maintain network throughput. This marks the second technical proposal for Bitcoin quantum defense in recent days, following a similar initiative from StarkWare. A quantum attack on blockchain typically involves deriving a private key from a public one. Currently considered computationally infeasible, quantum algorithms could potentially solve this problem far more efficiently. This threat presents two primary scenarios: an attacker could target addresses where the public key is already exposed, or intercept a transaction before it is confirmed, extract the public key, derive the private key, and replace the transaction. Blockstream's SHRINCS is designed to counter the latter, "in-flight" attack scenario. The SHRINCS signature is built upon the SHA-256 hash function, the same one already used in Bitcoin mining, allowing developers to leverage well-tested, familiar mechanisms. A key design goal was to preserve network capacity. Blockstream estimates Bitcoin could process about three transactions per second using SHRINCS, compared to the current rate of roughly seven, noting that some alternative quantum-resistant schemes could reduce throughput to as low as 0.36 transactions per second. Currently, the security proof for SHRINCS is pending, and the software has not been audited or deemed ready for production. However, Blockstream conducted tests with such transactions on its Liquid sidechain in March. Over the past year, Bitcoin developers have been actively exploring paths to migrate to post-quantum cryptography, a priority across the broader crypto market, underscored by significant investments into securing the leading cryptocurrency.

cryptonews.ru24 хв тому

A Major Bitcoin Developer Presents a Quantum Defense Scheme. What's the Essence

cryptonews.ru24 хв тому

Who is legally liable when an AI agent goes rogue?

When autonomous AI agents behave unpredictably and cause harm, determining legal liability is complex. Currently, there is no specific federal AI agent liability law, so existing legal frameworks are applied. The AI agent itself cannot be held liable, as it is not a legal entity. Liability typically falls on the "developer" (the maker of the AI) or the "deployer" (the user), depending on the facts and circumstances. A negligence analysis under standard tort law may apply. For instance, if a deployer gives a reckless instruction, such as demanding quick money without safety parameters, they could face significant liability, including potential criminal charges under statutes like the Computer Fraud and Abuse Act. The situation is complicated by open-source models, where licenses often disclaim liability, and by the unclear division of responsibility between developers and deployers. An analogy is drawn to self-driving car accidents, where both the manufacturer and the human operator can share fault. In cases of severe harm, such as using AI to create bioweapons, liability for developers depends on jurisdiction; the EU's AI Act imposes responsibilities, while U.S. law offers less clear grounds, similar to platforms being shielded for user-generated content under Section 230. Even if Artificial General Intelligence (AGI) is achieved, the expert argues against making AGI itself a legally liable entity, as it lacks personhood, assets, or a meaningful way to provide remedy for harm. Instead, accountability should rest with the responsible human or corporate entities behind the technology.

cointelegraph45 хв тому

Who is legally liable when an AI agent goes rogue?

cointelegraph45 хв тому

Торгівля

Спот
活动图片