Defipulse

Defipulse compared DeFi protocols through capital and wallet activity

Defipulse compared decentralized finance protocols using deposited capital and activity recorded on the blockchain. Its total value locked metric tracked economically active deposits, while Growth Internals classified interacting wallet addresses. The DeFi List supported project discovery; the separate DeFi Pulse Index provided tokenized exposure. The original website now displays a domain-registration page.

Updated -

Asset balances and prices shaped capital comparisons

Eligible asset balances and valuation prices jointly determined a protocol's recorded capital total, so either input could change the comparison. TVL, short for total value locked, attached a value to qualifying assets held in protocol contracts. Deposits and withdrawals changed the balances, while repricing changed their valuation. A rising capital chart therefore needed interpretation beyond assuming new deposits explained the entire movement. The metric described the value of a stock of assets, rather than the amount traded during a period.

The historical TVL rules excluded flagged assets minted by the protocol or a closely related protocol. The illiquidity filter excluded assets when liquidity divided by fully diluted valuation was below 0.0015. These filters meant a contract balance and the capital included in a comparison could differ. Economically active deposits were the starting category, with additional eligibility conditions shaping the measured total.

A capital total did not count interacting addresses or measure the revenue a protocol earned.

Contract coverage connected protocols to their measurements

The protocol contracts included in tracking determined which balances and interactions entered each protocol comparison. In the adapter-based integration system, project-specific code fetched token balances for a timestamp and block. Adapters needed to support historical points as well as recent ones. Their maintainers needed to update the integration when a project changed its deployment.

A separate address-submission workflow asked projects for factory contracts, where applicable, and other on-chain addresses. A factory contract creates additional contracts, such as liquidity pools. The TVL methodology monitored these factories and included the new addresses they created. Asset eligibility filters still applied to the resulting balances.

Growth Internals separated monthly wallet patterns

Growth Internals grouped unique wallet addresses by qualifying interactions with a protocol during a calendar month and their earlier interaction history. A qualifying interaction meant a non-zero transaction directed to one of the protocol's contracts. The system indexed on-chain activity and used unique addresses as a proxy for users. Its categories described participation over time, with each label depending on the address's relationship to that particular protocol.

First interactions

New Users were addresses making their first qualifying interaction with the protocol during the measured month. An address could have a long blockchain history before entering this category.

Returning and resurrected activity

Returning Users interacted during both the measured month and the preceding month. Resurrected Users interacted during the measured month and an earlier month, with no interaction during the preceding month. This separated uninterrupted monthly participation from activity following a gap.

Lost activity

Lost Users had interacted during the preceding month and recorded no qualifying interaction during the measured month.

Capital and wallet activity described different kinds of traction

The same capital total could accompany different patterns of wallet participation, because balances and interaction histories measured different objects within a protocol. TVL described eligible deposited value. Monthly wallet segments described whether addresses started interacting, continued interacting or returned after a gap. These measurements could support different statements about adoption without producing a single universal ranking of project quality.

A wallet address also differs from a person. One person may control several addresses, and a shared address may represent several people. Automated activity can enter an address-based dataset when its transactions meet the interaction definition. A count of interacting addresses therefore remains a count of addresses, even when a chart uses the word users. Converting that count into a precise number of people would require information the interaction metric itself does not supply.

Retention comparisons needed the same observation window and contract scope on both sides. A lifetime address total and a monthly returning-address count described different populations. Changes in the tracked contract set could also introduce activity missing from an earlier dataset. Keeping the scope consistent made changes in participation more interpretable without treating every newly visible address as a newly acquired person.

The DeFi List provided a project discovery route

The DeFi List was the named project list used as an entry point in the platform's adapter-based listing process. That process required projects to enter the list before proceeding to adapter implementation and testing. A project entry and a working data integration served different purposes: the entry made the project discoverable, while the integration supplied measurements from its contracts. The listing alone did not produce a complete historical balance record.

Was the DeFi Pulse Index the same as the analytics platform?

The DeFi Pulse Index was a tokenized portfolio product, while the analytics platform measured capital and activity across protocols.

Protocol measurements

An analytics metric described protocol state or activity. Reading it did not create a holding in the protocols appearing in the comparison. The measurements supplied information about the tracked protocols, with their own units and coverage.

The index token

DPI was an ERC-20 token representing a selected portfolio of DeFi assets on Ethereum. Its index construction used token market capitalization based on circulating supply. That weighting method concerned the value of selected tokens, rather than the capital deposited in their associated protocols. Inclusion rules determined which assets qualified for the portfolio. Appearance in protocol analytics did not automatically establish inclusion in the index, and its composition was not a permanent list of every DeFi token.

