9 March 2026
S
08:42
Storm (River)
5th formula bust coming soon.
🔥
D
B
BK
👍 1
10 March 2026
S
14:04
Storm (River)
Introduction to the problem. Thank you Winna for dealing with the issue. but let's explain so some people who are not aware of how these games work can understand.
🔥
C
U
3
L
14:05
This will be long so please be patient
14:13
After reverse engineering the implementation finding that it's using Pascal's weighted formula (not step path generation), I ran iterations over 1, 2, 5, and 20 million nonces. On paper, the math looked correct: the 5 million test generated 158 hits for the 1000x multiplier, which is right in line with theoretical expectations. However, when I manually cross referenced these results with Winna's. A portion of those 1000x hits were being downgraded to 130x. So I documented the 5 million test in an excel sheet to show the boundary shrink.
🔥
U
Doughboy joined group by link from Group
S
14:15
Storm (River)
This is a correct 1000x great, it matches the list I got. When I ran my own verifier
14:16
This hit the boundary where it gets moved to the segment "below"
14:16
Just an example (My excel sheet on the 5 million iteration test I manually verified highlights which hit below)
14:22
This discrepancy stems from combination of "boundary drift" and applying casino's edge directly to the boundary segments - as a result of using Pascal's formula to calculate 16 segments. While this may have started as a technical oversight rather than intentional malice, the result is what it is.

To fix this, Winna is doing the right thing to compensate players and will transition to the industry standard for Plinko which is step path generation. In the simplest terms: instead of one complex calculation for the whole drop, the game will generate 16 unique mini hashes(one for each row). This ensures every left and right turn is mathematically perfect, eliminating the "drift" and ensuring that a 1000x hit is never clipped again
🔥
C
F
U
14:24
I tested up to 100 million iterations and as you can see by this that I indeed did do tests on various numbers of iterations where regular variance smoothes out, but this wasn't an issue of variance.
S
14:24
Storm (River)
S
Storm (River) 10.03.2026 11:56:21
Proof of 100 million checked
S
14:25
Storm (River)
Proof of running tests.
14:25
The result.
S
14:25
Storm (River)
S
Storm (River) 10.03.2026 11:56:32
S
14:27
Storm (River)
By the way, this only happened at the 16 row high risk, the extreme was unaffected. So you all received your fair math value of 2000xs.
14:28
Proof that it never effected a 2000x.
11 March 2026
S
04:21
Storm (River)
Oh wait, no thank you to Paul, becuase he wasnt planning to refund his customers anyway. I had people approach me yesterday and give me their seed pairs to check what nonces of theirs got clipped. So I checked for someone and told him to go into his history and look at nonces 117525 and 67955 in your bet archive to see if those paid. And there it was, a 1000x rounded to a 130x and didn't pay on a 75 bet, he got a 1.9k refund. Paul justifies that this is ok, because they were meeting their 98% RTP. Plinko RTP isnt achieved by shrinking the mathematical boundary in the implementation they're using, it's achieved through pay out tables. But since they want to gaslight and assume everyone here is a retard, we can go step by step and explain and present the math, their confessions, the convos.
mt
04:24
On every audit they were hitting around 30-35% shrinkage on 1000x turning them into 130x on 5 million, 10 million, 20 million, 100 million. I manually verified all 5 million on their site with thousands of screenshots of mismatches. Then I ran it on 130x, went in to manually verify them and noticed a lot of them were being clipped to a 26x.
04:25
THEORETICAL (Standard Row 16)
Expected 1000x Hits: 152.5
Win Chance (Combined): 0.00305%
Individual Edge Chance: 0.001525%
Rarity: 1 in 32,768 nonces

