Get started here: https://t.co/KXuU32A7VH
查看来源 ↗Twitter · Crypto
报告生成:2026-11-17 06:00 HKT · 覆盖此前 24 小时
@StaniKulechov — StaniKulechov (0 tweets)
@Uniswap — Uniswap (5 tweets)
展开原文 · 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)
@LidoFinance — LidoFinance (0 tweets)
@SkyEcosystem — Sky (1 tweets)
展开原文 · 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)
@CurveFinance — Curve Finance (1 tweets)
摘要未完成,以下为原文节选。
展开原文 · 1 条
Good APR?
查看来源 ↗@CryptoHayes — Arthur Hayes (3 tweets)
展开原文 · 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)
@brian_armstrong — Brian Armstrong (2 tweets)
展开原文 · 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)
展开原文 · 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)
展开原文 · 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)
展开原文 · 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)
展开原文 · 1 条
RT @JupiterExchange: BREAKING: A NYSE-listed company is bringing its own shares directly to Jupiter Lend. Today at Breakpoint, we announc…
查看来源 ↗