60 sec update / Zakat per portfolio + closed-order attribution bug 🧾
Published 12 months ago · 2 min read
salam Reader
July leaned into Zakat. plus one of the more interesting bugs we've debugged in a while.
here's the 60 second recap:
Zakat, per portfolio 🧾
instead of importing an Excel of all your holdings, you can now calculate Zakat directly on each individual portfolio. holdings, shares, and live prices are already in the app — no upload needed, no privacy concerns about sending your holdings list to a third-party API.
Zakat: gains-based on long-term holdings 📈
we updated the long-term holdings calculation to use the Gains-Based Approach from the Fiqh Council of North America: 10% on gains (market value minus cost basis) instead of the previous flat method. short-term holdings still use 2.5% on full value. more in the halal-investing article if you want the reasoning.
two Alpaca accounts, one user → fixed 🐞🔫
a user had two Amal accounts pointing to the same Alpaca account. when we synced closed orders, we attributed all orders to whichever user's token we used — which meant his main account's filtered ARKQ fund showed $0 invested while the other account had a bunch of orders that didn't belong to it. dug in, root-caused, fixed: we now check that the user actually owns the slice before saving the order. ran a one-off script to repair the misattributed rows in prod.
FFLC, SFLO, GFLW now creatable 🌱
three funds that should have been creatable weren't — they're supported by FinSheets but we were defaulting them to FMP. added a fallback so we try FinSheets when FMP doesn't have them.
stock info API 📊
minor — exposed a stock info endpoint for the halal-investing blog.
July was satisfying. onward.
Best, Yazin