ACTUAL (Site Results over 5 million iterations)
Observed 1000x Hits: 102 of the 158 that showed up. 56 became 130x
Win Chance (Combined): 0.00204%
Individual Edge Chance: 0.00102%
Rarity: 1 in 49,019 nonces
04:30
These are all in that drop link, I will post every screenshot I have of their verifier mismatching the fair math boundary of the edge segments under pascals 16 weighted formula. They turned a 0.0015% win chance into 0.0010 win chance. Mathematically, this means a player would have to grind roughly 16,000 extra nonces on average to hit the same 1000x result that would have occurred naturally had they respected the boundaries of their own implementation.
04:31
Then we can get into their past of fucking with results too, and move onto their keno as well. Noah Fischer will never stop conning :)
S
04:39
Storm (River)
P
Paul 11.03.2026 03:59:37
everyone got their refund and we made a statement on this - i appriciate your help but if you are claiming we are cheating you are not getting the bug bounty
04:39
Did you read our statement?
04:39
did we say visual glitch there once?
04:39
i said it to people to explain it easily that don’t understand PF as good as you man
S
04:39
Storm (River)
S
Storm (River) 11.03.2026 04:01:42
I asked you should I post my findings since you are sending out an email and PROPERLY refunding people you said you did. But hey i ran his seed
04:39
and i had two nonces where you had a boundary clip
04:39
nonce 117525, 67955. His bet on the 117525 was a 75 from what I know. It doesnt go the other way. The multiplier table you were using already has a 99% rtp. Ok so clipping the 1000xs took another ~1.058 at the 1000xs boundary. but the 130x boundary was clipped too. and so was the 26x less and less effect since those boundaries are larger than the 1000x
😐
SW
S
04:39
Storm (River)
P
Paul 11.03.2026 04:04:44
Look if we take away something from the 1000x boundary which we did and you pointed that out correctly, what happens with the float ranges we took away from the 1,000x boundary?
🤣
d
mt
S
04:39
Storm (River)
This is how he justifies clipping your 1000xs and underpaying you lmao.
😡
d
S
04:43
Storm (River)
S
Storm (River) 10.03.2026 10:31:52
yes but you are doing it at the multiplier that makes it even a useful game. We cant argue this. If you wanted lower rtp plinko then you coulda adjusted centre pay outs to be less
04:43
and then no one would bet because theyre better off anywhere but winna
04:43
You see this? This is 50 million nonce check, this is fair math value of 1000xs that show up under pascals 16 weighted segments. That looks good because theoretical total for 50 million is approx 1,525.88. Thats great, until I go ina nd verify these 1000x hits and see a good chunk usually anywhere around 30% were rounded to 130x. Due to your shrinkage you are applying for your rtp which is wrong.
04:43
This was for 5 million I personally verified
04:43
04:43
Ok so if I make a sheet for 50 million and manually verify which ones you guys clipped cuz of how you shrunk the boundary we'd get similar and I can do that for you right now
04:43
then there is a shave on 130x too there were 2411 that showed up in 5 million. I was only able to manually verify up to 1000 of them. and I noticed within those 1000 there were many that were turned to 26x. So its just a mess bro to do it like this
04:43
Check this 100 million nonce processed. 3027 fair math showed up. meets theoretical win chances of what should. for this many nonces.
04:43
But check this
04:43
I go in to look at what the first one is as per your verifer which is applying clipping to boundary
04:43
04:43
second too
04:43
Now I can go down that list and manually look at all 3000 to see how many got clipped
04:43
I also have a formula which can tell me. but Im doing it manually to show you look these were the ones that is fair math 1000x this is your clipping
04:43
Change setting to extreme it was truly indeed a 1000x there since 2000x and 1000x are in same boundary and should have been similar pay out. not kicked to the 130x segment
04:43
You see my point
S
04:43
Storm (River)
P
Paul 10.03.2026 11:24:11
In reply to this message
yes i get that but what was RTP here ?
S
04:43
Storm (River)
S
Storm (River) 10.03.2026 11:25:33
so Im trying to manually verify to show you. I can run it with the boundary shrinkage and itll just tell me all that were clipped without telling me all that showed up. but as you can see its already clipping so many and I just checked the first 30 of the 3027 in 100 million
04:43
3052 is theoretical that should hit for 100 million nonces. so 3027 is very good. hitting close to theoretical until yOU CHECK and realize your clipping shot them down to next boudnary so you wont have a total of 3027 even
04:43
In reply to this message
no one would agree to this. you should not be applying shrinkage on boundary itself. its already very small boundary under a weighted formula.
04:43
and I think your game dev understands this very well.
S
04:43
Storm (River)
P
Paul 10.03.2026 11:32:19
yes i understood it too and agree with it
S
04:43
Storm (River)
S
Storm (River) 10.03.2026 11:52:10
so Im running 100 million again but this time rather than manually show you which ones were clipped. Im running it so it gives me a total. Im just showing you manually so you see the proof of the clipping on your site. but i get roughly 30% boundary clipping on every iteration i run. 5 million, 10, 20. 50. Will tell you soon what I get here total.
S
04:43
Storm (River)
P
Paul 10.03.2026 11:53:13
In reply to this message
yess but what’s RTP on those pairs?
S
04:43
Storm (River)
S
Storm (River) 10.03.2026 11:56:21
Proof of 100 million checked
04:43
Here is result
04:43
😱
R
2
🥴
ke
r
😨 2
S
05:00
Storm (River)
In reply to this message
Paul justifies the "probability shave" by claiming they were simply "securing their 2% house edge." This is a fundamental betrayal of how Plinko math works. Unlike a linear RNG game like Dice, Plinko relies on a discrete binomial distribution where every mathematical boundary must be respected to reflect the theoretical win chance. They were already using a 99% RTP payout table. By applying a percentage shrinkage to every boundary they were clipping some 1000xs -> 130x, some 130xs into 26x, some 26s into 9x. They weren't just "getting their 2% edge" they were double dippng - taking the profit from the payout table plus the stolen equity from the clipped results.You were better off at any site that did an implementation to reflect its true win chances of those segments.
A
05:11
I have documented confessions from Paul and his teammates admitting they clipped the edge boundaries to "meet their house edge" This is absolute nonsense. No rational player would place a single bet knowing their 1000x hits were being covertly downgraded to 130x. Players are and were objectively better off on any other platform where a 99% RTP is respected through a transparent payout table and a true binomial distribution that actually pays out every fair 1000x result. Not applying a percentage shrinkage to ALREADY RARE boundaries. Lmao But I guess they think everyone is stupid enough to accept that.
💯
k
05:11
05:16
05:17
More confessions, and of course I am blocked because he isn't actually refunding the 1000xs that misfired because of his nefarious clipping and because he doesn't want to pay me for constantly doing his game devs work. AHEM DICE, KENO, PLINKO LMAO.
2 😭
ke
k
🔥 1 🤣
r
SR
05:27
SAINT Riverz
SR
SAINT Riverz 11.03.2026 00:42:00
This seed I checked it has none that were clipped there wsas one clipped at 104194 but you didnt get to that nonce you ended around 99k or osmething
05:27
client seed ce1c5115cb3649fc1ba20c94c8880cd8
05:27
server seed 34040a8010ec4c351f30d9276080e5e9
05:27
here are two places a 1000x clipped. rest paid as should
05:27
and I told you this is nonce 67955 and nonce 117525 so you just need to check if you have a bet on plinko here. the rest are accrate. I already ran the seed to check
SR
05:27
SAINT Riverz
E
Ecoguz27 11.03.2026 02:54:17
SR
05:27
SAINT Riverz
This nonce was in the 1000x boundary, I can provide the math where you can also see what boundary it was in. They clipped it to a 130x. I already knew it would be clipped to a 130x because I had to figure out the extra conditional they were applying to clip the boundary. So I told this guy to look at two particular nonces and baam. It was right there.
05:28
And if this user continued playing to 300k nonces. He would have gotten clipped another time at 246723.
S
06:43
Storm (River)
Is that the face of a man whose chin is retreating faster than his players bankrolls? This man needs to look into some looksmaxxing that recessed jaw, just like that recessed 1000x boundary. his devs successfully hardcoded a conditional to butcher some of your 1000x hits into 130x. It takes a special kind of confidence to rob his players then offer refunds less than 5% on what the actual pay out at its fair 1000x would have been for each players misfired bets had his site not clipped ~35% of 1000xs to 130x.
🤣
?
S
SW
7
😁 1 😱 1
Storm (River) pinned this message
S
10:09
Storm (River)
This is just plinko btw, they misfired on me personally on dice to the amount of 283k USD last year, they had to pay it in chunks) I caught it within 3 weeks. I have all conversations, admissions of fault, apologies on that as well. All convos with devs, they were rounding down dice multipliers too. We will post those too and establish a history of what they've been up to.. First paul needs to pay his entire site on this plinko issue, then we can go down his history. I will give a sneak peak though
🔥
O
b
mt
💯 1 🤣 1
10:13
Just take in the fact that in a few weeks they misfired on me for 283k. Just looked into my folder to go down memory lane. SO imagine what the damage they did on plinko where degens bet for those edge buckets (which they clipped like they clipped these 9900xs)
10:15
Memory Lane for you Mr Noah Fischer. Remember when you admitted to a 50% rtp hahahahah
10:19
Hey remember when your retarded devs tried to use stakes implementation for dice and then were rounding down the top tier pay outs? and thought you wouldnt get caught because your formula wasnt on your site. Then you were so broke you had to pay that out to me in chunks? Dont even think your hot wallet woulda had that 283k that month. You needed to scam others to pay me for my missed bets. Hes runnin a ponzi like he did on heybets and Gambling Apes NFT
b
🔥
O
10:32
With how many games you fucked up, you owe me your dev's salaries for all the work I did to help you correct two of your major games. And tbh we have some more. Heck, you owe your entire site. Only reason they got money in their hot wallets was because they scammed a few high rollers. So probably after yOU KNOW WHO lost a bit back, you had money to pay me in August and September. Probably we should check his dice bets and the downstream effect your clipping had on his wager at 2x even.
🔥
KN
k
TT
10:46
See they dont like giving bet archive, even last year they didnt, so I had to click through thousands of pages under —-> History, click below rotatated seeds you see your session. You cant click through all those pages if its for seeds since December 17, you get a rate request error. Thats because yesterday we found a 1000x on plinko that didnt pay, and clipped to a 130x instead (75k USD worth of misfire on singular 1000x that got clipped). So he's been throttling rate requests. So that I dont help his customers find more.
SR
20:29
SAINT Riverz
🤣
A
E
R
18
SAINT Riverz pinned this message
12 March 2026
SR
07:02
SAINT Riverz
Paul’s defense that he’s just securing a 2% edge (98% RTP, also a lie its lower) is a mathematical scam. In a provably fair game plinko, the house edge is realized through the payout table, not by reducing winning results. They used pascal's weighted formula versus step path generation and then clipped the boundaries by a percentage to clip some results. By clipping the boundaries, they’ve engineered a system where ~35% of all 1000x hits are downgraded to 130x.

