I used to think fees were just transaction costs—pay the money, get the service, done. Until I saw a line that said: "collects the peg-in fee and distributes to participants". My first reaction was: Who gets it? Why should it be distributed?
Later, when I went through the agreement architecture, it finally made sense. The TBV protocol has three layers: Bitcoin side stores BTC, Ethereum side manages state, and off-chain software runs the process. FeeEscrow is one of the core smart contracts on the Ethereum side, alongside VaultRegistry and ApplicationRegistry.
FeeEscrow collects the peg-in fee—a fee paid when the depositor locks BTC. It is distributed to three parties: Vault Providers coordinate the full vault lifecycle, Universal Challengers monitor anomalies across applications, and Application Vault Keepers handle liquidation in Aave. #baby
The key is how the fee rate is determined. The Vault Provider’s commission is already embedded in the pre-signed Payout transaction when the vault is created. Once the depositor signs to confirm, the rate is fixed and cannot be changed throughout the vault’s lifetime. Each spending path is encoded as an independent leaf in a Taproot script. After the vault is created, none of the parties can forge new spending paths.
Only then did I realize my previous understanding was completely backwards—fees are the system’s compensation for the people who maintain it. And since the depositor holds the WOTS key and its own claim path, even if the Vault Provider runs away, it can still exit independently. The truly hard part of a decentralized protocol isn’t collecting fees—it’s how to distribute the money to those who continuously maintain the system’s security. $BABY
Later, I figured out one more thing: In traditional finance, fees are costs—you want them as low as possible. But in decentralized systems, there’s no CEO to backstop you; security has to be sustained by something. It’s sustained by this incentive structure—who protects the system gets the reward. The essence of fee design isn’t pricing; it’s responsibility allocation. As long as the money is split to the right people, the system can keep running on its own. @BabylonLabs_io
Later, when I went through the agreement architecture, it finally made sense. The TBV protocol has three layers: Bitcoin side stores BTC, Ethereum side manages state, and off-chain software runs the process. FeeEscrow is one of the core smart contracts on the Ethereum side, alongside VaultRegistry and ApplicationRegistry.
FeeEscrow collects the peg-in fee—a fee paid when the depositor locks BTC. It is distributed to three parties: Vault Providers coordinate the full vault lifecycle, Universal Challengers monitor anomalies across applications, and Application Vault Keepers handle liquidation in Aave. #baby
The key is how the fee rate is determined. The Vault Provider’s commission is already embedded in the pre-signed Payout transaction when the vault is created. Once the depositor signs to confirm, the rate is fixed and cannot be changed throughout the vault’s lifetime. Each spending path is encoded as an independent leaf in a Taproot script. After the vault is created, none of the parties can forge new spending paths.
Only then did I realize my previous understanding was completely backwards—fees are the system’s compensation for the people who maintain it. And since the depositor holds the WOTS key and its own claim path, even if the Vault Provider runs away, it can still exit independently. The truly hard part of a decentralized protocol isn’t collecting fees—it’s how to distribute the money to those who continuously maintain the system’s security. $BABY
Later, I figured out one more thing: In traditional finance, fees are costs—you want them as low as possible. But in decentralized systems, there’s no CEO to backstop you; security has to be sustained by something. It’s sustained by this incentive structure—who protects the system gets the reward. The essence of fee design isn’t pricing; it’s responsibility allocation. As long as the money is split to the right people, the system can keep running on its own. @BabylonLabs_io