与「locking」相关的搜索结果

Dylan Patel says Nvidia without Jensen Huang becomes a committee that decides slowly, with no clear technical lead and a weaker hand to lock up supply below market rate “I think that’s the biggest worry for Nvidia, is that now it’s like a committee of people doing stuff. And that’s just gonna make decisions slow. Technically, they could fall behind because of this.” “There’s sort of three main things. There’s the technical side. Nvidia is so ingrained in helping make decisions there. There’s no one clear technical lead. I mean, maybe Jonah is, but then there’s a lot of people who are also directly reporting to Jensen doing technical stuff, so it’s hard there to move as fast.” “Supply chain wise, Nvidia wants to do aggressive things, lock up supply, convince the supply chain to do things that they’ve never done before in terms of technology and supply, and locking it up to Nvidia. And that’s probably a lot harder to do given whoever the CEO is is probably not as charismatic as Jensen, and they’re not gonna be like, ‘Yeah, sure, Nvidia. You can have 60% of my capacity or 70% of my capacity at a price that’s below market rate.’ That’s just probably tough.”

Trade your shielded $ZEC for confidential USDC on Ethereum, without ever unshielding it. No bridge. No custodian. No wrapped ZEC. And the amount never shows up on chain. I connected @zama and @Zcash to make it work. Live on testnet 👇 What it is ZEC Desk is a small trading desk on Zama's FHEVM, on Ethereum Sepolia. On one side there's cUSDC, a dollar token whose balances are encrypted. On the other side there's shielded ZEC on Zcash testnet. You can trade either way. Built on Zama's model Zama's Confidential RFQ is already live on Ethereum mainnet, open to everyone: It runs confidential swaps with encrypted quotes, a sealed-bid pick on chain and a hidden floor. ZEC Desk takes that same model and extends it to native shielded ZEC. Zama's swap settles both legs on one chain, inside its own contract, so a Zcash leg can't plug into it directly. Here that leg lives on Zcash and settles minutes later with a proof, so the mechanics run in my own contract. It's a sketch of how native ZEC could sit next to Zama's swaps one day, with no wrapped token. How a trade works (buying ZEC) 👇 1️⃣ You lock cUSDC in the desk. The amount is encrypted. 2️⃣ Makers send encrypted quotes. Nobody sees anyone else's price, or the minimum you'll accept. 3️⃣ The contract picks the best one under FHE. 4️⃣ The winning maker sends shielded ZEC to your Zcash address, with the order's reference in the memo. 5️⃣ A zero-knowledge proof shows that payment happened, and the contract releases your cUSDC to the maker. If no proof arrives in time, your cUSDC comes back to you. Selling is the same in reverse: the maker locks cUSDC, you pay the ZEC, and the proof releases the cUSDC to you. Why these pieces Each piece does one job. Zcash keeps the payment private. Zama keeps the amounts encrypted and can still compute on them. Seam, the Zcash light client I built last month, connects the two: a contract checks every Zcash block header itself, and a RISC Zero proof shows a shielded payment reached the right receiver. The transaction, the note and the address never touch the EVM chain. The masked amount This was the hard part. Seam's proof used to write the paid amount in the clear, and ZEC amount × price gives away the dollar amount. So the amount is masked. The contract adds an encrypted one-time mask to the encrypted amount and reveals only the sum, which looks random to everyone else. The mask comes from a secret that the side receiving the ZEC hands to the payer. The proof checks that the payment was at least the sum minus the mask, and never states the amount. One-time pads are old, and Zama's RFQ uses one too. Using one to hand a value from FHE to a ZK proof is the part I haven't seen before. If you have, please send it my way. No vault, no signers Seam can read Zcash, but it can't take ZEC from anyone. So the design never needs someone to pay ZEC on someone else's behalf. Whoever pays, pays from their own wallet, and the escrow on the EVM side enforces the deal. The side that paid the ZEC can prove it itself, so nobody depends on the other side's goodwill. Seam does more than this Any EVM app that needs to know a shielded payment happened can use Seam: pay-with-ZEC checkouts, escrows, payouts, cross-chain orders. This desk is one example. Where it stands ↓ Testnet only, unaudited. On 12 November 2026 I ran a Buy end to end: ➡️ Settled with a proof: ➡️ One proof: 2 minutes on a rented RTX 4090, about $0.25 for the whole session ➡️ Gas per Buy on Sepolia: about 7.6M, in six transactions ➡️ A Sell also ran on Sepolia, up to the maker locking its cUSDC; it settles through the same proof step ➡️ Seam's light client is now deployed on Ethereum Sepolia too, next to Base Sepolia Where it can go ↓ → The desk only needs Zama's FHEVM and a cUSDC. Both already run on Polygon, where following Zcash costs a fraction of Ethereum mainnet. → Zama keeps adding chains. On any cheap EVM chain it reaches, the same desk can run, and if it comes to Base, Seam's relay already runs on Base Sepolia. → Zama's roadmap also goes beyond the EVM, to chains like Solana. Seam's verifier would need a port there. → On Ethereum mainnet, following Zcash header by header would cost over 2B gas a day, so batched header proofs are next for Seam. What it can't do yet - Settlement takes minutes, not seconds. Zcash confirmations set the pace, not the GPU. - Right now I'm the only maker, and a maker needs ZEC, cUSDC and a GPU. - Amounts are hidden, but EVM addresses are public. Read more ↓ Seam on Seam: ZEC Desk:

