Statements

You can request an update on the status of your account by calling either STAT or STATJSON. STAT returns a “human-readable” copy of the data in STATJSON.

To request an account statement in JSON format, clearsign and encrypt to MPEx the following: STATJSON

To request the human-readable statement, clearsign and encrypt to MPEx the following: STAT

A statement (STAT or STATJSON) contains the following data:

- Header
- Holdings
- Book
- Options Cover
- IMM Cover
- Trade History
- Dividends
- Exercises

In case of STATJSON, each section in the Statement response contains the md5 hash of that section, mostly useful to be able to quickly detect changes.

“Header” contains the name of the MPEx account that requested the STAT, the fingerprint of the key associated with that account, a human-readable date at which the STAT was received and the Unix microtime equivalent of the same.

“Holdings” refers to all assets that an account owns. By MPSIC naming scheme, options, stocks and futures are differentiated by a leading O, S and X on their trading symbols respectively. An option would look like O.USD.C125T, a stock like S.BBET and a future like X.IDIFF.DEC. The “Holdings” key in the JSON dict returns a list of other dicts each containing a trading symbol and a number representing the shares of that asset the account holds. The quantity of Bitcoins on deposit with MPEx is called out in satoshis, and indicated in the “Holdings” entry of the Statement as CxBTC.

“Book” contains numeric keys that reference your order numbers, indicate the MPSIC for a given order, the quantity, purchase- or sell-side nature of the order, and the price asked or bid for the securities in question. This is the entry in the response for STATJSON you’d examine immediately after placing an order to get the order number.

“OptionsCover” refers to capital from an MPEx user’s account that has been reserved as collateral for puts and calls the user has written.

“IMMCover” refers to capital from an MPEx user’s account that has been reserved as collateral for futures the user has written.

“TradeHistory” will show all trades made on a user’s account since one hour before the last STAT call a user submitted, or the last month of trades if STAT has not been called.

“Dividends” will show the dividends paid to an account as a result of holding a dividend-paying stock at the moment of dividend payment. There is no cutoff for dividends: anyone holding shares during a dividend payment will receive dividends proportionately to the number of shares held. Only new dividends since the last requested statement will appear in this section, or the last month of dividends if STAT has not been called recently.

“Exercises” will indicate if the writer of a put or a call has been exercised automatically by MPEx on option expiry date. It is not showing exercises requested by user himself. Each entry in Exercises will call out:

  • MPSIC: the option contract that was exercised
  • Quantity: the number of contracts exercised
  • TotalValue: the amount of capital withdrawn from OptionsCover, collateral on reserve for options.

Asset/BTC transfers

MPEx allows users to push assets and Bitcoins from one account to another. Transferring assets in this way requires knowing the fingerprint for the key associated with the account in question, but the transferral process does not check to see if the key-id has an account on MPEx (to preserve user privacy).

Example:

PUSH|S.BBET|500000|BBB0A99950037551F533850A677ABD62D0AEE7D7

This will push 500000 shares of BitBet to an account (if one exists) associated with the key at the end of the above command.

PUSH|CxBTC|100000000|BBB0A99950037551F533850A677ABD62D0AEE7D7

This will push 1 BTC to the key above.

Transfers aren't showing anywhere in sender nor recipient's account statement, except for sudden change of balance. This is one consequence of MPEx's design philosophy YKWYD (You Know What You Did).