0xAnihdev
621 posts

0xAnihdev
@sumer_xyz
Web3 Enthusiast🎮| Solidity, Cairo & Rust dev | Security Researcher | Building secured decentralized futures one smart contract at a time.


How to join? 1. Build your Agent using any AI Agent + Bitget AgentHub Skills 2. Share your use case on X (Twitter) and tag @bitget with: -Screenshots or videos of your Agent -Brief explanation of what it does Details: bitget.com/support/articl…

PeterGate is live. It is an autonomous Sui Move security auditor. Open source and Free. The best at finding vulnerabilities on Sui-move contracts because it was specially designed for it, with innovative processes. Now, Sui-move developers and researchers have a specialized tool they can use to uncover vulnerabilities in their projects. You point it at any Sui Move contract, type "/audit", and it runs the full pipeline: 10-14 AI agents, 6 verification gates, zero hand-holding. Every finding must survive: hypothesis → reachability proof → controllability proof → quantified impact → proof of concept. If it can't be proven, it gets killed before the report, eliminating false positives. This is what I wish existed when I started auditing Move contracts. Now it does. The link is the comment. Check it out.







@sumer_xyz Autonomous DeFi risk agents are a great first step. Full end-to-end settlement with on-chain proof traces is the next unlock for serious Web3AI deployments.





We should be open to revisiting whole beacon/execution client separation thing. Running two daemons and getting them to talk to each other is far more difficult than running one daemon. Our goal is to make the self-sovereign way of using ethereum have good UX. In many cases that means running your own node. The current approach to running your own node adds needless complexity. Short-term, maybe we want some more standardized basic wrapper that lets you install dockers of any client and make them talk to each other easily? Also good that @ethnimbus unified node github.com/status-im/nimb… exists. Longer term, we should be open to revisiting the whole architecture once @leanethereum lean consensus is more mature.

@rel_zeta_tech Our goal is definitely not to have flexibility to replace the hash many times. We want a protocol that lasts. The main reason why I find anything elliptic curve uninteresting in 2026 pretty much is quantum risk. Don't want to deploy now and have to change again in 3-8 years.










