Jinnnnn_
15 Beiträge
Jinnnnn_
45 Following
760 Follower
18 Like gegeben
Beiträge
Übersetzung ansehen
Spent part of the afternoon digging into @BabylonLabs_io 's Trustless Vault docs. The most interesting takeaway wasn't even the mechanics. Bitcoin stays locked on native Taproot, never leaves the Bitcoin network, yet can still be used as productive collateral elsewhere. That's a pretty elegant design.
Then I checked the charts.
As of the August 02 snapshot, $BABY was sitting around $0.0107, down roughly 5.5% over the week, with a market cap near $46M and about $1M in 24-hour volume. At the same time, the vaults it's meant to govern were securing roughly 56,800 BTC. That's billions of dollars in Bitcoin actively at work.
That's the part I couldn't stop thinking about.
The protocol appears to be doing exactly what it's built to do. Bitcoin remains native. Lending protocols receive real collateral. Users gain access to liquidity. The infrastructure is functioning.
Yet the governance token tied to that ecosystem is valued at only a tiny fraction of the assets it helps coordinate.
It feels like watching a powerful engine run flawlessly while the dashboard barely registers that it's on.
Maybe that disconnect narrows over time through higher borrow demand, additional BSNs, token burns, or stronger value accrual. Or maybe this separation between protocol utility and token value is simply how the system is designed.
Curious to see which direction it takes.
#BABY #BabylonLabs
Then I checked the charts.
As of the August 02 snapshot, $BABY was sitting around $0.0107, down roughly 5.5% over the week, with a market cap near $46M and about $1M in 24-hour volume. At the same time, the vaults it's meant to govern were securing roughly 56,800 BTC. That's billions of dollars in Bitcoin actively at work.
That's the part I couldn't stop thinking about.
The protocol appears to be doing exactly what it's built to do. Bitcoin remains native. Lending protocols receive real collateral. Users gain access to liquidity. The infrastructure is functioning.
Yet the governance token tied to that ecosystem is valued at only a tiny fraction of the assets it helps coordinate.
It feels like watching a powerful engine run flawlessly while the dashboard barely registers that it's on.
Maybe that disconnect narrows over time through higher borrow demand, additional BSNs, token burns, or stronger value accrual. Or maybe this separation between protocol utility and token value is simply how the system is designed.
Curious to see which direction it takes.
#BABY #BabylonLabs
Übersetzung ansehen
the peg-in wait is the part nobody warns you about properly.
you lock signet BTC, and then you wait for 12 confirmations before setup finalises. on the testnet that ran close to two hours for me.
nothing on screen is broken. nothing needs clicking. its just bitcoin being bitcoin.
i almost refreshed the page thinking i'd missed a step.
what i didnt expect was how much that wait told me. a bridge would have moved in minutes, and it moves in minutes becuse someone signed for it on your behalf.
"speed in crypto is usually somebody elses signature standing in for confirmation"
the 12 blocks arent friction. theyre the thing being purchased.
go in expecting the wait and the whole experience reads differently.
#baby @BabylonLabs_io $BABY
you lock signet BTC, and then you wait for 12 confirmations before setup finalises. on the testnet that ran close to two hours for me.
nothing on screen is broken. nothing needs clicking. its just bitcoin being bitcoin.
i almost refreshed the page thinking i'd missed a step.
what i didnt expect was how much that wait told me. a bridge would have moved in minutes, and it moves in minutes becuse someone signed for it on your behalf.
"speed in crypto is usually somebody elses signature standing in for confirmation"
the 12 blocks arent friction. theyre the thing being purchased.
go in expecting the wait and the whole experience reads differently.
#baby @BabylonLabs_io $BABY
Übersetzung ansehen
theres a dice example in the docs that explains this better than any diagram.
alice locks one bitcoin. she writes the rule herself. roll 1 to 3, her address can claim it. roll 4 to 6, bobs address can.
the roll happens on ethereum. the bitcoin never moves untill someone claims correctly. $SNDKB
if bob lies and claims on a roll of 2, alice challenges him on bitcoin. to get unstuck he has to produce a valid proof. he doesnt have one. he never will.
read that twice and the whole protocol opens up.
"the rule was written by the owner, not agreed to by a counterparty" $KOMA
i sat with this longer than i meant to, becaus i realised most of finance is just this with a company standing in the middle taking a fee for it.
alice trusts bitcoin, ethereum, and the contract she picked. thats the entire list.
no dice game is interesting. what the dice stands in for is.
#baby @BabylonLabs_io $BABY
alice locks one bitcoin. she writes the rule herself. roll 1 to 3, her address can claim it. roll 4 to 6, bobs address can.
the roll happens on ethereum. the bitcoin never moves untill someone claims correctly. $SNDKB
if bob lies and claims on a roll of 2, alice challenges him on bitcoin. to get unstuck he has to produce a valid proof. he doesnt have one. he never will.
read that twice and the whole protocol opens up.
"the rule was written by the owner, not agreed to by a counterparty" $KOMA
i sat with this longer than i meant to, becaus i realised most of finance is just this with a company standing in the middle taking a fee for it.
alice trusts bitcoin, ethereum, and the contract she picked. thats the entire list.
no dice game is interesting. what the dice stands in for is.
#baby @BabylonLabs_io $BABY
okay also habe ich heute endlich nachgeschaut, wofür das W in den Trustless Bitcoin Vaults (TBV) Self-Claim Keys eigentlich steht. Winternitz-Einmal-Signatur. Und der Teil „Einmal“ macht wirklich Arbeit.
Bei einem Peg-in erzeugst du ein frisches WOTS-Schlüsselpaaar für genau dieses Vault, und nur der Hash des öffentlichen Schlüssels wird in den On-Chain-Record der Vaults übernommen. Der Schlüssel selbst liegt in einer Datei, die du aufbewahrst. Er ist so designt, dass er genau einmal signiert — in dem Moment, in dem du jemals selbst deinen Claim auf Bitcoin durchdrücken musst.
Warum einmal? Weil diese Signaturschemata bei jeder Verwendung Teile des privaten Schlüssels leaken, daher geht das gesamte Sicherheitsmodell von einer einzigen Auslösung aus. Ein Vault, ein Key, ein Schuss. Deshalb erzeugt das Protokoll auch pro Vault ein neues Keypair, statt irgendetwas wiederzuverwenden.
Dein Notfall-Key ist eine Kugel, kein Werkzeug. Passt irgendwie zu etwas, von dem du hoffst, dass du es nie feuern musst. Hat sonst noch jemand wirklich gewusst, wofür WOTS steht, bevor er das hier gelesen hat?
#baby @BabylonLabs_io $BABY
Bei einem Peg-in erzeugst du ein frisches WOTS-Schlüsselpaaar für genau dieses Vault, und nur der Hash des öffentlichen Schlüssels wird in den On-Chain-Record der Vaults übernommen. Der Schlüssel selbst liegt in einer Datei, die du aufbewahrst. Er ist so designt, dass er genau einmal signiert — in dem Moment, in dem du jemals selbst deinen Claim auf Bitcoin durchdrücken musst.
Warum einmal? Weil diese Signaturschemata bei jeder Verwendung Teile des privaten Schlüssels leaken, daher geht das gesamte Sicherheitsmodell von einer einzigen Auslösung aus. Ein Vault, ein Key, ein Schuss. Deshalb erzeugt das Protokoll auch pro Vault ein neues Keypair, statt irgendetwas wiederzuverwenden.
Dein Notfall-Key ist eine Kugel, kein Werkzeug. Passt irgendwie zu etwas, von dem du hoffst, dass du es nie feuern musst. Hat sonst noch jemand wirklich gewusst, wofür WOTS steht, bevor er das hier gelesen hat?
#baby @BabylonLabs_io $BABY
Übersetzung ansehen
okay so buried in the Trustless Bitcoin Vaults (TBV) config contracts theres a phrase i had to read twice. borrow-delegation resolver registration. translated: the protocol supports delegating borrowing rights on your position to someone else — without transferring custody of anything.
the team has described the idea as letting users delegate borrowing to yield providers while keeping full control of their btc. think about what that separates. today, earning yield on your coins usually means handing them over first, becuase the manager needs custody to act. this splits the two cleanly — a provider can operate borrowing against your collateral, but the btc never leaves your co-signed vault and the exit paths stay yours.
delegation without surrender is a genuinely new shape for bitcoin holders. the obvious question is what the guardrails around a delegate look like in practice, and thats worth watching closely. would you ever delegate a position you didnt have to hand over??
#baby @BabylonLabs_io $BABY
the team has described the idea as letting users delegate borrowing to yield providers while keeping full control of their btc. think about what that separates. today, earning yield on your coins usually means handing them over first, becuase the manager needs custody to act. this splits the two cleanly — a provider can operate borrowing against your collateral, but the btc never leaves your co-signed vault and the exit paths stay yours.
delegation without surrender is a genuinely new shape for bitcoin holders. the obvious question is what the guardrails around a delegate look like in practice, and thats worth watching closely. would you ever delegate a position you didnt have to hand over??
#baby @BabylonLabs_io $BABY
Übersetzung ansehen
okay so i found the least dramatic sentence in the Trustless Bitcoin Vaults (TBV) docs and it might be the most reassuring one. upgrades go through a TimelockController, meaning changes are publicly visible before they take effect.
think about what that kills. the 3am rule change. the parameter tweak you learn about after it already hit your position. here, an upgrade sits in public view for its delay period first, so anyone watching can see whats coming, and if you dont like it you have a window to exit becuase your vault still runs on the rules it was born with.
no surprise patches on money you locked up. thats a small sentence doing heavy lifting. how many platforms holding your funds give you advance notice of their own rule changes??
#baby @BabylonLabs_io $BABY #BABY #Baby
think about what that kills. the 3am rule change. the parameter tweak you learn about after it already hit your position. here, an upgrade sits in public view for its delay period first, so anyone watching can see whats coming, and if you dont like it you have a window to exit becuase your vault still runs on the rules it was born with.
no surprise patches on money you locked up. thats a small sentence doing heavy lifting. how many platforms holding your funds give you advance notice of their own rule changes??
#baby @BabylonLabs_io $BABY #BABY #Baby
das creatorpad run und heute habe ich mit dem einen erschreckendsten Satz in den Trustless Bitcoin Vaults (TBV) Borrowing-Dokumenten gesessen. Sobald eine Position unter 1,0 fällt, wird eine Liquidation typischerweise innerhalb des nächsten Blocks oder zwei abgewickelt.
Ein Block oder zwei. Das ist die gesamte Schonfrist – also gibt es keine. Die Doku macht ganz klar, dass professionelle Liquidator-Bots um diese Ereignisse konkurrieren: Sie beobachten jede Position, berechnen im Voraus die profitablen Beschlagnahmungen und liefern sich ein Wettrennen, sobald der Oracle-Tick den Health Factor unter die Linie drückt. Der permissionless Trigger bedeutet, dass jeder ihn auslösen kann – und in der Praxis macht das die schnellste Maschine, weil der Liquidation Bonus an den geht, der als Erster landet.
Was ich immer wieder drehe, ist die Frage, wie das die Aufgabe der Einleger verändert. Die Durchsetzung ist kein Prozess mit Warnungen und Telefonaten, sondern ein Stolperdraht mit industrieller Konkurrenz, die auf der anderen Seite lauert. Es gibt keinen Moment, in dem ein Mensch deinen Fall prüft. Das Protokoll braucht das tatsächlich: Positionen müssen geschlossen werden, bevor das Sicherheitenpolster unter die Schulden sinkt, die es absichert – und der Bot-Wettbewerb macht das zuverlässig. Die Geschwindigkeit, die das System schützt, ist real, sie hat nur für dich persönlich kein bisschen Gnade budgetiert.
Also schreibt sich die praktische Regel praktisch von selbst: verwalte die Position so, dass 1,0 nie in die Nähe kommt, denn der Abstand zwischen sicher und beschlagnahmt wird in Sekunden gemessen. Verinnerlichen das eigentlich alle, die gegen BTC borgen, schon bevor sie ihre erste Position eröffnen – oder erst danach?
#baby @BabylonLabs_io $BABY
Ein Block oder zwei. Das ist die gesamte Schonfrist – also gibt es keine. Die Doku macht ganz klar, dass professionelle Liquidator-Bots um diese Ereignisse konkurrieren: Sie beobachten jede Position, berechnen im Voraus die profitablen Beschlagnahmungen und liefern sich ein Wettrennen, sobald der Oracle-Tick den Health Factor unter die Linie drückt. Der permissionless Trigger bedeutet, dass jeder ihn auslösen kann – und in der Praxis macht das die schnellste Maschine, weil der Liquidation Bonus an den geht, der als Erster landet.
Was ich immer wieder drehe, ist die Frage, wie das die Aufgabe der Einleger verändert. Die Durchsetzung ist kein Prozess mit Warnungen und Telefonaten, sondern ein Stolperdraht mit industrieller Konkurrenz, die auf der anderen Seite lauert. Es gibt keinen Moment, in dem ein Mensch deinen Fall prüft. Das Protokoll braucht das tatsächlich: Positionen müssen geschlossen werden, bevor das Sicherheitenpolster unter die Schulden sinkt, die es absichert – und der Bot-Wettbewerb macht das zuverlässig. Die Geschwindigkeit, die das System schützt, ist real, sie hat nur für dich persönlich kein bisschen Gnade budgetiert.
Also schreibt sich die praktische Regel praktisch von selbst: verwalte die Position so, dass 1,0 nie in die Nähe kommt, denn der Abstand zwischen sicher und beschlagnahmt wird in Sekunden gemessen. Verinnerlichen das eigentlich alle, die gegen BTC borgen, schon bevor sie ihre erste Position eröffnen – oder erst danach?
#baby @BabylonLabs_io $BABY
Übersetzung ansehen
the creatorpad run and today i caught a small design habit in Trustless Bitcoin Vaults (TBV) that quietly protects every vault from its own coordinator....
during peg-in the vault provider collects the PegIn input signatures from every participant, the depositor, the vault keepers, all of them. and instead of just holding that bundle in its own database, it posts the collected signatures on-chain in batched form. at first that looks like bookkeeping. its actually insurance....
becuase think about the failure case. setup completes, everyone signed, and then the vault provider goes dark before the final PegIn transaction broadcasts. if those signatures only lived on the providers servers, the vault would be stranded in limbo with the btc sitting in the pre-pegin output. since theyre recoverable from ethereum, any party observing the activation can reconstruct the full witness once the depositor reveals the secret, and broadcast the transaction themselves. the docs even say any party, typically the vault provider, which is a quiet way of saying the provider is replaceable at the exact moment it matters most....
the coordinator is forced to leave its fingerprints in public before it can be trusted with the job. thats the whole trick....
what other protocols make their operators deposit the evidence first?? feels rarer then it should be....
#baby @BabylonLabs_io $BABY
during peg-in the vault provider collects the PegIn input signatures from every participant, the depositor, the vault keepers, all of them. and instead of just holding that bundle in its own database, it posts the collected signatures on-chain in batched form. at first that looks like bookkeeping. its actually insurance....
becuase think about the failure case. setup completes, everyone signed, and then the vault provider goes dark before the final PegIn transaction broadcasts. if those signatures only lived on the providers servers, the vault would be stranded in limbo with the btc sitting in the pre-pegin output. since theyre recoverable from ethereum, any party observing the activation can reconstruct the full witness once the depositor reveals the secret, and broadcast the transaction themselves. the docs even say any party, typically the vault provider, which is a quiet way of saying the provider is replaceable at the exact moment it matters most....
the coordinator is forced to leave its fingerprints in public before it can be trusted with the job. thats the whole trick....
what other protocols make their operators deposit the evidence first?? feels rarer then it should be....
#baby @BabylonLabs_io $BABY
Übersetzung ansehen
today i chased a number that explains why Trustless Bitcoin Vaults (TBV) even became buildable. 42 gigabytes....
thats the off-chain storage one garbled circuit demanded under the earlier BitVM3 style approach. one circuit, 42 GiB. and remember from the setup ceremony, vaults dont keep just one instance around, so multiply that across pairs and across every vault and the thing stops being infrastructure and starts being a hard drive farm. verifying proofs on bitcoin was theoretically solved and practically absurd, becuase the fees werent the bottleneck, the storage was....
the BABE construction is the answer to specifically that. it keeps the on-chain cost savings but cuts the off-chain storage and setup burden by around three orders of magnitude. the trick as i understand it is combining a witness encryption scheme for the pairing relations with an efficient garbled circuit thats only responsible for scalar multiplication on elliptic curves, so the heavy machinery shrinks to the one piece that genuinely needs it....
a thousand fold reduction is the difference between a protocol that runs on real operator hardware and one that exists in a paper. everyone stares at gas costs, almost nobody asks what the watchtower has to store....
what other protocols died quietly on storage math nobody talked about?? genuinely curious now....
#baby @BabylonLabs_io $BABY
thats the off-chain storage one garbled circuit demanded under the earlier BitVM3 style approach. one circuit, 42 GiB. and remember from the setup ceremony, vaults dont keep just one instance around, so multiply that across pairs and across every vault and the thing stops being infrastructure and starts being a hard drive farm. verifying proofs on bitcoin was theoretically solved and practically absurd, becuase the fees werent the bottleneck, the storage was....
the BABE construction is the answer to specifically that. it keeps the on-chain cost savings but cuts the off-chain storage and setup burden by around three orders of magnitude. the trick as i understand it is combining a witness encryption scheme for the pairing relations with an efficient garbled circuit thats only responsible for scalar multiplication on elliptic curves, so the heavy machinery shrinks to the one piece that genuinely needs it....
a thousand fold reduction is the difference between a protocol that runs on real operator hardware and one that exists in a paper. everyone stares at gas costs, almost nobody asks what the watchtower has to store....
what other protocols died quietly on storage math nobody talked about?? genuinely curious now....
#baby @BabylonLabs_io $BABY
Übersetzung ansehen
the creatorpad grind and today i finally understood the strangest number in the Trustless Bitcoin Vaults (TBV) technical docs. 307....
during peg-in setup the participants run whats called a cut and choose ceremony for the BABE proof system. the garbled circuits that will later verify redemption proofs on bitcoin get generated in bulk, 307 candidate instances per claimer-challenger pair on testnet. then most of them get opened up and inspected, and only 6 survive to actually guard the vault....
took me a minute to see why youd throw away 301 circuits on purpose. its becuase a garbled circuit is basically a sealed box, and a dishonest party could seal a rigged one. so you make them build hundreds, you crack open a random majority to check the construction was honest, and if those all verify clean, the odds that the few unopened survivors are rigged drop to basically nothing. cheating would mean rigging everything and praying the inspection misses all of it....
no trust in the builder needed, just statistics doing the auditing. the 6 remaining instances also give redundancy if one path has issues later....
honest question, how many people using a vault will ever know 301 circuits died so their 6 could be trusted?? kinda love that detail tho....
#baby @BabylonLabs_io $BABY
during peg-in setup the participants run whats called a cut and choose ceremony for the BABE proof system. the garbled circuits that will later verify redemption proofs on bitcoin get generated in bulk, 307 candidate instances per claimer-challenger pair on testnet. then most of them get opened up and inspected, and only 6 survive to actually guard the vault....
took me a minute to see why youd throw away 301 circuits on purpose. its becuase a garbled circuit is basically a sealed box, and a dishonest party could seal a rigged one. so you make them build hundreds, you crack open a random majority to check the construction was honest, and if those all verify clean, the odds that the few unopened survivors are rigged drop to basically nothing. cheating would mean rigging everything and praying the inspection misses all of it....
no trust in the builder needed, just statistics doing the auditing. the 6 remaining instances also give redundancy if one path has issues later....
honest question, how many people using a vault will ever know 301 circuits died so their 6 could be trusted?? kinda love that detail tho....
#baby @BabylonLabs_io $BABY
Übersetzung ansehen
the creatorpad digging and today i hit the part of Trustless Bitcoin Vaults (TBV) that solves a problem i hadnt even registered as a problem....
liquidation on ethereum is atomic, repay debt and take collateral in one transaction. but a vaults btc lives on bitcoin, and releasing it runs through claim, challenge window, payout, roughly 3 days. those two speeds are incompatible. no liquidator waits days to get paid, becuase by then the price already moved....
the protocols answer is a liquidation liquidity provider layer. the first one is BTCVaultSwap, registered as its own WBTC spoke. when a permissionless liquidation fires, the liquidator gets paid instantly in WBTC from that pool, the seized vault goes into escrow, and a registered arbitrageur later buys it out and finalizes the slow bitcoin redemption in the background....
the detail that stuck with me, interest keeps accruing on escrowed vaults, so if a vault sits too long the arbitrage margin erodes and nobody wants to buy it. anyone can top up the accrued interest to keep the window profitable, which is a strange little public good baked into a liquidation engine....
so the instant settlement everyone expects is actually a liquidity layer fronting a 3 day process. clever plumbing or a new dependency to watch??
#baby @BabylonLabs_io $BABY
liquidation on ethereum is atomic, repay debt and take collateral in one transaction. but a vaults btc lives on bitcoin, and releasing it runs through claim, challenge window, payout, roughly 3 days. those two speeds are incompatible. no liquidator waits days to get paid, becuase by then the price already moved....
the protocols answer is a liquidation liquidity provider layer. the first one is BTCVaultSwap, registered as its own WBTC spoke. when a permissionless liquidation fires, the liquidator gets paid instantly in WBTC from that pool, the seized vault goes into escrow, and a registered arbitrageur later buys it out and finalizes the slow bitcoin redemption in the background....
the detail that stuck with me, interest keeps accruing on escrowed vaults, so if a vault sits too long the arbitrage margin erodes and nobody wants to buy it. anyone can top up the accrued interest to keep the window profitable, which is a strange little public good baked into a liquidation engine....
so the instant settlement everyone expects is actually a liquidity layer fronting a 3 day process. clever plumbing or a new dependency to watch??
#baby @BabylonLabs_io $BABY
Anmelden und weiter Inhalte entdecken