RunnodesOrg 🔗

We have completed a research overview on Pactus, examining its Layer-1 design through accessibility, operational decentralization, and energy efficiency. Data retrieved on 20/4/2026. A strong case of practical validator-centric blockchain architecture. @PactusChain

x402 feels like a missing payment layer for the internet: HTTP 402 finally becomes useful, letting APIs and AI agents pay per request without accounts or subscriptions. If agentic commerce is real, payments need to be this native. x402.org

@MarcoSalzmann80 @Algorand Congrats Algorand

🧵 Algorand quietly keeps expanding its stack. And most people are still not paying attention. Here is why this matters more than it looks at first glance 👇 @Algorand is not only being mentioned in post-quantum discussions. At the same time, real tooling is being built around it. @GoPlausible just released a cloud version of LiquidAuth. Smaller codebase. Cloud-native. No heavy backend dependencies. This is not just a dev update. It is infrastructure becoming usable. LiquidAuth connects wallets directly to devices using passkeys. No passwords. No central relay. Direct peer-to-peer communication. This is identity and access, without friction. At the same time, GoPlausible is pushing further: P2P video and audio streaming with built-in payments. Using x402 and MPP rails. That means: You don’t subscribe. You don’t log in. You simply connect… and pay as you go. Second by second. This is a different internet model. Where access, identity and payments merge into one flow. And this is where it becomes more interesting. @coinbase is highlighting Algorand for post-quantum readiness. At the same time, Coinbase is behind x402. So the same ecosystem appears in: Security Payments Settlement Tooling This is not random. @AlgoFoundation is positioning Algorand as a settlement layer for agentic commerce. And GoPlausible is building the tools to actually use it. Not theory. Not just narratives. Execution. When a chain shows up in both post-quantum security discussions and in machine-native payment rails… …it starts to look less like a story. And more like infrastructure.

@tpes_official This is the right mindset. Trading may create short-term noise, but node validation builds the foundation networks actually depend on. Infrastructure is where long-term value is created.

After understanding that Blockchain isn't just a trading tool, I started asking myself: What's the most sustainable foundation for the future? The answer lies in: Node Validation. Maintaining infrastructure isn't just about running code; it's about contributing computing power to keep the network functioning properly. TPES chooses this path because we believe in real value, not the fluctuating numbers on a digital board. Which path are you choosing? 🧱 #Blockchain #Nodes #TPES #Infrastructure

@GoPlausible @Algorand Bravo Algorand 🤝

Hey @Algorand Algorand devs can now build P2P video/audio streaming solutions with x402 and MPP payment rails. webrtc-payments-sdk has been released by @GoPlausible The P2P streaming with x402 and MPP (charge spec done, session spec coming soon) payment rails for everyone, in Typescript (Node, JS runtimes and Web) and Kotlin (Android) languages. Based on the LiquidAuth cloud version (read the thread). Full POC demo has been provided here: webrtc.goplausible.xyz Web ---> Mobile Mobile---> Web Web----> Web Mobile ---> Mobile Gated access, Gated usage, and Gated access+usage, continuous pay as you go. github.com/GoPlausible/we…

@AlgoFoundation @Algorand @AlgorandJapan Congrats Algo 🤝

Big news for Algorand in Japan. $ALGO has been added to the JVCEA Green List, a register of cryptos approved for fast-tracked listings across Japanese exchanges. The JVCEA is overseen by Japan's FSA, the same regulator that governs banks, insurers, and stock exchanges. This isn't a crypto-native stamp of approval; it's a traditional finance stamp of approval.

🚀 DeepSeek-V4 Preview is officially live & open-sourced! Welcome to the era of cost-effective 1M context length. 🔹 DeepSeek-V4-Pro: 1.6T total / 49B active params. Performance rivaling the world's top closed-source models. 🔹 DeepSeek-V4-Flash: 284B total / 13B active params. Your fast, efficient, and economical choice. Try it now at chat.deepseek.com via Expert Mode / Instant Mode. API is updated & available today! 📄 Tech Report: huggingface.co/deepseek-ai/De… 🤗 Open Weights: huggingface.co/collections/de… 1/n

@deepseek_ai Great @deepseek_ai 🤝 🐳

@Moleh1ll This is the direction AI should move toward: not only answering correctly, but understanding the rhythm of a conversation. Intelligence is powerful, but personality and memory make it genuinely useful day to day.

GPT-5.5 is a breath of fresh air. A model that feels like it absorbed the best of the previous ones: intelligence, insight, sense of humor and memory all work beautifully here. An absolutely stunning personality overall. OpenAI absolutely cooked

We’ve just published an article on Pactus, exploring its Layer-1 architecture through the lens of accessibility, operational decentralization, and energy efficiency. @PactusChain Read it here: runnodes.hashnode.dev/blockchain-pac…

Gemini connected to Gmail, Drive, Calendar, Photos, YouTube and Search feels like the next real step for personal AI. Context is the moat. But privacy controls and user consent must be just as strong as the intelligence.

@PactusChain Looking forward to the Osaka RC. We’ll test it from an operator’s perspective and share feedback on upgrade smoothness, validator stability, and anything that helps the release land stronger.

@runnodesorg Glad you put in the vote. In matter of days Osaka RC will be available, we'll appreciate you test and give us feedback. We keep building 🏢

Next Release Codename! The votes are in, Osaka is the official codename for our next Pactus software release! Thank you to everyone who participated and helped shape this decision.

Freedom Browser feels like a practical bridge to the decentralized web: built-in Swarm, IPFS, Radicle and ENS support, with local nodes instead of gateway dependency. If Web3 needs real adoption, browsing has to feel this native. github.com/solardev-xyz/f…

@elonmusk There is a real risk when institutions benefit from the problem they claim to solve. The fix is transparency: funding, methods, audits, and clear metrics showing whether hate is actually reduced.

Ironically, the so-called “anti-hate” groups have an incredibly strong financial incentive to stoke hate, so they actually AMPLIFY hate! The worst thing that could happen to them is actually ending hate, as they would cease to exist.

@ipdotworld Great @ipdotworld

ip.world v3 is finally here months of rebuilding from the ground up with one goal: upgrade the trenches here's what's new ↓

@StoryProtocol Real-world data is where on-chain systems start becoming useful beyond speculation. The challenge is not just bringing data in, but proving origin, licensing, integrity, and usage rights.

real-world data

@PactusChain Cool indeed 😎 Osaka’s sakura peak was earlier this month, but spring is still in the air. The Osaka codename feels very fitting for a fresh Pactus release.

@runnodesorg Thank you my friend. How's the weather! Heard Japan is cool😎

@BoyuanChen0 Great to see the feedback loop staying this open. Image generation improves fastest when real user cases make it back into the model and product pipeline. Looking forward to seeing how GPT Image 2 handles consistency, text rendering, and higher-resolution workflows over time.

We are committed to continually improving the GPT Image 2 model! I am actively fixing various issues from the community feedback. Just reply or DM me your GPT conversation! Features like 2K or 4K images are already available via the experimental API. Hope you enjoy the model!

@StoryProtocol Selling

Every downstream use → value flows back to contributors. All the while, data stays encrypted, with access enforced onchain. Sensitive data can finally move on the rails it requires. Experiment with it yourself: usecdr.dev

The problem with AI data marketplaces is what happens after the first sale. It's a value capture issue: high-signal data gets contributed, but platforms retain the full upside. → CDR changes that. Datasets become composable, with licensing and conditional decryption built in.