feat: Voting Power tracking for Saved Items in the Marketplace

[kevinszuchet]

---

layout: adr
adr: 231
title: Voting Power Tracking for Marketplace Saved Items
date: 2023-05-09
status: Idea
type: Standards Track
spdx-license: CC0-1.0
authors:

• kevinszuchet

---

Abstract

This document outlines the guidelines for counting the number of users who have saved an item in the Marketplace. The approach adopted is similar to the one used in Places for determining the highest-rated percentage of upvotes and downvotes from users with specific Voting Power. However, it has been adapted to meet the needs of the recently launched Marketplace Lists feature.

Context, Reach & Prioritization

Previously, users of the Decentraland Marketplace needed an option to save items for future reference, leading to missed opportunities for creators and potential customers. The Marketplace Lists feature was introduced to tackle this problem, enabling users to easily create and manage lists of items they plan to save for later and offering a gamified experience.

To improve accuracy and empower community members, a Voting Power criterion has been introduced for calculating the number of users who have saved an item in a list, ensuring a more precise count of saved items.

Solution Space Exploration

The strategy employed in Places has been adapted to the new feature requirements. When a new item is added to the list, the user's Voting Power (VP) is retrieved from the Snapshot platform and stored for future use. Then, the number of times an item has been added to a list only considers users with a specific VP.

One potential drawback of this method is that users may transfer their assets to a new account and re-add an item to the list with the same Voting Power, as it is only recorded once an item is added. As a result, this could cause the count for that item to be artificially inflated, as the same assets would be counted twice when retrieving the VP, resulting in an inaccurate count.

Specification

The guidelines mentioned above were introduced on May 4, 2023.

RFC 2119 and RFC 8174

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 and RFC 8174.