ing up treasury management for a small DAO and every comparison I find is written by someone selling one of the two. Unsurprisingly, they all conclude their own approach is better.

Here's where I've got to on my own. Multisig lives onchain so the rules are public and anyone can verify the threshold. The downsides are chain specific implementations, higher costs, and a setup that's visible to everyone. MPC splits a key into shares, so the chain only sees a normal signature. That makes it cheaper, portable across chains and more private. The catch is that you're trusting an implementation you probably can't audit, and share management happens entirely off chain

Recovery is the part I don't understand well. Rotating a multisig signer seems clear. Rotating MPC shares feels like a black box

Is anyone running either for real funds, and what made you pick one? Is anyone running both for different jobs, say MPC for daily operations and multisig for the treasury?

I shorted ETH with $100 at 20x leverage on Kraken and paid:

$16 opening fee
$16 closing fee
$5 margin fee

Made $7 gross but lost $30 after fees. A $1482 price drop breaks even but that doesn't even happen in a year...

Ideally, I want to short BTC from $80,144 to $79,673 (red to blue line in screenshot) using $100 at 20x leverage. That’s $11.76 gross profit, but Kraken’s fees wipe it out.

Any platforms that allow shorting with zero or very low fees so I can keep most of the profit?

I'm developing V-DAP, an experimental Rust engine that measures cryptographic execution timing. I'm trying to determine whether those measurements provide useful diagnostic information beyond conventional observability tools.

The practical problem I'm investigating is this: when a service experiences latency spikes, can measurements of cryptographic execution help distinguish between possible sources of delay, or do standard metrics, tracing and profiling already provide the same information?

My current experiments are preliminary. In a controlled HTTP pilot, I observed a strong correlation between the measured cryptographic interval and total request latency. In a separate experiment, I introduced a deliberate delay outside that interval and observed the request latency increase. These results demonstrate temporal decomposition in those test conditions, not scheduler causality or a proven diagnostic advantage.

What I want to validate next:

• Can V-DAP help distinguish two known causes of latency?
• Does it improve diagnostic accuracy or time-to-diagnosis compared with conventional tools alone?
• What confounders and measurement overhead should I investigate?
• What experiment would convince you that this has practical engineering value?

Repository and reproducibility details:
https://github.com/jorgecumbe0077/v-dap-engine

I'm looking for critical technical feedback, including reasons this approach may not be useful. I don't claim that V-DAP is production-ready or that it prevents timeouts.