XML 55 R9.htm IDEA: XBRL DOCUMENT
v3.23.1

REVENUE FROM CONTRACTS WITH CUSTOMERS | 3 Months Ended
--- | ---
Mar. 31, 2023
Revenue from Contract with Customer [Abstract] |
REVENUE FROM CONTRACTS WITH CUSTOMERS | NOTE 3 – REVENUE FROM CONTRACTS WITH CUSTOMERS The Company recognizes revenue in accordance with ASC 606. The core principle of the revenue standard is that an entity should recognize revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration to which the Company expects to be entitled in exchange for those goods or services. The following five steps are applied to achieve that core principle:
| ● | 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
In order to identify the performance obligations in a contract with a customer, an entity must assess the promised goods or services in the contract and identify each promised good or service that is distinct. A performance obligation meets ASC 606’s definition of a “distinct” good or service (or bundle of goods or services) if both of the following criteria are met:
| ● | The customer can benefit from the good or service either on its own or together with other resources that are readily available to the customer (i.e., the good or service is capable of being distinct); and
| ● | The entity’s promise to transfer the good or service to the customer is separately identifiable from other promises in the contract (i.e., the promise to transfer the good or service is distinct within the context of the contract).
If a good or service is not distinct, the good or service is combined with other promised goods or services until a bundle of goods or services is identified that is distinct. The transaction price is the amount of consideration to which an entity expects to be entitled in exchange for transferring promised goods or services to a customer. The consideration promised in a contract with a customer may include fixed amounts, variable amounts, or both. When determining the transaction price, an entity must consider the effects of all of the following:
| ● | Variable consideration
| ● | Constraining estimates of variable consideration
| ● | The existence of a significant financing component in the contract
| ● | Noncash consideration
| ● | Consideration payable to a customer
Variable consideration is included in the transaction price only to the extent that it is probable that a significant reversal in the amount of cumulative revenue recognized will not occur when the uncertainty associated with the variable consideration is subsequently resolved. The transaction price is allocated to each performance obligation on a relative standalone selling price basis. The transaction price allocated to each performance obligation is recognized when that performance obligation is satisfied, at a point in time or over time, as appropriate. Application of the five-step model to the Company’s mining operations The Company’s ongoing major or central operation is to provide bitcoin transaction verification services to the bitcoin network through a Company-operated mining pool as the operator and a participant in a private pool (“Operator”) (such activity as Participant and Operator, collectively, “mining”) and to provide computing power to collectives of third-party bitcoin miners (such collectives, “mining pools”) as a participant (“Participant”). The Company currently mines in a self-operated pool, which was previously open to third-party pool participants from September 2021 until May 2022. The following table presents revenue of the Company disaggregated for those arrangements in which the Company is the Operator and Participant: SCHEDULE OF DISAGGREGATION OF REVENUE
(in thousands) |  | 2023 |  |  | 2022 |
|  | Three Months Ended March 31, |
(in thousands) |  | 2023 |  |  | 2022 |
Revenues from contracts with customers |  |  |  |  |  |  |  |
Participant |  | $ | 17,876 |  |  | $ | — |
Operator - Transaction fees |  |  | 1,051 |  |  |  | 517 |
Other revenue |  |  |  |  |  |  |  |
Operator - Block rewards |  |  | 32,205 |  |  |  | 51,206 |
Total revenue |  | $ | 51,132 |  |  | $ | 51,723 |
Revenue |  |  | 51,132 |  |  |  | 51,723 |
Operator As Operator, the Company provides transaction verification services. Transaction verification services are an output of the Company’s ordinary activities; therefore, the Company views the transaction requestor as a customer and accounts for the transaction fees it earns as revenue from a contract with a customer under ASC 606. The bitcoin network is not an entity such that it may not meet the definition of a customer; however, the Company has concluded it is appropriate to apply ASC 606 by analogy to block rewards earned from the network. A contract exists under ASC 606 at the point the Company successfully validates a transaction to the distributed ledger. At this point, the performance obligation to validate the requested transaction has been satisfied and a contract is deemed to exist as follows:
| ● | The transaction requester, the bitcoin network, and the Company have approved the contract and have evidenced they are committed to the transaction at the point of successfully validating and adding the transaction to the distributed ledger. The parties’ rights, the consideration to be transferred, and the payment terms are clear. The transaction has commercial substance and collection of the block reward and transaction fees to which the Company is entitled is probable because they are transferred to the Company as part of closing a successful block.
| ● | By successfully mining a block, the Company satisfies its lone performance obligation of providing transaction verification services and, thus, earns revenue at that point in time. The amount to which the Company is entitled for successfully validating a block of transactions is fixed at the point in time the contract is deemed to exist and the performance obligation is satisfied. Thus, there is no variable consideration.
The Company engaged unrelated third-party mining enterprises (“pool participants”) to contribute computing power, and in exchange, remitted transaction fees and block rewards to pool participants on a pro rata basis according to each respective pool participant’s contributed computing power (“hash rate”). The MaraPool wallet (owned by the Company as Operator) is recorded on the distributed ledger as the winner of proof of work block rewards and assignee of all validations and, therefore, the transaction verifier of record. The pool participants entered into contracts with the Company as Operator; they did not directly enter into contracts with the network or the requester and were not known verifiers of the transactions assigned to the pool. As Operator, the Company delegated mining work to the pool participants utilizing software that algorithmically assigned work to each individual miner. By virtue of its selection and operation of the software, the Company as Operator controlled delegation of work to the pool participants. This indicated that the Company directed the mining pool participants to contribute their hash rate to solve in areas that the Company designates. Therefore, the Company determined that it controlled the service of providing transaction verification services to the network and requester. Accordingly, the Company recorded all of the transaction fees and block rewards earned from transactions assigned to MaraPool as revenue, and the portion of the transaction fees and block rewards remitted to MaraPool participants as cost of revenues. The Company operated a mining pool that engaged third-party pool participants from September 2021 until May 2022. ASC 606-10-32-21 requires entities to measure the estimated fair value of noncash consideration at contract inception, which is the same time the block reward and transaction fee is earned and the performance obligation to the requester and the network is fulfilled by successfully validating the applicable block of transactions. For reasons of operational practicality, the Company applies an accounting convention to use the daily quoted closing U.S. dollar spot rate of bitcoin each day to determine the fair value of bitcoin earned as transaction fees and block rewards in the Company’s wallet during that day. This accounting convention does not result in materially different revenue recognition from using the fair value of the bitcoin earned at contract inception (i.e., the moment a block is solved) and has been consistently applied in all periods presented. Expenses associated with providing the bitcoin transaction verification services to the customers, such as rent, electricity cost, and transaction fees and block rewards are recorded as cost of revenues. Depreciation on digital asset mining equipment is recorded as a component of cost of revenues. Participant When the Company is a Participant in a third-party operated mining pool, the Company provides hash rate that is an output of the Company’s ordinary activities in exchange for consideration. The Company considers the third-party mining pool operators its customers under Topic 606. These contracts are period-to-period contracts because they are terminable at any time by either party without compensation. A new contract is determined to exist each period (i.e., second, minute, hour) that neither the Company, nor the pool operator, terminates the arrangement. The consideration to which the Company is entitled is a fractional share of the block award and transaction fees; the amount of which is based on the proportion of the Company’s contributed hash rate to the total computing power contributed by all mining pool participants in solving the current algorithm as calculated and determined by the pool operator, usually through usage of a mining software, net of any pool fees due to the pool operator. The Company receives the consideration in aggregate typically within 24 hours of winning the block, and any disputes to the consideration to which the Company is entitled can be made by notifying and resolving the issues with the pool operators. However, there have not been any subsequent adjustments to the fees received, therefore the Company concludes that it is probable that a significant reversal of revenue recognized will not occur upon settlement. Providing computing power on rigs to solve complex cryptographic algorithms in support of blockchain mining (in a process known as “solving a block”) is the primary output of the Company’s ordinary activities. The provision of computing power is the only performance obligation under our arrangements with third-party mining pool operators. The transaction consideration the Company receives is non-cash (i.e., bitcoin) and entirely variable as it is unknown at each contract inception whether the Company will earn any consideration during the period, and if it does become entitled to consideration, how much consideration to which it will be entitled. The Company satisfies its performance obligation to provide computing power to the pool operator over time as described in FASB ASC 606-10-25-27(a) as the pool operator simultaneously consumes and receives benefits from the Company’s provision of computing power, which it uses continuously as an input to the pool’s efforts to solve a block. In accordance with FASB ASC 606-10-32-11 and 32-12, the Company constrains the variable consideration to which it is entitled and does not recognize revenue for such amounts until it receives confirmation of the amount, usually via the settlement of the fractional share of block reward and transaction fees in the Company’s digital wallet. Since the Company does not have visibility on its contributed computing power relative to the pool’s total computing power, which is one of the key inputs that determine the fractional block reward and transaction fees share to which it is entitled; therefore, it only knows the amount of non-cash consideration to which it is entitled upon settlement of the Company’s earned fractional share into its digital wallet. Because of this and the fact that the Company’s fractional share substantively varies from block to block, it is not probable that a significant reversal of revenue will not occur until the uncertainty related to the Bitcoin to which the Company is entitled ultimately resolves at settlement. At settlement, the total block reward and transaction fees consideration earned by the pool operator are allocated and distributed (with no provision for, or risk of, clawback) by the pool operator to each participant based on each participant’s contribution of computing power. Consequently, at that point in time, the risk of significant revenue reversal abates such that consideration should be added to the transaction price (and revenue recognized accordingly). Settlement of consideration typically occurs within 24 hours of when a block is won unless such block is won over a weekend or holiday, in which case settlement can take up to 72 hours. The Company uses its accounting convention to measure revenue based upon the daily quoted closing U.S. dollar spot rate of bitcoin on the day the transaction fees and block rewards are settled in the Company’s wallet. This accounting convention does not result in materially different revenue recognition from using the fair value of the bitcoin earned at contract inception and has been consistently applied in all periods presented. Expenses associated with providing computing power services to third-party operated mining pools, such as rent and electricity costs, are recorded as cost of revenues. Depreciation on digital asset mining equipment is also recorded as a component of cost of revenues.

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