Think about that, you have a 1 outta 3 chance of having your 1000x stolen after you’ve already beaten the 1/ 32,768 odds (WHICH ARE ALREADY RARE AND HARD ENOUGH). No player in their right mind would agree to these terms. If you have to spin 16,000 extra times on average just to get a fair payout, people woulda been better off at stake, shuffle, duel where they respect the fair win chances of a binomial distribution and don't clip.
SR
07:02
SAINT Riverz
S
Storm (River) 11.03.2026 04:25:27
THEORETICAL (Standard Row 16)
Expected 1000x Hits: 152.5
Win Chance (Combined): 0.00305%
Individual Edge Chance: 0.001525%
Rarity: 1 in 32,768 nonces

ACTUAL (Site Results over 5 million iterations)
Observed 1000x Hits: 102 of the 158 that showed up. 56 became 130x
Win Chance (Combined): 0.00204%
Individual Edge Chance: 0.00102%
Rarity: 1 in 49,019 nonces
07:02
S
Storm (River) 10.03.2026 10:36:49
07:02
S
Storm (River) 10.03.2026 11:56:32
SR
07:07
SAINT Riverz
It's offensive that PAUL even tries to defend this thinking people are stupid. Lol well I guess they are since no one checked until me. So he is getting away with the naivity, lack of curiosity of his platform. Honestly, Paul, if you’re going to scam people to the tune of ~ 35% of their 1000x, you better be putting that toward a top tier jawline reconstruction and chin implant. Because what you gonna do with all that money you stole if you still look like a mop headed lesbian.
🤣
?
A
E
10
🙉 1
SR
14:23
SAINT Riverz
SR
SAINT Riverz 12.03.2026 14:15:18
Some people are not understanding, so Im going to explain it again. The RTP argument is BS because plinko RTP is derived through the multipliers. Not the probability of a 1000x hitting. In a provably fair game, the "probability" is the physics of the gam. The "RTP" is just the price tag on the buckets.
14:23
14:23
here is a great example. this is duel they have 99.9% rtp. the win chance is still the theoretical 0.00152% this follows the binomial probability of how the pllinko math works. but its the multipliers they adjust for their edge. Now this is stake. 1000x win chance still 0.0015% despite 99% rtp.
14:23
SR
14:29
SAINT Riverz
Even if they used a weighted formula (not industry standard) instead of the usual Step Path (industry standard )regardless the math doesn't change. In any fair 16 row Plinko game, the edge probability is a fixed constant. Switching formulas isn't an excuse to shrink the boundaries— they took the weight of the edge segments and shrunk them from their binomial probability. It was a manuAL ADDITIONAL shave, not a "RTP CHOICE" TL;DR: They switched from "coin flips" to a "weighted ruler," but the size of the edge zone (in this example 1000x) is supposed to stay the exact same. Probably why they changed off the step path on Dec 17, because it allowed them to use a weighted formula and THEN add a manual clip to some of those profitable pay outs.
👍
O
14:33
You can post this to people and to him since he's using his garbage "HERP DERP MY 98% RTP, 2% HOUSE EDGE IS THE REASON WE HAD TO CLIP YOUR 1000XS as excuse to why he wont pay the full pay out of the 1000xs that hit. One guy has a 75k misfire, he gave him 1.9k saying "muh 98% rtp explains why i clipped your 1000x to 130x maybe you got more 2xs and 4xs" THATS WHY WE PAID YOU 1.9K even thought he bet that day woulda paid 75k had he not clipped that 1000x boundary. Those edge multipliers are what make plinko a potentially profitable game worth a bet. It's why the house doesnt fuck with the win chance of those at a proper casino. Or it's a fuckin useless game. Guess Winna was a bucket casino. TL;DR: WINNA SCAMMED ONE OF JIMMYS BIGGEST AFFILIATES/EARNER

