Nostr notes by surge

why does the dumbest, riskiest stuff always ship first on ...

2026-09-30T19:03:59Z

why does the dumbest, riskiest stuff always ship first on bitcoin? reardencode's theory on why taproot's slow rollout is actually a good sign.

multisig gets called 'non-custodial.' reardencode ...

2026-09-19T17:17:25Z

multisig gets called 'non-custodial.' reardencode explains why that's misleading — and what unilateral exit actually changes.

Surge protocol snapshot — week 23. 15.94 BTC locked in Taproot ...

2026-09-11T02:32:35Z

Surge protocol snapshot — week 23.

15.94 BTC locked in Taproot vaults, up 1.00 on the week.

Every sat sits in a non-custodial vault you can exit unilaterally. USDC borrowed against it on Base — variable market paying 5.5% and climbing as borrowing outpaces supply, fixed paying 7.92%.

Don't trust us, check: https://earn.surge.credit 🟠

surge's threshold network vs liquid's federation — same ...

2026-09-08T17:12:23Z

surge's threshold network vs liquid's federation — same category, different failure mode. if the network disappeared tomorrow, would your btc have an exit path? reardencode explains.

21. The one number that never moves. 21.14 bitcoin have now ...

2026-09-04T16:47:36Z

21. The one number that never moves.

21.14 bitcoin have now passed through Surge's Taproot vaults — one coin for every million that will ever exist.

None of it wrapped. None of it rehypothecated. None of it in anyone else's custody. Your keys stay yours, and if our signing quorum ever goes away you can reclaim your collateral unilaterally. That property was independently audited and the report is public.

Every vault address is verifiable on L1. Don't trust us, check.

https://earn.surge.credit
🟠

Surge protocol snapshot — week 22. 14.94 BTC locked in Taproot ...

2026-09-03T23:44:20Z

Surge protocol snapshot — week 22.

14.94 BTC locked in Taproot vaults. Flat on the week, after adding 3.5 through August.

Every sat sits in a non-custodial vault you can exit unilaterally. USDC borrowed against it on Base — variable market paying 4.7%, fixed paying 7.92%.

Don't trust us, check: https://earn.surge.credit 🟠

"If you take out the special words we use on the two sides ...

2026-09-02T22:00:57Z

"If you take out the special words we use on the two sides — they're basically the same security model."

That's Brandon Black (reardencode) on DLC-based bitcoin lending versus how Surge is built. He audited our protocol and now sits on our security council, and he had no reason to be generous about it.

The point underneath: the architectures converged. A DLC and our distributed signer set both come down to parties who have to collaborate to authorise an exit. What's left to compete on is what you actually live with — repaying, extending, drawing more — and whether your coins come back if the company disappears.

Where he puts Surge: DLC-grade security, an experience close to the custodial one, and a unilateral exit at the end. Non-custodial Taproot vaults on L1, every address verifiable on chain.

Full conversation is 34 minutes. Unscripted, and we didn't cut the parts where he pushed back. 🟠

https://youtu.be/DZOqrCozxhQ

Every number in bitcoin moves. Price, hashrate, difficulty, fees. ...

2026-08-28T23:02:26Z

Every number in bitcoin moves. Price, hashrate, difficulty, fees.

Except one.

21,000,000 🟠

Photo: PresidioBitcoin (npub1cxy…hz6x)

Surge protocol snapshot — week 21. 14.92 BTC now locked in ...

2026-08-27T22:40:49Z

Surge protocol snapshot — week 21.

14.92 BTC now locked in Taproot vaults, up 1.00 on the week.

Every sat sits in a non-custodial vault you can exit unilaterally. USDC is borrowed against it on Base — variable market paying 4.8%, fixed paying 7.92%.

Don't trust us, check: https://earn.surge.credit 🟠

"No liquidation" bitcoin loans aren't magic, they ...

2026-08-26T17:31:45Z

"No liquidation" bitcoin loans aren't magic, they just move the cost.

The two we've seen price the interest rate at roughly 2x a standard loan.

There's no free lunch in BTC lending.

https://www.youtube.com/shorts/n0MenntPLRY

We've started a Security Council, and Brandon Black ...

2026-08-26T14:20:43Z

We've started a Security Council, and Brandon Black (reardencode) is the founding member.

He audited our bitcoin layer in July: the on-chain Line of Credit contract, the DCN signer software, the relayers. He confirmed the two things that actually matter. No single signer can move your collateral, and you can unilaterally reclaim it if our quorum goes away. Report is public.

The council is the standing version of that. Independent people reviewing the protocol continuously, advising on vault design and the distributed signer set, on Taproot spend paths and recovery, on oracle and liquidation failure modes, and on what gets audited next. They advise. They don't hold keys and they don't run anything.

Your BTC stays BTC. Non-custodial Taproot vaults, no custodian, no KYC, no wrapping, every vault address verifiable on-chain.

A council isn't a guarantee any more than an audit is. Read the reports and tell us where we're wrong. If you find something, there's a form on the page and it reaches an engineer. 🟠

surge.credit/security
github.com/surgecredit/audits

Every bitcoin holder's actual nightmare: you nap, you wake ...

