Alex Nick

·

--

$BTC is approaching a decision point.

Price continues to compress between $60K support and $67K resistance.

Bulls have defended every dip so far, but they still haven't reclaimed the major supply zone.

A daily close above $67K = momentum shift.

A loss of $60K = liquidity hunt toward $56K–58K.

The longer Bitcoin ranges, the more explosive the breakout will be.

·

--

Some of the largest hacks in crypto history came from bridges and wrapped assets, not from Bitcoin itself. That has always bothered me as someone who writes about this space, because the risk was never really Bitcoin, it was the wrapping and bridging layered on top of it.

Trustless Bitcoin Vaults (TBV) from @BabylonLabs_io removes that layer completely. There is no wrapped token standing in for your BTC and no bridge holding it in the middle. TBV lets native Bitcoin function as collateral directly, so that attack surface is simply not part of the design.

The first application is native Bitcoin backed borrowing through Aave v4, live on public testnet. I deposited native BTC, borrowed USDC, and never touched a wrapped version of my coins. If avoiding bridge risk matters to you too, test the flow yourself and send feedback through the official form before mainnet.

@BabylonLabs_io #baby $BABY

·

--

$SUI is trading in an accumulation zone after a sustained downtrend. A successful hold above support could trigger a recovery toward the $0.72 resistance area, but confirmation is still needed.

SUI+3.64%

·

--

Most people in crypto focus on yield percentages, but what I actually track is contract execution path. For a long time, accessing DeFi meant handing custody over to cross chain bridges or wrapped token contracts, which basically turns hard native Bitcoin into soft counterparty promises.
The mechanism behind Trustless Bitcoin Vaults (TBV) flips that risk model completely upside down. By locking underlying Bitcoin in Taproot scripts right on the Bitcoin base layer, TBV generates cryptographic state verification on host chains instead of moving the actual assets. You can post native BTC collateral to borrow stablecoins on host protocols like Aave v4, but the primary asset stays bound by Bitcoin network rules. It moves the entire conversation from trusting multi sig custodians to evaluating raw cryptographic proofs and execution logic.
What makes TBV really compelling from a risk manager perspective is how it isolates vault level failures. Even if external application layers hit extreme volatility, the underlying Bitcoin redemption paths remain presigned and verifiable onchain. Eliminating bridging wrapped risk doesn't remove smart contract evaluation entirely, but it certainly cleans up the counterparty risk surface area. Which matters more to your portfolio strategy: maximizing raw lending yield or tightening execution security?
@BabylonLabs_io #baby $BABY

·

--

I spent time testing the native Bitcoin backed borrowing integration on Aave v4 public testnet, and the workflow feels like a major shift for onchain collateral. Most existing DeFi lending setups force users into wrapped tokens or centralized bridges, which introduces massive counterparty risk. With Trustless Bitcoin Vaults (TBV), the underlying asset remains locked on the Bitcoin network while enabling stablecoin borrows like USDC or USDT directly on Ethereum. Setting up a test vault, requesting testnet assets, and walking through the peg in and redemption sequence gives a clear preview of how liquidity can flow without surrendering custody.
The real value of TBV comes down to eliminating third party wrapping risk while maintaining maximum capital efficiency for active market positions. Testing this integration firsthand highlighted how smooth borrowing against native BTC collateral can be when execution logic interacts directly with Bitcoin Taproot scripts. Submitting detailed user feedback through the official testnet form is essential right now, because refining execution speeds and user interfaces during this public phase directly impacts how institutional liquidity adopts these vaults on mainnet. Has anyone else tested the Aave v4 testnet flow yet?
@BabylonLabs_io #baby $BABY

AAVE+2.21%

·

--

Bitcoin has a hard cap and the token securing its expansion into DeFi does not

I almost skipped past this line in the tokenomics docs, then reread it twice. BABY has an infinite supply. No hard cap, ever. Meanwhile the entire reason people trust Bitcoin enough to stake it through Babylon in the first place is because BTC has the opposite property, twenty one million coins, fixed forever, nothing can inflate it away.

That is a strange pairing when you actually sit with it. The asset being secured is defined by scarcity. The token orchestrating governance and security decisions around that asset has no such constraint. Vesting cliffs and unlock schedules controlling supply growth in the near term do not change the long run structural difference between a capped asset and an uncapped one sitting right next to each other in the same system.

I am not saying this breaks anything. Governance tokens rarely need Bitcoin style scarcity to function properly. But there is something almost ironic about Bitcoin holders trusting their capped, hard money to a coordination layer built on the exact monetary policy Bitcoin was designed to reject in the first place.