Great coverage by @TheDailyHodl on the next chapter of the AVA Smart Program! 170K+ members, enhanced lock levels, and a clear path toward the long-term goal of locking 30% of the total $AVA supply 🔒 Check out the article👇

All right, we’re locking in. Only things being worked on are simplifications, more efficiency for more usage, groundbreaking features or new models. Sometimes you have to invest ahead of the curve, but feedback is clear that you all want things to get simpler. On it.

“The weight of the jersey was extremely light this summer... when I put it on this morning, it was a little heavier.” 😅 After celebrating the @nyknicks’ NBA championship this summer, @joshhart is locking back in as New York begins their title defense this upcoming season!

🚨 On September 6, 2026, @Liquid_BTC was affected by a cache key collision vulnerability in rangeproof verification. An attacker minted ~3,998.5 L-BTC with no corresponding peg-in. Within minutes, the unbacked L-BTC was pegged out into real BTC on the Bitcoin mainnet. About 3,400 BTC was later returned to the federation peg wallet, while ~598.5 BTC remains under the attacker’s control. The SlowMist Security Team traced the fund flows on the #Bitcoin# side using @MistTrack_io and fully analyzed the incident. 🧩 Attack flow: 1️⃣ Two setup transactions first landed valid rangeproofs and commitments, while embedding a crafted payload in the locking script to seed node caches. 2️⃣ A follow-up minting output reused a colliding cache key — the same raw concatenation of proof, commitment, asset commitment, and scriptPubKey, but with different field boundaries. 3️⃣ On a cache hit, nodes skipped secp256k1_rangeproof_verify and min-value checks, accepted an unbacked commitment, and minted ~3,998.5 L-BTC. The fake UTXOs were consolidated and pegged out within minutes. ⚙️ Root Cause: The Elements rangeproof cache key concatenated variable-length fields without length prefixes. Distinct argument tuples could hash to the same key, so a positive cache hit meant skipping cryptographic verification. 🛡️ SlowMist Insight: A positive-result cache in a consensus verification path is itself a cryptographic primitive. Every field the verifier reads — and every field boundary — must be unambiguously bound into the key. Treat cache-key integrity as a mandatory item in consensus-layer audits. Full analysis👇

🎬 WES-SIDE IN THE BUILDING! Wesley Fei @CryptoApprenti1 brings the show to the Triton Invitational, locking in with Thomas Muehloecker @WushuTM, Austria's second all-time earner and one of the most precise players in the game. It's showtime. The Triton Invitational begins September 12.

POV: You almost missed these extra BNB rewards. 👀 Locking your BNB can also make you eligible for HODLer Airdrops and Launchpool rewards, no extra steps. Passive income, but make it passive-er. 💤 Explore →

Funding rate arbitrage used to be a complex and high maintainence strategy. We've turned that into a 2 click affair: > 1 click to open the perp positions on CrossEx > 1 click to open the corresponding Boros positions We set out to make funding rate arbitrage stupidly easy, and Arbitrage with CrossEx is the result of that endeavour. Here's a sneak peek at what some early users are already locking in 👀