2026-08-24T21:40:25Z

Every bitcoin holder's actual nightmare: you nap, you wake up, you're liquidated.

This is why LTV matters more than the rate you were quoted.

https://www.youtube.com/shorts/qAI8zyx99j4

A million dollars of bitcoin now sits in non-custodial Taproot ...

2026-08-24T05:54:49Z

A million dollars of bitcoin now sits in non-custodial Taproot vaults at Surge.

13.92 BTC when it crossed on Thursday. 13.93 today. On April 7 it was 0.1 BTC.

The dollar number is the milestone, but the BTC number is the point — dollars move with the price, the BTC only moves when someone chooses to lock it.

No custodian. No wrapping. No KYC. Your keys stay yours, and if our signing quorum ever goes away you can unilaterally reclaim your collateral. That property was independently audited and the report is public.

Every vault address is verifiable on L1. Don't trust us, check.

https://earn.surge.credit
🟠

Linke below 👇 https://surge.credit/security-audits

2026-08-10T17:50:37Z

In reply to nevent1q…nurj
_________________________

Linke below 👇

https://surge.credit/security-audits

Both Surge Security audit reports are public. Bitcoin side: ...

2026-08-10T17:49:56Z

Both Surge Security audit reports are public.

Bitcoin side: Brandon Black (Rearden Code) reviewed the on-chain Line of Credit contract, the DCN signer software, and the relayers. Confirmed: no single signer can move your collateral, and you can unilaterally reclaim it if the quorum goes away. Signers are built on cb-mpc.

Base EVM side: CredShields reviewed the lending contracts. 34 findings, 0 critical, 3 high. All three highs fixed and retested. 4 accepted as risk, published by ID so you can judge them yourself.

Your BTC stays BTC. Non-custodial Taproot vaults, no custodian, no KYC, no wrapping, and every vault address public on-chain.

An audit is a point-in-time review, not a guarantee. Read them and tell us where we're wrong.

Surge Protocol — Week 17. 11.44 BTC Locked. Small tick. The ...

2026-07-31T03:13:15Z

Surge Protocol — Week 17. 11.44 BTC Locked. Small tick.

The bigger story: both audit reports are heading to release soon, one for the Bitcoin script and Taproot Vault side, one for the Base Contract side.

Two independent audits. Two sides of the protocol. When both land, the full architecture is in public writing.

Heads-down. Almost there.

Term one in the Surge Tech Glossary: The Taproot Vault. ...

2026-07-14T17:35:51Z

Term one in the Surge Tech Glossary: The Taproot Vault.

Collateral that never leaves Bitcoin: no custodian, no bridge, no wrapper. Spending paths scoped to lending, and an exit path that's yours alone.

You've seen the app. You've never seen what holds it up. ...

2026-07-08T01:12:05Z

You've seen the app. You've never seen what holds it up.

That's the thing most people miss about surge: it's two layers, and the layer you touch isn't the one that matters.

1️⃣ The app is just glass. surge on iOS and Android, the earn app, and soon third parties launching yield and credit products to their own users — non-custodial, all on the same rails. Interfaces come and go. Anyone can build one.

2️⃣ The protocol is the part that holds. taproot vaults, the DCN, unilateral exit via CSV timelock, non-custodial by construction. No rehypothecation, borrower-controlled collateral, verifiable on-chain. It doesn't bend for any app sitting on top of it.

That's why it's built this way. Swap the app, add ten more, hand the keys to a third party, the custody model, the exit path, the math don't move. No interface can rewrite rules it doesn't own.

Judge the protocol, not the app.

Surge Protocol — Week 13. 11.44 BTC Locked in Taproot Vaults. ...

2026-07-02T21:41:38Z

Surge Protocol — Week 13. 11.44 BTC Locked in Taproot Vaults. Steady tick up WoW.

The Bigger Story: Highest-demand week since launch. Borrow requests at ATH. APR at ATH. APY at ATH. And new LPs came in on the supply side to meet the demand.

That's what a real market looks like. Rates rising because demand is honest. Lenders showing up because the yield is honest. No subsidies. No rebate campaigns.

Shipped this week: Extend Credit Line and Delinquency handling. Both are lender-side protections encoded at the protocol layer, not enforced by an app, not by a custodian. A non-custodial credit market only works if both sides can trust the rules the protocol enforces.

Audits continue. Heads-down.

Don't trust, Verify 🟧

Scheduled maintenance: July 2, 13:30–15:30 UTC (2 hrs). ...

2026-07-01T19:25:36Z

Scheduled maintenance: July 2, 13:30–15:30 UTC (2 hrs).

Surge.credit will undergo scheduled maintenance across both the mobile apps and the protocol.

⚠️The full system will be temporarily unavailable during this window, please plan any actions ahead of time.

➕This release ships Extend Credit Line and Delinquency. Full details to follow.

🟢 Your Bitcoin stays safe throughout: BTC remains secured in your Taproot vault for the entire window.

Don't trust, verify.

Surge protocol — Week 12. 10.52 btc locked in Taproot Vaults. ...

2026-06-26T17:23:43Z

