TheRawByte retweeted
This year feels like fixed-rate lending season.
Every few weeks, another lending market seems to be announcing a fixed-rate product.
And honestly, that’s a good thing.
But launching a fixed rate is the easy part.
The hard part starts after “5% for six months” is written down.
- Who provides that liquidity?
- Who holds the duration?
- How does the lender get out early?
- What happens when the six months are up?
That’s the part we’re digging into in our deep dive, live today.
Can I borrow $10M at 5% for six months?
That question is why lending protocols are suddenly obsessed with fixed rates.
DeFi lending assumed borrowers who could manage a position as rates moved. An RWA desk financing a Treasury or private-credit book can't. It needs a known cost of capital for a defined period.
Once borrowing goes fixed-rate, the hard parts move:
→ Who provides the liquidity, and who takes the duration risk?
→ What happens when the lender wants out?
→ What happens when the loan matures?
I went through how @Morpho, @TenorFinance, @longbowlend, @term_finances, @kamino, @Loopscale and @flexmeow each answer those three.
(SOUND ON!)
TheRawByte retweeted
5 key takeaways from the upcoming deep dive on fixed-rate lending:
before you dive in, play the video first ;)
1. Fixed rates are solving one core problem: predictability
Variable-rate lending gives users instant liquidity, but the borrowing cost can change sharply with utilisation. Fixed-rate markets let borrowers know their debt cost upfront and lenders know their expected return.
2. The borrower is changing
Fixed rates become more useful as DeFi moves beyond crypto-native borrowing into RWAs, institutional strategies, treasuries, basis/carry trades and credit. These users often need debt terms that match a specific investment horizon rather than an ever-changing pool rate.
3. Fixed rates create a new market-structure problem: duration
Once you lock a rate, liquidity gets fragmented across maturity, rate and collateral. The lender now has to think about how long capital is locked and how to exit before maturity. In other words, fixed rates don't remove risk, they make duration risk explicit.
4. The biggest protocols are attacking the liquidity problem in different ways
@Morpho Midnight uses intent-based offers and callbacks to avoid idle capital, @TenorFinance adds auto-renewal, fallback and OTC functionality; @JupiterExchange uses maturity-based collateral transfer; and @kamino builds fixed-rate liquidity into a rate × duration grid with withdrawal queues.
5. Curators may become much more important
Fixed-rate lending creates more moving parts for allocators: they need to manage maturities, collateral, liquidity and refinancing. That creates room for professional curators and vaults to abstract the complexity and package predictable credit products for larger capital.
Can I borrow $10M at 5% for six months?
That question is why lending protocols are suddenly obsessed with fixed rates.
DeFi lending assumed borrowers who could manage a position as rates moved. An RWA desk financing a Treasury or private-credit book can't. It needs a known cost of capital for a defined period.
Once borrowing goes fixed-rate, the hard parts move:
→ Who provides the liquidity, and who takes the duration risk?
→ What happens when the lender wants out?
→ What happens when the loan matures?
I went through how @Morpho, @TenorFinance, @longbowlend, @term_finances, @kamino, @Loopscale and @flexmeow each answer those three.
(SOUND ON!)
TheRawByte retweeted
RWAs are getting tokenized.
But most of that value still isn’t turning into onchain liquidity.
Tokenization is just step one.
TheRawByte retweeted
The Revolut incident makes the need for zk-KYC much, much more obvious.
But it also highlights the weirdest part of the zk-KYC market: the technology solves a very real problem, yet the business model is still weak.
zk-KYC is difficult to make profitable because it sits between two parties that already have the budget. The institution still has to perform the underlying KYC and carry the compliance liability, while the protocol usually just needs a yes/no eligibility check. Once credentials become reusable, each user can generate many verifications without creating many new billable KYC events. And as proving infrastructure gets commoditized, the proof itself becomes harder to differentiate.
That’s why the interesting companies keep moving downstream: @KeyringNetwork into structured lending, Human Passport into Sybil resistance, zkPass into broader private web-data infrastructure, etc.
The need for zk-KYC is getting stronger. The economics of selling zk-KYC alone aren't.
The zk-KYC market has produced plenty of proofs, but it has produced far fewer durable businesses.
Some shut down. Some made verification free. Some launched tokens. Others moved into Sybil resistance, compliance, or financial infrastructure.
So we looked at the actual business model:
Who pays for the proof?
And more importantly, what are they actually paying for?
New piece out today: What’s Wrong With the zk-KYC Business Model
TheRawByte retweeted
Only 8.3% of the $46.4B in onchain RWAs has made its way into DeFi, and nearly half of that ($1.8B) sits in private credit.
TheRawByte retweeted
A–Z Privacy & Cryptography in Web3
A – Anonymous Credentials
Systems like Idemix or zkCred that let users prove membership or identity attributes without revealing everything.
B – Bulletproofs
Short, efficient, non-interactive zero-knowledge proofs for confidential transactions.
C – Commitment Schemes
Cryptographic primitives that let users “commit” to a value without revealing it, then reveal it later.
D – Differential Privacy
A technique to add statistical noise to user data, protecting individual privacy in aggregate analysis.
E – Elliptic Curve Cryptography (ECC)
Widely used in blockchain wallets and signature schemes (e.g. secp256k1, Ed25519).
F – Fully Homomorphic Encryption (FHE)
Allows computations on encrypted data without decryption—still largely impractical but active area of research.
G – Groth16
A popular zkSNARK proving system with succinct, efficient proofs.
H – Hash Functions
Like SHA-256 or Keccak256—core to Merkle trees, commitments, and ZK proof construction.
I – Incremental Merkle Trees
Used in privacy protocols like Tornado Cash for mixing—enables adding leaves without recomputing the entire tree.
J – Join-Split Proofs
Used in shielded transactions (e.g. Zcash) to prove transaction validity without revealing sender/receiver.
K – Key Management
Managing private keys securely is essential—often uses hardware wallets or MPC-based custody.
L – Lattice-Based Cryptography
A post-quantum cryptographic approach, key to future ZK systems and FHE.
M – Multi-Party Computation (MPC)
Collaborative computation without revealing each party’s input.
N – Noise Protocol Framework
Used for encrypted communication (e.g. Signal) in decentralized networks.
O – Oblivious Transfer
Allows a sender to send one of many pieces of information without knowing which one was chosen by the receiver.
P – Privacy Pools
Newer protocols enabling shielded transactions with opt-in compliance features.
Q – Quantum-Resistant Primitives
Cryptographic algorithms designed to resist quantum computer attacks (e.g. lattice-based schemes).
R – Ring Signatures
Used in Monero for transaction privacy; makes it hard to trace the sender among a group of possible senders.
S – SNARKs (Succinct Non-interactive Arguments of Knowledge)
Core to zkRollups, private transactions, and scalability solutions.
T – Trusted Execution Environments (TEEs)
Secure enclaves (e.g. Intel SGX) for confidential computation, even on potentially compromised hosts.
U – Universal Setup
A trusted setup phase used in many SNARK systems (like Groth16)—requires careful design to avoid toxic waste.
V – Verifiable Delay Functions (VDFs)
Introduce time-based unpredictability, important in randomness beacons (e.g. drand).
W – Witness Encryption
Encrypt a message so that only someone who knows a solution to a computational puzzle can decrypt it.
X – XOR-Based Secret Sharing
Simple method to split secrets among multiple parties—used in secure key management.
Y – zk-STARKs
Zero-Knowledge Scalable Transparent ARguments of Knowledge—transparent (no trusted setup) and quantum-secure.
Z – Zero-Knowledge Proofs (ZKPs)
Prove a statement is true without revealing any additional information.
TheRawByte retweeted
gm to everyone except:
– people who still think “just make a new wallet” = privacy
– dApps that bury “privacy” toggles behind 17 menu layers
– folks who still haven’t read Vitalik’s privacy roadmap
and a heartfelt ❤️ gm to the few actually building real onchain privacy↓
TheRawByte retweeted
Everyone says “blockchains are too transparent.”
But the real issue?
Most privacy tech still treats finance as the endgame.
What we actually need is privacy for coordination for identity, messaging, gaming, DAO ops.
Until then, we're just hiding payments in a glass house.
TheRawByte retweeted
Not all onchain privacy tech works the same and not all of it is trustless.
Here’s a breakdown of PETs (Privacy-Enhancing Technologies) and how they’re used in blockchains:
TheRawByte retweeted
The most important shift in crypto today isn’t on price charts, it’s on the privacy layer.
From base chains to apps, onchain privacy is becoming modular, programmable, and compliant.
Welcome to the new era of attestable privacy.
↓ A quick thread:
TheRawByte retweeted
Privacy always sounds like a “nice-to-have”...
...until you're being tracked, scraped, profiled, or front-run.
Blockchain’s biggest blindspot? Treating privacy like a feature, not a foundation.
One Venn to rule them all ↓









