u/weaforex

AQMath is an institutional-grade portfolio assistant built on some pretty advanced math. We are actually launching on Product Hunt in a few days so this is the final beta stretch, and I wanted to drop a couple of full access keys before we go completely live.
The whole engine is designed around drawdown mitigation and tracking live asset correlations, running walk-forward stress tests rather than just giving you a basic tracker. I also just pushed a core update that adds a fully integrated private chat directly into the UI. I got sick of Discord data leaks and telegram spam, so this has zero third-party trackers and maximum privacy. It just works inside the app.
Since the PH launch is close, here are two keys that unlock the full engine and the private nfty alerts server for a year. There is no auto-renewal or strings attached to these. The basic DCA engine stays free forever regardless.

AQMBETA-F205-8F85
AQMBETA-FC70-C1E2

Just reply if you grab one so people don't waste time trying dead codes. You can check it out at aqmath.xyz

Before, always tested it on whole windows as you know from my previous work , bull and bear together. That is friendly, because bull legs pay for protection, and good Sharpe can hide a bad crash. But I wanted to ask the unfriendly question: what happens inside the worst segments, on regimes the optimizer never saw during fitting? So I did regime autopsy.

So, made three baskets. One is blue-chip majors with gold. Second is the 2019-20 generation coins with gold. Third is a stress basket — I deliberately put a token that went to zero. Weights are re-optimized every 180 days and then frozen. No changes between rebalance. Then I sliced these frozen-weight series after the fact along five named crashes: May 2021, LUNA, FTX, August 2024, and the 2025-26 corrections. Every regime is scored by parameters that were frozen before it happened. Out of sample by construction, zero parameter changes, real production code.

All 15 combinations of regime and basket showed a positive drawdown cut. Not one failed. The numbers that matter most: during LUNA contagion, the Shield held drawdown to 16.8% while Buy & Hold on majors basket did 44.1%. On 2019-20 basket it was 21.3% vs 44.8%. FTX collapse: majors basket cut to 3.3% vs 13.3% Buy & Hold. 2019-20 basket: 1.9% vs 9.2%. So in worst moments the protection worked.

The Shield v14 gives up absolute return in strong bull windows. It trails Buy & Hold on CAGR in all three full windows. On 2019-20 basket, even full-window Sharpe and Calmar favour Buy & Hold outright. In 2025-26 the system was parked in USDC about 40% of days. Also March 2020 is not covered by design. The gold anchor plus the 180-day warm-up means our baskets start on 2020-03-24, after the crash bottom. All this is in the article, not footnoted away.

One finding I think is most interesting
Crypto crashes are drift-dominated. I decomposed each regime damage into two parts: close-to-open gap (the unseen jump) and open-to-close drift (the intraday destruction). For these crashes, 95-100% of damage happened in the intraday leg, the part that a daily-close system can react to. The uncatchable gap residual concentrates in single worst days — like May 19, 2021, a minus 30% day on the equal-weight risky basket. That is the structural reason a close-based shield can do this job at all.

I've been running E2E WF stress test on a multi-asset basket featuring high-beta alternatives TIA, QNT and XRP anchored with a defensive allocation of PAXG 8%, managed through dynamic risk-exposure modulators rather than rigid stop-losses. Instead of relying on in-sample curve fitting, the simulation uses strict out-of-sample walk-forward windows across varying liquidity regimes. Here is a breakdown of what the numbers and structural results actually look like:

**Drawdown Compression**

While a pure B&H basket of TIA/QNT/XRP routinely suffers maximum drawdowns exceeding 65% to 75% during systemic liquidity flushes, the introduction of the 8% PAXG structural anchor alongside a dynamic volatility-adjusted exposure cap brought the max drawdown down to 24.5% across the tested OSS periods.

**Walk-Forward Degradation**

When splitting the dataset into rolling out-of-sample validation windows, static rebalancing models experienced a 35% performance decay. Introducing an adaptive lookback triggered by regime-switching volatility filters kept the out-of-sample degradation under 7.2%, proving that reacting to live covariance shifts beats optimized static parameters every time.

**The Flow Logic**

you don't fight market mechanics with brute force but you match the liquidity structure. Funds don't predict exact tops, they track systemic flow.

