Near Protocol (NEAR)

Using @idOS_network feels closer to session-based identity than traditional KYC. A single verification issues encrypted credentials. Applications request scoped access, not raw data. Identity moves with the user across protocols. Onboarding shifts from manual repetition to permissioned reuse. The system depends on shared identity rails, but control stays with the user. This structure reduces friction and limits data exposure across on-chain finance. @SIXR_cricket

HAPPY $NEAR YEAR! 🎆

Brave's per-tab VPN is pretty cool, indeed! Another pretty cool feature coming to @brave is → verifiable privacy for AI, powered by NEAR AI Cloud > puts your AI interactions into a privacy-enhancing TEE > generates a cryptographic verification onchain, certifying you are using the model the frontend claims you are using, and that it's really private (no one is getting your data) → Use Brave → Study $NEAR Privacy is the priority 🛡️

sent me down a bit of a rabbit hole. multisigs feel “standard” in crypto, but once you look at them through the lens of @0xMiden , the mental model flips. on most chains, multisigs work because everyone is staring at the same global state. same data, same visibility, same assumptions. coordination is easy when everything is public. miden doesn’t play that game. accounts are private, state lives locally, and nothing is implicitly shared. so the usual multisig patterns just don’t translate. that’s the interesting part. instead of bolting privacy on later, miden forces you to rethink coordination from the ground up. signing, validation, and execution have to respect local state first, not global exposure. it’s a different design space. more complex, sure but also way more honest about what privacy actually means when you don’t rely on everyone seeing everything.