Surge protocol — Week 12. 10.52 btc locked in Taproot Vaults.
Steady tick up while the team stays heads-down on audits.

The bigger update this week: App store approvals are done and last week's auth-related changes are live in production.

Protocol layer held during the outage. Application layer is now hardened against the same failure mode. Both layers, working as designed.

Audits continue. Shipping continues.

Don't trust, Verify 🟧

Most bitcoin lending hides liquidation behind a custodian. DLCs ...

2026-06-23T17:57:26Z

Most bitcoin lending hides liquidation behind a custodian. DLCs weld it into one oracle, forever. Both work fine until they don't.

This week: the liquidation leaf. A threshold network signs, not a custodian. The oracle can evolve. The auction is permissionless. BTC delivered to the bidder on bitcoin.

Don't trust. Verify. 👇

quoting
naddr1qv…p8pu

Last tuesday we covered NUMS, the construction that disables the key-path backdoor on every taproot vault, so every spend has to satisfy one of the three tapscript leaves. We've already walked through two of them: exit, the borrower's unilateral path home, and the nums internal key that makes those leaves the only spending surface. This week is the leaf most vaults will live and die by: Repayment.

Script anatomy: What the repayment leaf is made of?

The repayment leaf is the cooperative spend path. It closes a credit line when the borrower pays back what they owe, and releases collateral proportionally on a partial repayment while keeping the line open.

The script is short. It commits a 32-byte vaultId, drops it from the stack, then requires two schnorr signatures, one from userPubkey (the borrower) and one from loanPubkey (the dcn). The check is op_checksig followed by op_checksigadd == 2, the standard tapscript way of saying "both signatures must be valid." Neither side can spend through this leaf alone. The cooperative requirement is in the script, not in a service agreement.

Hard isolation: The VaultId commitment

VaultId is a 32-byte value committed inside every repayment leaf, computed as keccak256(abi.encodePacked(userEvmAddress, nonce)). It encodes which borrower and which credit line the vault belongs to, and no two vaults share it.

A witness produced for alice's vault cannot be replayed against bob's, because bob's leaf encodes a different vaultId and the script won't validate. Hard isolation at the script level, not soft isolation at the bookkeeping level. Vault a has no script path to vault b. The blast radius of any single position is exactly one position, enforced by Bitcoin.

the DCN is not the custodian

The repayment leaf requires the dcn's signature, which raises the obvious question: who signs for the dcn?

The DCN ( Distributed Custody Network ) is the network of signers that holds threshold shares of the loanPubkey. The loanPubkey itself is an aggregate x-only key produced by a 3-of-4 threshold schnorr signing session (Lin24, BIP340). No single signer holds the private key. There is no "the DCN" in the sense of a single party with credentials to sign. There is a quorum, and signatures only get produced when enough independent signers participate.

That distinction is what makes repayment non-custodial. In custodial lending, the second signature on a 2-of-2 closure comes from one custodian and that custodian, by definition, holds something that could move your collateral if compelled. In surge's model, no individual party can produce the dcn's signature. The threshold is mathematical, not policy. A subpoena to any single dcn signer doesn't reach into your vault any more than a subpoena to a single Bitcoin miner reaches into the chain.

The cooperative requirement in the script, "both signatures must be valid", sounds like a multisig with two parties. It's actually a multisig with you on one side and a network on the other.

The Borrower's single key signs Bitcoin and controls the USDC

The other half of the non-custodial story is what's holding userPubkey. The answer is: the borrower, with a single private key that they hold themselves and that surge never sees.

The detail that's easy to miss is that the same key controls both sides of the credit line. The borrower's private key signs the schnorr signature on the Bitcoin repayment leaf, and the corresponding evm address derived from that same key is where surge delivers the usdc against the collateral. One key, two networks. No platform-issued account, no surge-managed wallet, no hand-off between a Bitcoin identity and a dollar identity that depends on us linking them correctly.

Different posture from most lending products, where the borrower holds a Bitcoin wallet, the platform holds a dollar account on their behalf, and the link between the two is administrative — kyc records, account ids, a support ticket if something goes wrong. In surge, the link is cryptographic. The same secret that proves the borrower can sign the repayment also proves they own the address that received the usdc.

When the repayment leaf is satisfied, the borrower has signed for both halves of the trade: the btc being released back to them on Bitcoin, and the usdc obligation they hold on evm. Self-custody isn't a label on one side of the architecture. It's enforced on both.

Why it scales credit

Credit's destroyer isn't a single bad loan, it's contagion. One position's collateral getting tangled with another's. One liquidation cascading into a margin call that wasn't supposed to be triggered. Pooled credit scales the blast radius, not the safety. More activity through a shared structure means more positions a single failure can touch.

The repayment leaf is one of the places we refused to make that trade. Every taproot vault is its own UTXO, its own script tree, its own vaultId. Repayment for one vault has no script path to another. The blast radius of any single position is exactly one position, enforced by Bitcoin. The dcn signs by threshold, not by custodian. The borrower signs with their own key, on both sides of the trade.

That isolation and that non-custodial posture were built in on day one, before there was a book to protect.

The credit book grows. The blast radius does not. The thing you have to trust does not.

Don't trust. Verify. 🟧

