0 sats \ 2 replies \ @ek OP 24 Mar \ on: delphi.market Mega Thread #1 oracle
Unfortunately, I was only able to put up a 503 Service Unavailable page as a preparation for a full rewrite with cashu and more Golang, UX/UI experience etc. But I think I should be able to create MVPv2 within the next two weeks 👀
So new deadline is 2024-04-08.
I wrote down some more details about MVPv2:
1. Use 🐬 as mascot for delphi.market
- delphi sounds like dolphin (much more in German)
- dolphins are smart
- they live in water ("liquid markets")
2. Use cashu
- no need to track user balances in a database
- no tx fees for orders
- streamlined UX since onboarding can ask for a one-time deposit (see 4. Trading System)
- easy payout via push where receiver does not have to be online
3. Frontpage/Theme
- more inspiration from Metaculus and Manifold Markets like using charts
- active markets only (settled markets are hidden)
- use cashu color theme
4. Trading System
- onboarding: "What is your total budget for betting?" and mint corresponding amount of cashu tokens
- per market, you specify how sure you are and how much you want to bet
- there is only one order per market and user
- this should eliminate confusing UX around orders like big order books with multiple orders per user
- order form could simply be a slider for your current prediction and amount you want to bet
- if your prediction changes, just move the slider and your existing order is automatically updated
- if something happens that changes your prediction, you want to be able to update predictions as fast as possible
- precise changes with slider must be possible to make slider UX really good: use slider-in-slider on long press for small changes? (slider value can also be changed by simply typing a number into an input though)
- focus on partial settlement of orders
- how much you bet no longer matters to find a match: if you are 90% sure and someone else is 10% sure, you will match, even if you bet 900k sats and they bet 10 sats. (90 sats of your order will be marked as filled)
- shares and expiration prices are abstracted away during making predictions (= buying shares)
- users don't need to care about prediction market internals like buying and selling shares, only about their current prediction
- (internally, shares will expire at 0 or 100 sats)
- selling shares is for market exit / taking profits and considered to be an "advanced feature" from a UX perspective
More transparency for the subscribers to this post:
I talked with @k00b since my attention was split between SN and this self-inflicted deadline for delphi.market MVPv2.
We've decided that I will first finish a pressing chunk of work on wallet stuff and then I'll have two days off to focus on delphi. I think these two days off (+ weekend) are all I need to write the code for everything I thought about the past weeks months. If not, I will work on another SN chunk first.
So this means the deadline above is outdated now but I feel a lot of relief. Less pressure from multiple sides at once.
I almost want to set a new deadline or at least mention an ETA, but I won't. This feels like a bad habit where I pressure myself more and more in the hope I can get more and more stuff done until I crumble under the pressure and then do nothing, lol. I will simply get to this when I finished the aforementioned chunk of work.
reply
I predict that as excited as we all are for delphi, most of us are perfectly happy if delaying that means more SN improvements.
You're doing great work and we're all in your debt (to a limited non-legally binding degree).
reply