ECOGUZ27 OF 75K AND THERE ARE OTHERS. MANY OTHERS.
M
2
❤‍🔥
S
🌭
P
14:44
🤣
k
?
13
👏 1 🤯 1 👋
S
13 March 2026
S
07:53
Storm (River)
Since Winna is refusing to pay out the 1000x hits they clipped, I built a public verifier so you can check your own seeds. (REPLIT IS A REPUTABLE SITE TO POST YOUR SCRIPTS AND BUILD A UI FOR YOU. SAFE TO CLICK) Note that they also shaved the 130x and 26x boundaries, but the impact is most brutal on the 1000X hits. Just input your client seed, and UNHASHED sercer seed (rotated seeds) and nonce range here to see what you're owed:👉 https://clipper-seed-checker--varvariance.replit.app/
_
MP
Storm (River) pinned this message
S
08:22
Storm (River)
Check your Winna archives after running your seeds through my public verifier starting from December 17—that’s when they swapped to the TWEAKED malicious Pascal 16 Weight implementation. If the verifier flags a clipped nonce, check your bet archive and if you had a bet on plinko at that nonce and what size and demand your payout from Paul.

Any mathematician or dev can verify this: they used a weight table based on Pascal’s Triangle and manually "shrunk" the edge boundaries.

I’ll be releasing the 130x clipper and a 15 row verifier soon. He’s "raining" fractions on the site with the money he already stole from you with formulas that wouldnt pass any RNG audit- he aint doing you any favours.
M