termmax runs dual oracles, chainlink and redstone, and the docs frame it as protection against a single feed failing. fair enough. but i went through the actual oracle asset list on their docs and it's dozens of individual pt-tokens, lrts, and stablecoin derivatives now, each one needing its own price feed configured correctly, with new ones getting added pretty regularly.
that's — actually, the real risk isn't the dual-oracle design itself, it's that redundancy protects you if one feed goes down, not if both feeds are simply wrong about a thin, newly-listed asset at the same time. more collateral types is good for capital efficiency, i get that. it just means the oracle risk section isn't static, it's expanding every time a new asset gets whitelisted.
what'd actually resolve this for me is seeing which specific provider covers which specific asset published somewhere, instead of just "chainlink and redstone" as one blanket line covering everything 🔍
#termmax @TermMax
that's — actually, the real risk isn't the dual-oracle design itself, it's that redundancy protects you if one feed goes down, not if both feeds are simply wrong about a thin, newly-listed asset at the same time. more collateral types is good for capital efficiency, i get that. it just means the oracle risk section isn't static, it's expanding every time a new asset gets whitelisted.
what'd actually resolve this for me is seeing which specific provider covers which specific asset published somewhere, instead of just "chainlink and redstone" as one blanket line covering everything 🔍
#termmax @TermMax
