PolkaPulse: DeFi Dashboard for Polkadot Parachains

Small Spender
1mo ago
11 Comments
Rejected
Content
AI Summary
Reply
Up
Share
Request
78,000USDC
Status
Decision28d
Confirmation2d
Attempts
0
Tally
2.8%Aye
50.0%Threshold
97.2%Nay
Aye
1.21MDOT
Nay
42.5MDOT
  • 0.0%
  • 0.0%
  • 0.0%

Threshold

Support0.02%
327.18KDOT
Issuance
1.54BDOT
Votes
Nested
Flattened
Calls
Call
Metadata
Timeline4
Votes Bubble
Statistics
Comments

Update from AAG #206 Call on PolkaPulse Proposal

Hey everyone, sharing a quick update from today’s AAG call where we addressed two key questions and made clarifications to our proposal:

1️⃣ Web Traffic Data for Past Projects – We were asked about traffic data for our previous dashboards. For macro projects like the Arbitrum RWA Dashboard, we don’t own the URLs, as the data is delivered directly to the respective teams. Additionally, our dashboards are more specialized, focusing on niche analytics, so they naturally attract targeted users rather than mass traffic, unlike large aggregators like CoinMarketCap or DeFiLlama.

2️⃣ Inclusion of Hydration – During the AAG call, we mistakenly mentioned that our DeFi chain selection was based on advice from Parity—we want to clarify that this was not the case. After further review, we’ve decided to include Hydration in our proposal, alongside Acala, Moonbeam, and additional chains.

📌 Yield Opportunity Dashboard Update:
Users will be able to select a token (e.g., USDC/USDT) and compare yield opportunities across different parachains, including categories such as lending, borrowing, liquid staking, and liquidity provision (LP yield), with data available across various timeframes (1D, 1W, 1M, 1Y, 3Y, etc.).

We will update the proposal accordingly. Thanks to the community for the valuable feedback! 🚀

Reply
Up

Hey @vonyi,

Thanks for your reply both here and on the TG chat.

I understand your concerns about – the value, or lack thereof, of a DeFi dashboard, the prevalence of alternative data partners, and the fragmentation of data. Let me address them individually:

  1. Value of the dashboard: PolkaPulse is a set of two different dashboards. The first is a general overview dashboard of Polkadot's Parachains. This provides a single place for the community to compare parachains based on general metrics (like TVL, active users, volume, etc.) and a way for users to measure the health of a protocol with parachain-level metrics. The second is a DeFi yield opportunity dashboard to guide users about where to deploy their idle funds to earn passive yield.

We believe – PolkaPulse extends beyond a DeFi dashboard. Yes, it has a DeFi yield component and a general overview component.

  1. Data partners: Yes Polkadot has data partners – Dune, DeFillama, and TokenTerminal however, these either – provide chain level, not parachain level metrics (Dune), or do not integrate substrate data well (DeFillama), or help in distribution to Bloomberg, MarketVector and CoinbaseSMA (TokenTerminal) but does not focus on making insights actionable for Polkadot users.

Additionally, these platforms cover multiple chains with no dedicated branding, visibility, or tailored analytics for Polkadot. In contrast, PolkaPulse is designed to be ecosystem-first, bridging these gaps by integrating Substrate-specific data and surfacing insights in a way that benefits parachain teams and users directly.

  1. Fragmentation: We understand that the upcoming central smart contract chain could change the landscape of liquidity. If fragmentation remains, tracking liquidity movements and yield opportunities across parachains will be even more essential. To ensure accuracy + transparency, we will work directly with parachain teams to secure API endpoints, reducing data lag and maintaining transparency.

We want to build something the community truly finds valuable. What changes would you suggest that could make this proposal more aligned with your vision for Polkadot’s analytics ecosystem?

If there’s a way we can adjust our approach to gain your support, we’d love to explore that.

Reply
Up

Dear Proposer,

Thank you for your proposal. Our first vote on this proposal is NAY.

The Small Spender track requires 50% participation and simple majority of all voters according to our voting policy. This proposal has received two aye and six nay votes from ten members. Below is a summary of our members' comments:

In the recent referendum, opinions were divided on the proposal regarding dashboard integrations. Supporters appreciated the potential for discovering DeFi yield opportunities and valued community consultation. Conversely, several voters expressed concerns about the necessity of additional dashboards, citing existing resources and the risk of overwhelming the ecosystem. Some suggested that a proof of concept followed by retroactive funding might be a more effective approach. Ultimately, the proposal faced significant opposition, reflecting a desire for caution in expanding current offerings.

The full discussion can be found in our internal voting.

Kind regards,
Permanence DAO

Reply
Up
;