XML 22 R12.htm IDEA: XBRL DOCUMENT
v3.25.3

Summary of Significant Accounting Policies | 9 Months Ended
--- | ---
Sep. 30, 2025
Accounting Policies [Abstract] |
Summary of Significant Accounting Policies | Note 3 - Summary of Significant Accounting Policies There have been no material changes in the Company’s significant accounting policies to those previously disclosed in the 2024 Annual Report on the Company’s Form 10-K filed with the Securities and Exchange Commission. Cash and Cash Equivalents The Company considers all highly liquid investments with original maturities of three months or less when purchased to be cash and cash equivalents. The Company maintains cash and cash equivalent balances at financial institutions that are insured by the FDIC. As of September 30, 2025 and December 31, 2024, the Company had approximately $4,486,000 and $1,978,000 in cash. The Company has not experienced any losses in such accounts and believes it is not exposed to any significant credit risk on cash. Financial instruments that potentially subject the Company to concentration of credit risk consist principally of cash deposits. Accounts at each institution are insured by the Federal Deposit Insurance Corporation (“FDIC”) up to $250,000. As of September 30, 2025 and December 31, 2024, the Company had approximately $4,018,000 and $1,474,000 in excess of the FDIC insured limit, respectively. Stablecoins The Company holds stablecoins, including, but not limited to, USDT (Tether), USDC (USD Coin) and GHO (Aave Protocol’s native stablecoin), which are crypto assets that are pegged to the value of designed to maintain a value equivalent to one U.S. dollar. Our stablecoins are typically held in secure digital wallets or on crypto asset exchanges. The Company acquires and holds stablecoins primarily to facilitate crypto asset transactions, including, but not limited to, payments to third-party vendors. While not accounted for as cash or cash equivalents, these stablecoins are considered a liquidity resource. Crypto Assets The Company’s crypto assets primarily consist of Ethereum and other crypto assets held in non-custodial wallets. These assets are maintained under the Company’s control through secure private keys and are not held by any third-party custodian. The Company’s crypto assets are used to support its blockchain infrastructure operations, including NodeOps, Builder+ and Imperium. Fair Value Measurement The Company accounts for its crypto assets under Accounting Standards Codification (“ASC”) 350-60, Intangibles—Goodwill and Other—Crypto Assets, and measures such assets at fair value in accordance with ASC 820, Fair Value Measurement. Fair value represents the price that would be received for an asset in a current sale, assuming an orderly transaction between market participants on the measurement date. Market participants are considered to be independent, knowledgeable, and willing and able to transact. It requires the Company to assume that its crypto assets are sold in their principal market or, in the absence of a principal market, the most advantageous market to which it has access. Kraken serves as the principal market for the Company’s crypto assets, being the Company’s primary cryptocurrency exchange for both purchases and sales. Coinbase is designated as the secondary principal market. This determination results from a comprehensive evaluation considering various factors, including compliance, trading activity, and price stability. The fair value of crypto assets is primarily determined based on pricing data obtained from Kraken, the Company’s principal market. In the absence of Kraken data, pricing from Coinbase serves as a secondary source. While Kraken is designated as the primary exchange, the Company retains flexibility to conduct cryptocurrency transactions on other exchanges where it maintains accounts. This flexibility allows the Company to adapt to changing market conditions and explore alternative platforms when necessary to ensure cost-effective execution and fair value measurement using the most advantageous market. The selection of Kraken as the principal market reflects the Company’s commitment to informed decision-making and achieving the most accurate representation of fair value for its crypto assets. Regular reviews ensure alignment with the Company’s objectives and cryptocurrency market dynamics. Accounting for Crypto Assets Fair Market Value The Company measures its crypto assets at fair value in accordance with ASC 820, Fair Value Measurement, using the last closing price of the day in the UTC time zone at each reporting period end. Crypto assets are categorized based on their operational use as follows:
| ● | Crypto assets – treasury represent unencumbered holdings maintained for liquidity and investment purposes.
| ● | Crypto assets – DeFi represent assets deployed in decentralized finance protocols for lending and liquidity provision.
| ● | Crypto assets – staked represent assets actively staked to validator nodes and deployed in blockchain validation activities to earn staking rewards.
All crypto assets are measured at fair value under ASC 350-60 and are presented as current assets unless they are subject to protocol-imposed restrictions exceeding twelve months. Staked crypto assets are classified as non-current if their lock-up periods extend beyond one year. The majority of the Company’s crypto assets are deployed either in staking arrangements with lock-up periods of less than seven days or in DeFi liquidity pools that permit near-immediate redemption. Accordingly, these assets are classified as current under ASC 210-10-20, Balance Sheet, due to the Company’s ability to sell them in a liquid marketplace, as we have a reasonable expectation that they will be realized in cash or sold or consumed during the normal operating cycle of our business to support operations when needed. Cost Basis Effective January 1, 2025, the Company enhanced its accounting systems and processes related to the receipt and valuation of crypto assets. As a result of these enhancements, the Company updated its accounting policy for determining the cost basis of crypto assets received. The cost basis is now measured at fair value based on the hourly spot price at the time of receipt, consistent with the applicable guidance under ASC 350-60. Prior to January 1, 2025, the cost basis of crypto assets was measured using the last close price of the day in the UTC (Coordinated Universal Time) time zone on the date of receipt. The change has been applied prospectively and did not have a material impact on the Company’s financial statements. Cost Relief in Determining Realized Gains and Losses In conjunction with ongoing system and process enhancements, the Company updated its method for determining the cost basis of crypto assets used in computing realized gains and losses. Effective January 1, 2025, the Company adopted the Last-In, First-Out (“LIFO”) method for determining the cost basis of crypto assets disposed of. This method assumes that the most recently acquired assets are sold or used first and replaces the Company’s previous use of the specific identification method, which tracked the actual cost of each individual asset sold. The Company determined that the change in accounting principle is preferable as it better aligns with the Company’s operational systems and financial reporting objectives. The change has been applied prospectively beginning January 1, 2025, as retrospective application was deemed impracticable due to the nature of prior lot-level selection processes under the specific identification method. Realized gains (losses) on sale of crypto assets are included in operating expenses in the statements of operations. The Company recorded realized gains (losses) on crypto assets of approximately ($4,408,000) and ($122,000) for the three months ended September 30, 2025 and 2024, respectively, and approximately ($8,568,000) and $176,000 for the nine months ended September 30, 2025 and 2024, respectively. The Company does not believe the change materially impacts comparability of results. While the realized loss for the three and nine months ended September 30, 2025, reflects application of the new LIFO method, it is not practicable to quantify the exact impact of the change as compared to the prior method, given the subjective lot selection involved in specific identification. Based on this assessment, the Company does not believe the change has a material effect on the financial statements. Presentation of Crypto Assets in the Statements of Cash Flows The classification of purchases and sales in the statements of cash flows is determined based on the nature of the crypto assets, which can be categorized as ‘productive’ (i.e. acquired for purposes of staking or liquidity provision) or ‘non-productive’ (e.g., NFTs). Acquisitions of non-productive crypto assets are treated as operating activities, while acquisitions of productive crypto assets are classified as investing activities in accordance with ASC 230-10-20, Investing activities. ETH Deployed in DeFi Arrangements In DeFi arrangements, such as those transacted on the Aave protocol, the Company participates as a Liquidity Provider, depositing ETH into Aave’s decentralized lending pools. When ETH is supplied, it becomes part of the protocol’s available liquidity that borrowers may draw upon. The deposited ETH earns variable rewards based on market supply and demand for borrowing within the protocol. The ETH supplied by the Company is also eligible to serve as collateral supporting on-chain borrowing activities. The collateral value of the deposited ETH contributes to the overall “health factor” of the Company’s Aave wallet. The health factor is a protocol metric that measures the ratio of collateral value to outstanding borrowings and automatically updates with changes in ETH market prices. The health factor determines the safety buffer against liquidation; maintaining a value greater than 1.0 ensures sufficient collateralization, while a decline below 1.0 could trigger partial liquidation of the collateral by the protocol’s smart contracts. Upon deposit, ETH is automatically wrapped into Aave Wrapped ETH (“WAETH” or “aEthWETH”) to enable ERC-20 interoperability and facilitate reward accrual within the lending pool. The Company has concluded that this conversion does not constitute a derecognition event under ASC 610-20, Other Income—Gains and Losses from the Derecognition of Nonfinancial Assets, as no other counterparty obtains control or economic benefits of the deposited ETH. Rather, WAETH serves as a receipt or claim token evidencing the Company’s continuing interest in the underlying ETH. Accordingly:
| ● | ETH deployed into DeFi protocols remains recognized at its fair value under ASC 350-60.
| ● | WAETH is not recognized as a separate intangible asset since it is economically equivalent to the underlying ETH.
| ● | ETH deployed within DeFi protocols is disclosed as encumbered when serving as collateral for borrowing arrangements or liquidity provision activities.
| ● | No gain or loss is recognized upon wrapping or unwrapping ETH within DeFi protocols.
Any reward earned from such DeFi deployments is recognized as DeFi revenues on the statements of operations in accordance with ASC 606, as discussed in Note 3 - Revenue Recognition section. As of September 30, 2025, the Company had approximately 38,999 ETH deployed within DeFi protocols, which remains reflected as ETH within Crypto assets - DeFi on the balance sheet and disclosed separately in Note 4 – Crypto Assets, including disclosure of their restricted status. Deployed ETH is subject to protocol-specific risks, including smart-contract vulnerabilities, liquidity constraints, collateral liquidation risk, and potential protocol governance changes. Non-Fungible Tokens (NFTs) The Company holds certain non-fungible tokens (“NFTs”), which are unique digital assets recorded on a blockchain. NFTs do not represent ownership interests in an entity or contractual rights to cash flows, and therefore do not qualify as financial instruments or equity securities under ASC 320 or ASC 321. Consistent with the accounting treatment applied to other crypto assets, the Company accounts for NFTs as indefinite-lived intangible assets in accordance with ASC 350, Intangibles—Goodwill and Other. NFTs are initially recorded at cost and are not amortized. NFTs are assessed for impairment each reporting period to determine if any events or changes in circumstances indicate that it is more likely than not that the asset is impaired. If the fair value of an NFT is less than its carrying value, an impairment loss is recognized equal to the difference. Subsequent increases in fair value are not recorded. Realized gains or losses on the sale of NFTs are included in other income (expense) in the statements of operations. Fair value used in impairment testing is determined in accordance with ASC 820, Fair Value Measurement. Unlike fungible crypto assets, NFTs typically do not trade on centralized exchanges with quoted prices. Instead, the Company evaluates impairment by reference to observable transactions, where available, on active NFT marketplaces. During the three and nine months ended September 30, 2025, the Company purchased multiple NFTs for aggregate consideration of approximately $191,000. These NFTs are included within Non-fungible tokens on the balance sheets. No impairment losses were recognized for the three or nine months ended September 30, 2025. Operating Segments The Company’s blockchain operations include three revenue-generating business lines corresponding to its distinct sources of on-chain revenues: validator node operations (“NodeOps”), block building (“Builder+”) and DeFi operations (“Imperium”). The Company’s Chief Operating Decision Makers (“CODMs”) are comprised of several members of its executive management team, including the Chief Executive Officer (“CEO”) and Chief Financial Officer (“CFO”), who are responsible for evaluating the Company’s financial performance, managing operations, and allocating capital and resources. The CODMs regularly review discrete financial information related to Builder+ NodeOps and Imperium, assessing financial performance based on gross profit (loss), direct operating expenses, and key financial metrics. These financial reviews direct operational decisions and shape capital deployment strategies for each activity. While the CODMs evaluates NodeOps, Builder+, and Imperium individually for internal management purposes, NodeOps and Builder+ share common economic characteristics, technological infrastructure, and operational oversight and are therefore aggregated into a single operating segment, Blockchain infrastructure operations, under ASC 280, Segment Reporting. Imperium, which generates revenue through participation in DeFi protocols, is presented as a separate reportable segment, DeFi operations, due to its distinct economic drivers and underlying market characteristics. Consistent with ASU 2023-07, Segment Reporting (Topic 280): Improvements to Reportable Segment Disclosures, the Company discloses significant segment expenses and other measures that are regularly provided to the CODMs for decision-making purposes. Refer to Note 12 – Segment Information for more information. Revenue Recognition The Company recognizes revenue under ASC 606, Revenue from Contracts with Customers, which requires an entity to recognize revenue when control of the promised goods or services is transferred to the customer, in an amount that reflects the consideration the entity expects to be entitled to in exchange for those goods or services. Under ASC 606, the Company applies the following five-step model to all revenue-generating arrangements:
| ● | Step 1: Identify the contract with the customer
| ● | Step 2: Identify the performance obligations in the contract
| ● | Step 3: Determine the transaction price
| ● | Step 4: Allocate the transaction price to the performance obligations in the contract
| ● | Step 5: Recognize revenue when the Company satisfies a performance obligation
The Company’s revenues are generated from blockchain-based operations and comprise three primary sources: (i) staking rewards earned from validator node operations (NodeOps); (ii) execution-layer transaction fees, priority fees, and maximal extractable value (“MEV”) rewards earned from block-building activities (Builder+); and (iii) protocol-driven rewards earned from participation in DeFi protocols (Imperium). Revenues from NodeOps and Builder+ are aggregated and presented as Blockchain infrastructure revenues, while revenues from Imperium are presented separately as DeFi revenues in the statements of operations. The transaction consideration the Company receives in the form of native crypto assets, such as ETH or other network tokens, represents non-cash consideration measured at fair value on the date the crypto assets are earned. Collectively, these activities represent the outputs of the Company’s ordinary blockchain infrastructure operations and are measured at the fair value of the crypto assets earned at the time each performance obligation is satisfied. NodeOps The Company engages in network-based smart contracts by running its own crypto asset validator nodes as well as by staking (or “delegating”) crypto assets directly to both its own validator nodes and nodes run by third-party operators. Through these contracts, the Company provides crypto assets to stake to a node for the purpose of validating transactions and adding blocks to a respective blockchain network. The term of a smart contract can vary based on the rules of the respective blockchain and typically lasts from a few days to several weeks after it is cancelled (or “un-staked”) by the delegator and requires that the crypto assets staked remain locked up during the duration of the smart contract. In exchange for staking the crypto assets and validating transactions on blockchain networks, the Company is entitled to all of the fixed crypto asset award earned from the network when delegating to the Company’s own node and is entitled to a fractional share of the network-determined crypto asset award a third-party node operator receives (less crypto asset transaction fees payable to the node operator, which are immaterial and are recorded as a deduction from revenue), for successfully validating or adding a block to the blockchain. The Company’s fractional share of awards received from delegating to a third-party validator node is proportionate to the crypto assets staked by the Company compared to the total crypto assets staked by all Delegators to that node at that time. On certain blockchain networks on which the Company operates a validator node, the Company earns a validator node fee (“Validator Fee”), determined as a node operator’s published percentage of the crypto asset rewards earned on crypto assets delegated to its node. Token rewards earned from staking, as well as tokens earned as Validator Fees, are calculated and distributed directly to BTCS digital wallets by the blockchain networks as part of their consensus mechanisms. The provision of validating blockchain transactions is an output of the Company’s ordinary activities. Each separate block creation or validation under a smart contract with a network represents a performance obligation. The satisfaction of the performance obligation for processing and validating blockchain transactions occurs at a point in time when confirmation is received from the network indicating that the validation is complete, and the awards are available for transfer. At that point, revenue is recognized. Builder+ The Company earns revenue by participating as a Builder on blockchain networks that have implemented a Proposer-Builder Separation (PBS) framework, including Ethereum and Binance Smart Chain (“BSC”). In these roles, the Company bundles and proposes transaction blocks for submission to network Validators (“block building”), and is compensated when its blocks are selected, proposed, and successfully finalized on the applicable network. Ethereum Block Building The Company participates in the Ethereum blockchain network by engaging in the construction of blocks containing strategically bundled transactions from the Ethereum mempool and from searchers who connect to the Company’s endpoint with the intent of the Company’s builder proposing their transactions. Revenue recognition for these activities, conducted through Builder+, entails the recognition of execution layer transaction fees (or “transaction fees”) and priority fees (or “tips”) earned in exchange for successfully constructing blocks of bundled transactions and having these blocks selected and proposed by a validator to the Ethereum network for validation and successfully finalized on the network. These transaction fees and tips are earned as a direct result of the Company’s fulfillment of its performance obligations, which include the construction of blocks by bundling transactions to maximize the value of the included fees and the proposal of that block by a Validator. Each constructed block under a smart contract with the Ethereum network signifies a distinct performance obligation. As part of the block construction and proposal process, the Company’s Builder purchases block space through a fixed non-negotiable fee paid to a Validator (a “Validator Payment”) embedded in each proposed block. The Validator Payment, predetermined by the Builder, is paid to Validators as compensation for selecting and proposing the Company’s block to the network for validation. The Validator Payment is intrinsically linked to the Company’s performance obligations and is disbursed in the block constructed by the Builder if our Builder’s block is both selected by a Validator and successfully proposed to, and finalized on, the Ethereum network; otherwise, our Validator Payment may be included in a subsequent block. The Validator Payment represents a direct and fixed pre-determined cost. The satisfaction of the performance obligation occurs at a point in time when the constructed block is both proposed by a Validator and successfully finalized on the Ethereum network. At this juncture, the Company has fulfilled its obligations, and the transaction fees and tips associated with the transactions included in the block become available and are transferred to the Company’s digital wallet. The Company recognizes revenue, reflecting the fair value of the total transaction fees and tips earned from the constructed block. Binance Smart Chain (BSC) Block Building The Company also operates as a Builder on Binance Smart Chain (BSC), which uses a Proof-of-Staked-Authority (“PoSA”) consensus and a distinct block-building and reward structure. The native token of BSC is BNB, which is used for both transaction fees and transaction-based payments. Builders on BSC construct block bids composed of transactions and optional searcher tips. Unlike Ethereum, transaction fees on BSC are paid directly to the Validator’s coinbase and are not received by the Builder. Instead, the Builder earns revenue in the form of BNB-denominated tips, which are voluntarily sent by searchers to a Builder-controlled smart contract as priority fees. These tips accumulate in the smart contract and are periodically withdrawn to the Company’s Builder wallet. The Company recognizes revenue from BSC block building at the time the BNB tips are withdrawn from the tip smart contract to the Company’s wallet, measured at the fair value of BNB at the time the withdrawal occurs. Because BSC validator payments are embedded in the transaction fees of a self-transfer transaction appended by the Builder, the associated transaction cost is treated as cost of revenue. Builder performance obligations on BSC are satisfied when the constructed block is selected and proposed by a Validator and finalized on-chain. Similar to Ethereum, each block is considered a separate performance obligation. Imperium Beginning in 2025, the Company expanded its blockchain infrastructure operations to include DeFi activities under its Imperium business line. Through Imperium, the Company participates directly in DeFi ecosystems by deploying crypto assets, including ETH and stablecoins, into smart contract-based protocols that facilitate decentralized lending, liquidity provision, and other on-chain financial services. When the Company deposits ETH into a DeFi protocol, such as Aave, the ETH is converted into a tokenized representation (for example, Aave Wrapped ETH, “WETH” or “aEthWETH”) that represents the Company’s on-chain deposit position and entitles it to earn variable crypto asset rewards (e.g., ETH). These rewards accrue continuously based on protocol activity, supply-and-demand dynamics, and utilization of the Company’s deployed assets within the lending pool. The Company’s participation in DeFi protocols represents a distinct performance obligation that is satisfied over time, as the protocol’s users simultaneously receive and consume the benefits of the Company’s contributed liquidity or other deployed assets. Revenue is recognized over time in proportion to the variable rewards accrued to the Company’s position, measured at the fair value of the native token at the time the consideration is earned. Variable consideration is constrained to amounts not subject to significant reversal, consistent with ASC 606-10-32-11. Revenues earned through Imperium are classified as DeFi revenues in the statements of operations. The Company is considered the principal in these transactions because it controls the deployed crypto assets, bears protocol and market risks (including smart-contract, liquidity, and liquidation risk), and earns consideration directly from the protocol rather than through an intermediary. The following table summarizes the revenues earned from the Company’s operations for the three and nine months ended September 30, 2025 and 2024. Schedule of Revenues Earned from Company’s Operations
|  | For the Three Months Ended September 30, |  |  | For the Nine Months Ended September 30, |
|  | 2025 |  |  | 2024 |  |  | 2025 |  |  | 2024 |
Blockchain infrastructure revenues |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
NodeOps |  | $ | 858,867 |  |  | $ | 334,654 |  |  | $ | 1,461,130 |  |  | $ | 1,238,347 |
Builder+ |  |  | 3,356,357 |  |  |  | 404,503 |  |  |  | 7,215,227 |  |  |  | 513,388 |
Total blockchain infrastructure revenues |  |  | 4,215,224 |  |  |  | 739,157 |  |  |  | 8,676,357 |  |  |  | 1,751,735 |
DeFi revenues (Imperium) |  |  | 723,279 |  |  |  | - |  |  |  | 726,843 |  |  |  | - |
Total revenues |  | $ | 4,938,503 |  |  | $ | 739,157 |  |  | $ | 9,403,200 |  |  | $ | 1,751,735 |
The following tables detail the native token rewards and their respective fair market value recognized as revenue for the three and nine months ended September 30, 2025 and 2024. Revenues earned from blockchain infrastructure staking activities through NodeOps include token rewards earned from the delegation of cryptocurrency assets to third-party validator nodes as well as token rewards derived from BTCS-operated validator nodes, which include staking of the Company’s crypto assets to BTCS nodes and Validator Fees earned from third-parties asset delegations to our nodes. Revenues earned from block-building through Builder+ includes block rewards generated by BTCS Builders. Crypto assets earned from blockchain infrastructure staking activities through NodeOps Schedule of Crypto Assets Earned from Blockchain Infrastructure Staking Activities
|  | For the Three Months Ended September 30, |  |  | For the Nine Months Ended September 30, |
|  | 2025 |  |  | 2024 |  |  | 2025 |  |  | 2024 |
Asset |  | Token Rewards |  |  | Revenue ($USD) |  |  | Token Rewards |  |  | Revenue ($USD) |  |  | Token Rewards |  |  | Revenue ($USD) |  |  | Token Rewards |  |  | Revenue ($USD) |
Ethereum (ETH) |  |  | 206 |  |  | $ | 838,962 |  |  |  | 65 |  |  | $ | 180,487 |  |  |  | 345 |  |  | $ | 1,173,508 |  |  |  | 202 |  |  | $ | 610,153 |
Cosmos (ATOM) |  |  | - |  |  | $ | - |  |  |  | 13,603 |  |  | $ | 69,534 |  |  |  | 33,303 |  |  | $ | 159,486 |  |  |  | 37,334 |  |  | $ | 295,188 |
Solana (SOL)* |  |  | 108 |  |  | $ | 19,870 |  |  |  | 97 |  |  | $ | 14,414 |  |  |  | 317 |  |  | $ | 54,657 |  |  |  | 355 |  |  | $ | 51,139 |
Axie Infinity (AXS)* |  |  | - |  |  | $ | - |  |  |  | 5,796 |  |  | $ | 29,236 |  |  |  | 10,887 |  |  | $ | 30,476 |  |  |  | 16,949 |  |  | $ | 113,937 |
Akash (AKT) |  |  | - |  |  | $ | - |  |  |  | 6,151 |  |  | $ | 17,763 |  |  |  | 8,229 |  |  | $ | 15,202 |  |  |  | 16,971 |  |  | $ | 63,249 |
NEAR Protocol (NEAR)* |  |  | - |  |  | $ | - |  |  |  | 1,881 |  |  | $ | 8,802 |  |  |  | 3,482 |  |  | $ | 11,298 |  |  |  | 4,481 |  |  | $ | 25,724 |
Avalanche (AVAX)* |  |  | - |  |  | $ | - |  |  |  | - |  |  | $ | - |  |  |  | 543 |  |  | $ | 11,322 |  |  |  | 668 |  |  | $ | 18,491 |
Kava (KAVA) |  |  | - |  |  | $ | - |  |  |  | 7,046 |  |  | $ | 2,508 |  |  |  | 11,031 |  |  | $ | 4,983 |  |  |  | 19,970 |  |  | $ | 12,065 |
Stader (SD)* |  |  | - |  |  | $ | - |  |  |  | - |  |  | $ | - |  |  |  | 126 |  |  | $ | 89 |  |  |  | - |  |  | $ | - |
Polkadot (DOT)* |  |  | - |  |  | $ | - |  |  |  | 398 |  |  | $ | 1,980 |  |  |  | 9 |  |  | $ | 40 |  |  |  | 1,134 |  |  | $ | 7,556 |
Rocket Pool (RPL)* |  |  | 8 |  |  | $ | 35 |  |  |  | - |  |  | $ | - |  |  |  | 18 |  |  | $ | 69 |  |  |  | - |  |  | $ | - |
Kusama (KSM) |  |  | - |  |  | $ | - |  |  |  | 288 |  |  | $ | 5,782 |  |  |  | - |  |  | $ | - |  |  |  | 576 |  |  | $ | 14,365 |
Polygon (POL)* |  |  | - |  |  | $ | - |  |  |  | 6,851 |  |  | $ | 2,716 |  |  |  | - |  |  | $ | - |  |  |  | 19,395 |  |  | $ | 12,205 |
Tezos (XTZ)* |  |  | - |  |  | $ | - |  |  |  | 594 |  |  | $ | 419 |  |  |  | - |  |  | $ | - |  |  |  | 1,266 |  |  | $ | 1,124 |
Mina (MINA) |  |  | - |  |  | $ | - |  |  |  | 720 |  |  | $ | 319 |  |  |  | - |  |  | $ | - |  |  |  | 6,480 |  |  | $ | 6,404 |
Oasis Network (ROSE) |  |  | - |  |  | $ | - |  |  |  | - |  |  | $ | - |  |  |  | - |  |  | $ | - |  |  |  | 26,567 |  |  | $ | 3,254 |
Cardano (ADA)* |  |  | - |  |  | $ | - |  |  |  | 1,683 |  |  | $ | 628 |  |  |  | - |  |  | $ | - |  |  |  | 5,010 |  |  | $ | 2,218 |
Evmos (EVMOS)* |  |  | - |  |  | $ | - |  |  |  | 3,321 |  |  | $ | 66 |  |  |  | - |  |  | $ | - |  |  |  | 21,581 |  |  | $ | 1,275 |
Total earned from blockchain infrastructure staking activities through NodeOps |  |  |  |  |  | $ | 858,867 |  |  |  |  |  |  | $ | 334,654 |  |  |  |  |  |  | $ | 1,461,130 |  |  |  |  |  |  | $ | 1,238,347 |
| * | All or a portion of revenue earned from staking to third-party validator nodes
Crypto assets earned from block-building through Builder+ Schedule of Crypto Assets Earned From Ethereum
|  | For the Three Months Ended September 30, |  |  | For the Nine Months Ended September 30, |
|  | 2025 |  |  | 2024 |  |  | 2025 |  |  | 2024 |
Asset |  | Token Rewards |  |  | Revenue ($USD) |  |  | Token Rewards |  |  | Revenue ($USD) |  |  | Token Rewards |  |  | Revenue ($USD) |  |  | Token Rewards |  |  | Revenue ($USD) |
Ethereum (ETH) |  |  | 770 |  |  | $ | 2,952,033 |  |  |  | 152 |  |  | $ | 404,503 |  |  |  | 2,176 |  |  | $ | 6,403,386 |  |  |  | 186 |  |  | $ | 513,388 |
BNB Chain (BNB) |  |  | 446 |  |  | $ | 404,324 |  |  |  | - |  |  | $ | - |  |  |  | 1,084 |  |  | $ | 811,841 |  |  |  | - |  |  | $ | - |
Total earned from block-building through Builder+ |  |  |  |  |  | $ | 3,356,357 |  |  |  |  |  |  | $ | 404,503 |  |  |  |  |  |  | $ | 7,215,227 |  |  |  |  |  |  | $ | 513,388 |
Crypto assets earned from DeFi activities through Imperium
|  | For the Three Months Ended September 30, |  |  | For the Nine Months Ended September 30, |
|  | 2025 |  |  | 2024 |  |  | 2025 |  |  | 2024 |
Asset |  | Token Rewards |  |  | Revenue ($USD) |  |  | Token Rewards |  |  | Revenue ($USD) |  |  | Token Rewards |  |  | Revenue ($USD) |  |  | Token Rewards |  |  | Revenue ($USD) |
Ethereum (ETH) |  |  | 178 |  |  | $ | 723,279 |  |  |  | - |  |  | $ | - |  |  |  | 181 |  |  | $ | 726,843 |  |  |  | - |  |  | $ | - |
Total earned from DeFi activities through Imperium |  |  |  |  |  | $ | 723,279 |  |  |  |  |  |  | $ | - |  |  |  |  |  |  | $ | 726,843 |  |  |  |  |  |  | $ | - |
Cost of Revenues The Company’s cost of revenues primarily consists of direct expenses incurred in connection with its blockchain operations, including NodeOps, Builder+ and Imperium activities. Blockchain Infrastructure Operations (NodeOps and Builder+) The Company’s cost of revenues related to its blockchain infrastructure operations primarily includes direct production costs associated with transaction validation and block construction on blockchain networks. These costs include cloud-based server hosting expenses related to our validator nodes and Builders and allocated employee compensation related to the monitoring, maintenance and support of these operations. Additionally, for Ethereum block building, cost of revenues includes Validator Payments made by the Company’s Builder to Validators as compensation for proposing constructed blocks. These are fixed amounts embedded within the proposed blocks and are paid only when the block is successfully finalized on-chain. For Binance Smart Chain (BSC) block building, although the Builder does not receive the transaction fees attached to the bundled transactions included in a finalized block, it must still compete for inclusion by proposing an additional bid, structured as a self-transaction, that specifies extra fees intended to incentivize the Validator to select its block. This self-transaction results in a direct payment to the Validator’s coinbase address. These Builder-specified bids are separate from the transaction fees attached to user transactions and represent incremental value added by the Builder intended to increase the likelihood of block inclusion. The Company records these Builder-specified bid payments as cost of revenues, as they are a direct cost of fulfilling the block-building performance obligations under the BSC block-building arrangement in accordance with ASC 606. The Company also includes in cost of revenues any third-party fees for hosting, infrastructure support, or software maintenance related to validator or builder operations. These expenses are collectively presented as Cost of blockchain infrastructure revenues in the statements of operations. Imperium Beginning in 2025, the Company’s DeFi operations under its Imperium business line generated revenues from participation in decentralized finance protocols. Related costs of revenues primarily consist of allocated employee compensation and related expenses associated with establishing, monitoring, and maintaining DeFi activities, as well as any third-party services that support these operations and other direct on-chain expenses incurred in connection with deploying or interacting with DeFi protocols. These costs are presented as Cost of DeFi revenues in the statements of operations. The following table further details the costs of revenues for the three and nine months ended September 30, 2025 and 2024. Schedule of Costs of Revenues
|  | For the Three Months Ended September 30, |  |  | For the Nine Months Ended September 30, |
|  | 2025 |  |  | 2024 |  |  | 2025 |  |  | 2024 |
Cost of blockchain infrastructure revenues |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |
Cost of staking revenues (NodeOps) |  | $ | 8,265 |  |  | $ | 42,813 |  |  | $ | 68,287 |  |  | $ | 142,180 |
Cost of block-building revenues (Builder+) |  |  | 3,835,369 |  |  |  | 500,495 |  |  |  | 8,197,139 |  |  |  | 730,601 |
Total cost of blockchain infrastructure revenues |  |  | 3,843,634 |  |  |  | 543,308 |  |  |  | 8,265,426 |  |  |  | 872,781 |
Cost of DeFi revenues (Imperium) |  |  | 6,916 |  |  |  | - |  |  |  | 6,916 |  |  |  | - |
Total cost of revenues |  | $ | 3,850,550 |  |  | $ | 543,308 |  |  | $ | 8,272,342 |  |  | $ | 872,781 |
Internally Developed Software Internally developed software consists of the core technology of the Company’s ChainQ platform. For internally developed software, the Company uses both its own employees as well as the services of external vendors and independent contractors. The Company accounts for computer software used in the business in accordance with ASC 985-20 and ASC 350. ASC 985-20, Software-Costs of Computer Software to Be Sold, Leased, or Otherwise Marketed, requires that software development costs incurred in conjunction with product development be charged to research and development expense until technological feasibility is established. Thereafter, until the product is released for sale, software development costs must be capitalized and reported at the lower of unamortized cost or net realizable value of the related product. Some companies use a “tested working model” approach to establishing technological feasibility (i.e., beta version). Under this approach, software under development will pass the technological feasibility milestone when the Company has completed a version that contains essentially all the functionality and features of the final version and has tested the version to ensure that it works as expected. ASC 350, Intangibles-Goodwill and Other, requires computer software costs associated with internal use software to be charged to operations as incurred until certain capitalization criteria are met. Costs incurred during the preliminary project stage and the post-implementation stages are expensed as incurred. Certain qualifying costs incurred during the application development stage are capitalized as property, equipment and software. These costs generally consist of internal labor during configuration, coding, and testing activities. Capitalization begins when (i) the preliminary project stage is complete, (ii) management with the relevant authority authorizes and commits to the funding of the software project, and (iii) it is probable both that the project will be completed and that the software will be used to perform the function intended. Property and Equipment Property and equipment consists of computers, equipment and office furniture and fixtures, all of which are recorded at cost. Depreciation and amortization are recorded using the straight-line method over the respective useful lives of the assets ranging from three3 to five years. Long-lived assets are reviewed for impairment whenever events or circumstances indicate that the carrying amount of these assets may not be recoverable. Use of Estimates The accompanying condensed financial statements have been prepared in conformity with U.S. GAAP, which requires management to make estimates and assumptions that affect certain reported amounts of assets and liabilities, the disclosure of contingent assets and liabilities at the date of the financial statements, and the reported amounts of revenue and expenses during the period. The Company’s significant estimates and assumptions include, but are not limited to, the recoverability and useful lives of indefinite life intangible assets, stock-based compensation, valuation allowances related to deferred tax assets, allocations of compensation and other shared costs among functional expense categories, accruals for employee bonuses and incentives, and the fair value of certain financial instruments, when applicable. Actual results could differ from those estimates due to changes in external conditions or other factors, and such differences may be material to the financial statements. Income Taxes The Company recognizes income taxes on an accrual basis based on tax positions taken or expected to be taken in its tax returns. A tax position is defined as a position in a previously filed tax return or a position expected to be taken in a future tax filing that is reflected in measuring current or deferred income tax assets and liabilities. Tax positions are recognized only when it is more likely than not (i.e., likelihood of greater than 50%), based on technical merits, that the position would be sustained upon examination by taxing authorities. Tax positions that meet the more likely than not threshold are measured using a probability-weighted approach as the largest amount of tax benefit that is greater than 50% likely of being realized upon settlement. Income taxes are accounted for using an asset and liability approach that requires the recognition of deferred tax assets and liabilities for the expected future tax consequences of events that have been recognized in the Company’s financial statements or tax returns. A valuation allowance is established to reduce deferred tax assets if all, or some portion, of such assets will more likely than not be realized. Should they occur, the Company’s policy is to classify interest and penalties related to tax positions as income tax expense. Since the Company’s inception, no such interest or penalties have been incurred. Accounting for Warrants The Company accounts for the issuance of Common Stock purchase warrants issued in accordance with ASC 815, Derivatives and Hedging. Warrants are evaluated for liability or equity classification at the time of issuance based on the specific terms of the arrangement and settlement features. Liability-Classified Warrants Warrants are classified as liabilities when they: (i) require net cash settlement (including upon occurrence of an event outside the Company’s control), or (ii) provide the counterparty with a choice of cash or share settlement, or (iii) require the issuance of registered shares and do not explicitly preclude a right to cash settlement. In accordance with ASC 815-40, these instruments are measured at fair value upon issuance and at each subsequent reporting period, with changes in fair value recognized in the statements of operations as “Change in fair value of warrant liabilities.” These warrants are classified as Level 3 liabilities within the fair value hierarchy due to the use of unobservable inputs in the valuation model (see Note 5 - Fair Value of Financial Assets and Liabilities). The Company estimates the fair value of these warrants using a Black-Scholes option pricing model, with key inputs including the Company’s stock price, the warrant exercise price, expected term, expected stock price volatility, risk-free interest rate, and expected dividend yield. The warrant liability is presented as a current liability on the Company’s balance sheet. Equity-Classified Warrants The Company also issues warrants that qualify for equity classification under ASC 815-40. Warrants are classified in equity when they: (i) require physical or net-share settlement, and (ii) do not include terms that could require cash settlement outside the control of the Company, and (iii) do not include contingent provisions or other features that would cause the instruments to be classified as liabilities. For equity-classified warrants, the Company estimates the grant-date fair value using a Black-Scholes option pricing model. The fair value is recognized in additional paid-in capital (APIC) at the time of issuance and is not subsequently remeasured. If the warrants are issued in connection with a financing transaction (e.g., convertible notes), the fair value is allocated to APIC and, when applicable, also recorded as a debt discount in accordance with ASC 470-20, Debt with Conversion and Other Option, and amortized over the term of the related debt instrument using the effective interest method. Once classified in equity, these warrants remain in equity unless modified in a way that results in liability classification. These instruments are not included in the fair value measurements disclosure under ASC 820, as they are not remeasured on a recurring basis. Stock-based compensation The Company accounts for stock-based compensation in accordance with ASC 718, Compensation - Stock Compensation. ASC 718 addresses all forms of share-based payment awards including shares issued under employee stock purchase plans and stock incentive shares. Under ASC 718, awards result in a cost that is measured at fair value on the awards’ grant date, based on the estimated number of awards that are expected to vest and will result in a charge to operations. Share-based payment awards exchanged for services are accounted for at the fair value of the award on the estimated grant date. Options Stock options issued under the Company’s long-term incentive plans are granted with an exercise price equal to no less than the fair market value of the Company’s stock at the date of grant and expire up to ten years from the date of grant. These options generally vest over a one-year period. The Company estimates the fair value of stock option grants using the Black-Scholes option pricing model and the assumptions used in calculating the fair value of stock-based awards represent management’s best estimates and involve inherent uncertainties and the application of management’s judgment. Expected Volatility – The Company uses historical volatility as it provides a reasonable estimate of the expected volatility. For options granted prior to January 1, 2025, historical volatility was based on the most recent volatility of the stock price over a period equivalent to the expected term of the option. For options granted on or after January 1, 2025, historical volatility is determined using a two-year lookback period. Management selected this approach to better reflect the Company’s current market conditions and exclude periods of non-representative volatility associated with significant changes in the Company’s business, market conditions, and capital structure. The two-year lookback period balances capturing industry and market cycles with avoiding outdated and non-representative data. Risk-Free Interest Rate – The risk-free interest rate is based on the U.S. treasury zero-coupon yield curve in effect at the time of grant for the expected term of the option. Expected Term – The Company’s expected term represents the weighted-average period that the Company’s stock options are expected to be outstanding. The expected term is based on the expected time to post-vesting exercise of options by employees. The Company uses historical exercise patterns of previously granted options to derive employee behavioral patterns used to forecast expected exercise patterns. Expected Dividend – The Company has not historically declared or paid any cash dividends on its common shares and does not plan to pay any recurring cash dividends in the foreseeable future, and, therefore, uses an expected dividend yield of zero in its valuation models. Restricted Stock Units (RSUs) For awards vesting upon the achievement of a service condition, compensation cost measured on the grant date will be recognized on a straight-line basis over the vesting period. Stock-based compensation expense for the market-based restricted stock units with explicit service conditions is recognized on a straight-line basis over the longer of the derived service period or the explicit service period, regardless of whether the market condition is satisfied. However, in the event that the explicit service period is not met, previously recognized compensation cost would be reversed. Market-based restricted stock units subject to market-based performance targets require achievement of the performance target as well as a service condition in order for these RSUs to vest. The Company estimates the fair value of market-based RSUs as of the grant date and expected derived term using a Monte Carlo simulation that incorporates pricing inputs covering the period from the grant date through the end of the derived service period. Expected Volatility – The Company uses historical volatility as it provides a reasonable estimate of the expected volatility. Historical volatility is based on the most recent volatility of the stock price over a period of time equivalent to the expected term of the RSUs. Risk-Free Interest Rate – The risk-free interest rate is based on the U.S. treasury zero-coupon yield curve in effect at the time of grant for the expected term of the RSUs. Expected Term – The Company’s expected term represents the weighted-average period that the Company’s RSUs are expected to be outstanding. The expected term is based on the stipulated 5-year period from the grant date until the market-based criteria are achieved. If the market-based criteria are not achieved within the five-year period from the grant date, the RSUs will not vest and shall expire. Vesting Hurdle Price – The vesting hurdle prices are determined by taking the vesting Market Cap criteria divided by the shares outstanding as of the valuation dates Convertible Notes Payable Convertible notes are accounted for in accordance with ASC 470-20, Debt with Conversion and Other Options. Upon issuance, the Company evaluates embedded features and freestanding instruments for separate accounting. If applicable, proceeds are allocated between the debt host and any freestanding equity-classified instruments, such as warrants, using a relative fair value method. Issuance costs and any original issue discount are recorded as a reduction to the carrying amount of the debt and amortized over the term of the notes using the effective interest method. Interest expense includes both cash interest and amortization of debt discounts. Defi Lending Arrangements The Company accounts for DeFi lending and borrowing arrangements, such as those executed through the Aave protocol, in accordance with ASC 470, Debt. Borrowings When the Company borrows crypto assets under a DeFi protocol, the arrangement is recognized as a financial liability measured at the principal amount of the borrowed tokens, net of repayments, in accordance with ASC 470. Such borrowings are presented on the balance sheet as Loans payable – DeFi protocol. Borrowings are collateralized by the Company’s crypto assets, such as ETH, which are deposited into protocol-specific smart contracts as collateral. The deposited collateral remains recorded on the balance sheet within Crypto Assets, as the Company retains both custody and beneficial ownership. Collateralized assets are considered restricted while serving as security for DeFi borrowings and are disclosed as such in the notes to the financial statements. Fair value measurement of the collateralized ETH follows the guidance in ASC 820, Fair Value Measurement. Although the ETH is restricted and subject to liquidation risk, the Company continues to account for the underlying asset at fair value under ASC 350-60, Intangibles – Crypto Assets. Debt modifications and extinguishments The Company accounts for debt modifications and extinguishments in accordance with ASC 470-50, Debt – Modifications and Extinguishments. When existing DeFi debt is repaid or substantially modified, the previous liability is derecognized and replaced with a new liability at fair value. Any resulting gain or loss is recognized in the statement of operations under Loss on extinguishment of debt. Interest expense Interest or borrowing costs accrued under DeFi lending arrangements are recognized over the borrowing term and presented as Interest Expense in the statements of operations. Any rewards earned from the Company’s separate participation as a liquidity provider or protocol participant (e.g., Imperium) is recognized as revenue under DeFi revenues rather than interest income. Advertising Expense Advertisement costs are expensed as incurred and included in Marketing expenses in the statements of operations. Net Income (Loss) per Share Basic income (loss) per share is computed by dividing the net income or loss attributable to common shares by the weighted average number of common shares outstanding during the period. Diluted earnings per share is computed using the weighted average number of common shares and, if dilutive, potential common shares outstanding during the period. Diluted earnings per share reflects the potential dilution that could occur if securities or other contracts to issue common stock were exercised or converted into common stock. Potential common shares consist of the Company’s restricted stock units, restricted common stock, stock options, warrants and shares issuable upon conversion of outstanding convertible notes. For periods when the Company reports a net loss, diluted net loss per share is the same as basic net loss per share because the inclusion of potentially dilutive securities would be anti-dilutive. For periods in which the Company reports net income, diluted net income per share includes the effect of dilutive potential common shares, if any. The Company reported net income for the three and nine months ended September 30, 2025 and net losses for the three and nine months ended September 30, 2024. The following potentially dilutive securities were excluded from the computation of diluted loss per share during the 2024 periods of net loss, as their effect would have been anti-dilutive: Schedule of Earnings Per Share Anti-diluted
|  | As of September 30, 2024 |
Warrants to purchase common stock |  |  | 712,500 |
Options |  |  | 1,302,500 |
Non-vested restricted stock unit awards |  |  | 1,806,373 |
Total |  |  | 3,821,373 |
Anti-dilutive securities |  |  | 3,821,373 |
Recent Accounting Pronouncements The Company continually assesses new accounting pronouncements issued by the Financial Accounting Standards Board (“FASB”) and other standard-setting bodies to determine their applicability. When it is determined that a new accounting pronouncement affects the Company’s financial reporting, the Company undertakes a study to determine the consequences of such change to its Financial Statements and assures that there are proper controls in place to ascertain that the Company’s Financial Statements properly reflect the change. In November 2023, the FASB issued ASU 2023-07, Segment Reporting (Topic 280): Improvements to Reportable Segment Disclosures (“ASU 2023-07”). ASU 2023-07 is intended to enhance reportable segment disclosures by requiring disclosures of significant segment expenses regularly provided to the CODMs, requiring disclosure of the title and position of the CODMs and explanation of how the reported measures of segment profit and loss are used by the CODMs in assessing segment performance and a location of resources. ASU 2023-07 is effective for the Company for annual periods beginning after December 31, 2023. The Company adopted ASU 2023-07 for the year ended December 31, 2024. As a result of the adoption, the Company expanded its disclosures in Note 12 - Segment Information, to present significant expenses that are included within cost of revenue, by reportable segment, which are presented to the CODMs. In December 2023, FASB issued ASU 2023-09, Income Taxes (Topic 740): Improvements to Income Tax Disclosures, to enhance the transparency and decision usefulness of income tax disclosures. The amendments in ASU 2023-09 provide improvements primarily related to the rate reconciliation and income taxes paid information included in income tax disclosures. The Company is required to disclose additional information regarding reconciling items equal to or greater than five percent of the amount computed by multiplying pretax income (loss) by the applicable statutory tax rate. Similarly, the Company is required to disclose income taxes paid (net of refunds received) equal to or greater than five percent of total income taxes paid (net of refunds received). The amendments in ASU 2023-09 are effective January 1, 2025. Early adoption is permitted for annual financial statements that have not yet been issued or made available for issuance. The Company is currently evaluating the impacts of ASU 2023-09 on its financial statements. In December 2024, the FASB issued ASU 2024-03, Income Statement—Reporting Comprehensive Income—Expense Disaggregation Disclosures (Subtopic 220-40) (“ASU 2024-03”). ASU 2024-03 requires, in the notes to the financial statements, disclosures of specified information about certain costs and expenses specified in the updated guidance. ASU 2024-03 is effective for annual reporting periods beginning after December 15, 2026, and interim reporting periods beginning after December 15, 2027. Early adoption is permitted. The Company is evaluating the impact the updated guidance will have on its disclosures. Other recent accounting pronouncements issued by the FASB, including its Emerging Issues Task Force, the American Institute of Certified Public Accountants, and the Securities and Exchange Commission did not or are not believed by management to have a material impact on the Company’s present or future financial statements.

X
- References No definition available. + Details
Name: | us-gaap_AccountingPoliciesAbstract
Namespace Prefix: | us-gaap_
Data Type: | xbrli:stringItemType
Balance Type: | na
Period Type: | duration

X
- Definition The entire disclosure for all significant accounting policies of the reporting entity. + References Reference 1: http://www.xbrl.org/2003/role/disclosureRef -Topic 235 -Name Accounting Standards Codification -Publisher FASB -URI https://asc.fasb.org/235/tableOfContent Reference 2: http://www.xbrl.org/2003/role/disclosureRef -Topic 235 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 1 -Publisher FASB -URI https://asc.fasb.org/1943274/2147483426/235-10-50-1 + Details
Name: | us-gaap_SignificantAccountingPoliciesTextBlock
Namespace Prefix: | us-gaap_
Data Type: | dtr-types:textBlockItemType
Balance Type: | na
Period Type: | duration