#baby $BABY I spent the afternoon in the security research documentation @BabylonLabs_io — I was trying to figure out exactly how slashing is performed if the validator on PoS messes up. It wasn't the punishment formulas that stopped me. Rather, it's what I discovered in the logic of connecting networks closer to night. That's what really got me hooked. There is no physical "burn coins" function in Bitcoin. To punish a dishonest player through the EOTS signature mechanism, Babylon forcibly sends his native BTC to the dummy address OP_RETURN, making him permanently unavailable. Wait a minute — this does not mean that cryptography is "breaking". Everything works exactly according to the Whitepaper. It's just that it's both true that "the system protects PoS networks" and that any bug in the logic of states on the border between the Cosmos hub and the Taproot script leads to false slashing. If the intermediate layer fails, your pure BTC will fly to the burner address without a chance to appeal. The Bitcoin network does not know that an error has occurred on the PoS side — it will simply execute the lock transaction forever. It reminds me of looking at an automatic fire extinguishing system that, at the slightest false signal, pours acid over all the gold in the jar. This vulnerability at the interface of environments will ever be closed programmatically, or this risk of irretrievable loss of BTC is simple... design now?