Open sche opened 2 years ago
Currently, we lack analytical on-chain data on:
Do we have "off-chain" data on e.g. which client was used to make an off-chain signature in our backend somewhere?
@tschubotz I tend to have NO answer, but @Uxio0 might know better.
We do not have such information in our services (and probably also don't want to, as this might be personal information which would potentially fall under gdpr). Only thing you could check if it was a mobile app, as you could cross check it with the data we have to push mobile devices.
Part 1: Define the problem
What problem are you trying to solve?
Currently, we lack analytical on-chain data on:
Having this data would help us understand our interfaces' role compared to other ecosystem participants.
What is your hypothesis?
Having a better understanding of our ecosystem will help us to evolve faster.
What value does this bring to our customer and/or our mission? What is the goal?
Bringing transparency to the ecosystem makes it stronger.
How do we measure it?
Not measurable.
Links:
// Include useful research, such as user tests, competitive analysis, metrics, or surveys.
Part 2: Shaping the problem
// Once the problem statement has passed the Great Filter, work with the team on the problem statement and elaborate on the following points to create more certainty around the problem and possible solutions. Make sure to identify dependencies and invite the necessary stakeholders early into the shaping process.
Problem Owner
// Who is responsible for leading the shaping process of this problem statement. Owner should be assigned directly after the Great Filter meeting. PM will assist.
Non Goal(s)
// Controlling the scope of solving the problem.
Solution
// At the end of the process, if possible, leave only the solution here that you want to be considered during the prioritization vote. Move all other solutions or ideas to Alternative solutions.