NODE40

Institutional Solana staking is maturing fast. The latest data from P2P.org shows treasuries weighing liquid staking wrappers against native delegation, largely to preserve control over the underlying position. That control question has an accounting mirror: once staking rewards flow through a wrapped token, can your finance team still attribute rewards back to the originating validator and delegation for close reporting and audit? For most institutional stakers, the answer today is manual reconciliation, not a system of record. Validators and treasuries that get ahead of this now will be the ones with a defensible close process before an auditor asks the question for them.

A default lot method is still a tax decision. That is a bigger deal than most digital asset teams realize. FIFO, HIFO, LIFO, highest basis, long-term first: these are not just calculation preferences. Each method can change which acquisition history, basis, and holding period attach to a disposal. For material digital asset activity, that choice can affect the result your tax, finance, or audit team later has to explain. Bedrock is built around a simple principle: lot selection should be governed, explicit, and defensible. That means preserved basis history, documented override logic, deterministic selection, and an audit trail that shows why a lot was used. The default method is not neutral. It is policy. https://lnkd.in/gJhCA5Ty

SEC.gov and KPMG both flagged the same thing this week: banking regulators, the SEC and the CFTC are moving toward coordinated rulemaking on stablecoins and crypto assets in 2026. For accounting firms and treasury teams already handling digital-asset clients, that coordination doesn't reduce the reporting burden, it raises the bar. Reconciled subledger data and defensible transaction histories move from best practice to expected baseline before the rule text is even final. Firms that build audit-ready reporting infrastructure now won't be scrambling when the agendas turn into requirements. https://lnkd.in/gFFPQB5q

There's a new procurement playbook out for ETF issuers picking validator infrastructure (P2P.org, link in comments) , uptime, slashing protections, custody architecture, compliance attestations. All the right questions for choosing a validator. None of it answers the question that shows up six months later: when a slashing event or a restaking reward hits, who's recording it, at what value, and can it survive an audit request. Infrastructure due diligence and reporting readiness get evaluated by two completely different teams, and right now almost nobody is checking that the second team even exists before the first team signs.

Today we are introducing NODE40 Bedrock. The market does not need another digital asset dashboard. It needs accounting records that can defend themselves. For too long, digital asset accounting has been treated as a reconstruction exercise: - Pull the data. - Reconcile the activity. - Produce the number. - Then, when tax, audit, finance, or the board asks why the number is defensible, go back and rebuild the story from spreadsheets, exports, assumptions, and institutional memory. That workflow breaks as digital asset treasury gets more sophisticated. Staking, internal transfers, yield products, covered-call strategies, custody movement, lot selection, and policy changes all create accounting questions that cannot be solved by a balance alone. Bedrock is built around a different standard: The reasoning belongs in the record. Lot-level decisions. Transfer evidence. Overrides. Closed periods. Shortfalls. Feed corrections. Reporting history. Policy assumptions. Controls. All preserved in a governed digital asset treasury accounting system. Because once digital assets become material to the business, reporting is not enough. The record has to stand up to review.

Vanguard is searching for a digital assets executive to evaluate custody, stablecoins, tokenization, and blockchain-enabled settlement. Every category on that list generates transactions that need to be reconciled, attributed, and reported with precision. The institutions that move from evaluation to execution fastest are the ones who already know what their on-chain records look like. The strategic decision -- build, partner, or wait -- is downstream of the infrastructure question. Most large institutions find that out after the hire, not before. https://lnkd.in/gB7jz_jp

SOL Strategies published their June 2026 monthly business update. 460,017 SOL in treasury as of June 30, actively managed in service of their operating business. For public companies managing validator-weighted treasuries at this scale, the balance sheet line is visible. The defensibility of what sits behind it is not. Reward attribution, lot selection history across the year, disposition treatment for staking positions, and the subledger reconciliation that supports audited financials - those are the questions that come next. Not at year-end. During the audit. NODE40 builds the subledger infrastructure that makes those questions answerable before auditors ask them. https://lnkd.in/gnRJH_Cz

OCC has proposed treating permitted payment stablecoin issuers as financial institutions under the Bank Secrecy Act. Comment period closes July 24. If that proposal moves forward, stablecoin operations are no longer a payments infrastructure conversation. They are an examination readiness conversation. For treasury teams holding payment stablecoins, this means: AML program documentation tied to on-chain transactions, transaction provenance traceable by counterparty, and sanctions screening logs that can survive regulatory review. Not general policy documentation. Transaction-level records. Most institutional stablecoin users built their treasury operations around the payment use case. The controls and books-and-records requirements of a BSA-regulated entity are a different layer, and most are not ready for it. The July 24 comment window is the time to understand what this actually requires operationally.

FalconX received MiCA authorization from Malta's MFSA, expanding regulated institutional digital asset services across the EU. The authorization clears the regulatory path. What follows is the operational work. For institutions operating under MiCA's framework, the requirement is reconciled subledger data, jurisdiction-specific reporting, and audit-ready transaction history across the EU book. That infrastructure does not come with the license. MiCA creates the compliance obligation; the reporting layer is what determines whether operations hold up under examination. https://lnkd.in/eRaZnMUT

FASB is considering expanding fair value accounting to wrapped tokens. Is your accounting program built to handle that? In April 2026, the Financial Accounting Standards Board discussed bringing additional crypto structures, including wrapped tokens, into Subtopic 350-60 scope. It also considered guidance on when stablecoins might qualify as cash equivalents. Neither position is final. But if you are a public company or approaching an audit, this is the direction your methodology needs to anticipate. What examination-ready accounting requires under this framework: - Wrapped asset positions tracked separately from native asset equivalents at the transaction level - Subledger data that supports attribution by asset type, protocol, and wrapper contract - Stablecoin classification analysis with documentation supporting the cash-equivalent determination None of these require waiting for final rules. They follow from the same subledger discipline that good digital-asset accounting already demands. The gap for most teams is that this level of granularity was not built into the original workflow. If you are operating without transaction-level subledger data that distinguishes wrapped from native positions, that is the gap to close before an auditor asks.