Curious how others here are structuring your walk-forward validation parameters. Are you seeing similar out-of-sample degradation when testing multi-token baskets across high-volatility regimes, or how are you handling your covariance lookback windows?

ust finish big test on my systematic crypto model. i did around 1.8m out of sample oos tests in grid over 11 years which is 3982 days with daily data. i use risk parity for tokens allocation and dynamic deleverage modulator. everything is under strict kkt conditions like drawdown limits and local volatility limits. objective function look only at sharpe and calmar and i do not care about beating buy and hold curve. the framework do identical dca 100 dollar every 30 days to stop timing luck.
when i test only 3 tokens btc and eth and xrp the results are best. calmar is 1.37 and sharpe is 1.18 and max dd is 36.2 percent where b&h making was 84 percent crash so big save here. average exposure is 40 percent and system spend 2679 days in defense mode with less than 50 percent exposure. why this work? xrp have crazy non korelaten pumps sometime compared to btc eth beta. so risk parity engine can do rebalance nicely with 3968 rebalances total and kkt limits do not trigger at same time because vectors are orthogonal. corr is very low.
but when i add more tokens like bnb and sol and ada and xlm everything go to shit. if i add bnb sharpe collapse to 0.44 and calmar down to 1.20 and defense days go to 72 percent because high corr kills it. if i add sol and bnb with 5 tokens sharpe go up a bit to 0.76 but calmar drops to 0.93 with ann return 30.7 percent vs max dd 33.1 percent. ada and xlm completely kill the model because of bad corr trend.
in crypto when market crash all corr go to 1.0. if you put too much altcoins with bad trend vs btc you just add more failure points. joint variance spikes up fast and kkt conditions instantly saturate and deleverage modulator panics and goes to cash. then because these tokens have no real alpha on way up the system stay trapped in defense mode too long. this is huge opportunity cost because we miss explosive bull market start.
also big issue is fees. the best 3 token model make 3968 rebalances. i pay 14 559 dollar fees on total 14 200 dollar invest. profit is still good with 1 113 410 dollar net but this trading churn is too high. i think i will add band based rebalance threshold to only rebalance if weight is out by like 5 percent to stop overtrading. and i will put defense cash in de-fi stablecoin yield.
how you fix lag when you want to re engage market after kkt deleverage event

