$BR $H
What keeps bothering me on Bedrock 2.0 isn't the Selini Vault itself.
It's the spread loop hiding under the Selini Vault line.
That part.
Because wrapper sounds finished way too early. BTC in. uniBTC there. Selini Vault there. Bedrock 2.0 looking grown-up on the screen. Fine. Hedge somewhere underneath. Spread capture somewhere underneath. CEX leg, DEX-CEX leg, basis, funding, timing. All ugly little Machinery pushed below one calm vault label.
Lovely.
Very adult-sounding too.
The Bedrock wrapper gets credit first.
Selini loop does the work.
That's the split.
And that's where Bedrock starts irritating me properly. The uniBTC side stays calm. vault path stays calm. The yield line behaves.Great. Meanwhile Selini execution loop still has to keep the hedge lined up. Keep spread worth taking. Keep the path tight enough that the edge doesn't get chewed up on the way through.
I've seen this kind of sentence before. Clean vault up top. Busy route underneath. Works fine right until one leg lands worse, one venue clears thin, funding shifts, basis moves, and suddenly the nice Bedrock wrapper is sitting over a spread loop that needed more discipline than label ever admitted.
Good little vault.
Or good-looking vault. Better way to put it.
Because once Bedrock 2.0s Selini path is doing the real work, the BTC holder isn't holding some tidy vault category anymore. They're holding a live execution stack that still has to earn the spread every time the market gets a bit less polite.
Thats the part people smooth over in their heads.
Or try to. Same thing.
User still sees yield.
Bedrock's router still shows path alive.
Risk, later, is asking what actually carried the return there. The wrapper? The hedge? The venue path? The spread capture?
I keep coming back to that. Not because Bedrock Vault loop is broken. Worse. Because it can look mature while still being conditional.
So what exactly is user holding there... once @Bedrock Selini Vault starts depending on spread capture, hedge timing, and route quality all behaving at once?