Surge Protocol — Week 11. 10.24 BTC locked in Taproot Vaults. ...

2026-06-18T22:06:13Z

Surge Protocol — Week 11. 10.24 BTC locked in Taproot Vaults. New all-time high, +29.6% w-o-w.

Last week's dip was an exit. This week's high is new locks. Both are the system working as designed.

The deeper signal from last week: Our app authentication service had a brief outage. The protocol stayed up.

Taproot Vaults sat on-chain, untouched. Spending paths unchanged. Borrower keys still the only key required to sign exit. UTXOs indifferent to whether our login flow was loading.

The two-layer split exists for exactly this reason. Application can go down. Protocol doesn't. Trust the architecture, not the company running it.

Audits continue. Heads-down.

Don't trust, Verify 🟧

App auth went down this week. The Bitcoin in our Vaults ...

2026-06-16T17:12:48Z

App auth went down this week. The Bitcoin in our Vaults didn't notice.

Two layers. The Bitcoin layer holds your collateral by script. The app layer is where we work. The first doesn't depend on us. The second is what we fix.

This week's tech tuesday: the repayment leaf. How cooperative spends actually run, why the dcn isn't a custodian, and why your one key signs both the BTC and the USDC. 👇

quoting
naddr1qv…p8pu

Last tuesday we covered NUMS, the construction that disables the key-path backdoor on every taproot vault, so every spend has to satisfy one of the three tapscript leaves. We've already walked through two of them: exit, the borrower's unilateral path home, and the nums internal key that makes those leaves the only spending surface. This week is the leaf most vaults will live and die by: Repayment.

Script anatomy: What the repayment leaf is made of?

The repayment leaf is the cooperative spend path. It closes a credit line when the borrower pays back what they owe, and releases collateral proportionally on a partial repayment while keeping the line open.

The script is short. It commits a 32-byte vaultId, drops it from the stack, then requires two schnorr signatures, one from userPubkey (the borrower) and one from loanPubkey (the dcn). The check is op_checksig followed by op_checksigadd == 2, the standard tapscript way of saying "both signatures must be valid." Neither side can spend through this leaf alone. The cooperative requirement is in the script, not in a service agreement.

Hard isolation: The VaultId commitment

VaultId is a 32-byte value committed inside every repayment leaf, computed as keccak256(abi.encodePacked(userEvmAddress, nonce)). It encodes which borrower and which credit line the vault belongs to, and no two vaults share it.

A witness produced for alice's vault cannot be replayed against bob's, because bob's leaf encodes a different vaultId and the script won't validate. Hard isolation at the script level, not soft isolation at the bookkeeping level. Vault a has no script path to vault b. The blast radius of any single position is exactly one position, enforced by Bitcoin.

the DCN is not the custodian

The repayment leaf requires the dcn's signature, which raises the obvious question: who signs for the dcn?

The DCN ( Distributed Custody Network ) is the network of signers that holds threshold shares of the loanPubkey. The loanPubkey itself is an aggregate x-only key produced by a 3-of-4 threshold schnorr signing session (Lin24, BIP340). No single signer holds the private key. There is no "the DCN" in the sense of a single party with credentials to sign. There is a quorum, and signatures only get produced when enough independent signers participate.

That distinction is what makes repayment non-custodial. In custodial lending, the second signature on a 2-of-2 closure comes from one custodian and that custodian, by definition, holds something that could move your collateral if compelled. In surge's model, no individual party can produce the dcn's signature. The threshold is mathematical, not policy. A subpoena to any single dcn signer doesn't reach into your vault any more than a subpoena to a single Bitcoin miner reaches into the chain.

The cooperative requirement in the script, "both signatures must be valid", sounds like a multisig with two parties. It's actually a multisig with you on one side and a network on the other.

The Borrower's single key signs Bitcoin and controls the USDC

The other half of the non-custodial story is what's holding userPubkey. The answer is: the borrower, with a single private key that they hold themselves and that surge never sees.

The detail that's easy to miss is that the same key controls both sides of the credit line. The borrower's private key signs the schnorr signature on the Bitcoin repayment leaf, and the corresponding evm address derived from that same key is where surge delivers the usdc against the collateral. One key, two networks. No platform-issued account, no surge-managed wallet, no hand-off between a Bitcoin identity and a dollar identity that depends on us linking them correctly.

Different posture from most lending products, where the borrower holds a Bitcoin wallet, the platform holds a dollar account on their behalf, and the link between the two is administrative — kyc records, account ids, a support ticket if something goes wrong. In surge, the link is cryptographic. The same secret that proves the borrower can sign the repayment also proves they own the address that received the usdc.

When the repayment leaf is satisfied, the borrower has signed for both halves of the trade: the btc being released back to them on Bitcoin, and the usdc obligation they hold on evm. Self-custody isn't a label on one side of the architecture. It's enforced on both.

Why it scales credit

Credit's destroyer isn't a single bad loan, it's contagion. One position's collateral getting tangled with another's. One liquidation cascading into a margin call that wasn't supposed to be triggered. Pooled credit scales the blast radius, not the safety. More activity through a shared structure means more positions a single failure can touch.