X
- Definition The entire disclosure of revenue from contract with customer to transfer good or service and to transfer nonfinancial asset. Includes, but is not limited to, disaggregation of revenue, credit loss recognized from contract with customer, judgment and change in judgment related to contract with customer, and asset recognized from cost incurred to obtain or fulfill contract with customer. Excludes insurance and lease contracts. + References Reference 1: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 9 -Publisher FASB -URI https://asc.fasb.org//1943274/2147479806/606-10-50-9 Reference 2: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 10 -Publisher FASB -URI https://asc.fasb.org//1943274/2147479806/606-10-50-10 Reference 3: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 15 -Publisher FASB -URI https://asc.fasb.org//1943274/2147479806/606-10-50-15 Reference 4: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 12 -Subparagraph (a) -Publisher FASB -URI https://asc.fasb.org//1943274/2147479806/606-10-50-12 Reference 5: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 12 -Subparagraph (b) -Publisher FASB -URI https://asc.fasb.org//1943274/2147479806/606-10-50-12 Reference 6: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 12 -Subparagraph (c) -Publisher FASB -URI https://asc.fasb.org//1943274/2147479806/606-10-50-12 Reference 7: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 12 -Subparagraph (d) -Publisher FASB -URI https://asc.fasb.org//1943274/2147479806/606-10-50-12 Reference 8: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 12 -Subparagraph (e) -Publisher FASB -URI https://asc.fasb.org//1943274/2147479806/606-10-50-12 Reference 9: http://www.xbrl.org/2003/role/disclosureRef -Topic 606 -SubTopic 10 -Name Accounting Standards Codification -Section 50 -Paragraph 13 -Subparagraph (b)(2) -Publisher FASB -URI https://asc.fasb.org//1943274/2147479806/606-10-50-13 Reference 10: http://www.xbrl.org/2003/role/disclosureRef -Name Accounting Standards Codification -Topic 606 -Publisher FASB -URI https://asc.fasb.org//606/tableOfContent + Details
Name: | us-gaap_RevenueFromContractWithCustomerTextBlock
Namespace Prefix: | us-gaap_
Data Type: | dtr-types:textBlockItemType
Balance Type: | na
Period Type: | duration