Chain scope bounded each protocol comparison

The historical FAQ specified tracking only on Ethereum mainnet; the adapter documentation also described multichain integrations, including Polygon. A protocol name could encompass deployments beyond the contracts included in a dataset. Chain and contract scope therefore mattered when interpreting both a protocol total and a broader ecosystem total. Assets outside the tracked scope did not acquire coverage merely because they belonged to a similarly named deployment. A project's later expansion would not retrospectively extend an older chart's coverage.

Dataset coverage belonged to its period and version. This mattered when comparing projects with different deployments or combining records from different periods.

Global totals handled claims on shared collateral

When derivative assets represented underlying assets already counted in another tracked protocol, the global TVL calculation excluded those overlapping claims from the aggregate. The methodology identified debt tokens, liquidity-provider tokens and vault tokens for this treatment when their backing assets already contributed elsewhere. A protocol-level balance and its contribution to the sector total could therefore differ. Simply adding all protocol totals could count the same underlying capital through several claims.

Visual summary: Defipulse - Global totals handled claims on shared collateral
Global totals handled claims on shared collateral

View image file

Former website access and the legacy index

The original web entry now shows a domain-registration page, while the separate DPI product has legacy status following the end of regular rebalancing. In March 2024, Index Coop approved buying out Scalara's interest in DPI. Scalara, formerly Defipulse, had served as the product's methodologist.

Index Coop approved discontinuing DPI rebalancing in January 2025. Earlier rebalance schedules therefore describe the product's historical management, rather than ongoing portfolio maintenance. Existing holdings continued to represent exposure to the underlying components without the former regular adjustments.

Conditions for using a historical protocol comparison

A saved Defipulse comparison can support a conclusion when its observation period, contract coverage and measurement definitions match the reader's question.

  • For deposited capital, use the eligible assets and valuation basis belonging to the recorded snapshot.
  • For recurring participation, compare wallet segments over the same monthly window and tracked contracts.
  • For an ecosystem total, account for derivative claims backed by assets already counted elsewhere.
  • For coverage, keep the recorded chain scope separate from deployments outside the dataset.
  • For index exposure, distinguish the portfolio's component holdings and maintenance status from protocol capital figures.

A change in observation period or tracked contracts changes the question the original record can answer. Historical capital data cannot supply a current portfolio balance, and a legacy index holding cannot establish current analytics availability.

Common questions about Defipulse

Did a high Defipulse ranking certify a protocol's contract security?

A high capital ranking does not certify contract security. TVL measures eligible deposited value under its calculation rules, rather than the correctness of the contracts holding those assets. A security audit examines a different question, and a balance-based ranking cannot substitute for that examination.

Can an interacting wallet address identify the person controlling it?

A public wallet address does not inherently reveal its controller's real-world identity. Blockchain activity can expose transaction relationships, and separate information may connect an address to a person. Growth Internals classified interaction history; it did not turn its address counts into a verified register of personal identities.

How were calendar boundaries defined for Growth Internals?

Growth Internals used midnight UTC to define monthly boundaries. That cutoff determined whether a qualifying interaction belonged to the measured month or the preceding month. Local calendar dates can differ around the boundary, so interpreting the monthly labels through a different time zone can change their apparent meaning.

What information did an address-based project suggestion require?

The address-based submission process requested project details and the relevant on-chain contract addresses. Basic details included the project's name, website and Twitter handle. The contract information included factory contracts where applicable and non-factory addresses, helping identify the deployment the analytics would track.

Does a Lost Users label mean the address withdrew its deposits?

Lost Users meant an address interacted during the preceding month but had no qualifying interaction during the measured month. That label alone did not establish a withdrawal or an empty balance. Interaction history and deposited assets were separate measurements, so withdrawal claims needed balance or transaction information.

How often did the adapter-based TVL pipeline collect balances?

The legacy adapter-based TVL system specified hourly balance collection. Each run used a timestamp and block to retrieve balances for that point. Hourly snapshots could miss deposits or withdrawals between samples, so they described sampled balances rather than every movement throughout the period.

Can DPI holders redeem tokens after regular rebalancing ended?

The legacy discontinuation plan retained on-chain, in-kind redemption of DPI for its underlying components. In-kind redemption returns component assets rather than automatically converting the position into one chosen payment asset. Ending regular rebalancing changed portfolio maintenance and did not, by itself, erase the underlying component holdings.