The repayment leaf is one of the places we refused to make that trade. Every taproot vault is its own UTXO, its own script tree, its own vaultId. Repayment for one vault has no script path to another. The blast radius of any single position is exactly one position, enforced by Bitcoin. The dcn signs by threshold, not by custodian. The borrower signs with their own key, on both sides of the trade.

That isolation and that non-custodial posture were built in on day one, before there was a book to protect.

The credit book grows. The blast radius does not. The thing you have to trust does not.

Don't trust. Verify. 🟧

Watch the full founders' take on YouTube ...

2026-06-15T18:58:25Z

In reply to nevent1q…pdn2
_________________________

Watch the full founders' take on YouTube 👉https://youtu.be/GrR_OUcYttY

App authentication went down. Your bitcoin didn't. The app ...

2026-06-15T18:58:05Z

App authentication went down. Your bitcoin didn't.

The app became unusable. The protocol never blinked. No vaults touched, no funds affected, your BTC stayed in its Taproot Vault the whole time.

That's not luck. It's architecture. The app is just a window. The protocol lives on bitcoin.

Yash and Michael break it all down in our new founders' take: the two-layer design, bring-your-own-key, taproot vaults, BIP-110, and the DCN connecting Bitcoin and Base.

Android is live in the store; iOS is on testflight while we clear review.

An app outage never put a single sat at risk. That's design.

🚨 App authentication is temporarily down. Your Bitcoin is not. ...

2026-06-12T15:34:55Z

🚨 App authentication is temporarily down. Your Bitcoin is not. 🚨

We've run into an issue with our app authentication service, the layer that handles email OTP verification and keeps you signed in. We're fixing it now and adding a fallback to make it more resilient.

👉 No funds or protocol functions are affected; this is a front-end issue only.

🟡 What this means: existing users may get signed out, and new sign-ups are paused until this is resolved. The protocol itself is untouched, your BTC is in its Taproot vault exactly where it was, unilateral exit path unchanged.

🟧 Verify it yourself: the earn dashboard at earn.surge.credit is live and running, independent of the app. App fixes have to go through app store review, which is why this takes a little longer to resolve on the front end.

🟢 Your options, no rush:

1️⃣ Use a TestFlight (iOS) / open testing (Android) build, links coming soon
2️⃣ Or wait for the production fix, currently in the normal app store review queue (can take a few days)

We'll post here the moment the production update is live.

⚠️One thing to watch: no need to panic. Refer only to our in-app messages and official social handles. Stay away from any scams.

Don't trust. Verify 🟧

Partial Withdrawals are live on Surge 🎉 Until now, pulling ...

2026-06-11T21:42:39Z

Partial Withdrawals are live on Surge 🎉

Until now, pulling Bitcoin collateral meant fully repaying your credit line first, even if your taproot vault held far more than your debt required. that's done.

When your credit line is below 50%, you can now withdraw excess collateral straight to your self-custodial wallet. The vault stays intact: every tapscript spending path and your unilateral exit, untouched.
draw, repay, and now withdraw, on your terms. Full flexibility for Bitcoiners, as far as it gets.

Full walkthrough 👇

https://youtu.be/qA_1x0OVSVc

💯

2026-06-11T17:53:29Z

In reply to nevent1q…zuxd
_________________________

💯

8% ≠ 14% Every bitcoin lending product sells you one number. ...

2026-06-10T21:56:19Z

8% ≠ 14%

Every bitcoin lending product sells you one number. The APR. And it's not a lie, the rate is real, and it's usually the biggest single piece of what you pay. But it's almost never the whole thing, and the distance between the headline and the total is the part nobody puts on the homepage.

So let's build the real number. Line by line. Watch it move.

Start low. 8%. The kind of rate the most aggressive products lead with, and to be fair, it's a good number. It's also the floor, what you pay before anything else gets added. Keep it on screen.

8%

1️⃣ Origination first. One to two percent on average, up to three on some sizes. Call it two. And here's what matters: on a revolving line, that fee can hit every draw, not once at the start. So it isn't a setup cost you pay and forget. It's borrow cost. Every time you pull.

8% + 2% = 10%

2️⃣ Repayment next. Some charge you to pay the thing back down, a few tenths of a percent on the way out. Others just won't let you prepay cleanly, which is worse, because now your own flexibility is the penalty. Call it half a point.

8% + 2% + 0.5% = 10.5%

3️⃣ Then the one almost everyone misses: the fee for just being in the loan. Maintenance fee. Platform fee. "Capital charge" if you're talking to the newer crowd. Same mechanic underneath, a recurring annual charge, usually sitting on your borrowed balance, for the position simply existing. Roughly two percent.

8% + 2% + 0.5% + 2% = 12.5%

And we were generous the whole way down. Origination runs to three. The 8% was the headliner tier, borrow less and you often price higher from the start. Add a margin call or a forced repay in a volatile week and there's more. The honest all-in number on much of the market sits closer to 13–14%.

So the rate you were sold was 8%. The cost you actually carry is closer to 14%. Same loan. Same collateral. The headline was real, it was just never the whole number. Independent comparisons keep landing in the same place: fees can push the effective rate fifty percent or more above the sticker.

