Topic: ⎛🌟🔴🌟🎲🌟🔴🌟MONEYPOT.com -- Crypto Casino Suite and Web Wallet 🌟🔴🌟🎲🌟🔴🌟 - page 3. (Read 30129 times)

In absolutely no way am I impressed with the way you guys rolled out v2 or how you prepared current app owners to be ready to have their apps able to run on it. Total BS. I'll continue to support the app I have from the beginning via their doge betting option but I am 100% done with Moneypot.com.

Tips have been enabled. See https://bitcointalksearch.org/topic/m.21557119

Excited for this.... CoinPro.fit will support multiple alt-coins and be fully ready for V2 when it goes live!

can not connect to bit-exo

The investment page is currently disabled. If you need stats or want to divest, please contact one of us to assist.

After long time, I login into new site.

Where do I find my investment details?

thanks

Yes, this might be a great update but what I want to see is about their rbies. Last time they said their rbies going to be implemented but until now there has been nothing since last update. So whether this rbies got to be implemented, please give some answers to us. I believe some of us are holding rbies for their own good

can't wait till v2 goes live. i know one big surprise coming and can't wait to talk about it when it goes live.


Congrats MP

It is safe to deposit. The depositor in use was completely rewritten and tested significantly. It has actually been in use for some time on version 1.

The invest page is currently offline until we bring up the rest of the api. If you would like to divest, let one of the team members know and we will get you settled.

New site interface looks awesome to me, good job with it.

A couple of questions:

 - Is it safe to deposit now ( I mean deposit process is already copleted and tested)?
 - Cannot find investiment option anymore. Am I just missing it or it has not to be implrmented?

ATTENTION APP OWNERS

THIS POST WILL SERVE AS A QUICK REFERENCE UNTIL A FORMAL API DOCUMENT IS CREATED

Below is the v2 auth configuration. Adapting to these changes should allow you to authenticate users into your app for chat etc while other routes are being tested / implemented. We do not have api docs on hand at the moment. Please refer to the migration guide for other changes.

For those who are curious, we removed some of the bloat on some api calls to streamline them as we add additional fields in the api responses. While a separate call may be needed, it allows us to adapt while keeping a function specific to its design.

Take for instance the following routes:

Proper use of login auth
User Login -> Verify Token (/v2/token) -> Get Auth (/v2/auth)

With confidential applications, you can verify a token and then tie the auth information to a secure session internal to your application.

Current Enabled Functionality
Token
Auth
Tips
Hashes
Bets (Except Plinko)


Current Disabled Functionality
Buckets
Stats
Bankroll
Dialogs
Address Generation


IMPORTANT NOTES
'hash' was deprecated in 1.5 and has been replaced with 'bet_hash'

We have modified our provably fair algorithm to support hashed seeds and client seeds as strings. (See migration guide)

serverSeed = sha256()
salt = sha256()

hash = sha256(serverSeed + salt)

clientSeed = "string"

result = sha256(serverSeed + clientSeed)

PHP outcome

JavaScript outcome
(cryptocoinjs/sha256)


Generate Hash -> Reduce to 8 characters -> Convert to Integer from base 16 (0 - 2^32)
__________________________________________

GET /v2/auth

______________
Paramaters
______________
Confidential:
   ?auth_id=INT&app_secret=UUID
   
Implicit:
   ?access_token=UUID

______________
Response - 200
______________
{
    "auth_id": 0,
    "app_id": 0,
    "user": {
        "uname": "user",
        "role": "role",
      "balances": {
          "btc": 0,
          "ltc": 0,
          "dash": 0
      },
      "unconfirmed": {
          "btc": 0,
          "ltc": 0,
          "dash": 0
      }
    }
}
__________________________________________


GET /v2/token

______________
Paramaters
______________
Confidential:
   ?confidential_token=UUID&app_secret=UUID
   ?access_token=UUID&app_secret=UUID
   
Implicit:
   ?access_token=UUID

______________
Response - 200
______________
{
    "token": "uuid",
    "expires_in": 0,
    "expires_at": "1970-01-01T01:00:00.000Z",
    "kind": "token",
    "auth_id": 0,
    "app_id": 0
}
__________________________________________

GET /v2/bankroll

______________
Paramaters
______________
Confidential:
   []
   
Implicit:
   []

______________
Response - 200
______________
{
    "btc": {
        "balance": 32218539609,
        "invested": 32218554363,
        "wagered": 9972019158897
    },
    "ltc": {
        "balance": 0,
        "invested": 0,
        "wagered": 0
    },
    "dash": {
        "balance": 0,
        "invested": 0,
        "wagered": 0
    }
}
__________________________________________


POST /v2/tip

______________
Paramaters
______________
Confidential:
   ?auth_id=INT&app_secret=UUID
   
Implicit:
   ?access_token=UUID

______________
Request
______________
{
  "amount": int,
  "coin": "coin`", //not required, defaults to btc
  "uname": "uname"
}

___________
Response - 200
______________
{
    "id": int,
    "from": "uname",
    "to": "uname",
    "amount": int,
    "coin": "coin",
    "created_at": "1970-01-01T01:00:00.000Z"
}
__________________________________________


POST /v2/hashes

______________
Paramaters
______________
Confidential:
   ?auth_id=INT&app_secret=UUID
   
Implicit:
   ?access_token=UUID

______________
Request
______________
{}

___________
Response - 200
______________
{
    "bet_hash": "sha256"
}
__________________________________________


POST /v2/bets/*


______________
Paramaters
______________
Confidential:
   ?auth_id=INT&app_secret=UUID
   
Implicit:
   ?access_token=UUID

______________
Request
______________
coin = btc || ltc || dash
bet_hash previously hash

___________
Response - 200
______________

Nothing Changed Here
__________________________________________

same for me with bit-exo, and betterbets to dsnt works!
so its moneypot maintenance issues.

The app improperly configured error is set because  we are enforcing specific guidelines on the login request. I have removed the requirement for a temporary duration until API is live and app owners update their apps to comply.

API will be up asap (wanted wallet up so people can see the new design, get acquainted with it, etc.). You still have access to funds through the MP site (visit the app there -> withdraw/deposit) even without access to log into the apps.

so is it done or what ?? I can access the new platform but things seem not working fine
like I'm trying to login to bitexo but I'm getting App improperly configured. Invalid Response Type , so IDK what that is

is that happening with all the users and in all apps or just exo ?? cause most of my bitcoins are in exo atm

hello there, I want to know when maintenance will be over, and all will be 100% completed and when I will can play dice on bit-exo and betterbets?

 Don't rush it man, we have time, we can wait. I am super excited about the new wallet system, its gonna be freaking awesome

Good work! 

Like/retweet: https://twitter.com/hyipexa/status/905017256459063297

- Luis.

hi geras

why do you think V2 will attract more players and investors? everyone is welcome to answer

best of luck wherever you put your coins

hope that because with BK launch and the low traffic on MP they need a big new like this to bring again players here