Quick follow-up on that KKT projection bug the senior quant helped me squash under stress.
Engine just had its first real fire drill. Wanted to share how it actually behaved when shit got sweaty:
Peak DS vol hit 17.6% — blew right past my 12.4% lockout. Deleverage Shield flipped ACTIVE and immediately chopped exposure to 40.4%. Portfolio's basically hibernating in cash now — 75.93% USDC, ~24% still in risk.
The patched KKT constraints are holding. ETH capped at 10%, LINK at 11%, etc. — even with individual asset vols screaming above 60%. Zero budget leaks. That was the whole point of the fix.
Global DD at 36.9% which stings, but at least capital's parked in stables until this cools off. This is exactly why I gate de-risking through vol/correlation mechanics instead of panic-selling into random drops.
How do yo guys handle lockout thresholds?
Anyone running downside variance as the primary trigger, or do you keep it simpler?
(no links, just sharing the math

Every time Bitcoin drops and we see on-chain data showing that institutions or big players are reducing their positions, the crypto community instantly copes with the same old narrative:
"They are just shaking out the weak hands! Diamond hands will win! Don't sell them your cheap BTC!"
Let’s look at the other side of the coin for a second, because the reality is much less cinematic. There is no secret cabal trying to steal your 0.05 BTC. It’s just cold, hard, boring risk management.
The Illusion of the "Ideological HODLer"
Retail investors love the DCA and HODL strategy because they are investing their own money. If you go through an 80% drawdown (DD) and lose sleep, that’s your personal problem. You can afford to wait 4 years for the next halving because nobody is going to fire you for underperformance.
Institutions cannot do that. They manage billions of dollars of other people’s money (their clients).
When an institutional client allocations capital to a crypto product, they aren't signing up for a "community vibe." The fund managers present them with a strict risk mandate. They define hard boundaries, and one of the most critical metrics they monitor is the Maximum Drawdown (Max DD).
It's Math, Not Manipulation
If a fund's automated risk model or corporate mandate specifies a maximum drawdown of, say, 20% for that specific allocation, they must sell when the market hits that threshold. It doesn't matter if the fund manager "believes" Bitcoin is going to $1 million.
How institutional risk control actually works:

Volatility Spikes: The market starts dropping.

Thresholds Triggered: Automated mathematical models and risk boundaries are hit.

Exposure Deleveraging: The institution reduces exposure (sells) to protect the remaining client capital and prevent structural breaches.

Re-entry: They sit in cash or stablecoins, wait for the volatility to die down, and re-enter when the trend stabilizes.

They aren't trying to "make you panic." They literally do not care about retail. They are protecting themselves from having to explain to a pension board or a billionaire client why their portfolio just experienced a 60% wipeout. You can't tell an institutional client to "just stay calm and buy the dip, bro."
The Irony of Retail Panic
The funniest part? Retail investors don't understand these mechanical risk mechanisms. So, when they see a massive entity reducing exposure, retail starts to panic-sell.
This retail panic drops the price even further, which triggers the next layer of institutional risk-off mechanisms and circuit breakers. It’s a self-fulfilling feedback loop driven by a complete lack of understanding of traditional risk management.
Institutions aren't playing 4D chess to take your coins. They are playing a very strict, mathematical game of capital preservation.
Change my mind.
TL;DR: Big funds don't "HODL through the pain" because they have fiduciary duties and strict Max Drawdown limits. When they sell, it’s not a conspiracy to shake you out — it’s just automated risk management doing exactly what it was programmed to do.

ive been grinding on some portfolio math and the one problem that keeps coming back is what happens when correlation spikes to 1.
standard fixed-weight rebalancers just keep buying whatever is most underweight. btc drops 40% system sees it underweight keeps deploying capital. no circuit breaker no risk awareness. that is not rebalancing thats catching a falling knife on autopilot.

so what i build uses 7 layers before any dca dollar gets deployed. circuit breaker that halts all buys above drawdown threshold. volatility safety factor per token. trend filter no buying above moving average only dips. apy filter to skip self compounding positions. hard caps per token based on actual volatility not some arbitrary % i set 6 months ago. risk budget cap on total risky exposure max 60%. safe haven redirect surplus flows into usdc instead of getting lost.

math is erc covariance and kkt projection. 180 days price history. computation on backend portfolio stays in browser only nothing stored server side.
v1 is working and stress tested. fed it btc at 71% with target 10% and every cap holded. Some quant do this not me 🤣
what i havent solved is what to do when correlation goes to 1 and tou already holding positions that are overweight. pipeline stops new buys but never trims. i know thats the hard problem thats v2.
curious how others handle trim on breach. do tou deleverage linearly scale by vol wait for correlation to drop before reactivating.
happy to share math if anyone wants to poke at it 🍻

im mapping out a mechanical defense system for highly volatile assets that automatically runs to cash based on the drop from the all-time high. the logic is a continuous reduction of exposure. when a drop happens, the system reduces the weights and moves the rest into a safe asset.
currently my app already has some defense mechanisms: the upper limit is maximum 20% for each risky token, the total budget for all risky tokens together is maximum 60% (the rest stays in stablecoin), and i have an automatic fuse where if the portfolio drops more than or equal to 40% from the all-time high, only the new regular buying stops, but existing positions are not touched.
my plan for the next step (read V2) is to stop the system from making false exits and entries at the liquidation limits during choppy sideways markets, so im testing a hysteresis loop. for example, the exit trigger starts at -40%, but the reentry confirmation is locked until a 30% recovery.
dilemma is that during sudden massive drops, correlations jump to 1. in my model, i use a time window of 180 days in the past for historical data. if the variance-covariance matrix updates monotonically day by day, those 180 days create a massive lag and delay in execution. by the time the math figures out what is happening and starts reducing risk, tou have already taken the maximum hit and loss on the price difference during the sale.
for those who designed these automated triggers: how do you mathematically solve the problem of this lag? do you scale the loop thresholds dynamically based on sudden spikes in overnight implied volatility, or do you just hardcode a wider safety buffer because of transaction costs and issues?
because right now this looks like a mathematical trap where protection always arrives too late. thoughts?

guys, quick update on my last post about the covariance risk parity engine for crypto rebalancing. A senior institutional quant from Reddit actually took the time to test the logic and try to break it. I was glad that people like to break things.
He found a bad bug under stress where tokens blew past the hard caps. The issue was the KKT projection failing to bind correctly under stress. The engine printed dynamic caps but failed to enforce them, which allowed risky assets to aggregate toward 100% instead of staying capped at 60%.
I fixed the projection logic and cap enforcement, so now the governor holds the limits exactly where they belong. I retested it with 180d real data and now the limits hold perfectly. This is pure risk management for the book. It protects the portfolio by controlling allocation weights when asset correlation spikes near 1.
Here is a quick breakdown of the latest stress-test run on v1:

Method: ERC+covariance+KKT (6 iter)
Portfolio vol: 27.5%
Weights (KKT-projected):
BTC: 17.62% (vol:48.9%, erc:30.57%, rc:30.3%) A (cap: 18%)
LINK: 10.8% (vol: 63.8%, erc:23.35%, rc:24.2%) (cap: 11%)
XRP: 10.06% (vol:65.5%, erc: 23.33%, rc:22.5%) A (cap: 10%)
ETH: 10% (vol: 65.6%, erc:22.75%, rc:23.0%) (cap:10%)
Top correlations:
ETH_LINK: 0.93
BTC_ETH: 0.92
BTC_LINK: 0.89
KKT constraints:
BTC capped at 18% (vol: 48.9%)
ETH capped at 10% (vol: 65.6%)
LINK capped at 11% (vol: 63.8%)
XRP capped at 10% (vol: 65.5%)
Data: BTC=180d, ETH=180d, LINK=180d, XRP=180d

Right now v1 is stable, mathematically verified, and ready for further testing.
I am looking for alpha/beta testers and technical minds from the DeFi community to stress-test this engine further or discuss the mathematical logic behind KKT stability during extreme correlation spikes.
I am not posting any direct links here due to the subreddit promo rules. If you are interested in checking out the logic or testing the engine, let's open up a discussion below or feel free to reach out!

Hey guys, quick update on my last post about the covariance risk parity engine. A senior institutional quant from quant sub actually took the time to test the logic and try to break it. I was glad that people like to break things.
He found a bad bug under stress where tokens blew past the hard caps. The issue was the KKT projection failing to bind correctly under stress. The engine printed dynamic caps but failed to enforce them, which allowed risky assets to aggregate toward 100% instead of staying capped at 60%.
I fixed the projection logic and cap enforcement, so now the governor holds the limits exactly where they belong. retested it with 180d real data and now the limits hold perfectly.

Method: ERC+covariance+KKT (6 iter)
Portfolio vol: 27.5%
Weights (KKT-projected):
BTC: 17.62% (vol:48.9%, erc:30.57%, rc:30.3%) A (cap: 18%)
LINK: 10.8% (vol: 63.8%, erc:23.35%, rc:24.2%) (cap: 11%)
XRP: 10.06% (vol:65.5%, erc: 23.33%, rc:22.5%) A (cap: 10%)
ETH: 10% (vol: 65.6%, erc:22.75%, rc:23.0%) (cap:10%)
Top correlations:
ETH_LINK: 0.93
BTC_ETH: 0.92
BTC_LINK: 0.89
KKT constraints:
BTC capped at 18% (vol: 48.9%)
ETH capped at 10% (vol: 65.6%)
LINK capped at 11% (vol: 63.8%)
XRP capped at 10% (vol: 65.5%)
Data: BTC=180d, ETH=180d, LINK=180d, XRP=180d

This is pure risk management for the book and advance mathematical allocation and DCA
It is not a direct hedging strategy with shorts or options, but it protects the portfolio by controlling allocation weights when asset correlation spikes to 1.
Right now v1 is stable and ready. I am not posting any links here due to the promo rules. I would love to discuss the mathematical logic or how you handle DCAand Aloccation?

most people doing dca with 5-10 coins just split cash by fixed % evry month (30% sol, 20% eth, 5% alts
if you actually look at the math this has 2 big flaws.

1st is portfolio drift.

you keep blindly buying tokens that already pumped and are overweight instead of routing new cash only to what is actually underwater. you end up chasing pumps inside your own portoflio.

2nd is fee bleed.

if you have small 5% alocations like toshi xlm hbar on a modest budget, you throw like 5-10$ into small coins. exchnage minimums and trading fees eat your gains fast over 12 months.

So i decided and built a small severles browser tool called aqmath to automate it. it runs iterative proportional alocation to calculate drift so it routes dca budget only into tokens that need it based on risk adjusted drift. Using math from hedge fund managers and institutions, also has a small dca rule so if budget is too low it drops everything into the single most underweight coin to bypass exchnage fee limits. zero acounts, no tracking, data stays in localstorage.

unless im missing some hidden benefit of buying already pumped tokens, doing static percentage splits is mathematically inferior for alts??? Explain me pls?

I’ve been experimenting with rebalancing models to minimize drawdown during market shocks. The issue I keep running into is that standard fixed-percentage models fail when asset correlation spikes to 1.0.
I'm curious how you guys approach this—do you strictly use covariance matrices to calculate your next DCA, or are you utilizing other risk-parity frameworks? I’m interested in hearing about your approach to local-only rebalancing math.

hey guys,
i’m a solo dev and i just finished the core engine for aqmath.
i built it because i wanted to apply institutional risk-management (like risk parity and covariance matrices) to my pasive crypto dca, but i hated the fact that every other tool wanted my email, wallet login, or exchange api keys.
aqmath runs 100% client-side in your browser. zero data tracking, no backend server expect math, no login. your data stays in your localstorage.
i am prepairing for a product hunt launch and i currently have zero beta testers. i need honest, brutal feedback on the ui and the math.
if you want to test the full version, just drop a comment and DM me, and i will dm you a premium promo code immidiatly.
check it out here: aqmath.xyz - would love to hear your thoughts!

I've been grinding on some portfolio math lately. Most platforms are fine for "set and forget," but they live and die by fixed % targets.
It’s flawed. If an asset crashes, the system blindly buys more to hit the target, regardless of the risk.
I’m building a local-first browser tool that skips fixed weights entirely and runs covariance matrices + risk parity. The goal is to cap assets based on their actual volatility, not just some arbitrary % I set 6 months ago.
Has anyone here actually tried moving away from fixed weights, or is everyone just sticking to the standard rebalancing? Genuinely curious if you guys think it’s worth the overhead.

my last post was basically a pure UI roast (more than 3.6k views((fixed the mobile spacing btw, thanks for that)).
but since everyone was talking only about the wrapper, let's talk about what the app actually does under the hood.

aqmath is a quantum portfolio rebalancer. every calculation runs 100% locally in your browser (no server, no tracking, no wallet connect). standard rebalancers just force fixed % weights, meaning if a coin crashes, they blindly buy more regardless of risk.

aqmath runs a full covariance matrix and risk parity optimization to ensure equal risk contribution. basically, high-variance or heavily correlated assets get smaller dynamic caps so they don't dominate your overall volatility.

right now, i need exactly 10 beta testers to put the automation and free plan features through its paces.

in return, i'll give you a beta key that converts into a 1-year free pro annual license once the premium layer goes live later….

if you want to lock in a free year of pro math, drop a comment below or shoot me a reddit DM. i'll send you the access link and details directly. (you can also check the link in my reddit bio). only 10 slots available.

I’m currently building a client-side portfolio optimization engine that runs heavy math (Risk Parity, Covariance matrix, etc.) directly in the browser.
Today, a UI designer on Twitter took a look at my landing page and completely roasted it.
He told me the text is too technical, the dark grid with neon accents feels too raw, and running it on a .xyz domain makes it look sketchy. He even generated a "beautiful,(by AI, I DO NOT USE AI IN APP) polished B2B SaaS mockup" for me with onboarding flows, cheerful colors, and social proof placeholders.
But he completely missed the psychology of the audience.
When people who handle serious capital look for a tool to run heavy optimization math, they don't want a slick, polished corporate funnel. They don't want to see a marketing page trying to capture their email, track their cookies, or force a wallet connection. To a hardcore tech/finance niche, massive marketing sh*** actually screams "trap."
They want privacy. They want zero tracking, local browser storage, and raw code. For them, a raw, terminal-like UI is a trust feature, not a bug.
It made me realize how generic modern web advice has become. Everyone is optimizing for the standard SaaS template, forgetting that sometimes your niche just wants pure logic and zero noise.
Has anyone else deliberately chosen a raw, "engineering-first" UI because it builds more trust with your specific audience than a polished template?