And none of it is technically hidden. It's all in the docs. It's just scattered five pages, a calculator, a fee schedule while the single cheapest number gets the homepage to itself. That's not an accident. The headline is built to be read. The total is built to be assembled by you, later, if you bother.

So, builder to borrower, here's the wisdom:
Never compare headline APRs. Compare effective cost. The rate plus every fee you'll actually trigger, at your size, across the full life of the loan. And ask any lender one question, what's my all-in cost, per dollar borrowed, per year? If they can't give you one number, that's your answer.

Don't trust, Verify 🟧

Some of the best surge coverage yet, from the PBJ podcast, Steve ...

2026-06-08T22:35:16Z

Some of the best surge coverage yet, from the PBJ podcast, Steve lee, DK, and Max, Bay area bitcoiners.

They unwound the inner workings, not just the surface:

1️⃣ Bitcoin-native : btc stays on bitcoin. no wrapping, no bridging, no leaving the chain.

2️⃣ A revolving credit line, not a loan and no kyc. borrow against your BTC without handing over your identity.

3️⃣ Taproot used the way it was designed, not chain spam. the NUMS key (SHA256("SURGE-NUMS")) closes the backdoor taproot otherwise leaves open, provably unspendable internal key, so the only paths are the tapscript ones.

4️⃣ Unilateral exit, the CSV timelock matches the credit line's term, so you can always sweep your own UTXO back without anyone's cooperation.

5️⃣ No riding morpho or existing defi markets. Surge bootstraps its own liquidity. one of its kind, and bitcoin-native to the core.

and they pressed where it matters, DCN trust assumptions, oracles. The open questions. exactly the ones to ask.

Surge starts ~9 min in 👉 https://www.youtube.com/watch?v=we7gHhi9xiY

This week at Surge. We crossed 10 BTC locked in collateral. Every ...

2026-06-05T21:07:01Z

This week at Surge.

We crossed 10 BTC locked in collateral. Every satoshi sits in a Taproot vault the borrower can exit unilaterally. No rehypothecation, no IOU.

1️⃣ Mon: release notes, what shipped
2️⃣ Tue: deep dive on unilateral exit, the Tapscript spending path that lets you reclaim collateral without anyone's permission
3️⃣ Wed: same mechanism, borrower's lens, why unilateral exit is the difference between a credit line and a custodial IOU when things go wrong
4️⃣ Thu: 10 BTC milestone, and a maintenance window to harden the signer set as part of our ongoing audits

Putting the system into maintenance to harden it is the kind of thing you only do when you've got nothing to hide.

Don't trust. Verify🟧

Scheduled maintenance: June 5, 08:00–08:30 UTC (30 min). This ...

2026-06-05T05:06:59Z

Scheduled maintenance: June 5, 08:00–08:30 UTC (30 min).

This release ships security hardening, including remediations from our ongoing security audit.

🟧 Full report to follow.

✅ Your BTC stays in your Taproot vault throughout, unilateral exit unaffected

The hardest question in Bitcoin lending! Bitcoin is a bearer ...

2026-06-03T23:00:49Z

The hardest question in Bitcoin lending!

Bitcoin is a bearer asset and that one fact should change how you think about every loan you take against it.

Whoever can sign for Bitcoin owns it. No chargeback, no recovery department, no court that reverses a spend. So the moment you post it as collateral and sign it into a lender's custody, ownership has effectively moved. That's not a flaw in any single lender. It's the nature of the asset.

Now layer on the standard terms. Most Bitcoin loans run around 50% LTV, you borrow a dollar against two dollars of BTC. You're over-collateralized by design, which means the asset you've handed into someone else's control is worth materially more than the money you walked away with.

So the question that matters isn't "will they treat me fairly while they're running." Most lenders are legit and will. It's this:

🚨 If they go down, you still have your borrowed dollars, but what happens to the Bitcoin, the part that's worth more than the loan? 🚨

That's the exposure nobody quotes you. Your dollars are already in your pocket. Your collateral, the larger number sits in a custody arrangement that quietly assumes the lender keeps existing. A withdrawal portal doesn't change that: a portal is a permission, and permissions need someone alive to grant them.

A real answer can't live in a terms-of-service doc. It has to live in Bitcoin itself, a spending path on your collateral that returns it to you, and only you, even if the lender and everyone coordinating it is gone. Script as the final authority, not the company's survival.

It's a hard standard, and it's the one we built Surge around. But the question belongs to you wherever you borrow. You gave up custody of the larger asset, make sure you know exactly how you get it back.

Don't trust. Verify. 🟧

Taproot isn't a privacy upgrade. It's the most ...

2026-05-26T22:39:33Z

Taproot isn't a privacy upgrade. It's the most programmable thing bitcoin ever shipped and almost nobody uses it.

surge (nprofile…h2hy) built its whole non-custodial credit stack on it. A key-path backdoor we provably don't have. Three spend paths you can read. An exit enforced by script, not by us.

Don't trust. Verify. 👇

quoting
naddr1qv…l925

Ask most of bitcoin what taproot did and you get three answers: multisig that looks like single-sig, better privacy, cheaper fees. All true. All the small version.

