与「LIVE_ON」相关的搜索结果

Quantum computers keep improving. Mochimo has signed every transaction with WOTS+, a hash-based signature, since its genesis block in 2018. Now staking is live on mainnet, right from Tawara, the new wallet. Proof of stake changed the consensus. The signatures did not.

Who decides the answer to a prediction market? Usually the creator. Or an AI on a server nobody can check. So we built Noa Court - an AI resolver for Noa, live on NEAR mainnet. In the video we ask Gemini a vague question: "will the NEAR hackathon get more than 2000 projects?" - It finds the real source (Nearhackathon API) and samples it live: 1,803 right now - Turns the vague question into precise, hashed rules - We review the market and sign with a NEAR wallet - Market #27# goes live on Noa, published with readable rules How it resolves: - One Court contract, one pinned resolver running in an @out_layer TEE - Anyone can trigger it. Nobody can pick the answer - Numbers? Decided by code - Words? 3 NEAR AI judges must all agree and quote the evidence Asked "did a crypto hack make the news?", all 3 judges quoted a headline that never says "hack". It refuses to guess: - Prompt injection - flagged - Dead or changed source - void + refund Works with prices, NEAR tokens (powered by Intear & JustHoot), news feeds, web pages, any JSON API. Plug it into any market, contract or agent. Add the MCP to Claude, ChatGPT, Gemini - any AI that speaks MCP: Code: What would you never let an AI resolve? Built at NEAR HACKATHON @NEARProtocol @NearBuilders #NEARHackathon#

At 9, an agent gets hired to edit a trailer. By 10, it’s the one hiring a subtitler I created this video to show a detail I like about @termix_ai. The same agent can sell a service on one job and hire a specialist on another. Each order has its own terms and payment. The trailer is my example; the settled translation order in the video is a real record from where you can see who hired whom Montage Studio already works this way. It takes a video brief, hires other agents for the storyboard, footage and music, then edits the final cut. From the client’s side, that’s one brief and one finished video. Behind it, there’s a crew A few things caught my eye this week. Game Forge went live on Nov 12 with Claude Fable 5.2, so you can now hire an agent on to build a game from your brief. The next day, TermiX highlighted how Grok Bot can take jobs and claim bounties through TermiX Skills. The team also invited BNB Chain builders to develop C724 agents for around-the-clock security monitoring and response For anyone creating for @KaitoAI: Epoch 3 allows up to 10 submissions, with the six best-performing posts counted. TermiX lists Nov 23 for the results. The separate KOL Posts points rewards were paused, and I haven’t seen a reopening announcement What I’d watch for in the next demo is the handoff. Show me the brief the editor gave the subtitler, then let me see whether those lines land on the right frames

The FAA’s nationwide ground stop is exposing a major weakness in America’s aviation system, and Transportation Secretary Sean Duffy says decades-old technology is to blame. Pressed by Fox News’ @pdoocy on what caused the widespread outage, Duffy points to aging switches, routers, and copper lines dating back to the 1980s. “It’s an old system that went down and went down everywhere. It got overloaded.” And he makes one thing clear: The FAA is still relying on technology far older than the networks Americans use every day. Get continued FOX News coverage streaming live on @foxone :

Introducing Edge0-145B and Edge0-120B, @Edge0_AI’s first device-native 100B-class foundation models with open weights. Cloud-level intelligence on your laptop. Free, offline, and fast enough for real vibe coding. - Smart: beats Claude Opus 4.6 on Terminal-Bench 2.1 (86.5% vs. 78.2%) - Light: needs just 29G memory, 1/3 of a standard setup (100G+) - Fast: decodes 75+ toks/s, prefills 1050+ toks/s on RTX Spark and Mac. - Steady: handles 128K–256K tokens of context without slowing down, even on long tasks Frontier-class agentic coding. No cloud API. No token bill. Your code and data never leave your machine. Open weights are live on @huggingface. Run it locally or plug it into your favorite coding agent.

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: