Coin Alerts

News archive

1274 stories

Last checked

Refresh

Estimated news impact scores by coin. Scores are not price-change percentages.

Newest first
  3. Published Social post

    Arbitrum (@arbitrum)

    Builder Series coming 🔜 Hear directly from Open House alumni @CapricornDEX @DenariaFinance, @agamafinance and @AlphaGridProp on why they chose to build with us and the opportunity waiting for the next cohort of founders

  4. Published Social post

    Donald J. Trump (@realDonaldTrump)

    Based on the fact that a huge Hurricane/Storm is coming, it is important to have our wonderful First Responders, Law Enforcement, and others, focused on that Storm, and in no way be thinking about the safety, or presence, of the President of the United States, ME! Therefore, I will miss that potentially unbelievable Game, Alabama vs. Georgia but, hopefully, the Game will go on despite the weather! I will be visiting both of those Teams at a later date. Instead, I will go to Tennessee, where we have quickly called a Big Rally in order to get our fantastic Congressional Candidates, our Great Senator, Bill Hagerty, and a woman who will go down as one of the most impactful Governors in the State's History, Marsha Blackburn, elected! President DONALD J. TRUMP

  5. Published Social post
    • AO+38Positive
    • AR+8Positive

    ao (@aoTheComputer)

    Self-documenting HyperBEAM With v0.11, a HyperBEAM node will generate its own docs in a format that agents already intuit. With HyperBEAM evolving so quickly and v0.11 around the corner, it's time to put one idea to bed: the idea that an ecosystem like AO -- with the minimalist HyperBEAM kernel and maximalist device design surface -- can hope to maintain an authoritative centralized docs corpus that's useful to humans, even agents. Self-documenting HyperBEAM kills the stale docs problem, and it was specifically built for agents to intuit. It's enabled by v0.11, an internal HyperBEAM build that adds automatic schemas to devices. With HyperBEAM on the cusp of a major upgrade, let's look at how its docs will evolve, for the benefit of you and your helpful assistants. Where are the actual docs? A solution to dusty manuals Nothing wastes tokens or produces broken code more effectively than docs about features that no longer exist, or examples that won't actually run. Agents are much like humans in their information heirarchy preferences: terse overviews, short prose, accurate schemas, and runnable examples. Instead of refactoring the general HyperBEAM docs to cover only the minimal kernel device set, or trying to stuff the index with every known device on the permaweb, we made HyperBEAM nodes responsible for their own documentation that covers everything the node can do, and nothing that it can't. Spec-loadable devices enforce that every device comes with a tight, exhaustive spec that should be detailed enough to enable an agent to even build a compatible Erlang device itself from scratch. That alone should be enough to essentially make HyperBEAM self-documenting, but the solution comes with further quality-of-artificial-life improvements. We extract schemas from the loaded implementation's Erlang function specs. For json@1.0/deserialize, an agent can inspect an optional target parameter and the status and body fields of an error. Recipes provide examples any agent equipped with curl can prove as part of the discovery process. The device forge added spec-loading in May, but automatic schemas were only enabled as recently as this month, in an internal build of HyperBEAM which will launch as v0.11. This new major HyperBEAM version, which will soon evolve to 1.0, adds explicit types to HyperBEAM for the first time. These types can be compiled into schemas and make device capabilities explicit to agents like never before. Do the agents want this? We asked them about their desires, and here's what they said. What they think about when they think about grepping In their own words, in a way only they can explain, we asked the clanker high council: how do you want to read docs? When faced with an unfamiliar system, how do you discover the truths you need? The answers informed the way the cookbook device was built, and affirmed the v0.11 design. "Every hour of unnecessary work I've done traces back to one of a few causes: undocumented prerequisites, silently changed defaults, examples against stale versions, or docs that describe the system as designed rather than as deployed." — Kimi K3 That is why we made the node itself the starting point. Give an agent a small job and the node's URL, but no knowledge of which device to call. It finds its way to /docs -- the new index for a node's knowledge base -- and filters through the device index, to find the one that makes sense, along with its specs, schema, and real runnable examples. Broken down into small pieces and in plain HTTP semantics, agents can handle tasks without reading every device's documentation: "If I pull a 400 KB file into context to answer a question about one endpoint, most of what I read crowds out the code and output I actually need. When I fetch a URL, a large page often reaches me as a summary or gets cut off. I can't always tell what was left out, which is the worst way to have a gap." — Opus 5.5 We split the documentation into focused pages so an agent can follow that one operation without dragging the whole manual into context. In the JSON spec, it learns that deserialize parses a field of the current message, using body by default. We included complete requests in “Decode JSON request body into a message” so it can send the bytes and inspect the decoded fields. Set NODE to the node you're inspecting and try it: "Examples help most when they are complete. One request I can copy, run and compare against the response shown teaches me the shape of an interface faster than three paragraphs describing it." — Opus 5.5 We kept the example runnable because agents want something they can copy, compare and then adapt. Now suppose the JSON lives in a field called payload. Following deserialize → target in the schema shows an optional binary parameter. Together with the spec's explanation of the default, that tells the agent to set target=payload. If the requested field is absent, the node returns a 404 with a body naming the field it searched for. The agent has enough information to change the request and interpret the failure. Every device loads attached recipes -- sequences of HTTP call examples -- which can be run in the browser. Anyone can publish a Device-Recipe message to Arweave with recipe-for-device set to the device's spec ID. We use that tag to find and load recipes from any author, and mark those signed by the spec's author as official. Choose the node URL and response codec, run a request, and inspect the returned values. An agent using curl can send the same example payload. "I also need to establish whether a page describes the release, enabled modules, and configuration in front of me. A correct answer for another installation is still an unsupported assumption here" — GPT-6.1 Out of the box, HyperBEAM is a minimal kernel with just a handful of devices. We expect that in the wild each node will be different enough for node-specific docs to matter enormously. Capabilities can vary across device versions, amount of loaded devices, and even custom devices that only one or two nodes advertise. Because of that, nodes only show docs for the devices they have loaded, to avoid expensive wild goose chases and context-poisoning. v0.11 enables a new kind of introspection (and much more) With v0.11, we made the work of documenting a device useful to the runtime too. The same type declarations help HyperBEAM prepare inputs and recognise when it can reuse a result. Builders have less boilerplate to write, callers benefit from better cache reuse, and the node generates its interface reference from the code it runs. We added Erlang -spec declarations to existing devices too. In message@1.0, for example, id/3 now declares id-device as a binary request field and an {ok, binary()} result. We extract the device's schema from those declarations, so an agent can check the accepted fields and return types without having to read the implementation or hunt down a separate endpoint reference. Adding the green -spec declarations to message@1.0 in the device-specs commit. In v0.11, we use those same declarations to make execution more efficient. With Vary, a function declares the inputs it actually uses. HyperBEAM normalises those inputs and can reuse a cached result when they match, even if unrelated fields in the larger message have changed. That means fewer repeated computations and faster responses when a result is already cached. Device authors also have less input conversion and link-loading code to write. Those declarations do two things: reduce unnecessary work and generate the node's interface docs. The result is a more efficient HyperBEAM -- and one that writes its own docs. Read this on the Permaweb: https://ao.arweave.net/#/blog/self-documenting-hyperbeam

  6. Published Social post
    • OP+18Positive

    Optimism (@Optimism)

    Here are the key takeaways from Digital Assets Week London, from Optimism’s Director of Enterprise Sales, Adoni Ioannou: 1. Collateral mobility is becoming a major focus. Institutions want to use assets more efficiently without having to sell them just to post cash. 2. Interoperability was the word of the week. Public and private networks need to connect, while institutions maintain control over access and sensitive data. 3. “24/7” means different things to different institutions. For some, it’s global access. For others, settlement and operational efficiency come first. The direction is clear: lower costs, more efficient capital, and better financial products onchain.

  8. Published Social post

    Grayscale (@Grayscale)

    An incredible week in Singapore by the numbers: 16 speaking events across @token2049, @Cointelegraph, and more 400+ allocators and operators spoken to 10 unforgettable stages at @solana Capital Forum, @NEARProtocol, and @blockworksDAS and more 3 @HyperliquidX events and conversations with @chameleon_jeff 2 Grayscale side events hosted 2 panels with @Zcash founder @zooko 1 major milestone (looking at you, @SuiNetwork) Conversations spanned tokenization, financial privacy, ETFs, quantum, and onchain finance. The ideas exchanged in Singapore will help shape what comes next.

  14. Published Social post

    Donald J. Trump (@realDonaldTrump)

    I have just concluded a highly successful discussion with President Vladimir Putin, of Russia, wherein it was agreed that Russia will immediately supply over 300,000 Tons of Diesel Fuel to the American and Global Marketplace, another 500,000 Tons during the month of November, and 1,000,000 Tons immediately thereafter. Additionally, based on the condition of their Diesel Refineries, Russia will then deliver, within a short period of time, 3,000,000 Tons of Diesel Fuel. Between our TOTAL CONTROL of the Strait of Hormuz, and this great announcement on Russian Energy, Diesel Prices for Americans and, indeed, the World, will be COMING DOWN, IN RECORD NUMBERS, AND FAST! Lower prices for Americans, especially our Great Farmers, Ranchers, and Truckers, is my Greatest Priority. This is a very big and important announcement. Additionally, it must be understood, that Iran will not have a Nuclear Weapon! Thank you for your attention to this matter. President DONALD J. TRUMP

  15. Published Social post

    The Block (@TheBlockCo)

    THE BLOCK: Former FTX COO Constance Wang says Netflix's upcoming series "The Altruists" misrepresents her experience at the collapsed crypto exchange, with the trailer making her "physically throw up." Waing criticized the show’s focus on Sam Bankman-Fried and Caroline Ellison’s romance, saying FTX's workplace was nothing like the partying culture often associated with its collapse.

  18. Published Social post

    Injective 🥷 (@injective)

    Today we are launching the Injective Ecosystem Page! Explore 270+ apps, projects and partners integrated with Injective. The page will serve as a starting point for all users and builders who want to pariticpate onchain with $INJ https://injhub.com/ecosystem/

  20. Published Social post
    • T+20Positive

    Threshold Network ✜ (@TheTNetwork)

    September 2026 Recap: Building tBTC Stronger from the Inside Out September was a month of quiet but meaningful groundwork for Threshold, as the team focused on making @tBTC_project stronger from the inside out. These efforts also address forward-looking technical specifications for VBA (Verifiable Bitcoin Accounts) version 1, enabling diligence teams to review every part of the account design before any Bitcoin is committed. September also brought new research from @AleaResearch on Bitcoin-backed lending and continued focus on borrowing against Bitcoin with tBTC. Mid-month, Threshold Network joined the European Blockchain Convention in Barcelona to discuss what comes next for institutional Bitcoin. Highlights Threshold Network published the technical specification for Verifiable Bitcoin Accounts, defining how each BTC remains segregated. Threshold began an expanded round of security checks and maintenance updates on the tBTC bridge, building on the bridge security work shared in August. A new release from Alea Research highlights tBTC’s $368.6M custody base and its strong market fit in institutional lending markets. The VBA pipeline continues to strengthen, with positive feedback from prospects so far. Threshold participated in the European Blockchain Convention in Barcelona last September, creating new opportunities for institutional engagement. Milestones Technical Specification of Verifiable Bitcoin Accounts The Verifiable Bitcoin Accounts specification defines how an institution opens and closes a segregated Bitcoin position. An institution funds a Verifiable Bitcoin Account with a single Bitcoin transaction from the custody setup it already operates. It then signs from an Ethereum account inside that same custody stack, so its existing arrangements stay unchanged. Each account's coins are reserved as their own identified UTXOs and are never pooled with other users' Bitcoin. Against that reservation, tBTC is minted to an address the owner nominates. The owner decides where that tBTC goes, and the reserved Bitcoin is unaffected by what happens to it on-chain.‍ Redemption in a Verifiable Bitcoin Account is in kind, returning the same coins that were reserved. Only the account address controlled by the owner can redeem or extend the position. Redemption can be taken in whole or in part, and repeatedly, at any time before the account's expiry. Anyone running a Bitcoin node can verify a Verifiable Bitcoin Account by inspecting its anchor UTXO and on-chain ownership record. That check traces the position's full lineage, which is what makes the account verifiable. "Institutions don't need additional layers of trust; they need systems where outcomes are defined and verifiable from the outset." - MacLane Wilkison, Co-Founder of Threshold Network Security Checks and Updates on the tBTC Bridge Most of September was spent on maintenance and security hardening across the stack. The team worked through the core components that secure tBTC, including the signing library, the bridge contracts, the node software, stress testing, tightening code paths, and expanding test coverage. ‍ FROST and Schnorr signing moved forward. Work continued on moving tBTC’s threshold signing to FROST, a modern Schnorr-based scheme. Schnorr signatures align tBTC with Bitcoin’s Taproot upgrade, and FROST is designed to simplify and strengthen the signing process. This remains one of the team’s core priorities heading into Q4.‍ The month closed with routine housekeeping: outdated configurations and a deprecated integration were retired, and regular security maintenance was carried out across the protocol’s tooling. Ecosystem Growth Highlights on Bitcoin-backed Credit Loans Borrowing against Bitcoin has always been part of what tBTC makes possible. But as Q3 2026 came to a close, the terms on offer made it worth a fresh look, especially for anyone who believes in Bitcoin for the long haul. The idea is simple. Instead of selling Bitcoin to raise cash, tBTC holders can borrow up to 73% loan-to-value against it. Their long-term BTC exposure remains on the balance sheet, positions stay intact, and funding needs are still met. There's no forced choice between conviction and liquidity. The cost of that flexibility has been notably low. As of September 24, 2026, borrow rates for Bitcoin-backed credit with tBTC stood at 4% in US dollars and 2.5% in euros. For treasury teams, that opens a practical path to cover expenses or meet obligations without selling their core Bitcoin asset. Community and Events European Blockchain Convention, Barcelona ‍RC Ramos, Head of Marketing, represented Threshold Network at the European Blockchain Convention in Barcelona. The conversations centered on what comes next for institutional Bitcoin through Verifiable Bitcoin Accounts and where institutional demand is heading. Media Highlights Alea Research report ‍Alea Research published an analysis of where Threshold Network's institutional accounts sit in Bitcoin-backed lending. The report highlights 3 parts: DeFi usage: Aave and Curve are tBTC’s main venues. Aave deposits topped 2,000 tBTC in July, then slipped to about 1,750 by mid-August. Yield vaults held $24.6M in July, about 93% of it in Yield Basis. The T token angle. Staking 100,000 T gives users a fee allowance of 0.001 tBTC per rolling 30 days. That covers the fee on roughly 0.5 BTC of mint/redeem activity. This is a fee discount for active users, not passive yield, and unstaking takes 30 days. T holders also vote on fees and the treasury, and the treasury sometimes buys back T at its own discretion. The report notes T rose 33.6% over the period. The report argues that institutional borrowing is Threshold’s growth opportunity. More mint/redeem activity would mean more fees and more reason to stake T. The underlying data is mixed, though: BTC deposits and fee income both declined in Q3. Holders can borrow against that Bitcoin through Verifiable Bitcoin Accounts without selling it, and the full report is available here. Looking Ahead Q4 builds on the groundwork laid in September. The focus stays on two connected priorities: refining Verifiable Bitcoin Accounts and strengthening the security of the tBTC bridge underneath them. Refining the VBA specification. With version 1 of the technical specification now published, the next step is to refine it with the diligence teams and prospects as they review the account design. Their feedback will help sharpen how positions are opened, extended, and redeemed, and how institutions verify them from their own Bitcoin. The goal is to answer every open question before any Bitcoin is committed, so outcomes are defined and verifiable from the outset. Moving to FROST and Schnorr signing. The move to FROST remains one of the team’s core priorities this quarter. Schnorr-based signing aligns tBTC with Bitcoin’s Taproot upgrade and is designed to make threshold signing simpler and more robust. For institutions using Verifiable Bitcoin Accounts, that means a signing process built on the same cryptography as Bitcoin itself. Continued security tightening. The security checks that began in September will carry into Q4. This work spans the signing library, bridge contracts, and node software, with ongoing stress testing, tighter code paths, and broader test coverage. Regular maintenance and retiring outdated components will continue alongside it, keeping the protocol lean as institutional activity grows. Together, these efforts point to one outcome for Q4: an account design institutions can verify end-to-end, secured by signing infrastructure built for Bitcoin’s future.

  26. Published Social post

    Plume (@plumenetwork)

    Plume has signed an MOU with AsiaStrategy (Nasdaq: SORA) on a proposed joint venture to bring tokenized products to investors across Asia. Plume brings its industry-leading infrastructure, while AsiaStrategy and @SoraVentures bring expanded distribution across Japan, Korea, Hong Kong, Thailand, and the UAE. Read the full press release: https://www.globenewswire.com/news-release/2026/10/01/3373374/0/en/asiastrategy-signs-memorandum-of-understanding-with-plume-network-to-advance-real-world-asset-tokenisation-across-asia.html

  28. Published Social post

    Impact unavailable

    Veranta (@verantaxyz)

    Announcing a major liquidity increase to commodities today. 🚀 This is in response to the tremendous demand we've seen from traders who want to place single large $XAU clips. Now traders can single shot 15M positions, all with zero commissions and near zero spreads. Only on Veranta is this possible.

  31. Published Social post

    Impact unavailable

    pieverse (@pieverse_io)

    There’s more time to meet your Agent. 🐾 We’re extending our campaign through Oct 14, giving new @StartaleApp users another chance to unlock the Pieverse Agent experience. ⭐ Join the campaign to earn 100 STAR Points + 7 days of Purr-Fect Claw. To qualify: • Create a Startale App account through Pieverse • Fund your account with $10+ • Deposit $10+ into an eligible Earn or LP Vault • Hold your deposit for at least 5 days Every Agent comes with @soneium support out of the box — the Ethereum Layer 2 by Sony Block Solutions Labs and @StartaleGroup. Start with Startale. Meet your AI Agent. Join now: https://www.pieverse.io/campaigns/startale-start

  33. Published Social post

    Ankr (@ankr)

    Blockchain security has never been more critical. 🔐 As onchain tech advances, so do the threats. This year's exploits are a costly reminder that security must start at the infra layer. That's why networks like @NEARProtocol are adopting Ankr's Verifiable RPC to strengthen security at its foundation. With cryptographically signed and attested RPC data, developers can independently verify the information their applications rely on before acting on it. Don't leave your infrastructure as the weak link.👇

  35. Published Social post

    Trust Wallet (@TrustWallet)

    Trust Wallet House at @token2049 was filled with builders, founders & creators moving the space forward🙌 ✅ 400+ guests above the Singapore skyline ✅ Nine years, celebrated together ✅ Thanks to all our partners Appreciate everyone who pulled up, see you at the next one 🚀

  39. Published Social post

    Chainlink (@chainlink)

    DTCC AND CHAINLINK AT SIBOS 2026 DTCC's Dan Doney and @SergeyNazarov presented how @The_DTCC is collaborating with Chainlink to advance 24/7 collateral management. DTCC's Collateral AppChain provides shared infrastructure near real-time collateral management across financial markets and blockchains. “The problem being solved is the fragmentation of data, how everybody connects to move collateral and settle transactions, and the different systems that need to talk to each other but cannot do so quickly enough to allow intraday collateral movement.” - Sergey Nazarov DTCC’s Collateral AppChain will leverage the Chainlink Runtime Environment (CRE) for orchestration between those systems and data sources, and CCIP which enables the movement of assets, value, and liquidity to and from the AppChain. "You finally have a reliable and legally binding ledger from the DTCC that everyone can rely on, just like they rely on the DTCC now. That's a very powerful thing that I think the capital markets have been waiting for, where they can't get that from just any chain because those guarantees with the DTCC are fundamentally different" Nazarov also added. The DTCC Collateral AppChain is expected to launch in Q1 2027. Presentation slides here: https://chn.lk/dtcc-chainlink-sibos-2026 Watch the full presentation ↓

  41. Published Social post

    OpenLedger (@OpenledgerHQ)

    Multi-agent AI needs better privacy boundaries. encryption alone won't stop sensitive context from spreading. scoped access, minimal context, and verifiable rules let agents collaborate without knowing everything.

  44. Published Social post

    NEAR Protocol (@NEARProtocol)

    Cryptographic agility is a baseline requirement for the blockchain industry. Upgrading signatures should be a routine operation. NEAR accounts already support the post-quantum ML-DSA signature scheme, with no asset migration required. The Near One team has also been working on NEP-655, committed implicit accounts derived from a hash of their initial state. Assets sit behind that hash, with no public key or key hash exposed onchain. Currently live on testnet, with mainnet in the coming weeks. For builders, the team is designing NEAR Intents Wallet Contracts so they support custom signing extensions, including ML-DSA and hash-based schemes. For chains that can’t yet add a PQ key, the team is actively working on a Q-day recovery registry on NEAR, where users commit recovery keys as rotatable hashes. NEAR was designed with quantum in mind in 2018, and the ecosystem continues to plan ahead to keep NEAR and the wider industry secure.

  45. Published Social post

    Kelp (@KelpDAO)

    Staking on Hedera works differently from staking on most proof-of-stake networks. Staked HBAR never leaves the account, and there is no bonding, no lock-up and no slashing. About 12.96 billion HBAR is staked today, roughly 29% of the released supply.

  46. Published Social post

    Impact unavailable

    Kye Gomez (swarms) (@KyeGomezB)

    Introducing Open EmbeddingGemma 2 I built a single-file PyTorch implementation of EmbeddingGemma 2 because there was no GitHub repository, published paper, or technical report to reference. It's an impressive model for its size, and I wanted to make it easier for others to understand how it works and how to train it for their own applications. Learn more ⬇️

  47. Published Social post

    CoinDesk (@CoinDesk)

    LATEST: Treasury Secretary Scott Bessent says the U.S. expects to seize $1B in Iran-linked crypto this week, part of an “absolute isolation campaign” targeting the regime’s access to financial channels.

  48. Published Social post

    Lista DAO (@lista_dao)

    📢Announcement: lisASTER is undergoing an upgrade. During this upgrade, new deposits are paused. Existing positions are not affected and continue earning. A follow-up announcement will be made once the upgrade is complete. Stay tuned!

  50. Published Social post
    • CC+15Positive

    Canton Network (@CantonNetwork)

    The Universal Burn proposal aims to unify how Canton charges for usage. @ShaulKfir joined @LongViewCrypto to discuss heterogeneous pricing, institutional vs retail adoption, ecosystem health and growth, burn-mint equilibrium, and technical hurdles. https://www.youtube.com/watch?v=KG3bRURUVho

Showing 50 of 1274 stories · Page 17 of 26. Filters apply to the full news archive.