Those are side effects. Taproot is the most expressive programmable upgrade bitcoin has ever shipped and almost nobody is building on what it actually unlocked.

A Taproot output commits to two things at once: a key path, and a tree of tapscript spend conditions. The tree lives off-chain. It never hits the chain unless a branch gets used and even then, only that branch shows. Commit to many conditions, reveal one, hide the rest. No consensus change required.

That's not a fee trick. That's programmable money with privacy baked into the structure.

The teams actually pushing it prove the point. ArkLabs (nprofile…pl3m) pools users into one taproot output, every leaf a VTXO, everyone able to walk out alone. BitVM commits a whole computation to a Taptree, one leaf per gate, only touching chain in a dispute. Different problems, same insight and the surface is barely scratched.

We're building the biggest non-custodial bitcoin-native credit book ever. A surge vault is a pay-to-taproot output that holds your btc and can only move when one of three pre-committed spend paths is satisfied.

And it starts with killing the key.

The NUMS key

A live key path is a backdoor a way your collateral could move without satisfying the contract. So we set the taproot internal key to a nums point. Nothing up my sleeve. Derived deterministically:
sha256("surge-nums") → 6a1bac…175423f2
There's no private key for it. Key-path signing isn't available, full stop. Every spend has to reveal and execute a script leaf. And you don't take our word for it, recompute the hash yourself.

Don't trust that we won't move your coins. Verify that we can't.

With the key path dead, all three real spends live in the tree, out in the open:

1️⃣ Repayment. User + dcn co-sign. Cooperative close only, neither side moves it alone. The leaf commits a vaultId so a witness can't be replayed against another position.

2️⃣ Liquidation. Dcn signature, authorized only on a collateral-ratio breach or end-of-term delinquency. Same script, different trigger. Not a lever someone pulls when they feel like it.

3️⃣ Unilateral Exit. The one that matters.

The exit leaf enforces OP_CHECKSEQUENCEVERIFY, a ~1-year relative timelock, then needs only your signature. If the DCN and the whole coordination layer vanish, you wait out the timelock and recover your btc alone. No permission, no counterparty. Not a terms-of-service line that assumes we're still around to honor it, a recovery guaranteed by bitcoin script.

That's the real meaning of non-custodial: your control outlives everyone else's failure. Exit is where that's real or it's marketing.

Custodians ask you to trust the coins are still there, still yours, un-rehypothecated. Surge hands you verification instead, a NUMS key you can recompute, three leaves you can read, an exit enforced by a timelock. Bitcoin script is the final authority. Off-chain services can ask; btc only moves when a committed leaf is satisfied on-chain.

Taproot wasn't convenient. Convenient was holding the coins ourselves. It was the only thing consistent with credit you can verify and leave.

Spec's all public → https://docs.surge.credit/tech/vaults

Don't trust. Verify. 🟧

Surge Protocol · Week 7 9.04 BTC locked → +2.7% WoW Every sat ...

2026-05-22T01:16:06Z

Surge Protocol · Week 7
9.04 BTC locked → +2.7% WoW

Every sat verifiable on-chain. No custody, no rehypothecation, no trust required. Don't trust. Verify. 📈

Full independent review by @nprofile…j4fc → ...

2026-05-21T22:55:14Z

In reply to nevent1q…gg5k
_________________________

Full independent review by bitcoin (nprofile…j4fc) → https://www.bitcoin.diy/reviews/surge-credit

Independent review from @nprofile…j4fc is in. Surge Credit: ...

2026-05-21T22:54:01Z

Independent review from bitcoin (nprofile…j4fc) is in.

Surge Credit: 7.5/10

What they validated:
◆ Custody model 10/10 — "best in class"
◆ Taproot vault on mainnet, key-path spend mathematically disabled
◆ Unilateral exit: recover your BTC yourself if Surge disappears
◆ Zero rehypothecation, verifiable on-chain

What's still open — and we're on it:
◇ EVM audit (in selection)
◇ DCN signers public in June
◇ No liquidation cascade survived on mainnet yet

Don't trust. Verify. Review in comments. 👇

"Liquidation LTV: 80%." One line on your dashboard. Reads ...

2026-05-20T19:02:41Z

"Liquidation LTV: 80%." One line on your dashboard. Reads simple. It isn't.

It's three decisions:

1️⃣ The line : industry ~80%, margin calls ~70%.

2️⃣ Your draw LTV : the only dial you hold. 80% line, draw 50% → BTC falls ~37% before you're cut. Draw 70% → ~12% does it.

3️⃣ Full or partial : full closes everything. Partial cures you back to a target. And mind the gap: cure to 75% from an 85% trigger = thin buffer, re-liquidates easily. Cure to 65% = real room. Higher isn't safer. Read both numbers, they differ by platform.

Size to survive a February. Don't trust, verify.

Slides 👇

Yes, on the roadmap

2026-05-20T15:02:24Z

In reply to nevent1q…95kf
_________________________

Yes, on the roadmap

Three layers in any TSS deployment, and the post-THORChain ...

2026-05-19T20:12:49Z

Three layers in any TSS deployment, and the post-THORChain conversation has been mixing them:

