There was a problem operating a batch job which synched paper crypto positions between two internal databases. As A Result Of it didn\u2019t run, none of the positions obtained transferred so it seemed like they disappeared from paper accounts. This is being addressed and should be mounted for tomorrow\u2019s positions. Again apologies and thanks for reporting this. There is currently an issue with the P&L and the fee basis reported for crypto that are being resolved. Crypto trades incur a \u2018spread markup\u2019 of .1%.<\/p>\n
This course of started taking an extremely long time to finish. At the time, the order issue was thought to be associated, however it turned out to be something easy and unrelated. I definitely love how Alpaca works in reside crypto buying and selling. However broken paper is a important blocker for me before investing more money into my bot.<\/p>\n
I wrote a bot which buys and sells crypto, it solely sells when there’s a 2% achieve in profit from when it was originally purchased. When these trades happen the Alpaca dashboard does indeed say the commerce was bought at a higher price than when it was bought. However, the total equity quantity on the paper buying and selling account truly loses money.<\/p>\n
<\/p>\n
What this implies is that if one is buying and the present ask value of $1000 then Alpaca will charge, or debit the account for a thousand x 1.001 or $1001. The cost foundation and P&L are presently incorrectly being reported as that quote value (eg $1000 within the above example) and never the actual executed value price (eg $1001 in the above example). The account fairness accurately uses the executed prices.<\/p>\n