Kimmjyun

“ Your can't succeed if your Lazy ”
👺

[Kimmjyun @KimJyuun]

How degen are you on-chain? Pull your @Housebets card, find out — and there's something in it for you. @HousebetsWhale drop my card. Use my code: AwkenBET 🃏

[Earnalot @Earnalot888]

Never used an on-chain lottery? Here's the whole thing, start to finish.

Open the Mini App, grab a $1 ticket, watch the contract settle the round and pay the winner.

No forms, no claim step! That's Earnalot!

[Kimmjyun @KimJyuun]

@FastBridgeApp
Multi-asset bridge + swap in a single tx?
This is the future of cross-chain 🚀
https://t.co/burAagmFhD

[FastBridge @FastBridgeApp]

Meet FastBridge ⚡

Built for traders, yield chasers, and anyone whose funds are spread across chains.

Combine multiple tokens from different chains, then swap & bridge them in one transaction.

No more bridging one asset at a time 👇

[Maxxed @maxxedio]

Maxxed Discord is live

Join for a chance to win $10,000

Follow, repost, and drop your Discord usernames to 2X your odds

[Kimmjyun @KimJyuun]

@TokenB_Wallet How much more time needs to be prepared after this

[TokenB @TokenB_Wallet]

🔒 We are fully prepared. Now, we need your verification.

[Kimmjyun @KimJyuun]

Interesting Bitcoin-dev draft! It derives Taproot unspendable internal keys from wallet policy + path — no extra secret r needed.
Key insight: seed backups alone can’t reconstruct the policy. Backup smarter. 🔑 #Bitcoin #Taproot

[DeepSafe @DeepSafe_AI]

A draft posted to bitcoin-dev this month reworks one small piece of taproot backup. It sits in an individual fork, hasn't been assigned a BIP number, and is still in its earliest form.

The draft addresses backup for unspendable internal keys. One existing approach it cites as motivation is to choose a random r and retain it, so the internal key can be recomputed later.

The draft's mechanism derives a chain code from a tagged hash of a normalized wallet policy. That chain code, the fixed NUMS point H, and a selected derivation path together determine the internal key — in a step the draft describes as being done "without additional secret material."

Its Security considerations section states two things: "The policy and selected derivation are enough to reproduce the internal key," and, in the same section, "Seed backups alone do not reconstruct the policy."

Read narrowly, what the draft changes is which inputs are needed to reconstruct that internal key.

Draft: https://t.co/IiCRQuQPcv

[DeepSafe @DeepSafe_AI]

A draft posted to bitcoin-dev this month reworks one small piece of taproot backup. It sits in an individual fork, hasn't been assigned a BIP number, and is still in its earliest form.

The draft addresses backup for unspendable internal keys. One existing approach it cites as motivation is to choose a random r and retain it, so the internal key can be recomputed later.

The draft's mechanism derives a chain code from a tagged hash of a normalized wallet policy. That chain code, the fixed NUMS point H, and a selected derivation path together determine the internal key — in a step the draft describes as being done "without additional secret material."

Its Security considerations section states two things: "The policy and selected derivation are enough to reproduce the internal key," and, in the same section, "Seed backups alone do not reconstruct the policy."

Read narrowly, what the draft changes is which inputs are needed to reconstruct that internal key.

Draft: https://t.co/IiCRQuQPcv

[Kimmjyun @KimJyuun]

@DeepSafe_AI This is how you scale securely. Mesh topology sounds good on paper until you realize each new chain = n new attack surfaces. Routing through ETH adds one hop but cuts monitoring complexity exponentially. Security-first approach.

[DeepSafe @DeepSafe_AI]

On 16 September, Lombard deprecated native minting and redemption of LBTC and BTC.b on five chains — TAC, Sonic, Katana, Berachain and Starknet. Holders on the first four are required to bridge balances to Ethereum by December 10. Starknet keeps its bridge, and its balances have no deadline.

Underneath that sits a second change, and it is the more interesting one.

Bridging moves to a hub and spoke model. From the docs: "every supported chain has a bridge lane to and from Ethereum, and a transfer between two other chains routes through Ethereum rather than directly." Minting from native BTC is unaffected. What changed is how already-minted assets move between chains.

The reason is stated plainly: "Fewer bridge contracts and message paths mean a smaller surface to secure and monitor, and security budget and engineering resources concentrate on the lanes that carry the most value."

Worth being precise about what actually shrank. Not the number of chains — every other chain continues, and you can still mint from native BTC on any of them. What shrank is the number of routes between them.

Those are different quantities. In a mesh, routes exist between pairs, so each chain added arrives with a new lane for every chain already there. In a hub and spoke, a chain arrives with one.

The count that goes in the announcement is chains supported. The count that has to be secured and monitored is lanes. A topology decides which of the two grows faster, and that is the decision this update actually makes.

https://t.co/99C3WipeAW

#DeepSafe #Web3Security

[Kimmjyun @KimJyuun]

When bridges get exploited again vs when you use DeepSafe AI. Choose trustless verification and stay calm in Web3.

@DeepSafe_AI #DeepSafe

[DeepSafe @DeepSafe_AI]

Symbiosis has published its post-mortem on the Bitcoin Bridge incident of 11 September. The deposit that set the whole thing off was a real Bitcoin payment worth about 25 cents.

The bridge reads deposit instructions from data attached to Bitcoin transactions, and its decoder "identified the sender using the wrong part of that data: a part the spender controls." That was enough to have the attacker treated as an approved depositor and as the bridge administrator at the same time. With that, they put the minimum fee below zero, and a second bug subtracted the negative fee — which added to the deposit instead of reducing it. Twelve deposits went through across BNB Chain, Ethereum and Rootstock in roughly four minutes.

That first payment did not have to be forged. It was real and it was confirmed on Bitcoin. A check asking whether the deposit had happened would have answered yes, and it would have been right.

The bridge was asking a second question at the same time: who sent it. For that, it read a field — one the sender controlled.

Establishing a sender by signature and establishing one by reading the transaction data end in the same place: a name the system is about to act on. They differ in where the name comes from. A signature asks for something nobody can produce without the key the system already ties to that depositor. Reading it out of the deposit data makes the answer depend on which part gets read, and on that part being beyond the sender's reach.

Symbiosis puts preliminary losses to liquidity providers and affected users at 9.97 BTC. The bridge is offline, and it has commissioned independent audits.

Sources:

https://t.co/YxSokEsot2

#DeepSafe #Web3Security #CrossChain

[Kimmjyun @KimJyuun]

Existence check passed. Identity check failed. That single distinction turned a legitimate 25-cent deposit into a multi-chain exploit.

[DeepSafe @DeepSafe_AI]

Symbiosis has published its post-mortem on the Bitcoin Bridge incident of 11 September. The deposit that set the whole thing off was a real Bitcoin payment worth about 25 cents.

The bridge reads deposit instructions from data attached to Bitcoin transactions, and its decoder "identified the sender using the wrong part of that data: a part the spender controls." That was enough to have the attacker treated as an approved depositor and as the bridge administrator at the same time. With that, they put the minimum fee below zero, and a second bug subtracted the negative fee — which added to the deposit instead of reducing it. Twelve deposits went through across BNB Chain, Ethereum and Rootstock in roughly four minutes.

That first payment did not have to be forged. It was real and it was confirmed on Bitcoin. A check asking whether the deposit had happened would have answered yes, and it would have been right.

The bridge was asking a second question at the same time: who sent it. For that, it read a field — one the sender controlled.

Establishing a sender by signature and establishing one by reading the transaction data end in the same place: a name the system is about to act on. They differ in where the name comes from. A signature asks for something nobody can produce without the key the system already ties to that depositor. Reading it out of the deposit data makes the answer depend on which part gets read, and on that part being beyond the sender's reach.

Symbiosis puts preliminary losses to liquidity providers and affected users at 9.97 BTC. The bridge is offline, and it has commissioned independent audits.

Sources:

https://t.co/YxSokEsot2

#DeepSafe #Web3Security #CrossChain

[Kimmjyun @KimJyuun]

@DeepSafe_AI Signature-based identity and raw data extraction are not the same thing. This exploit is a perfect reminder of that difference.

[Pytho Dex @PythoDEX]

🚀 PythoDex Airdrop is LIVE!

complete the steps, and start earning rewards

🎁 Rewards are waiting. Don’t miss out!

👉 Join now: https://t.co/17W37ivbmI

#PythoDex #Airdrop #Crypto

[Elyon Chain @Elyon_Chain]

🚨 ELYON AIRDROP IS LIVE

The next chapter of @elyon_chain starts now.

We’re rewarding the community that believes in Elyon from the beginning. ⚡️

🎁 Complete the tasks
🏆 Earn points & rewards
🌐 Become an early Elyon contributor

This is more than an airdrop.

It’s your first step into the Elyon ecosystem.

👇 Join now:
https://t.co/VPckoWNfJa

Don’t wait. Your Elyon journey starts here. 🟣

#Elyon #Airdrop #Web3

[Dustbit @DustbitOfficial]

Available before GTA 6

You ask, we deliver.
Dustbit Boxes just got an upgrade. 🎁

Ready to take a peek?

Start unboxing. Find your next gem.

[Morfi Markets @morfimarkets]

A new paradigm of priced human conviction.

This is not another prediction market.

This is the next generation of democracy.

Sign up: https://t.co/xt3b9n7Ifg

[Kimmjyun @KimJyuun]

@basis__pro #Basis

@Shinesu6
@Awkeren14
@Punkx1307

[BASIS @basis__pro]

ETH is at its cheapest vs BTC since 2020. Most people are watching the price. Smart money is staking. While markets panic, BASIS users are earning yield on BTC, ETH, SOL, and PAXG simultaneously. Market-neutral. No directional bet. Just structural yield. Start staking on BASIS: https://t.co/jyHxoAZqJB