Pages:
Author

Topic: MagicalDice - Need beta testing [Bounty for bugs] (Read 2971 times)

full member
Activity: 143
Merit: 100
LET'S MINING, EARN & LIVE WITH IT. JOIN ME
username:
Zakorus. i hope to find some bugs Cheesy

I have found 1 bug (reported to Stars) but never given any particular "bounty" yet.! poor me

-KOZO-
full member
Activity: 143
Merit: 100
LET'S MINING, EARN & LIVE WITH IT. JOIN ME
I appreciate everybody that has found bugs/actively looking for bugs. You will be paid a bounty once our dev has fixed the bug(s). Thanks Smiley

yeah, Stars, you never pay me any particular bounty yet as I sent to you the error (or bug) (whatever you call it) thru' a link(screenshot) in the chat i've reported to you the other day and i still have it in store. Are you really on your word? but still waiting for it(the bounty)until i got it anyway tyvm in advance.

-KOZO-

p.s. please remember me. c ya around sometimes. magicaldice is owesome..!
sr. member
Activity: 336
Merit: 254
CEO of Privex Inc. (www.privex.io)
I found this in chat box


That was a temporary issue while we were correcting some database settings. Shouldn't happen any more.


when setting an email in account details:


I'll look into that
sr. member
Activity: 476
Merit: 500
Re-Evolution
I found this in chat box

legendary
Activity: 1876
Merit: 1295
DiceSites.com owner
I think the "start screen" has a username min. limit of 4 characters and the "name change sceen" has a min. limit of 5 characters.
sr. member
Activity: 476
Merit: 500
Re-Evolution

when setting an email in account details:



What's going on there?
I have setting my email and it's good running well
newbie
Activity: 9
Merit: 0

when setting an email in account details:

https://i.imgur.com/yX6XCyv.png
sr. member
Activity: 462
Merit: 250
We'll be live within 30 minutes! Make sure you're around, lots of giveaways within the first few hours!
legendary
Activity: 997
Merit: 1002
Gamdom.com
gonna go live soon, we also cant wait ourselfs to finally launch!
hero member
Activity: 736
Merit: 500
username:
Zakorus. i hope to find some bugs Cheesy
newbie
Activity: 9
Merit: 0
at the time of my original faucet-exploit post the 3-minute static timer was not operating.
sr. member
Activity: 420
Merit: 250
I already can not wait for this dice
username magicaldice: septianuciha  Kiss  Kiss  Kiss
I will wait for his birth magicaldice
newbie
Activity: 16
Merit: 0
Hey Kuz here with another update. Testing the autopilot system again this morning I seemed to have found another bug, very minor but yea.

With Autopilot if you was to reach the max bet limit during a single run, the max bet limit popup won't display and autopilot would continue to run performing no bets. As you can see in the screenshot below, I set my autopilot to a basebet of 0.1 and lost all the way to 1.6; i can't perform a 3.2 BTC bet as it exceeds the max bet limit of 5 BTC, so in reality I should be getting the max bet limit popup error... but I don't:

https://i.imgur.com/DraYaMM.png


[FIXED BY SOMEGUY123]
sr. member
Activity: 336
Merit: 254
CEO of Privex Inc. (www.privex.io)
Hey Lyco. I'm not sure how your "exploit" is a problem. I just checked, and most other BTC dice site's with a faucet, including PrimeDice, and Rollin.io, uses the exact same captcha, and similar static timer. You can't make another claim within 3 minutes of the previous.

If it's so easy to turn 0.00000500 into 0.049, then why do you need to abuse the faucet anyway? From that 0.049 you could make close to 10,000 500 whole satoshi bets.

I could understand if it was bet>instant claim>bet repeat etc. but you can't do that, you have to wait 3 minutes before you can claim again.
hero member
Activity: 490
Merit: 500
~ScapeGoat~
We will be launching in roughly 24h from now!

Will bounty be distributed for bugs before launch or after launch.
On behalf of all Bug finders i request you to mention the names of the guys who found bugs in OP as your list there is still blank.

Good Luck for the Launch , hope to enjoy. Tongue

sr. member
Activity: 462
Merit: 250
We will be launching in roughly 24h from now!
hero member
Activity: 994
Merit: 500
Hit me up when i have time i will check if there is any bug in your website, i would be happy to find one
newbie
Activity: 35
Merit: 0
how long again launcing ?
newbie
Activity: 16
Merit: 0
@lyco yes I believe so to, that issue has something to do with connectivity as it occurred on a lag. After getting that issue popping up it's been difficult to make it arise again. Smiley
newbie
Activity: 9
Merit: 0
Hey, I am liking this website - seems pretty stable. When testing it this morning I only came across 2 bugs which need to be fixed:

1. Max bet limit [FIXED BY KALE]

When betting through the website the max accumulated profit is 5 BTC if you put the wager and profit together. For example, if you try betting over 2.5 BTC on the x2 multiplier you get this error:

https://i.imgur.com/SNOR7mr.png

However when I dug deeper into the code, I noticed this check was being done client sided in both of the roll button event handlers.
So what I did instead was made a PHP script which contacted the server directly to make the bet, where the wager itself was over 5 BTC. This ended up going through successfully:

https://i.imgur.com/GwBTkIj.png



2. Autopilot Bug

When testing out the increment feature on autopilot I noticed another unusual occurrence. I set the start bet to 0.01 BTC and on loss told it to increase by 100%; after a few runs on this setting, I noticed autopilot bet the same amount on win twice after it lost the initial 0.01 bet. (Autopilot also lagged a couple of times, which may of caused this to happen)

https://i.imgur.com/MTSzTxs.png


That's all from me Smiley
 


clap clap! that php impostor-script exploit is brilliant.

by the by, re issue #2: earlier today another user tried automated betting, and the option to reset to base after a win was defective, betting and losing double once after a win before then resetting to base as the user programmed it to do. i haven't been able to clone that event or any of the other autobet errors, which leads me to believe they're based on latency issues.
Pages:
Jump to: