Nova_eth_20

#baby $BABY @BabylonLabs_io
Was comparing validators for my BABY delegation and almost skipped past "jailing" as the standard Cosmos boilerplate every chain has, missed blocks, temporary timeout, nothing specific to Babylon. Then I read what validators actually sign twice, not once.
Every Babylon Genesis validator does two separate jobs. Regular CometBFT block signing, the ordinary work any Cosmos validator does, and a second one: BLS voting at the end of each epoch, where validator signatures get aggregated into a checkpoint that's timestamped directly onto Bitcoin. That second signature is the entire reason people call this chain Bitcoin-secured.
Downtime jailing only cares about the first job, on its own terms, standard liveness enforcement, nothing dramatic. What I couldn't pin down precisely is the exact interaction, whether a jailing that lands mid-epoch quietly disqualifies that whole epoch's BLS contribution, or only matters if it's still active the moment the epoch closes. Babylon's docs confirm the two jobs are separate. They don't spell out that specific timing boundary anywhere I found.
Either way, the two jobs share one uptime record. A validator jailed for ordinary missed blocks, the same rule any Cosmos chain runs, isn't protected from also missing the signature that actually gets anchored to Bitcoin that epoch, for a reason that has nothing to do with Bitcoin security at all.
I don't think this is a design flaw, there's no clean way to jail someone from one role and not the other on the same key. What I hadn't separated in my head before this was that downtime history isn't just about missed rewards. It's a rough proxy for how often a validator was actually present for the signature that makes "Bitcoin-secured" true.
Checked my shortlist's jailing history again. Two names had one entry each, both over a year old, both followed by long clean stretches since. Not a red flag. Just not the same zero I'd assumed a clean uptime percentage was already telling me.

$BLESS
🤔 What's the first thing you check before delegating your baby

#baby @BabylonLabs_io

私は今、Babylon経由でBTCをステークしています。昨夜、古いCap-3のドキュメントに埋もれていた「overflow」という言葉を見つけたとき、歴史のことだとは読みませんでした。自分の立場に関する問いとして読みました。つまり、これは自分にも起こり得るのか、と。
フェーズ1では、キャップがすでに埋まった後に確定したステーキング取引でも、BTCは他の人とまったく同じようにコントラクトにロックされました。ですが、得られるものは何もありません。ポイントも、割り当てもなし。コインが自動的に返ってくるわけでもありません。ドキュメントは明確で、overflowのステークは、解除して引き出す必要がありました。待機期間もアクティブなポジションと同じで、ステークがロックされている間ずっと支払いが0だった場合は、その間ずっと0のままです。
誰がその枠に入ったかを決めたのは、「誰かがステークをクリックしたタイミング」ではありません。実際に取引が確定したビットコインのブロック番号です。これは、ウォレットの外に出た瞬間に誰も完全には制御できない数字です。2人が数分差でブロードキャストしても、手数料やメンプールの混雑、あるいは次のブロックを最初に見つけたマイナーによって、順番がどちらになるかは変わり得ます。
フェーズ1のキャップはもうなくなりましたが、overflowを生んだ仕組みはそのフェーズ固有ではありません。今後のキャップ付きラウンド、新しいBSNオンボーディングで固定の割り当て、限られたスロットの統合など、キューではなくブロックの確定で処理する瞬間に、同じ「競争」が発生します。つまり、この設計上の欠陥は修正されていません。キャップが消えたときに、単にスケールアウト（使われなくなって）しただけです。
私は、元の設計が不公平だったとは思いません。ハードキャップには何らかの打ち切りが必要で、ブロックの確定は、タイムスタンプのように偽装できるものではありません。私に残っているのはもっと小さな点です。今自分のBTCがロックされたままだという事実は、スキルや良いタイミングで守られていたわけではありません。私によって引かれた線を越えたのではなく、マイナーによって引かれた線を越えただけで、次にその線が引かれるときも、同じことが起きます。

$SKYAI $BICO $BABY


"このoverflowのリスクが、将来のキャップ付きラウンドでのステークをやめさせますか？" 🎯

#baby $BABY @BabylonLabs_io

Half my BTC sits staked through Babylon right now. I never once asked what happens to it if half the validator set goes dark at once — until last night, reading the half of Babylon's founding paper I'd skipped.
Bitcoin checkpointing fixes safety. One honest validator submitting proof to Bitcoin is enough to slash the liars and settle which history is real. Liveness is a separate question: does the chain keep producing blocks at all.
Here's the part Bitcoin can't touch. No proof-of-stake protocol guarantees liveness once adversarial validators cross half the active set. Not with Bitcoin behind it, not with any timestamping service — not unless every validator's data gets posted on-chain, and Bitcoin's throughput was never built to carry that.
The proof holds against malice. It says nothing about validators that simply stop showing up. The chain stalls exactly the same either way, and Bitcoin can't tell you which one happened.
"Secured by Bitcoin" reads like one guarantee. It's two. Bitcoin buys certainty about which history is true. It doesn't buy a promise the chain keeps moving if half the validators vanish at once — outage, exit, or an attack nobody caught in time.
A committee needing one honest signer, a relayer needing one to stay online — those get fixed by more operators showing up. This ceiling is proven math, not a staffing problem. Watching harder doesn't move it.
My BTC is locked either way. Bitcoin will hand me a receipt for the exact moment the chain died. Getting it breathing again was never part of the proof.
$BLESS $HOME
If half of Babylon's validators went dark tonight, what happens to your BTC?

@BabylonLabs_io $BABY #baby

Every time you unbond BTC from Babylon, nine keys stand between your Bitcoin and your wallet. Six of them have to agree before you get your funds back.
One of those nine belongs to Babylon Labs.
The pitch is "trustless": no custodian, no company holding your BTC, just Bitcoin Script enforcing the rules. And that's real — no single key can touch your funds alone. But unbonding is the only door back to your coins before the 15-month timelock runs out, and the team that built the door also holds one of the keys to open it.
That's not a scandal. The other eight keys sit with named, reputable entities, and the committee can only approve or deny standard transactions — it was never built to be able to run off with anyone's BTC. Still, read Babylon's own docs closely enough and you'll find the builder listed as a signer on the system it built to not need signers.
Ask a Babylon staker why they moved BTC into the protocol and "trustless" is usually the first word out of their mouth. Ask them who's holding key number one, and most won't know the answer is Babylon Labs.

$IDOL

Does the builder holding one of the unbonding keys change how you see "trustless"?

2am, still awake, reading Babylon's checkpointing docs for no reason except I couldn't sleep. One line stopped my scrolling: one honest and live vigilante throughout the network is enough to guarantee successful and secure checkpoints to Bitcoin.
Read fast, that sounds like decentralization doing its job. Dozens of independent operators, only one needs to behave.
I went back to Babylon's own 2022 academic paper, co-authored by its founders, the one that proves this claim as a formal theorem instead of a marketing line. The proof holds on one condition: there is one honest validator active at all times. The paper states that plainly.
Here's what it doesn't spell out. "One is mathematically sufficient" and "one is currently online" are two different guarantees. Only the first comes with a proof attached.
Then the same sentence showed up again, this time next to the covenant emulator and IBC relayer, named as their own separate programs: secure operation requires at least one honest operator of each program listed, or the system raises an alarm. Not sure if that covers all three equally, or if it was written with just the vigilante suite in mind. Either way, the headcount stays unpublished.
Babylon calls this voluntary, anyone can run one. True, and it still doesn't say how many currently do, or whether that number holds during a Bitcoin fee spike nobody wants to pay through.
There's a reason nobody publishes that count. Revealing how thin the buffer is helps an attacker more than it helps you.
If you're staking through Babylon right now, this is the assumption sitting underneath your BTC that no dashboard shows you: not whether the math works, but whether someone is actually awake to run it, tonight, and every night after.

@BabylonLabs_io $BABY #baby

$1000RATS $KOMA
Would you stake if the “one honest operator” count is unknown? 👀

#baby $BABY @BabylonLabs_io

I used to think slashing was Babylon's way of punishing dishonesty. That changed at 2am scrolling through an independent security audit of the EOTS implementation, the kind of document nobody opens without a reason.
The mechanism is elegant on its own terms. A finality provider commits to a piece of randomness before signing any block at a given height. Sign it once, nothing happens. Sign it twice, with two different messages, and the math behind Schnorr signatures turns that same randomness into the provider's exposed private key. Intentional double-signing becomes self-punishing by construction, and there's a reason for that: a protocol can only read signatures, not intent, so a rule strict enough to catch an attacker can't tell an attacker from an accident.
That tradeoff is what the audit flagged. A deliberate attack and an honest backup-node failover firing at the same height produce the exact same signature pattern. Both look identical to EOTS. Both get slashed the same way, tombstoned, no reinstatement.
That's not theoretical. Hex Trust, an institutional custodian running finality provider infrastructure on Babylon, lists specific safeguards against exactly this: no private key reuse across machines, manual failover instead of automatic, because automatic failover is exactly what can produce two live signers for one key at once.
Here's the part with no clean answer. There's no public disclosure standard for which failover setup a provider runs. You can check commission, uptime, delegator count. Not this, not before your BTC is already locked.
Delegating was never just a bet that the operator wouldn't attack you. It's also a bet their infrastructure never has a bad day for as long as your BTC is locked, on a detail the protocol makes unknowable in advance .

$KOMA

$BABY $UAI $COTI #baby @BabylonLabs_io

At first I assumed the covenant committee was a bootstrap step, something Babylon would retire once its own roadmap matured, the same way most young protocols promise to decentralize on their own timeline. The documentation says something quieter and stranger than that.
The committee exists because Bitcoin itself has no native way to enforce covenants, no opcode that can force a UTXO to spend only through pre-agreed rules. So Babylon built a 6-of-9 multisig to emulate that missing function, watching staking requests, co-signing unbonding and slashing, standing in for a capability Bitcoin Script simply doesn't have yet. That part is honest engineering around a real gap, and the trust assumption is genuinely lighter than a normal custodial multisig, existential honesty instead of majority honesty, one honest signer is enough to stop theft.
What stopped me was the exit condition. Babylon's own documentation doesn't say the committee retires once governance matures, or once a certain TVL threshold is hit, or once some internal milestone ships. It says the committee stays until covenant functionality becomes available natively on Bitcoin, through opcodes like OP-CAT or OP-CTV that Bitcoin Core hasn't adopted and has no committed timeline to adopt. The retirement date isn't on Babylon's roadmap. It's sitting inside a different protocol's governance process, one Babylon has no vote in and no ability to accelerate.
So the trust didn't disappear when Babylon called this a Bitcoin-secured system. It moved one layer further away, off a multisig with a defined membership and onto a Bitcoin soft fork that may or may not ship this decade. Six of nine known signers is at least a trust assumption you can name. A pending opcode upgrade with no deadline is a trust assumption you can only wait on.

The covenant committee stays until Bitcoin adds covenant opcodes. No Babylon timeline controls it.
Your take? 👀

Was choosing a finality provider last week, staring at a list of about 30 verified names, and caught myself about to click whichever one already had the most delegators. The same reflex that turned a big chunk of Ethereum staking into a Lido story.

Then I actually read Babylon's own staking guide.

It names the risk directly: delegating to the most popular providers increases centralization risk. Not a critic's observation, their own documentation says it.

➡ Roughly 30 providers carry a verified checkmark in the app.

➡ Nothing in that list caps how much delegation any single one can absorb.

Give Babylon credit for saying this out loud, most staking products never warn the end user before they click.

Here's what stayed with me. The checkmark exists to build trust. But if most stakers default to whichever verified name already has the most delegators, the exact pattern Ethereum lived through, the thing meant to build trust becomes the mechanism concentrating the very risk it warns about.

I looked for actual delegation-share numbers, how much the top 5 or 10 finality providers control combined. Found nothing public. One crypto exchange's own writeup on the protocol called this "still requiring further discussion," an open problem, flagged by an outside source, not something Babylon itself has addressed on record.

I split my delegation across three smaller providers instead of one large one. At this scale it's probably closer to a symbolic gesture than an actual fix, and I know that.

@BabylonLabs_io $BABY #baby $ON

"Would you delegate to a smaller finality provider on purpose?"

#baby @BabylonLabs_io
Almost put a small amount of BTC into a vault-backed lending position last week. Before I did, I wanted to know one thing: if the market moved fast against me, what actually decides when I get liquidated? That question is what sent me looking past the marketing and into Babylon's own site — for wherever the word "trustless" stops applying. It wasn't buried. It just doesn't survive translation into every headline built around that one word. ➡ Babylon's own Learn page says plainly that the real risk sits on the DeFi side, not in the vault itself, and gives liquidation in lending as the example. ➡ The whitepaper backs it up: liquidation needs a signature from a price oracle, treated as a separate dependency from the vault's core design. Give Babylon credit — they wrote this down themselves. Nobody had to dig it out of them. Here's the part that stuck with me, the part that actually changed how much I was about to deposit. "A price oracle" sounds abstract, until one report on this exact system named which networks actually hold that relationship with Babylon: Band Protocol and Pyth, the same general-purpose networks pricing dozens of other chains at the same time. Babylon's own materials don't name them directly, so treat that specific pairing as reported, not confirmed by Babylon itself. If one of those feeds is late or wrong during a fast move, my liquidation still fires exactly as coded. Correctly, acting on bad information. Bitcoin's base layer doesn't get a vote in that outcome. The vault does exactly what it promised. The oracle just hands it something false. That's not the vault failing. That's DeFi risk, wearing a trustless label, inheriting whatever outage history its actual price feed already carries from other chains I don't even use. I still made the deposit. Just smaller than I would have an hour earlier. Trustless describes what happens to your BTC. It was never a promise about what happens to your money once it leaves the vault.

$BROCCOLIF3B $ON $BABY

#baby $BABY @BabylonLabs_io

Almost put a small amount of BTC into a vault-backed lending position last week. Before I did, I wanted to know one thing: if the market moved fast against me, what actually decides when I get liquidated?
That question is what sent me looking past the marketing and into Babylon's own site for wherever the word "trustless" stops applying.
It wasn't buried. It just doesn't survive translation into every headline built around that one word.
➡ Babylon's own Learn page says plainly that the real risk sits on the DeFi side, not in the vault itself, and gives liquidation in lending as the example.
➡ The whitepaper backs it up: liquidation needs a signature from a price oracle, treated as a separate dependency from the vault's core design.
Give Babylon credit — they wrote this down themselves. Nobody had to dig it out of them.
Here's the part that stuck with me, the part that actually changed how much I was about to deposit. "A price oracle" sounds abstract, until one report on this exact system named which networks actually hold that relationship with Babylon: Band Protocol and Pyth, the same general-purpose networks pricing dozens of other chains at the same time. Babylon's own materials don't name them directly, so treat that specific pairing as reported, not confirmed by Babylon itself.
If one of those feeds is late or wrong during a fast move, my liquidation still fires exactly as coded. Correctly, acting on bad information. Bitcoin's base layer doesn't get a vote in that outcome. The vault does exactly what it promised. The oracle just hands it something false.
That's not the vault failing. That's DeFi risk, wearing a trustless label, inheriting whatever outage history its actual price feed already carries from other chains I don't even use.
I still made the deposit. Just smaller than I would have an hour earlier.
Trustless describes what happens to your BTC. It was never a promise about what happens to your money once it leaves the vault.

$EUL
Can a trustless vault still depend on oracles?

⚡✨

#baby $BABY @BabylonLabs_io

Couldn't sleep last night, so I pulled up three separate write-ups on Babylon's Aave Temp Check side by side, more out of habit than anything.
One word wouldn't stop bugging me.
Bitcoin.com, Cointribune, and LiveBitcoinNews all describe the TBV liquidation flow the same way. A permissionless liquidator swaps a seized vault for WBTC instantly, at a small premium. A separate set of "permissioned arbitrageurs" then buy that position and redeem the real BTC later, on Bitcoin's own timeline.
Give Babylon credit for the first half permissionless liquidation checks out exactly as advertised.
It's the second half where I went looking further back than the Aave proposal. Babylon's own August whitepaper on Trustless Bitcoin Vaults never says "permissioned" either it says liquidations run through "whitelisted liquidators" who monitor price and vault state. Different word, same shape. An independent analyst who exchanged messages with Babylon's team on X raised the same point directly to them: enough of those whitelisted parties behaving correctly is a trust assumption the marketing doesn't mention.
So the word turned out accurate. The real question is why that role has to be restricted at all, when the WBTC-swap side isn't. Bitcoin's scripting language can't evaluate arbitrary off-chain state. BitVM3 works around that by wrapping a zero-knowledge proof verifier inside a garbled circuit, but someone still has to generate and submit that proof to trigger redemption. The WBTC-swap side is easy to leave permissionless any liquidator with capital takes the trade. Proof-submission is the harder problem BitVM3 hasn't solved yet.
This isn't about whether the vault is trustless. Babylon didn't hide the whitelisting in its own whitepaper. Trustlessness doesn't disappear here. It just ends one step earlier than most of the coverage lets on.

$EUL


What defines a truly trustless BTC vault?

参加する

#baby $BABY @BabylonLabs_io

昨夜、暇つぶしのほとんどでAaveのv3からv4への移行メモを読み漁っていたんですが、タブを閉じたあともバビロン自身のバルト論文からの1行が頭に残りました。つまり、TBV型のバルトの支出条件（送付先コントラクトを含む）は、それが作成された瞬間に固定される、ということです。これが文字通りトラストレス（信頼不要）たる所以で、誰も後からそのBTCを別の経路へリダイレクトできません。静かに意味するのは、もしAaveがまたv3からv4のようにコントラクト移行を行うなら、既存のバルトは追随できず、ビットコイン側のタイムラインに沿って解消（アンワインド）され、新しい送付先を指す形で毎回作り直される必要がある、という点です。送付先となるプロトコルがアップグレードされるたびに、です。ここでのトラストレスはただではありません。柔軟性と引き換えに頑なさ（リジディティ）を買っているので、誰もそのコストを本質的には価格に織り込めていない。バビロンやAaveが、この移行をよりスムーズにするためのツールを予定しているのかどうか、公に見つけられませんでした。これは、バルトを作成したその日、見た目がどれだけ安全かという話ではなく、相手側が変わらなければならないその日、何が起きるのかという話なんです。

$DEXE

ここでのより大きなトレードオフは何でしょうか？

#baby 数日前、私はAaveのガバナンスフォーラムでBabylonの「Temp Check」を見つけました。そこには、ネイティブBTC担保向けの新しいAave V4 Spokesが2つあります。私の目を引いたのは、みんなが繰り返す「ノー・カストディアン」という見出しではありません。鍵になるのは、ロックされたビットコインを表すトークンであるvaultBTCが譲渡制限されており、動かせるのはAave V4 Hub、Babylon Core Lending Spoke、そしてアダプターコントラクトの間だけで、他の場所には一切送れない点です。これは、自由に取引され、プロトコルをまたいで再担保（rehypothecated）され、実際のリスクを誰も正確に値付けできなくなるWBTCやrenBTCとは構造的にまったく違います。ここでは担保はクローズドループから外へ出られません。BTC Vault Swap Spokeが難しい部分を引き受けていて、清算業者は即座にWBTCで決済でき、許可された裁定業者はその後、ビットコイン本来のタイミングで実BTCを償還します。つまり、DeFiが求めるスピードと、ビットコインの遅い決済がぶつからないようにしているわけです。市場はこれを「別のBTCラッパー」として出していますが、循環できないラッパーは、実際にはラッパーとは言い難いです。vaultBTCはロックされたら他で再利用できないので、この制限が長期の組成性（composability）をどこまで制約するのか、私は本当に確信が持てません。これはビットコインをラップする話ではありません。各マーケットを分離することで、BTCレンディングを安全に保ちつつ、使い勝手を過度に硬直化させないのか——それが論点です。Spoke間で流動性を分割すると、より安全になるのか、それとも単に小さくなるだけなのか？ @BabylonLabs_io $BABY


$RIF $AKE

質問：Aave V4 Spoke間で流動性を分割することは…

goooo

#Newt $NEWT @NewtonProtocol
メインネットは6月23日に稼働を開始しました。ニュートンのエクスプローラーを確認したのは、12日後でした。忘れたからではありません。「誰でも検証可能」という文言が、招待状というより機能説明のように感じられたからです。誰か別の人が領収書を見ているものだと思っていました。
それから実際に開いてみました。ページ最初の記載は9分前のものでした——タスクID、適用されたポリシー、合否、タイムスタンプ。要約はありません。ダッシュボードの数字にするためのパーセンテージによるスムージングもありません。ニュートンで各ポリシー評価が行われるたびに、署名付きのオンチェーン証明（オンチェーンアテステーション）が生成されます——実行前に、設定されたポリシーに対してそのトランザクションが通過したか失敗したかを記録する暗号学的な領収書です。エクスプローラーはそれらを誰でも公開して読み取れるようにします。誰か他の人が先に解釈して要約したり、集計したりはしません。ブラウザさえあれば検証できる、生の領収書です。
私はその文を何度も何度も読み直しました。読んだことと、エクスプローラーを開いたことは同じではありません。
最初に私を止めたのは複雑さではありませんでした。それは「公開的に検証可能」が、実際に自分がやるべきことではなく、技術仕様だという前提でした。検証できるシステムと、実際に検証されているシステムの間にあるのは、完全に行動面のギャップで——そしてその行動の大部分はプロトコル側ではなくユーザー側にあります。
ニュートンはあなたにチェックさせることはできません。チェックが可能になるようにすることしかできません。領収書は、誰かが読もうが読まなかろうが存在します。これは、この仕組みの最も強い点でも、もっとも静かな制限でもありえます——リンクを実際に開くかどうか次第です。

$PORTO $SKHYB

"あなたは実際に、エクスプローラー上でニュートンのオンチェーン証明（アテステーション）をチェックしていますか？"

去年私はエアドロップを獲得したのですが、その半分が私より先に請求したウォレットにファームされるのを見届けました。人間が処理できるよりも速く実行され、塵が落ち着く前に姿を消しました。誰も止めなかった。何も確認されなかった。取引は有効だったので、そのまま通ってしまったのです。

それが、ニュートンの「Human Passport」統合が解決することです。

3月4日、ニュートンはHuman Passportデータオラクルを公開しました。これはオープンソースの統合で、human.techのシビル・レジスタンス・プロトコルと組み合わされています。これにより、120以上のプロジェクトにわたって$512 million超の資本フローが確保されてきました。この統合は、ニュートンのポリシーレイヤーに3つのシグナルを持ち込みます。

1つ目：パスポートの「stamps score」。検証済みの資格情報によって、固有の人間性（personhood）が裏付けられたスコアです。
2つ目：models APIのスコア。機械学習によるオンチェーンの行動パターンの解析で、受動的にシビルのような活動を検知します。
3つ目：「proof of clean hands」—ゼロ知識のKYCと、サンクション（制裁）スクリーニング。個人データを公開せずに、規制コンプライアンスを検証します。

ポリシーでは、最小stamps scoreを20以上、models APIスコアを50超、そしてclean handsアテステーションを設定でき、請求（claim）または支払い（disbursement）の実行前に3つすべてが評価されます。ウォレットが3条件を満たさない場合、アクションは進行しません。

ニュートンがHuman Passport“単体”にはない形で加えるのは「執行（enforcement）」です。Human Passportは、ウォレットが人間のように見えることを示せますが、そのシグナルは情報に留まります。ニュートンはそれを認可（authorization）の経路に直接組み込みます。そのため、クリアされない限りトランザクションは実行できません。情報が拘束力になります。

反論としてよくあるのは、シビル耐性はそれに供給されるシグナル次第だということです。stamps scoreはアカウントをまたいでファームされうる。models APIはアイデンティティではなく行動パターンを検知する。proof of clean handsは、制裁コンプライアンスをカバーしますが、厳密な意味での「人間性」を直接保証するものではありません。3層にすることで乱用のコストは引き上げられますが、決意した敵対者は常に抜け道（エッジケース）を探し続けます。

私は、私のエアドロップを奪ったあのウォレットたちのことを考え続けています。彼らは賢くある必要はありませんでした。必要だったのは、速さと、確認のないシステムでした。「技術的に有効」から「実際に許可される」までの間にチェックがない。

ニュートンは、そのチェックを作りました。

#newt $NEWT $EVAA