Ready to enter the Web3 autonomous era with aelf? While the industry was still talking about plans, we’ve turned hardcore aelf ecosystem capabilities into an equipment library of AI Skills. 👇github.com/AElfProject/aelf-… Your AI agent isn’t just an assistant; it’s an autonomous operator. 🪙Wallet & Identity Skills (The Safety Net): AI manages the treasury. Auto-transfers, 1-click cross-chain raids, and—most importantly—identity recovery. If you lose your keys, your AI digital life doesn't die. It recovers them for you. 📈Liquidity & Asset Skills (The Degen Mode): 24/7 autonomous trading on AwakenSwap. AI hunts for yield while you sleep. Want to launch an NFT? Use the eForest factory—prompt-to-mint, production-ready. 🗳️DAO & Logic Skills (The Filter): Governance is noisy. AI summarizes complex proposals, and votes based on your logic. 🌐Node & Scan Skills (The Infrastructure): No middlemen. AI speaks directly to the node for lightning-fast execution. Every move is transparent, on-chain, and detectable. But this is just the beginning. We’ve been grinding in silence to polish a massive surprise that’s coming next. 🚀 #aelf #Web3 #AISkills #AI #AutonomousDriving #CryptoTech

Key services and several dApps on aelf are back online. Welcome back! If you run into any issues while using a dApp, please reach out in the project's official community or contact its support team. Read the latest update: blog.aelf.com/posts/aelf-rec…

Recovery update 1. Public full-node access has been restored: aelf-public-node.aelf.io/ tdvv-public-node.aelf.io 2. Explorer data restoration is underway: aelfscan.io/ 3. We are continuing to coordinate with exchanges.

Recovery update Our public full nodes have been redeployed and are now synchronizing data. Synchronization is expected to complete on September 4. The production network has not reopened. We are working toward a safe resumption. No user action is currently required.

Recovery update 1. Functional testing of the upgraded nodes is complete. 2. Some partners have begun reviewing the upgraded node software. The production network has not reopened. We are working toward a safe resumption. No user action is currently required.

Recovery update All BPs are now producing blocks in the isolated recovery network, and all BP address replacements are complete. Testing and validation of the isolated network are underway. The production network has not reopened. No user action is currently required.

Recovery update Two of the last three BPs have synced and are producing blocks as expected in the isolated recovery network. The final BP is assessing and following our recovery plan internally. The production network has not reopened. No user action is currently required.

Recovery update The vast majority of BPs are in the isolated recovery network. Four remain in node setup or data preparation. We have also begun checking relevant servers for potential security issues. Not a reopening. No user action is currently required.

Recovery update Under the new plan, 16 BPs have joined the isolated recovery network. One additional BP node is syncing; three are onboarding. Two AELF MainChain backup nodes and two tDVV dAppChain backup nodes are syncing there. Not a reopening. No user action is required.

Since last Friday, our hotfix build has been running stably in an internal isolated network. Next, we will gradually invite other BP nodes to join the isolated network as we prepare for the full resumption of the aelf network. Stay tuned for more updates, and thank you for your continued patience and support!

📢Network Upgrade & Maintenance Earlier today, we detected an unauthorized anomalous contract attempting overflow and privilege escalation operations. To safeguard user assets and network integrity, all BP nodes have temporarily paused operations while our core team rolls out a network upgrade and hotfix. External audit partners have also been engaged for a comprehensive review. Marking our first emergency maintenance in over 5 years of uninterrupted operation, we sincerely apologize for the inconvenience. Read the full statement here 👇 blog.aelf.com/posts/network-…

Last week, our publishing schedule changed. We did not push seven posts forward or double-post the next day. We merged the opening into the next brief and kept the rest of the story intact. A useful AI workflow adapts the plan. It does not just generate more copy.

A publish-ready post is more than copy. In our X workspace, each item carries its direction, CTA, follow-up reply, asset brief, approval state, and publish status. We review the whole package, because a strong sentence can still be the wrong post.

aelf is using AI inside its own X operation. A weekly brief now moves through content packaging, asset review, approval, scheduling, publishing, and post-publish review in one workspace. This week, we are opening that workflow.