Twitter · Crypto

报告生成:2026-11-17 06:00 HKT · 覆盖此前 24 小时

历史记录:2026-11-17 2026-11-14 2026-11-13 2026-11-12 2026-11-11

@aave — Aave (4 tweets)

- Aave推广其应用提供的收益服务,声称APY高达7.25%,收益按秒计算(需适用条款)。 - Aave与Mantle官方账号进行社交互动。 - Aave转发了Token_Logic的相关内容。
展开原文 · 4 条

Get started here: https://t.co/KXuU32A7VH

查看来源 ↗

Make your dollars work harder. Earn up to 7.25% APY, paid every second, with Aave App. T&Cs apply. https://t.co/63carL1hN0

查看来源 ↗

@Mantle_Official 👻👻👻

查看来源 ↗

RT @Token_Logic: https://t.co/lUoWBhAUpa

查看来源 ↗

@StaniKulechov — StaniKulechov (0 tweets)

过去 24 小时无推文。

@Uniswap — Uniswap (5 tweets)

- Uniswap Labs强调对hooks(钩子)功能的支持与重视 - Arc Studio新增支持在Uniswap Explore上构建链上FX、交易和DeFi相关应用体验 - Uniswap与stoveprotocol合作,实现韩国股票代币化24/7全天候交易 - 代币化话题引发讨论,被认为能让价值更具可编程性
展开原文 · 5 条

we 💚 hooks

查看来源 ↗

@arc It's time to build on Arc 🦄

查看来源 ↗

RT @arc: Arc Studio supports @Uniswap Explore building onchain FX, trading, and DeFi experiences in your next app on Arc. With the new U…

查看来源 ↗

The market never closes on Uniswap Korean equities are now trading 24/7 with @stoveprotocol

查看来源 ↗

RT @saintniko: tokenization makes value more programmable https://t.co/yROeom8Ab7

查看来源 ↗

@haydenzadams — haydenzadams (0 tweets)

过去 24 小时无推文。

@LidoFinance — LidoFinance (0 tweets)

过去 24 小时无推文。

@SkyEcosystem — Sky (1 tweets)

- Sky Agents 将公开报告作为运营模式的一部分 - Grove Finance 允许任何人实时追踪资金分配和风险资本状况 - 用户可将月度财务结果追溯至与 Sky Protocol 的结算记录 - 帖子引导查看 Grove 实现透明报告的具体方式
展开原文 · 1 条

Public reporting is part of how Sky Agents operate. @grovedotfinance lets anyone track allocations and risk capital in real time and trace monthly financial results back to settlements with Sky Protocol. See how Grove does it ↓

查看来源 ↗

@RuneKek — RuneKek (0 tweets)

过去 24 小时无推文。

@CurveFinance — Curve Finance (1 tweets)

摘要未完成,以下为原文节选。

- Good APR?
展开原文 · 1 条

Good APR?

查看来源 ↗

@CryptoHayes — Arthur Hayes (3 tweets)

- 呼吁用户提前在 Devnet 做好准备,以便在 2026 年 11 月 24 日 Testnet 启动时获取收益 - 认为若"有人"打压黄仁勋以削弱开源 AI,这对 $ANT 代币 IPO 是利多,呼吁抄底 - 核心观点:AI 是史上最大信贷泡沫,相关公司普遍零利润
展开原文 · 3 条

Just the beginning, get setup on Devnet to be ready to earn during Testnet starting 24 Nov 2026. https://t.co/oMBY35UinM

查看来源 ↗

If “they” whacked Jensen to cripple open source AI, it’s the most shortsighted bullish thing for the $ANT IPO. BTFD mofos.

查看来源 ↗

RT @anna_tutova: 😱 https://t.co/6nKR8gnHoq - @CryptoHayes says: the biggest credit bubble in history is AI. Companies with ZERO profit com…

查看来源 ↗

@satofishi — satofishi (0 tweets)

过去 24 小时无推文。

@brian_armstrong — Brian Armstrong (2 tweets)

- 过去数十年,资产投资回报率长期高于工资收入,而此前全球约半数人口在就业和财富积累方面受到限制 - 代币化股票有望改变这一局面,让更多人平等参与资产增值 - Coinbase 正与 Broadridge 合作开发链上股东通信的开放标准,以实现代币化股票的代理投票功能 - 该基础设施将以开放标准发布,供全行业免费使用
展开原文 · 2 条

For decades, owning assets has outperformed working for wages. Meanwhile about half the planet was only allowed to work. Tokenized stocks finally fix this.

查看来源 ↗

Tokenized stocks are great, but still developing. We’re working with Broadridge on an open standard for delivering shareholder communications onchain, which will make proxy voting through tokenized stocks possible. This is infrastructure the whole industry should build on, so we're publishing it in the open, for everyone to use.

