ERC-7776 Transparent on-chain financial statements (Transparent Financial Statements)

Review · Other · created 2024-09-20

A standard API by which a blockchain-based company (protocol) discloses financial information such as revenue, expenses, net income, and earnings per token on-chain through a smart contract. It lets investors check financial status in a format similar to the disclosures of a publicly listed stock.

Why it is needed

Current token investment analysis is opaque. Most information is abstract description rather than concrete figures. Many ERC-20 tokens issued by blockchain-based companies (protocols) do not grant rights to company equity or profit the way stock does, and instead function like a commodity consumed within the platform. Yet they are advertised and traded as if they represented the company like stock, without the kind of open, clear financial information that listed stocks are required to disclose. Token analysis reports found on the internet are also mostly informal posts written by anonymous authors, lacking fact-based financial figures. As a result, there is no standard, trustworthy way for investors to evaluate a project's financial health using real numbers. This standard aims to solve this by putting verifiable financial data directly on-chain, modeled on reporting structures like the US Securities and Exchange Commission's (SEC) quarterly report (10-Q).

What to implement

In depth

ERC-20 required implementation and the principle of stablecoin denomination

All implementations MUST implement ERC-20 to represent equity, and SHOULD also implement ERC-20's optional metadata extension. The name and symbol functions SHOULD reflect, in some form, the name and symbol of the underlying token. Financial figures such as Revenue, Cost of Goods Sold, Operating Expenses, Operating Income, EBITDA, Other Income and Expenses, Net Income, and Earnings Per Share MUST all be denominated in the stablecoin value chosen by the protocol. All methods MUST have external visibility and MUST return values denominated in the provided stablecoin. Per the Rationale, ERC-20 is enforced because implementation details such as per-token profit calculations feed directly into accounting, and to ensure compatibility with all existing ERC-20 tooling.

Timestamp rules: snapshots and income statements through a single API

In all methods, startTimestamp MUST be less than or equal to endTimestamp. If the two values are equal, the function returns a snapshot of financial state at that point in time, i.e. a balance sheet; if startTimestamp is smaller, it returns an income statement for that period. This design lets a single set of functions query both point-in-time financial state and period-over-period profit and loss changes. The reference implementation checks this constraint with require(startTimestamp <= endTimestamp).

Struct returns and optional detail items

Each method returns a struct holding one or more uint256 items rather than a single uint256 value. For example, revenue can include optional detail items from optionalAdditionalRevenueDetail1 through optionalAdditionalRevenueDetailN in addition to grossRevenue, each with its own name. earningsPerShare returns basicEPS and dilutedEPS together. otherIncomeExpenses splits out totalOtherIncome and totalOtherExpenses. fullFinancialReport bundles RevenueStruct, COGSStruct, OperatingExpensesStruct, OperatingIncomeStruct, EBITDAstruct, OtherIncomeExpensesStruct, NetIncomeStruct, and EPSstruct into a single FullFinancialsStruct, returning the whole report in one call.

Definitions of financial line items

The source defines each item as follows. Revenue is total income from product or service sales before expenses. COGS is the direct cost of production, including labor and materials. Operating Expenses are operating costs such as SG&A and R&D. Operating Income is revenue minus operating expenses. EBITDA is earnings before interest, taxes, depreciation, and amortization. Other Income and Expenses covers non-operating gains and losses such as interest or investment income. Net Income is profit after all expenses and taxes. EPS is the profit allocated per unit of the ERC-20 token. The netIncome method computes this by adding other income and expenses to operating income, then subtracting taxes and depreciation.

Verification duty when using external contracts

If the contract owner uses data or methods from other smart contracts they own that lie outside this standard's implementation contract, those contracts MUST be verified on the relevant blockchain explorer and MUST have publicly available source code. This requirement lets anyone inspect the code that financial figures originate from, underpinning the credibility of the disclosures. The Rationale also notes that the standard anticipates interacting with separate smart contracts within the same protocol to source financial information.

Proposal status: Review

This proposal is currently in Review status. It has not yet been finalized, and the specification may still change during review, so developers intending to implement it should check the latest state of the source.

Things to watch out for

Original ERC · ← ERCs