Ссылка
click to show
click to show
New video about Solidity Libraries is live 👇🏻
https://x.com/ConfluxDevs/status/2082536964557770755
Фотография
click to show
click to show
📢 Conflux Monthly Progress Report - July 2026
Our July Progress Report is now live!
This month, we celebrated several important milestones across the Conflux ecosystem, including USDT0 supply surpassing $10M on Conflux eSpace and Infini adding support for USDT0 and USDC, giving users new ways to make payments, transfer funds, and earn yield.
We also welcomed a number of new ecosystem partners across AI, payments, creator tools, prediction markets, and decentralized verification, continued the KuCoin × Conflux 60,000 USDT campaign, and connected with builders at Futurist Conference Toronto, where our DevRel Tony joined the panel "The Agentic Economy: Verifiable AI & Autonomous Finance."
https://confluxnetwork.medium.com/monthly-progress-report-july-2026-c6b2f0
557 · Thanks, the replacement guide is clear for implementation. Is there also a machine-readable migration manifest that maps every deprecated Pyth feed ID to the Conflux oracle feed, decimals, confidence-policy changes and the final valid timestamp? That would let applications validate the cutover automatically instead of maintaining their own mapping from the documentation.
Ссылка
click to show
click to show
Did you go through https://doc.confluxnetwork.org/docs/espace/tutorials/oracle/conflux-oracle/
Thanks, that clarifies the main point — especially that the oracle addresses stay the same and the limitations reflect a different trust model. One last implementation detail: are the supported feeds plus staleness/confidence rules exposed in a machine-readable source, or should applications treat the migration guide as the canonical specification?
@XGRNetwork thanks for the question. let me confirm whether there is a manifest / area where you can see the rules like conf, pricefeedids, etc. in machine-readable source.
Thanks, that’s exactly what I’m looking for. If there is a canonical machine-readable source, the useful minimum would be feed ID, decimals, staleness/confidence rule, trust-model or version marker and effective timestamp. That would let applications validate the migration instead of re-encoding prose rules. I’ll wait for what you find.
Ссылка
click to show
click to show
📢 Conflux v3.1.0 Network Hardfork Upgrade
Conflux v3.1.0 introduces several network improvements, including EVM compatibility updates, bug fixes, RPC changes, and security enhancements.
⚠️ Node operators: Please make sure your nodes are upgraded before the hardfork. The upgrade is estimated for August 25, with CIP-173 activation estimated for August 26.
Full upgrade details and instructions 👇
https://forum.conflux.fun/t/conflux-v3-1-0-network-hardfork-upgrade-announcement-aug-3-2026/23984
185 ·