Maybe that is fine because BABY was never meant to store value the way BTC does. Or maybe it is the kind of detail that gets ignored until token emissions actually start pressuring price years down the line.

Does an infinite supply governance token undermine the hard money principles of what it is coordinating, or are the two simply unrelated by design

@BabylonLabs_io #baby $BABY

BABY+7.08%

·

--

🇺🇸 BREAKING: Markets are now pricing a 38% chance of a Fed rate hike this week.

·

--

Bitcoin cannot run smart contracts and that constraint is the whole design challenge

Here is something people gloss over. Ethereum style restaking works because Ethereum has expressive smart contracts. You can program complex slashing logic, arbitrary conditions, whatever the network needs. Bitcoin has none of that. Bitcoin script is deliberately limited. No loops, no rich state, nothing close to what a modern smart contract can do.

So Babylon had to solve trustless staking inside a system that was never built for this kind of coordination.

That is a much harder engineering problem than people give it credit for.

Timelocks. Multisig constructions. Careful use of what Bitcoin actually allows. No shortcuts through a smart contract layer because there isn't one to lean on.

I keep thinking about what this means practically. Ethereum restaking can iterate fast because the logic lives in flexible contracts. Babylon cannot move that fast by design, every mechanism has to fit inside Bitcoin's constraints, which is slower but also harder to break in unexpected ways since there is less surface area for bugs to hide in.

Slower and more rigid, or slower and safer. Those might be the same thing here.

Does building security on a deliberately limited scripting language make the whole system more trustworthy or just less adaptable long term

@BabylonLabs_io #baby $BABY

·

--

Collateral that never leaves Bitcoin might be the boring detail that matters most

Everyone gets excited about staking yield and security narratives, but the collateral problem in DeFi has always been messier and less talked about. Every lending protocol that wants BTC exposure ends up relying on wrapped tokens, and wrapped tokens carry a silent tax, you are trusting whoever minted that wrapped asset to actually hold what backs it. Most people forget that risk exists until something breaks.

Trustless Bitcoin Vaults are the part of Babylon I think gets underrated. Collateral for DeFi without wrapping, without bridging, without a custodian standing between your BTC and the loan or position it backs. That is not a flashy feature but it solves the exact failure mode that has burned people before when a bridge got exploited or a custodian froze withdrawals.

The interesting tension here is whether DeFi protocols actually want collateral that stays this native, since a lot of existing infrastructure was built assuming wrapped assets with programmable flexibility. Native BTC collateral through TBV might mean less composability in exchange for fewer trust assumptions.

I keep wondering if builders will trade some flexibility for that safety or if convenience wins anyway.

@BabylonLabs_io #baby $BABY

BABY+7.08%

·

--

$BTC has reclaimed the $65,000 level.

The next key resistance is $67,500-$68,000, which means Bitcoin has some room to pump.

If BTC manages to reclaim the $68,000 resistance too, it could rally another 5%-6% very quickly.

·

--

#Bitcoin has now closed three consecutive weekly green candles, but price is still trading below the key weekly resistance at $65,776.
For me, this level remains the line in the sand. Until $BTC can reclaim and close above $65.8K on the weekly timeframe, my higher-timeframe bias stays bearish.

A rejection from here could lead to another short-term pullback. That said, I'm not expecting a major move before the monthly candle closes.

·

--

$SOL is showing strength after the recent pullback. If buyers keep the momentum, a move toward the $78–$80 area looks likely.

SOL+3.73%

·

--

$INJ weekly chart looks bullish and Ready!

Wave 1: 2021 ✅
Wave 2: 2024 ✅
Wave 3: 2026-2027 ?

Sitting at $5.05 inside a multi-year ascending triangle.

If history rhymes, Wave 3 targets 80-100$.

Not financial advice. Just vibes + Elliott.

INJ-1.11%

·

--

Retail Never Actually Wanted Decentralization, We Wanted A Safety Net

Here is the uncomfortable thought that hit me trading on GRVT last week, most retail traders do not care about self custody until the moment they get burned by a centralized platform, and by then it is too late to matter. We talk a big game about wanting control over our own keys, but the second execution gets slow or clunky, we abandon that principle instantly and run back to whatever feels fast.

GRVT is built around that exact contradiction. A 600k TPS matching engine gives me the speed I actually want day to day, while ZK settlement sits quietly underneath as the thing I only think about when something goes wrong. I am not checking proofs before every trade, I am checking my fill price and my slippage like every other session.

So the real question is whether decentralization only matters to us retrospectively, as insurance we forget exists until we need it. If that is true, then the platforms that win are not the ones preaching autonomy, they are the ones fast enough that we never think about the safety net at all until it saves us.

$GRVT capped at 1 billion supply feels almost secondary next to that behavioral puzzle.

Do you actually think about self custody while trading, or only after something breaks ?

@grvt_io #grvt

self custody while trading

0%

after something breaks

0%

0 votes • Voting closed

·

--

Who Actually Holds The Upgrade Keys Is The Question I Keep Coming Back To

$NEWT

The Newton Keystore is a specialized rollup, and every rollup at this stage usually has some multisig or admin key that can push upgrades or pause the system if something breaks. That's normal early infrastructure practice, but it also means the whole zk permission and TEE security model can get overridden by whoever controls that key. Mainnet beta almost always means training wheels are still on, and I want to know exactly who's on that multisig and what the threshold is before I treat this as trustless. A verifiable automation layer isn't fully verifiable if a small group can still flip a switch.

I'm not against upgrade keys existing early on, that's just reality for new rollups. But I want a public timeline for when control actually decentralizes or gets renounced. Admin key risk is the one thing marketing never leads with.

@NewtonProtocol $NEWT #Newt

Newton Versus Keeper Networks Is The Comparison Nobody's Actually Written YetI keep seeing Newton pitched next to generic AI hype instead of its actual competitors. That's lazy. The real comparison is Gelato Network and Keep3r Network, both established players handling basic task execution on command. Neither of those verifies that an agent's action actually matched what the user authorized, they just execute the trigger and trust the script that wrote it. Newton's entire pitch is closing that exact gap with cryptographic proof instead of blind trust in a keeper bot. Revocation is where this gets genuinely user friendly, and it's underrated. A user granting an agent access through zkPermissions can revoke that permission at any point, and because the rule lives in the Keystore rather than a private key handoff, revoking it doesn't require rotating wallets or migrating funds anywhere. You just kill the permission object and the agent loses its authorization instantly, no scramble, no exposure window left hanging. Compare that to a Telegram bot holding your actual keys, where revocation basically means hoping the bot operator listens. DAOs and treasuries are the use case that actually sells this to normal people, not solo traders. A treasury can grant a rebalancing agent narrow permissions, funding limits, specific contract addresses, a defined time window, and every action that agent takes generates a proof tying it back to those exact boundaries. That's auditable by any DAO member without needing to trust a multisig signer's judgment call in the moment, which is a real improvement over how most DAO automation currently works today. My honest take. Verifiable automation sounds academic until you frame it against Gelato and Keep3r, and then it's obviously the more defensible model long term. But defensibility on paper doesn't win developer mindshare overnight, and those keeper networks have years of integrations Newton still has to catch up on. I like the architecture more than I like Newton's current adoption curve, and those two things aren't the same bet. @NewtonProtocol $NEWT #Newt

·

--

Article

Newton Versus Keeper Networks Is The Comparison Nobody's Actually Written Yet

I keep seeing Newton pitched next to generic AI hype instead of its actual competitors. That's lazy. The real comparison is Gelato Network and Keep3r Network, both established players handling basic task execution on command. Neither of those verifies that an agent's action actually matched what the user authorized, they just execute the trigger and trust the script that wrote it. Newton's entire pitch is closing that exact gap with cryptographic proof instead of blind trust in a keeper bot.
Revocation is where this gets genuinely user friendly, and it's underrated. A user granting an agent access through zkPermissions can revoke that permission at any point, and because the rule lives in the Keystore rather than a private key handoff, revoking it doesn't require rotating wallets or migrating funds anywhere. You just kill the permission object and the agent loses its authorization instantly, no scramble, no exposure window left hanging. Compare that to a Telegram bot holding your actual keys, where revocation basically means hoping the bot operator listens.
DAOs and treasuries are the use case that actually sells this to normal people, not solo traders. A treasury can grant a rebalancing agent narrow permissions, funding limits, specific contract addresses, a defined time window, and every action that agent takes generates a proof tying it back to those exact boundaries. That's auditable by any DAO member without needing to trust a multisig signer's judgment call in the moment, which is a real improvement over how most DAO automation currently works today.
My honest take. Verifiable automation sounds academic until you frame it against Gelato and Keep3r, and then it's obviously the more defensible model long term. But defensibility on paper doesn't win developer mindshare overnight, and those keeper networks have years of integrations Newton still has to catch up on. I like the architecture more than I like Newton's current adoption curve, and those two things aren't the same bet.
@NewtonProtocol $NEWT #Newt