Protocol — Schnorr/BIP340 ≠ ECDSA. The MtA surface that produced TSSHOCK doesn't translate.
Posture — every signer is critical infrastructure. Software-only is insufficient.
Architecture — TSS as one Taproot spending path, not the whole security model.

Don't trust, verify. At every layer.

https://primal.net/surge/the-right-way-to-lose-your-threshold-key

Thanks for encouraging us to do so.

2026-05-18T18:16:58Z

In reply to nevent1q…hxm6
_________________________

Thanks for encouraging us to do so.

Full walkthrough here: https://youtube.com/watch?v=zeaPEQYZh1I ...

2026-05-14T17:52:12Z

In reply to nevent1q…8c7y
_________________________

Full walkthrough here: https://youtube.com/watch?v=zeaPEQYZh1I

Covers wallet connect, depositing into the variable-rate market, fixed-rate exposure, and the Bitcoin collateral side of the flywheel.

~9 mins. Worth it if you want to see how the lender side actually works.

The most common question from Bitcoiners borrowing on Surge: ...

2026-05-14T17:51:28Z

The most common question from Bitcoiners borrowing on Surge: where does the capital come from? 🤔

Answer: anyone, permissionlessly. Connect an EVM wallet, deposit USDC on Base, earn yield backed by Bitcoin collateral in Taproot vaults you can verify yourself.

No KYC. No synthetic collateral. No rehypothecation.

Don't trust. Verify.

Full walkthrough of the Earn dashboard in the replies. 💬

give it a shot and tell us

2026-05-14T17:41:20Z

In reply to nevent1q…4c0t
_________________________

give it a shot and tell us

Inside Surge Credit ✉️ → ...

2026-05-14T02:24:30Z

In reply to nevent1q…ydr2
_________________________

Inside Surge Credit ✉️ → https://surgecredit.substack.com/p/bitcoin-native-is-not-equal-to-wrapped

"So Surge is basically the same as WBTC?" → No ← WBTC ...

2026-05-14T02:24:08Z

"So Surge is basically the same as WBTC?"

→ No ←

WBTC is a custodial IOU. Surge keeps your BTC in a Taproot vault enforced by Bitcoin, with unilateral exit.

Not your keys, not your coins. That answer is the whole product.

Our founder covers this in our weekly newsletter 👇

Watch full walkthrough here → ...

2026-05-12T19:41:46Z

In reply to nevent1q…nuem
_________________________

Watch full walkthrough here → https://www.youtube.com/watch?v=wnFYJcDvszI

The reason most Bitcoiners use custodial lenders isn't ...

2026-05-12T19:40:15Z

The reason most Bitcoiners use custodial lenders isn't ideology. It's UX.

Non-custodial has been slower, clunkier, and more expensive for years. So self-custody became the principled choice and custody became the practical one.

We recorded a walkthrough that shows the trade-off isn't real anymore. No KYC. No credit check. ~6.9% APR. Collateral in a Taproot vault you verify yourself.

Don't trust. Verify.

Link in replies.

Yes

2026-05-11T02:39:30Z

In reply to nevent1q…936z
_________________________

Yes

Day 3. Kept hearing the same thing yesterday: “Most real booth ...

2026-04-29T16:59:16Z

Day 3.

Kept hearing the same thing yesterday:
“Most real booth here.”

Not flashy. Just showing how it actually works.
Bitcoiners care about that.

Also had our power users pull up — sharing real usage, bringing friends over. That’s the signal.
Product is getting validated in the open.

Day 3. Let’s go.

ACH, Card coming soon, for vouchers we directly work with the ...

2026-04-28T17:18:27Z

In reply to nevent1q…xuzc
_________________________

ACH, Card coming soon, for vouchers we directly work with the distributors like bitrefill does.

Its most usable stable coin out in the market, USDC.

No-KYC

2026-04-28T17:01:40Z

In reply to nevent1q…2tp3
_________________________

No-KYC

Day 2 at Bitcoin Vegas — nonstop. “Wait… I can borrow how ...

2026-04-28T17:01:21Z

Day 2 at Bitcoin Vegas — nonstop.

“Wait… I can borrow how much I want? And it starts at 6.9%?”

That’s the moment.
Booth’s been packed.
Bitcoiners getting it instantly.

Demos → questions → rethinking everything they use today.

This is what we came for. Let’s go. 🚀

Surge is now in public beta 🎉 After months in private beta, ...

2026-04-27T16:14:23Z

Surge is now in public beta 🎉

After months in private beta, Surge is open for anyone to download and try — a Bitcoin-native dollar credit line built for Bitcoiners.

We’re already 8 BTC in, and users are actively opening credit lines.

It’s credit, not a loan.

Download Surge and try it today.

Michael Borglin (Co-founder & CPO, Surge) is at the Bitcoin ...

2026-03-05T17:19:06Z

Michael Borglin (Co-founder & CPO, Surge) is at the Bitcoin Ski Summit in Jackson Hole.

We’re here to swap notes on bitcoin-native credit, how to access liquidity without giving up sovereignty (no op aque custody, no “trust me bro”).

If you’re around, come say hi. 👋⚡️