查看来源 ↗

@VitalikButerin — vitalik.eth (9 tweets)

- EIP-8288 通过在 mempool 聚合 STARKs 来解决量子时代签名和零知识证明体积膨胀问题,链上只需存储声明哈希和单一聚合证明,大幅降低链上数据量。 - Vitalik 认为短期内 gas 会很高,但中期应用会调整策略,从依赖存储转向更多使用计算和 Merkle 树结构,隐私协议也会更激进地增加使用量。 - 推荐 airdrops 采用 Merkle 树方式空投(发行方只发布根,用户自付 gas 提供分支),长期建议用 UTXO 和密钥随机数存储代币余额以降低成本。 - 推文中提及 EIP-8037,观点认为 ETH 作为主权资产在文化上具有重要意义。
展开原文 · 9 条

Over the past few weeks I've gone from thinking leanPCS is total bull to being a total bull. So let me explain some of these buzzwords in more detail. At the core, 8288 is about hyper-scaling data and execution for any computation that needs to get performed on a piece of data once, the chain learns the answer, and then we never need to see that data again. This sounds very specific, but it includes most "heavy" things happening on Ethereum: * Signatures * STARKs * Merkle branches * FHE computation * ... Really the first two are the most important. Once we go quantum-safe, signatures get bigger (65 bytes ECDSA -> 1-6 kB WOTS/SPHINCS depending on params) and ZKPs get much bigger (200-1000 bytes with groth16, PLONK, etc -> 128 kB with STARKs). This is unsustainable to put on chain, and 8288 fixes this. 8288 works by aggregating STARKs in the mempool. First, you as a user generate the STARK or SPHINCS signature or PCS opening (more on that last one later), and publish it. Then, each node listens. Each tick, each node takes all of the new objects that it has seen, and generates a STARK containing a list of "claims": "pubkey P has signed message M" "program X run on data D has output Y" "p(X) = Y for some polynomial P whose hash is H" and a proof that it has seen a signature, STARK or PCS opening verifying those claims. So the only information getting re-broadcasted is: (i) hashes of inputs and outputs (~64-96 bytes per claim) (ii) a single STARK proof per tick These aggregate proofs themselves get re-aggregated, and eventually you get to a single "master proof" in the block, that verifies that all of those statements are true. And so the only other data that has to actually go on chain is the statements (the (P, M), (X, D, Y), (X, Y, H) tuples I described above), not the actual signatures or proofs. This gets put into a specialized frame type. Now, let's get into the leanSPHINCS vs leanSTARK vs leanPCS part. The core distinction is: *what is the underlying object that the user is creating?* In leanSPHINCS, it's a signature, and specifically this particular type of purely-hash-based signature: https://t.co/HOazliHq9N If we add leanSPHINCS, then users will be able to make quantum-safe accounts, and pay only a little bit of gas (4096 for the 64 bytes) for each signature. So we get scalable quantum-safety for regular accounts, multisigs, etc. But it's only one specific signature scheme, you can't do anything else. In leanSTARK, it's a STARK. This means it's fully general: the user runs whatever computation they want, and publish a STARK of it. So you can use it for: * Any signature scheme (including eg. lattice-based ones if you like those) * A multisig that hides its internal logic * Privacy protocols * Private account abstraction: authorization logic that depends on some value hidden elsewhere in the state, so you can have one key that controls all your accounts without publicly linking them to each other Basically, it's a free for all, in the same way the EVM is a free for all. But leanSTARK has a practical downside. The protocol would have to specify the language in which users write their programs (we call this the "ISA"). So we would have to agree on that language. This is a really big deal - it's the first big case of "Ethereum moving beyond the EVM" - and so it's likely to take time to agree on the details of it, especially since the ISA would be hard to upgrade. There are benefits to taking longer on this, figuring out the ideal ISA, and then even giving access to it inside regular contracts. LeanPCS is the third option. PCS stands for "polynomial commitment scheme": a proof that P(x) = y. The most important thing to know about PCSes is that they are by far the most important "hard" component of a STARK (see here: https://t.co/EEQWMU0gAf ). If you have a "magic PCS oracle" (which from the EVM's point of view, 8288 is), you can verify a STARK in ~20-40k gas. The most important gain with PCS is that there is far less that we need to choose. Specifying a PCS only requires specifying a field, and there is a natural option: the 128 bit binary field (technically, we can go more general than that, and say the 2^k-bit binary recursive tower field, going up to 256) LeanPCS is less efficient than leanSTARK onchain, because you would have to put multiple claims to prove one thing. But it's arguably more efficient offchain, because you have much more flexibility to choose proof systems. But most importantly, leanPCS gives you the same generality as leanSTARK, in a way that could potentially be implemented very quickly. And once we figure out the ISA, we can add leanSTARK later. So there is a route to getting "the cryptographic proof singularity" much faster than any of us expected, and that route runs through 8288 with leanPCS. https://t.co/dUHONMh75g

查看来源 ↗

@0xSero @i3uuve1 Then make it your profile picture!

查看来源 ↗

@i3uuve1 It's a moonkin. Moonkin and yeti both often live in caves, but moonkin hang out outside more, and they cast arcane and nature spells whereas yeti stick to melee and a few limited frost actions. Moonkin are generally somewhat smarter than yetis, but both species deserve love.

查看来源 ↗

@kay_myg Very short run, yes. Medium run, apps will retool to use more computation and less state (eg. airdrops switching to being merkle tree based), and apps that are exec heavy (eg. privacy protocols) will be bolder in increasing their usage.

查看来源 ↗

@YuriSez Дякую за підтримку

查看来源 ↗

@samuel_kiri98 It's already been recommended for airdrops to use a merkle tree based approach: the issuer only posts the root, each user provides their branch and pays their own gas to claim. Longer term, use UTXOs and (for privacy) keyed nonces to store token balances instead of storage slots. The expectation is that both will be significantly cheaper than storage slots because the more restricted rules of how that state can be accessed allows most nodes to avoid fully storing it.

查看来源 ↗

Call on this topic happening in 9 hours! https://t.co/VxtFW9LGhr

查看来源 ↗

My views on EIP-8037: https://t.co/WUeR5lxJiC https://t.co/eUnHJiUsgk

查看来源 ↗

RT @casparschwa: This is culturally so important to realize: eth as sov is the ambitious and inspiring path for Ethereum too. Ethereum as…

查看来源 ↗

@newmichwill — Michael Egorov (4 tweets)

- 建议使用 AI agent 追踪 DeFi 头寸的赎回金额变化,以获取更准确的数据,而非仅看图表 - 提醒分析数据时需警惕噪音干扰 - 澄清所讨论的是未质押状态,质押头寸的余额基本保持恒定,主要收益来自激励 - 认为用 AI agent 查询数据比直接查看图表更有意思
展开原文 · 4 条

@archtuxfan @yieldbasis This one yes

查看来源 ↗

@Kelvin_json @0xAero8 @WenLlama @yieldbasis There's a graph of deposit value growth in analytics. But asking an agent is so much cooler!

查看来源 ↗

@0xAero8 @WenLlama @yieldbasis Beware of noise though. To see the balance - ask some AI agent to track someone's position's redemption amount over time to see for real

查看来源 ↗

@0xAero8 @WenLlama @yieldbasis Yes of course (this is unstaked though, staked has ~constant balance and incentives)

查看来源 ↗

@JupiterExchange — Jupiter (6 tweets)

- Jupiter 发布「代币化后」产品栈:Global Passport(准入)、Liquidity Services(流动性服务)和原生解决方案 - 与 Bullish 合作推出 NYSE 上市公司股票代币 $BLSH 市场,Issuer Token 首次可作为 Jupiter Lend 抵押品 - Ledger 硬件钱包集成,用户可在 Jupiter 交易前查看实际交易详情,避免盲签风险 - Humafinance 的 JupUSD 存款规模达 810 万美元
展开原文 · 6 条

@solana @Bullish @kashdhanda 🚢🚢🚢

查看来源 ↗

RT @solana: .@JupiterExchange unveils its post-tokenization stack: Global Passport for access, Liquidity Services for issuers, and a native…

查看来源 ↗

@humafinance @jupiter_earn $8.1M JupUSD 👀

查看来源 ↗

Note: The market will launch with $BLSH, with more Issuer Tokens to follow. Not available in all jurisdictions.

查看来源 ↗

BREAKING: A NYSE-listed company is bringing its own shares directly to Jupiter Lend. Today at Breakpoint, we announced our partnership with @Bullish to launch a dedicated, permissioned $BLSH market. For the first time, Issuer Tokens can be used as collateral inside Solana’s largest money market. Everything that comes onchain, comes together on Jupiter.

查看来源 ↗

No more blind signing. Now you can see the actual transaction details on your Ledger. Know what you’re swapping and how much. First on Jupiter with @Ledger https://t.co/wYARnhb2NM

查看来源 ↗

@weremeow — meow (1 tweets)

- @weremeow 转发了 Jupiter Exchange 的快讯,称一家纽交所上市公司正将其自身股票直接引入 Jupiter Lend - 此消息在 Breakpoint 大会上公布 - 内容不涉及任何投资建议或法律相关信息
展开原文 · 1 条

RT @JupiterExchange: BREAKING: A NYSE-listed company is bringing its own shares directly to Jupiter Lend. Today at Breakpoint, we announc…

查看来源 ↗

@ponsdotfamily — ponsdotfamily (0 tweets)

过去 24 小时无推文。