·

--

TEE Attestation Is A Trust Assumption Nobody's Pricing In

Newton leans on TEEs to enforce policy before settlement, and that sounds airtight until you remember a TEE is still hardware built by a vendor, running firmware that vendor controls. The whole security model assumes that hardware attestation can't be spoofed or compromised at the chip level. History says otherwise, there have been real world cases where trusted execution environments got broken through side channel attacks nobody predicted until it happened. I'm not saying Newton's setup is weak, I'm saying the zk proof and the TEE together are only as strong as the weakest hardware assumption baked into the design.

I want to know which TEE vendor they're actually using and what their disclosure policy looks like if a vulnerability ever surfaces. My exposure stays capped until that's public. Hardware trust is the one variable in this entire stack I can't verify myself.

@NewtonProtocol #Newt $NEWT

Newton's First Real Agent Is Just A Recurring Buy Bot And Honestly That's The Smart MoveNewton's First Real Agent Is Just A Recurring Buy Bot And Honestly That's The Smart Move Everyone expected Newton to launch with some flashy multi agent trading suite. They didn't. The first agent live on the Protocol is a Recurring Buy Agent, letting users automate scheduled crypto purchases directly onchain instead of relying on a centralized exchange's internal cron job. It's boring by design, and boring is exactly what you want when you're asking regular users to trust a brand new permission system with their wallet. The onboarding side matters more than people give it credit for. Magic Labs built the embedded wallet layer underneath Newton, so a new user doesn't need a browser extension or a seed phrase ritual just to grant an agent scoped access. You sign in, pick an agent from the Model Registry, define your limits through zkPermissions, and the wallet handles the rest quietly in the background. That's a real attempt at making onchain automation feel closer to a normal app than a DeFi terminal. Four roles keep this running. Developers build and publish agent models, operators execute the actual tasks, users submit the automation intents, and validators secure everything through delegated proof of stake. Early on, transaction fees were subsidized to lower the barrier for first time users testing the system, which tells me the team knew gas friction would kill adoption faster than any security concern. Subsidies don't last forever though, and NEWT becomes the required gas token for every permission update once that training wheel comes off. Here's my honest read. A recurring buy bot isn't exciting, but it's the correct first product because it fails safely if something breaks. The real test comes when developers start publishing more aggressive strategy agents into that same registry, competing for the same user trust. I don't think the friendly onboarding survives contact with a bad actor listing a malicious model dressed up as a simple dollar cost averaging tool. Watch the registry curation closely, that's where this either holds together or doesn't. @NewtonProtocol #Newt $NEWT {spot}(NEWTUSDT)

·

--

Article

Newton's First Real Agent Is Just A Recurring Buy Bot And Honestly That's The Smart Move

Newton's First Real Agent Is Just A Recurring Buy Bot And Honestly That's The Smart Move
Everyone expected Newton to launch with some flashy multi agent trading suite. They didn't. The first agent live on the Protocol is a Recurring Buy Agent, letting users automate scheduled crypto purchases directly onchain instead of relying on a centralized exchange's internal cron job. It's boring by design, and boring is exactly what you want when you're asking regular users to trust a brand new permission system with their wallet.
The onboarding side matters more than people give it credit for. Magic Labs built the embedded wallet layer underneath Newton, so a new user doesn't need a browser extension or a seed phrase ritual just to grant an agent scoped access. You sign in, pick an agent from the Model Registry, define your limits through zkPermissions, and the wallet handles the rest quietly in the background. That's a real attempt at making onchain automation feel closer to a normal app than a DeFi terminal.
Four roles keep this running. Developers build and publish agent models, operators execute the actual tasks, users submit the automation intents, and validators secure everything through delegated proof of stake. Early on, transaction fees were subsidized to lower the barrier for first time users testing the system, which tells me the team knew gas friction would kill adoption faster than any security concern. Subsidies don't last forever though, and NEWT becomes the required gas token for every permission update once that training wheel comes off.
Here's my honest read. A recurring buy bot isn't exciting, but it's the correct first product because it fails safely if something breaks. The real test comes when developers start publishing more aggressive strategy agents into that same registry, competing for the same user trust. I don't think the friendly onboarding survives contact with a bad actor listing a malicious model dressed up as a simple dollar cost averaging tool. Watch the registry curation closely, that's where this either holds together or doesn't.
@NewtonProtocol #Newt $NEWT