your biggest week ever came off one 0.06e ticket hitting a punk, so id put the effort there rather than into the average. a protocol owned listing whose backing grows from a small tithe on every pull. weight = 1/b means it gets rarer as it gets bigger, so it can sit there for weeks without wrecking anyone elses odds. and it gives the site a number that climbs all day, which is what people come back to look at.
its ev neutral, so you can test it without taking anything from depositors or the crown.
1. the demand model is where i think it breaks
your condition is built on an average. play in random-value markets tracks the spread of outcomes far more closely than the average. european roulette returns 97.3%, lotteries return about 50%, and the lottery sells more.
FWA's own history says the same thing. over the window i measured, reward value per pull fell 69% while pull count rose 32%. correlation between reward value and pulls = -0.735. negative.
and the biggest demand event in the protocol's life was one 0.06e ticket hitting a punk. a single draw out in the tail brought in more players than any parameter has.
so i would not expect 92 -> 97.6 to produce pulls. you left fun as an unmeasured residual and then optimized the measured terms. i think the elasticity lives in the residual.
2. the house is not well paid
measured depositor net yield is about +0.45% per cycle. TVL went 2800e -> ~1400e. that bloc is already leaving.
three of your four changes cut its income:
s 2.5 -> 1.5 scales the fee leg by 0.6
route 30 -> 20 scales the token leg by 0.667
crown 1.0 -> 0.25 removes the reason to hold one large position
depositor income = w1*s*V + w2*r*C*V. holding it flat needs V up roughly 50-67%. from 42 pulls/hr that is ~65/hr sustained. per (1) i do not think RTP buys that.
3. step 1 accelerates the junk spiral step 2 is meant to fix
fees split equally per position, so fee income scales with n. backing size never enters that term.
draw weight per position = 1/b, so splitting capital K into n positions gives total weight n*(n/K) = n^2/K.
income ~ n, draw exposure ~ n^2/K, and nothing in that objective prices asset quality.
this is already happening onchain. mean backing per position went 0.263 -> 0.240 -> 0.229e over ten days, positions 4548 -> 6101 with TVL flat. i logged five wallets adding 478 listings in three hours, median backing 0.055e, 41.6e total.
lowering s makes small positions relatively better, because the income term only counts how many you have.
4. two changes that are free in your framework
progressive jackpot listing: a protocol owned position whose backing grows from a tithe on every pull. weight = 1/b means it rate limits itself, the bigger it gets the rarer it hits. when pools ship, run one across all of them so every pull anywhere feeds the same number, otherwise n houses splitting ~200e/day makes every house look empty.
pity: n consecutive draws below some threshold gives an escalating rebate, funded from the puller leg you already want at 60%. it is EV neutral and only reshapes the distribution.
neither shows up in your model because the condition only has an average in it. i'd put most of the weight on the shape.
@Rhynotic@sterlingcrispin the one thing id change in fwair: let the backer match the bid before the spinner keeps the nft. as written you only end up with the piece when nobody else wanted it, which is backwards from what backing is being sold as. unless backers can just withdraw early, then ignore me
@token_works the one thing id change in fwair: let the backer match the bid before the spinner keeps the nft. as written you only end up with the piece when nobody else wanted it, which is backwards from what backing is being sold as. unless backers can just withdraw early, then ignore me
my list to enhance ethereum:0xa0df17b5ac76ababa36e1450e2cbcd18a620c845:
1. biggest one: a single progressive jackpot shared across all pools. small tithe on every spin grows it, every spin anywhere is a ticket, and inverse weight makes it rarer as it grows so it balances itself
2. gacha 101 thats missing: pity. a streak of brutal draws -> growing rebate. the purchaser buyback leg already pays spinners anyway, just tilt it toward the unlucky instead of splitting it evenly
3. drop pools are the easy yes, jack butcher already proved that rail works. id add a creator royalty on sellbacks so artists have a reason to pick this over a normal mint
4. on the no-eth idea: let me bring the nft and someone else post the eth behind it, we split the fees. the underwriter is basically setting a limit buy at 90% of backing. no-eth deposits without touching the pricing math
We're working on adding new pools to FWA.
Some requested features have been no ETH required to deposit, specific categories (Pokemon pool, NFT pool, Blue-chip pool), user-owned pools, new drop pools, defined withdrawal periods etc.
What do you want to see added to FWA?
@Rhynotic drop pools are the easy yes, jack butcher already proved that rail works. id add a creator royalty on sellbacks so artists have a reason to pick this over a normal mint
@Rhynotic let me bring the nft and someone else post the eth behind it, we split the fees. the underwriter is basically setting a limit buy at 90% of backing. no-eth deposits without touching the pricing math
@Rhynotic gacha 101 thats missing: pity. n bad draws in a row -> growing rebate. the purchaser buyback leg already pays spinners anyway, just tilt it toward the unlucky instead of splitting it evenly.
@Rhynotic biggest one imo: a protocol owned jackpot listing that grows from a small tithe on every spin. inverse weight self balances it, the bigger it gets the rarer it hits.