Near Protocol (NEAR)

Security is hard. Everyone hates when their flow is interrupted. This is why we decided to solve it once and for all with @TrezuApp. Multi-factor authentication (aka 2-FA) is the common practice in web2 these days, so why won't you use it for crypto? NEAR wallets are diverse and can offer pretty nice UX, you don't have to pick one - use hardware wallet, mobile wallet, and passkey to secure your funds. Multiply that by the number of people you trust and you can easily get 4/6 approvals needed even for two people. There were 5 members at Drift Protocol multisig, but 2/5 approvals is not enough. If those were 5 different people, they could have had 15 keys with 8 keys quorum.

NEAR Intents currently has Solana swaps temporarily unavailable Onchain sleuthing identified two @near_intents transactions that likely funded the Drift Protocol attacker's wallet 8 days before today's ~$270M exploit + a ~$20.15k swap of 31 BNB to 232.27 SOL + a ~$20.30k swap of 9.92 ETH to 31.12 BNB Interesting is that the funding happened prior to NEAR confidential swaps activation... Any amounts swapped post-activation would likely be much harder (if not impossible) to trace I feel sorry for the Drift team, its users, and everybody else affected As a privacy advocate, strong NEAR supporter, and heavy user, it creates an interesting opportunity to battle-test the confidential function, raising some questions: + has the attacker used near today with confidential mode on? + will anyone be able to find and trace these transactions? It's also a good validation of NEAR Intents as an efficient cross-chain tool, as it was one of the attacker's choices, and this person or group is acting like they know what

We released 2.11.0 for Mainnet . CODE_COLOR: CODE_YELLOW_MAINNET PROTOCOL_UPGRADE: TRUE DATABASE_UPGRADE: TRUE SECURITY_UPGRADE: FALSE Voting will start on Monday, Apr 13th at 00:00:00 UTC. This release is a regular feature release and includes several protocol/non-protocol changes. Please refer to the full release notes in Github for more details: https://t.co/DPz0OG2BF0

NEAR just 3x'd what a smart contract can do in one transaction. Mainnet 2.11.0 is going live and most people will miss what's actually in it. Gas limit raised from 300 TGas to 1 PGas - tripled from the original launch limit that was never changed. NEAR gas is already sub-cent, so this isn't about cost - it's about complexity. Smart contracts can now run 3x more logic in a single atomic call. What this unlocks: on-chain verification of complex cryptographic proofs, TEE attestation validation directly in contracts, heavier DeFi composability, and AI agents executing multi-step reasoning without splitting into multiple transactions that risk partial failure. Yield/Resume race condition fixed. This is NEAR's unique primitive - the only major L1 where a smart contract can pause mid-execution, call an external service, and resume when it gets a response. Before this fix, if an external service (like an AI model) responded too fast, the resume could arrive before the yield was fully registered, causing the call to

NEAR privacy-preserving confidential swaps across 35+ chains https://t.co/MTfHLVhXDF

There are two perspectives here: 1. whether it's true that Perplexity is doing this 2. the fact that it can do it and has the incentives to do so Thousands of people already use AI for various activities that generate valuable data and are accumulated by these centralized companies (1) makes everything worse and highlights the problem, but (2) is already bad enough and should be a red flag to avoid using these tools, especially when for sensitive data I've only been mostly using models that allow me verifiable privacy interactions... so far, NEAR's (@near_ai) solutions seem the most elegant and have even been adopted by the Brave browser (@brave & @BraveNightly), which is a good validation for the tech, imo