Jump to content

toohoola

Member
  • Content Count

    357
  • Joined


Reputation Activity

  1. Thanks
    toohoola got a reaction from Noeprellik1 in Guide to using the Primedice API   
    As far as I know, everything is possible via API, that you can do on the official site, since the site uses the API as well.
    Last time I checked this was the withdrawal mutation:
    mutation CreateWithdrawalMutation( $address: String!, $amount: Float!, $currency: CurrencyEnum!, $tfaToken: String, $oauthToken: String ) { createWithdrawal(currency: $currency, address: $address, amount: $amount, tfaToken: $tfaToken, oauthToken: $oauthToken) { id amount refFee currency hash address reference { ... on User { id balances { available { amount currency } vault { amount currency } } } } } }  
  2. Like
    toohoola got a reaction from Dan in Guide to using the Primedice API   
    For deposit address:
    query DepositAddress($currency: CurrencyEnum!) { info { currency(currency: $currency) { requiredConfirmations } } user { id depositAddress(currency: $currency) { id address currency } } }  
    To get the chat messages you have 2 options, either get the history manually with this, using the limit and the offset parameters:
    query PublicChats( $includeHistory: Boolean = false $limit: Int $offset: Int ) { publicChats { id name isPublic messageList(limit: $limit, offset:$offset) @include(if: $includeHistory) { ...MessageFragment } } } or you can use subscription to get them as soon as possible:
    subscription ChatSubscription($chatId: String!) { chatMessages(chatId: $chatId) { ...MessageFragment } } The MessageFragment is the same in both cases, don't forget to attach it to your query. I left it out to save some space:
    fragment MessageFragment on ChatMessage { id data { ... on ChatMessageDataRace { race { name status startTime leaderboard(limit: 10) { ...RacePositionFragment } } } ... on ChatMessageDataTrivia { status question answer currency amount winner { id name } } ... on ChatMessageDataText { message } ... on ChatMessageDataBot { message } ... on ChatMessageDataTip { tip { id amount currency sender: sendBy { id name } receiver: user { id name } } } ... on ChatMessageDataRain { rain { amount currency rainUsers { user { id name } } giver: user { id name } } } } createdAt user { id name } } fragment RacePositionFragment on RacePosition { position user { id name } wageredAmount payoutAmount currency }  
  3. Like
    toohoola reacted to Zoltan in [0.01 BTC] The long running giveaway (Test 2)   
    Congratulations to everyone especially to those who were being persistent and played till the end! I would like to thank you for participating and hereby send you the winners list, also some extra prizes, which will be explained. Whoever had only one bet will be added an extra 1k satoshi so i can tip them
    Username and prize in BTC:

    Bonuses for hitting the "round" numbers (BTC):

    Also special prizes for the top 5! (BTC):

     
    Prizes will be sent out in a bit in chat  Thank you!
  4. Haha
    toohoola got a reaction from GKD09 in [0.01 BTC] The long running giveaway (Test 2)   
    Bet: 33,190,892,315
    placed by toohoola on 20/07/2019
    Wagered
    0.00000000 Multiplier
    3.19x Profit
    0.00000000 69
  5. Thanks
    toohoola got a reaction from MiaMia in Guide to using the Primedice API   
    I don't really understand why does it have to be private, since pretty much all info available from sources, we just have to dig it out, but I respect your decision.
    You should also remove the API button from the footer in that case.
    Also I have to note your roll dice mutation returns your internal DB id and not the roll id. If someone wants to look up the roll id they have to use a separate query:
    query Betiid($betId: String!) { bet(betId: $betId) { id iid } } I needed the Tip mutation, so here it is for those who might need it and don't want to waste time opening the sources:
    mutation SendTipMutation( $userId: String! $amount: Float! $currency: CurrencyEnum! $isPublic: Boolean $chatId: String! ) { sendTip( userId: $userId amount: $amount currency: $currency isPublic: $isPublic chatId: $chatId ) { id amount currency user { id name } sendBy { id name balances { available { amount currency } } } } }  
  6. Like
    toohoola got a reaction from Dan in Guide to using the Primedice API   
    I don't really understand why does it have to be private, since pretty much all info available from sources, we just have to dig it out, but I respect your decision.
    You should also remove the API button from the footer in that case.
    Also I have to note your roll dice mutation returns your internal DB id and not the roll id. If someone wants to look up the roll id they have to use a separate query:
    query Betiid($betId: String!) { bet(betId: $betId) { id iid } } I needed the Tip mutation, so here it is for those who might need it and don't want to waste time opening the sources:
    mutation SendTipMutation( $userId: String! $amount: Float! $currency: CurrencyEnum! $isPublic: Boolean $chatId: String! ) { sendTip( userId: $userId amount: $amount currency: $currency isPublic: $isPublic chatId: $chatId ) { id amount currency user { id name } sendBy { id name balances { available { amount currency } } } } }  
  7. Confused
    toohoola got a reaction from Landak in [0.01 BTC] The long running giveaway (Test 2)   
    .
  8. Haha
    toohoola got a reaction from Owly in [0.01 BTC] The long running giveaway (Test 2)   
    32187519458
    I wasn't fast enough.
  9. Haha
    toohoola got a reaction from alexandre12 in [0.01 BTC] The long running giveaway (Test 2)   
    I'm aware of the rules, hence why I said 'too bad it does not count'
  10. Haha
    toohoola got a reaction from pedrojmelo in [0.01 BTC] The long running giveaway (Test 2)   
    I'm aware of the rules, hence why I said 'too bad it does not count'
  11. Confused
    toohoola got a reaction from kouki in 35 players team up for 1 BTC from 1000 Satoshi   
    Why do you need different players for this and why don't you do it yourself with alts?
  12. Like
    toohoola got a reaction from Bojana in Can't bet exactly 0.00000012   
    I was wondering why did I get that, now I know. Thank you!
    No @Ssociety, I'm just a regular player like most of the users on the site, except I'm interested in coding, fixing bugs and reporting them with at least one solution.
  13. Thanks
    toohoola reacted to Bojana in Can't bet exactly 0.00000012   
    @toohoola, just a small token of appreciation  Keep up with the good work!


  14. Like
    toohoola got a reaction from PARANORMAL in 🏆 [0.08 BTC] The Master Detective Challenge!   
    Bet: 22,726,326,140
    placed by toohoola on 19/06/2018
    Wagered
    0.00001200 Multiplier
    2.00x Profit
    0.00001200 Bet: 22,726,325,998
    placed by toohoola on 19/06/2018
    Wagered
    0.00001200 Multiplier
    2.00x Profit
    0.00001200 Bet: 22,726,325,895
    placed by toohoola on 19/06/2018
    Wagered
    0.00001200 Multiplier
    2.00x Profit
    0.00001200 Bet: 22,726,325,792
    placed by toohoola on 19/06/2018
    Wagered
    0.00001200 Multiplier
    2.00x Profit
    0.00001200 Bet: 22,726,325,705
    placed by toohoola on 19/06/2018
    Wagered
    0.00001200 Multiplier
    2.00x Profit
    0.00001200 Bet: 22,726,325,614
    placed by toohoola on 19/06/2018
    Wagered
    0.00001200 Multiplier
    2.00x Profit
    0.00001200
  15. Like
    toohoola got a reaction from baronn007 in 🏆 [0.08 BTC] The Master Detective Challenge!   
    Bet: 22,726,326,140
    placed by toohoola on 19/06/2018
    Wagered
    0.00001200 Multiplier
    2.00x Profit
    0.00001200 Bet: 22,726,325,998
    placed by toohoola on 19/06/2018
    Wagered
    0.00001200 Multiplier
    2.00x Profit
    0.00001200 Bet: 22,726,325,895
    placed by toohoola on 19/06/2018
    Wagered
    0.00001200 Multiplier
    2.00x Profit
    0.00001200 Bet: 22,726,325,792
    placed by toohoola on 19/06/2018
    Wagered
    0.00001200 Multiplier
    2.00x Profit
    0.00001200 Bet: 22,726,325,705
    placed by toohoola on 19/06/2018
    Wagered
    0.00001200 Multiplier
    2.00x Profit
    0.00001200 Bet: 22,726,325,614
    placed by toohoola on 19/06/2018
    Wagered
    0.00001200 Multiplier
    2.00x Profit
    0.00001200
  16. Thanks
    toohoola reacted to Marija in 🏆 [0.08 BTC] Extravagant Swing Challenge!   
    Thank you for participating, guys! 
    This giveaway has been paid.
    Congratulations and good luck!🍀
  17. Like
    toohoola got a reaction from Dan in PD5 GraphQL new API   
    Why do you use the authorization field? You have to send it via the x-access-token field, just like your browser does.
    No, you should not encrypt it nor hash it. As long as you use HTTPS, you should be fine.
  18. Like
    toohoola got a reaction from PARANORMAL in 🏆 [0.08 BTC] Bingo Challenge!   
    Bet: 22,132,761,480
    placed by toohoola on 18/04/2018
    Wagered
    0.00000082 Multiplier
    2.23x Profit
    0.00000101 Bet: 22,132,784,281
    placed by toohoola on 18/04/2018
    Wagered
    0.00000082 Multiplier
    2.23x Profit
    0.00000101 Bet: 22,132,806,851
    placed by toohoola on 18/04/2018
    Wagered
    0.00000051 Multiplier
    2.97x Profit
    0.00000100
  19. Like
    toohoola got a reaction from PARANORMAL in 🏆 [0.08 BTC] Roller Coaster Challenge   
    22,109,423,082 placed by toohoola on 4/12/2018 Wagered: 0.00000100 Multiplier: 1.01x Profit: 0.00000001 22,109,422,831 placed by toohoola on 4/12/2018 Wagered: 0.00000100 Multiplier: 1.01x Profit: 0.00000001 22,109,422,779 placed by toohoola on 4/12/2018 Wagered: 0.00000100 Multiplier: 1.01x Profit: 0.00000001 22,109,422,625 placed by toohoola on 4/12/2018 Wagered: 0.00000100 Multiplier: 1.01x Profit: 0.00000001 22,109,422,590 placed by toohoola on 4/12/2018 Wagered: 0.00000100 Multiplier: 1.01x Profit: 0.00000001
  20. Upvote
    toohoola got a reaction from kivi489 in 0.01 BTC from faucet in 3 rolls!   
    It's not that hard, especially if your faucet is 2485 sat. It's like reaching 40k from 100.
  21. Upvote
    toohoola got a reaction from Kargai in Bug with the "Ignore list" in chat?   
    Yes, he means that.
    If you like nerdy things:
    The ignore list is saved locally (on client side, to your browser, via localStorage), when you log out it is erased. When you log in again, your browser have no idea about the list and since it's saved only locally, it can't ask the server for it. You can't do much about it, but to report it and hope for a fix in the near future. Or if you are into programming, you can develop a browser extension to save the ignore list into the extension's database, so you can save the list between sessions, but that's too much of a hassle if you ask me.
    There is a similar issue with the bets. If you bet some, you can check your latest bets under the My bets tab, but after you log out and you log in again, the list is empty. That's because the bets are saved the same way as the ignore list. However, the API has a GET mybets method to get the last couple of your own bets, but it returns an empty array. I might be wrong, but they might coded the client side to just return the last bets from the locally saved data instead of getting it from the server, or I might be wrong and they don't use this API on client side at all which would make sense.
  22. Upvote
    toohoola got a reaction from Carollzinha in Hit the Number!   
    Bet:17922339947

  23. Downvote
    toohoola reacted to gwapoman in faucet win   
    maybe..
    can you show some of your recent deposits and how much wagered you already made in pd?
    First of all my account is a vip and we are the one who suffered most about the faucet low down.
    Think first dude.??
     


  24. Upvote
    toohoola reacted to Memek in Setting the correct multiplier on PD   
    What everyone needs to be aware of is that, you bet on win chance, not payout. The payout is calculated base on the win chance.
    Unfortunately, the PD web page have a serious visual bug which gives the impression that you can bet on non existing payout.
    You can bet on any win chance from 0.01% all the way to 98%. Lets see how it works.
    Payout can be calculated from win chance by using this formula :
    Payout = ( 100% - House Edge % ) / Win Chance % Since PD have a 1% house edge the formula can be simplified to :
    Payout = 99% / Win Chance % Some sample results :
     
    0.01% = 9900x 0.02% = 4950x 0.03% = 3300x 0.04% = 2475x 0.05% = 1980x Payouts in between any of the above values don't exist. For example, 8000x, 6600x, 3000x etc don't exist.
    Unfortunately, the PD website allows you to choose these payouts. If you make a bet on these non existing payout, it will choose the nearest existing payout. You can verify this by checking your bet ID.
    PD should fix this visual bug to prevent misunderstanding.
     
     
     
  25. Upvote
    toohoola got a reaction from bloomy in Giveaway! *Roll Hunt*   
    Here is mine: 17862191248
    PD: toohoola
×