CoinShares Q3 earnings: Sells all ETH holdings and half of SOL holdings; net profit rises 27% year over year
ChainCatcher reports that digital asset management firm CoinShares (Nasdaq: CSHR) released its unaudited financial results for the third quarter of 2026. As of September 30, the company’s assets under management (AUM) had rebounded to $7.4 billion, up approximately 34.5% from $5.5 billion at the end of the second quarter. Net inflows totaled $125 million for the quarter and $152.6 million for the first three quarters combined. In the third quarter, CoinShares generated total revenue of $27.7 million, while operating income and gains totaled $46.5 million, a marked increase from $15.9 million in the second quarter. Operating profit was $28.4 million, compared with an operating loss of $5.9 million in the second quarter. Net profit was $39.58 million, up 27% year over year. The increase in net profit was mainly driven by $14.4 million in gains on the company’s proprietary digital asset holdings. Adjusted segment EBITDA for the period was $20.57 million, down 61.4% year over year.
Gate Delists ANTHROPIC3L/3S and Relists Them as ANT3L/3S, Launching a Trading Challenge with a Prize Pool of 40,000 USDT Worth of WLFI
According to ChainCatcher, Gate announced that it suspended trading of ANTHROPIC3L/3S at 15:00 on November 18 (UTC+8), and simultaneously canceled the associated trading bots and unfilled orders. The platform will buy back users’ tokens at their net asset value at the time trading was halted, automatically convert them to USDT, and distribute the funds to users’ accounts within seven business days. Meanwhile, Gate relisted the corresponding 3x leveraged long and short tokens under the names ANT3L/3S, with trading reopening at 15:00 on November 18 (UTC+8). To celebrate the new token listing, Gate is holding an ANT3L/3S trading challenge from 17:00 on November 18 to 17:00 on November 30 (UTC+8). Users who trade the designated tokens and complete the tasks will earn chances to enter a prize draw, with prizes including Lucyd Aero smart glasses, a Plaud Note Pro AI note-taking device, and up to 200 USDT in Claude Pro subscription credits.
According to ChainCatcher, Onchain Lens monitored a Solana trader who bought 77 million DACITY for $14,500 and has sold 70.7 million for $89,100. After holding for 29 days, the trader has made a total profit of approximately $112,300, including $32,800 in unrealized gains. The trader currently holds 6.3 million tokens.
ChainCatcher reports that Glassnode data shows publicly listed mining companies tracked by the firm have sold nearly half of their Bitcoin holdings since January, using the proceeds to pivot to AI data centers.
Acala network to stop producing blocks in February 2027; users must migrate assets by year-end
According to ChainCatcher, Astar Network said that Acala, a parachain in the Polkadot ecosystem, has voted to shut down its network and will stop producing blocks after February 10, 2027. Users must migrate their assets via the Astar Portal cross-chain bridge by December 31, 2026. Users holding aSEED, LDOT, or ACA on the Astar network must transfer their assets to Acala; users holding ASTR on the Acala network must transfer it to Astar. The Astar Portal will remove the Acala cross-chain channel in early January 2027. The cross-chain connection between Astar and Acala will then be shut down through a governance proposal. After that, ASTR still on the Acala network will no longer be transferable out.
Should You Build, Buy, or Combine Web3 Data? Most Teams Need a Combination
1. Why This Question Is Often Underestimated When teams set out to build project pages, research terminals, rankings, or AI products, they often reduce the choice to “collect the data themselves” or “buy an API.” In reality, the cost of maintaining on-chain data, market data, public disclosures, and entity relationships varies, and either approach on its own can leave blind spots. 2. What Information Foundation Do You Need to Build? Building in-house is best suited to interactions and metrics that closely align with your product logic and offer unique value. Purchasing structured data is better suited to layers such as projects, funding rounds, people, investors, and categories that require ongoing maintenance, standardization, and entity relationships. The RootData API covers this off-chain and relationship-based information, with endpoints for projects, funding rounds, people, rankings, and tokenized markets, so teams don’t have to build all the foundational data from scratch.
Data Attribution Is Not Footer Decoration: It Is Part of Product Trust
1. Why this issue is often underestimated When users see information about projects, funding, or teams, they often want to know where the data comes from, when it was last updated, and whether it can be verified. If a page presents conclusions without explaining the sources or update schedule, even accurate content can struggle to build lasting trust. For data providers and product teams alike, attribution also defines the boundaries of responsibility. 2. What information foundation needs to be established In publicly visible RootData partnership cases, pages such as Binance Alpha, HashKey, CoinGlass, Blockworks, CertiK, and eToday display source labels like “Data from RootData” and “Sourced from RootData.” This practice is more than brand promotion: it tells users which data layer provided the information and offers a path to learn about update frequency, methodology, and further details.
A Free API POC Should Do More Than Verify That the Endpoint Works
I. Why This Problem Is Often Underestimated Free quotas are great for lowering the barrier to getting started, but if a POC sends only a few requests and ends as soon as it sees a JSON response, it cannot tell the team whether the data is suitable for a real product. More important questions are: On which pages will users see this information? Are the fields clearly explained? How many calls and how much caching will be needed after launch? II. What Information Foundation Needs to Be Established The RootData API Basic plan publicly offers 1,000 API Credits per month and 60 calls per minute, making it suitable for validating a specific use case first. Choose one clearly defined endpoint, such as project search, project details, funding, or people, and build a small-scale prototype. If your goal is professional market data, batch processing, or synchronization, confirm the relevant subscription capabilities and call costs in advance.
Why Data Goes Stale After Launch: Incremental Sync Is Key to Long-Term API Usability
1. Why this issue is often underestimated Many teams complete a one-time data integration before launch but fail to design a sync mechanism for subsequent changes. Company information gets updated, people change positions, funding records are supplemented, and market status shifts. If the only option is to repeatedly fetch everything, costs and latency quickly rise. 2. What information foundation needs to be established RootData API’s sync update capability gives Pro users a way to process data changes. Its purpose is not to guarantee that every field updates at the exact same moment, but to help engineering teams identify which objects have changed and then schedule refreshes according to their own caching, display, and audit needs. For user-facing pages, the update time should be considered alongside the data status.
One of the Hardest Problems in Web3 Data: Does the Same Name Actually Refer to the Same Entity?
I. Why This Problem Is Often Underestimated Entity naming in Web3 is inherently complex: projects may change their names, multiple projects may share the same name, a token’s name may differ from its protocol’s brand, and a project may deploy multiple contracts across multiple chains. If a product relies only on string matching, it can easily combine unrelated information or split the same entity across multiple pages. II. What Information Foundation Needs to Be Built The RootData API organizes information into structured objects such as projects, people, investors, and tags, providing a foundation for entity resolution. Stable project IDs, official links, aliases, tokens or contracts, and team and funding relationships are all clues for determining whether two records refer to the same entity. No single field is sufficient, but multiple pieces of public evidence can significantly reduce false matches.
Funding Records Should Be More Than Just Amounts: How data_status Helps Assess Credibility
I. First, identify the real problem The first thing to get shared about a funding record is often the amount, but the amount itself offers little context: Was it publicly announced or reported by the media? Does it refer to a single round, cumulative funding, or a valuation-related figure? Is the investor list complete? Without status and source information, the data can hardly support more serious research. II. What information needs to be verifiable RootData's funding data can serve as a connective layer between projects, rounds, investors, and timelines. Combined with data_status and source information, the product can distinguish records by their degree of verifiability rather than treating every entry as an equally certain fact. For data users, the status field is not an ancillary note; it is part of understanding the boundaries of risk.
When AI answers funding questions, credibility comes from the evidence chain, not the tone
I. First, identify the real question When users ask, “How much has this project raised?” or “Which institutions have invested in it?”, AI can easily generate a fluent answer—but fluency does not mean accuracy. Funding events often involve disclosure delays, differing definitions of amounts, incomplete investor lists, or projects with the same name. If any link in the chain is inaccurate, the conclusion may seem complete but be impossible to verify. II. What information needs to be verifiable RootData API’s funding, project, investor, and people data enables AI or research products to organize answers around entity relationships. What matters is not just returning an amount, but also preserving context such as the round, timing, investors, public sources, and data status, so users know what the conclusion covers and what uncertainties remain.
X Data Belongs in Web3 Research Only When It Can Be Verified
I. Identify the Real Problem First Discussions on X move quickly and can easily be amplified by hype, repost networks, and short-term narratives. Treating social media data directly as a measure of project quality or as the basis for investment conclusions often amplifies noise. But ignoring it entirely may mean missing early signals such as team communications, product updates, and community changes. II. What Information Can Be Verified The RootData API provides data on trending projects and people on X, detailed follow information, and bulk data capabilities. In particular, information about follow relationships and influence can serve as research leads: it can help you observe which entities are being discussed and which relationships between people are changing, but it should not be misinterpreted as definitive proof of a project's value.
Wallet products are competing not over balance displays, but over the context behind the assets
I. First, identify the real problem A wallet takes users on-chain, but a token balance alone does not explain the risks, use cases, or project background. For new users and those with diversified holdings, what is truly valuable is being able to quickly see what a project is, whether public information is available about its team and funding, and whether there are any upcoming events worth watching before taking action. II. What information can be verified The public example of Binance Wallet shows how RootData project overviews, team information, event calendars, and news feeds can be integrated into the EARN experience. This information layer does not replace the wallet’s transaction and asset functions. Instead, it provides fuller context when users are preparing to participate, hold, or research, while offering a gateway to further reading.
Why Researching Tokenized Assets Requires Cross-Market Context, Not Just On-Chain Numbers
I. First, identify the real question Tokenized stocks, ETFs, and other RWA products are bringing the pricing, issuance, trading, and settlement of traditional assets onto different infrastructures. The question for users is not simply “Does this asset exist on-chain?” They also need to know who issued it, what underlying asset it represents, where it trades, and how its liquidity and product status change. II. What information needs to be verifiable RootData’s tokenized market data can be queried by dimensions such as underlying ticker or entity, market category, issuer, trading venue, chain, and contract address. It returns information including price, trading volume, open interest, spreads, depth, supply or AUM, time, and status. These fields help researchers compare traditional assets, on-chain representations, and trading environments within a single framework.
Why a Searchable Web3 Project Directory Must Start with Entities and Categories
1. Where the Problem Begins “Including more projects” does not mean “making projects easier to find.” When project names are similar, brands are renamed, projects deploy across multiple chains, or a team launches several products, a directory built on a simple pile of keywords can show users duplicate, missing, and difficult-to-compare results. 2. Information Structure Determines What Users Can See Project, tag, ecosystem, person, funding, and investor data from the RootData API can work together to support the directory structure. A project should be more than a short description: it should have a stable entity identifier and be linked to its official links, sector tags, funding records, team members, and ecosystem. This allows search to do more than match names—it can also answer questions such as “Which funded projects are in this sector?”
Exchange Transparency Is More Than a Promise: It Requires an Information Checklist That Can Be Maintained Over Time
I. Where the Problem Begins During security incidents, liquidity concerns, or changes to platform rules, users first look for reliable information. But terms like “secure” and “transparent,” without corresponding public materials and update mechanisms, can easily become unverifiable marketing claims. Exchanges need a disclosure system that can be maintained over time, not a one-off response. II. Information Structure Determines What Users Can See A basic checklist should cover licensing or applicable jurisdictions, the scope of reserve or asset proofs, explanations of user and platform liabilities, hot and cold wallet management mechanisms, audit or attestation materials, the team and official channels, fees and risk rules, and announcements and progress updates following major incidents. The information boundaries differ across platform types, but the principle is the same: users should know what has been disclosed, when it will be updated, and who is responsible.
How to Turn a Stock Perpetual Contract Leaderboard into a Research Product, Not Just a Buzzing List of Rankings
1. Where the Problem Begins Rankings are naturally shareable, but if users can only see who ranks from first to tenth, their value is quickly exhausted. For tokenized stocks or stock perpetual markets, users usually also want to know why rankings have changed, how trading conditions differ across platforms, whether a particular metric is deteriorating, and what they should focus on monitoring. 2. Information Structure Determines What Users Can See RootData’s exchange stock perpetual contract ranking data provides fields such as overall score, number of contracts, open interest, trading volume changes, weighted depth, spread, funding rate, fee rate, margin, and maximum leverage. This allows the product to go beyond simply showing “who ranks where” and explain “which metrics are driving the changes,” while also making it easier to build filters and explanations around different user goals.
Research Terminals Need a Reproducible Research Path, Not More Tabs
I. Where the Problem Begins Researching a Web3 project often starts with a news story or a token, then leads to constant switching between official websites, social media, funding databases, wallet tools, and media pages. The problem is not just inefficiency: inconsistent naming, timelines, and levels of disclosure across sources also make findings difficult to verify. II. Information Structure Determines What Users Can See The RootData API brings projects, funding rounds, investment firms, people, tags, ecosystems, and calendars together in a unified entity framework. Researchers can start with a project, review its related funding and investors, then expand their research to people’s backgrounds, projects in the same sector, or events from a specific period. This structure is well suited to filtering, comparison, and research documentation, rather than relying on one-off search screenshots.
What’s Next for Asset Pages: Why Web3 Project Details Need Verifiable Background Information
I. Where the Problem Begins If an asset page contains only the price, candlestick chart, and contract address, users may still find it difficult to understand what they are researching. Especially when a new asset launches, narratives shift, or a risk event occurs, context such as the project background, team, funding, official channels, and on-chain identifiers often helps users make better-informed judgments than yet another price metric. II. Information Structure Determines What Users Can See The RootData API provides data endpoints for project search, project details, funding, people, investors, tags, and ecosystems, enabling asset pages to fill in background information centered around entities. The goal is not to display every field, but to establish a traceable path from a token or project name to its team, funding sources, affiliated organizations, and public links.
Log in to explore more content
Join global crypto users on Binance Square
⚡️ Get latest and useful information about crypto.