SAFE Token Utility Proposal

Thank you for the clear and strategic proposals @lakejynch! Both the integration queue and app market aim to solve for existing inefficiencies in the Safe ecosystem by building processes and rules that are open and implemented through code. Both proposals take a practical approach for SAFE token utility which seems like the right place to begin.

Then, after practical applications we can explore experimental use cases. Pro features for organizations and businesses is an interesting area to explore. It also aligns with the ethos of providing valuable public goods to individuals for free and adding value for orgs and businesses at a recurring price that is profitable to them.

Part 1 – Integration queue

Front-end integration proposals (FEIP)

  • The on-chain SafeDAO FEIP vote is a great way to move towards more decentralization of the app integration process.
  • As part of building this utility we should also define and outline the existing integration process with the help of the core Safe team to better understand areas to improve.
  • Reducing the workload of the core Safe team would be great. They won’t need to spend as much time and energy on prioritization given an effective DAO process.
  • The DAO could also own a larger part of the educational onboarding process in terms of educating potential apps on the technical requirements and governance process.

Prioritization

There will likely be apps that have a potentially higher impact to the ecosystem and would be beneficial to prioritize. The DAO vote could incorporate an element for prioritization.

  • I imagine the core team would be able to communicate a goal of integrating X apps per N time period.
  • The DAO would vote per each time period, “round”, similar to Gitcoin grants, on which apps to integrate and the prioritization.
  • Perhaps there is a way to balance an element of both first come first serve and prioritization.

Part 2 – App market

Building a marketplace around the Safe app is a big opportunity.

Organic vs paid

  • It’s important for us to think through how much of the app feed should be organic vs. paid.
  • I worked with mobile app developers while at Google to help apps optimize their Google ad spend. The Google Play store has a mix of mostly organic content with purchaseable ad spots. I don’t know what the current ratio is. Let’s call it 90/10 organic/paid.

Customization

  • There is a lot of potential for customization of recurring ad revenue.
  • The most expensive spots sold were the US YouTube mobile mastheads that show first thing when opening youtube.com or the mobile app with different ad placements and prices per country and day.
  • There could be an option to select different views of the app store.
    • "Curated”: Shows the organic apps derived through SafeDAO methodology and paid app spots.
    • “Custom”: User manually selects and saves apps to display in their app feed. Perhaps this is a paid feature paid in SAFE.

Analytics

  • There needs to be analytics within the Safe apps marketplace to prove the value of app placement for dapps.
  • Analytics need to be non-intrusive and open-source.
6 Likes