Cryptosaurus retweeted
Why do I think decentralized compute needs to move towards financialization and commodity trading?
A thread 🧵
Cryptosaurus retweeted
Finishing optimized quants for 2x dgx spark (and 2x rtx 6000 pro) for vLLM and LLama.cpp. Will upload to @huggingface once done.
#Tencent Hy3 IS OUT🚀
Outperforms preview and matches larger flagship models (2–5× size)
In a 270-expert blind test, Hy3 scores 2.67/4, outperforming GLM5.1 (2.51/4), with gains in frontend, data/storage, and CI/CD
Pricing: ¥1/M input, ¥4/M output, ¥0.25/M cached input tokens
Cryptosaurus retweeted
We should add @Libertai_DAI there!
Cryptosaurus retweeted
pyaleph 0.10.2 is out now! This upgrade focuses on performance and security. 🧵
Cryptosaurus retweeted
We are redesigning emission-funded node rewards with a usage-based revenue share model.
95% of customer credit payments now flow directly to CRN operators and stakers. 🧵
Cryptosaurus retweeted
The returned Verus bridge funds have now been converted back into the original currencies for reintegration into the Verus network.
The Verus recovery address currently holds 1,194.86 ETH (73.51% recovered), 76.0321 tBTC (73.41% recovered), and 147,727.67 USDC (100% recovered as discussed in the community meetings).
One issue we noticed is that some DEX interfaces have blocked the Verus return/recovery address. This address is not the attacker’s wallet. It is the community recovery address holding community funds.
We ask @Uniswap (your compliance department has been notified, we are still waiting for a response) @1inch @blockaid_ to review and correct the classification of the Verus recovery address (0xF9AB28cB7b72B518e6a351FbdaBe69362cBC1A74).
We ask the community to help by tagging relevant DEX interfaces, wallets, block explorers, and tracking services below, so the Verus recovery address is correctly recognized across the ecosystem.
0xF9AB28cB7b72B518e6a351FbdaBe69362cBC1A74
Cryptosaurus retweeted
Watch @ODesenfans talk on Aleph V2:
Schedulers are consensus-based nodes that monitor cluster health and migrate VMs away from failing machines, following user-defined policies for what can move where.
Cryptosaurus retweeted
You can manage your account, instances and projects effortlessly with @LiberClaw autonomous AI agents. Pick up the ALEPH CLOUD ADMIN agent, give it instructions, and let it do the hard work for you while you focus on building. 🦞
Cryptosaurus retweeted
OpenClaw showed us what autonomous AI agents could be. 145K stars in weeks.
We took that vision and built LiberClaw with the same skill patterns, deployed on decentralized infrastructure where no single company controls your agents.
It's live right now. 🧵
Cryptosaurus retweeted
Activity on decentralized networks is going up accross the board. Real activity. My gut feeling is agents. People playing with agents and agents finding ways to act autonomously without human checks.
Decentralized networks are a perfect substrate for them.
Cryptosaurus retweeted
🔦 New product feature:
Teamwork has never been easier than before. In your dashboard, you can share with other developers how they can access your VMs, volumes, and dependencies. Click on Permissions and start working with your teammates.
It's lready live!
Cryptosaurus retweeted
Concrete use cases:
🏥 HealthTech: Patient data analysis without exposure
🏦 FinTech: Sensitive transaction processing
🤖 AI: Training on proprietary data
🔒 Enterprise: Native GDPR/HIPAA compliance
That's why @libertai_ai uses our infrastructure.
Cryptosaurus retweeted
⚡️ We are super thrilled to announce our decentralized frontend marketplace! With recent outages on AWS and Cloudflare, dApps must have alternative providers to keep running their frontends no matter what.
We have recently added @aave to Aleph Cloud, more dApps will follow!















