Skip to content

Trace API Enhancements #118

@stephenpdiesel

Description

@stephenpdiesel

See #109

Problem

Opportunity: What are the needs of our target user groups?

Ability to set up a history solution with lesser complexity and overhead that solutions such as SHiP or Deepmind.

Target audience: Who is the target audience and why?

Strategic alignment: How does this problem align with our core strategic pillars?

Blockchain made easy - simpler history solutioning for developers.

Context

Competitors: Who are our top competitors (up to 5) and why? How do they solve this problem today?

Product differentiation: what would make our solution different?

Audience definition

Solution

Solution name: How should we refer to this product opportunity?

Trace API Enhancements

Purpose: Define the product’s purpose briefly

To make the previously delivered solution, Trace API, to be more general purpose for utility outside of just exchanges and specifically tailored to developer use cases.

Success definition: What are the top metrics for the product (up to 5) to define success?

Assumptions

Risks: What risks should be considered? https://www.svpg.com/four-big-risks/

Business Objectives/Functionality

Features/Epics

User stories

Additional tasks

  • [ ]

Timeline

Cost

Open questions

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    🪨 Opportunity

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions