The Rio upgrade has successfully been deployed to the Polygon POS Amoy TestNet, marking an important step in significantly scaling the capacity of the network.

Polygon has deployed Rio Upgrade, a central step in the Gigagas roadmap that shapes the design of the network. The upgrade is intended to increase the mainnet capacity to 5,000 transactions per second. This is a sudden jump from the current level.

The upgrade was confirmed by X’s Polygon team.

“The Rio upgrade will be live on Polygon Pos Amoy Testnet.”

Blog: https://t.co/SdCB2ea7Yt pic.twitter.com/mw0LebqhGq

— Polygon (@0xPolygon) September 12, 2025

At the heart of the upgrade is a new system called Validator-Elected Block Processers (VEBLOP).

This model shifts more control over validators, which play a more powerful role in determining how blocks are generated. Polygon says the change will improve fairness and efficiency while enhancing decentralization.

Other changes include Stateless block validation, which reduces the cost of validators by reducing the data burden of node execution.

Upgrades also eliminate block reorganization. This is a move aimed at increasing stability and stopping unfair reconstruction of block production.

The update is not technical. It comes when the polygon’s native token, Rio/USDT, shows signs of recovery. After several weeks of decline and side-to-side trading, the tokens went above $0.31 this week.

Together, network overhauls and token rebounds mark moments that are prominent for the polygon. Rio upgrades signals when the project is at the top. Towards a structure designed for faster, lower cost, and wider use with payment and asset tokenization.

Discovery: Next 1000x Ciphers: 10+ Ciphers tokens that could hit 1000X in 2025

Rio Price Prediction: Can Rio maintain the rally towards the $0.34-$0.35 resistance zone?

After weeks of pressure, Rio suddenly recovered, avoiding a $0.23 drop from $0.34 in August. The turning point occurred on September 9th, when trading volumes rose sharply, when buyers took control and unlocked more tokens.

Rio’s 50-day EMA was $0.2729 and the 100-day EMA was $0.2696, with its latest closing price of $0.3137, which was +3.26% higher than its previous closing.

(Source – Rio USDT. TradingView))

This reversal marks a bullish reorganization, usually followed by a stronger gathering.

The momentum is clear on the charts. Lowering and growing green candles indicate a build-up of confidence, with decisive moves beyond the $0.30 area changing the mood.

The next key test is $0.3176. Clean breaks to that level may open the road to the $0.34 that will be last seen in mid-August.

Support is currently at a level of $0.28, with additional protection being in the $0.27 EMA cluster.

The structure resembles a classic inversion: a long downtrend followed by accumulation, and a breakout backed by an increasing volume. Its volume profile suggests that both retail and institutional money is involved.

Analysts say the short-term focus is in the $0.3176 to $0.32 range. With a high sustained push, profits can range from $0.34 to $0.35, which can reach psychological barriers. However, if the token fails to adhere to $0.30, the profit could be back to $0.28.

Overall, the outlook is bullish, but it is likely volatile as Rio works through these levels of resistance.

Discovery: Next 1000x Ciphers: 10+ Ciphers tokens that could hit 1000X in 2025

How does Rio upgrade make transactions faster and cheaper?

Upgrading polygon Rio is another move that will remain competitive with network scaling.

This update is intended to increase throughput and reduce the final time of transactions, and therefore to create transactions faster and cheaper for users and developers.

Another biggest change is the increased role of validators. Polygon wants to enhance decentralization of the system and maintain a low-cost system by assigning higher responsibilities.

This change serves the overall purpose of establishing a platform that helps you manage global payments and manage tokenization of your actual assets.

The Rio upgrade is a series of major upgrade improvements from the previous year. In September 2024, Polygon renamed the native token to Pol. It is used throughout the ecosystem.

Next, in June 2025, Bhilai Hard Fork released the first step in its Gigagas Roadmap, increasing its throughput to 1,000 transactions per second, increasing the stability of its gas bills.

A month later, Heimdall V2 reduced the transaction’s finality to about 5 seconds, clearing outdated code. In summary, these updates show a steady push to strengthen the technical foundation of polygons.

With Rio currently live, the network continues to build towards greater efficiency, stability and decentralization, aiming to meet the demands of the evolving blockchain market.

Discovered: 20+ Next Cryptocurrency Exploding in 2025

For the latest market updates, please join us in the discrepancy in 99bitcoins news here

Why you can trust 99 Bitcoin?

Over 10 years

Founded in 2013, 99 Bitcoin team members have been experts in crypto since the early days of Bitcoin.

90 hours+

Weekly research

100k+

Monthly Readers

50+

Expert Contributors

2000+

Crypto project reviewed

Follow 99 Bitcoin on Google News Feed

Provide the latest updates, trends and insights directly to your fingertips. Subscribe now!

Subscribe now

AIverse is opening its iNFT marketplace on testnet, with One Gravity holders getting the first look. Built on 0G’s decentralized AI protocol, the platform lets users mint, trade, and explore intelligent NFTs that are central to the growing AI agent economy.

Key Takeaways

• AIverse testnet goes live on September 4, 2025, on 0G’s Galileo testnet.

• One Gravity NFT holders (1,888 total) are the first to access and mint iNFTs.

• iNFTs minted on testnet will be tradable and exchangeable for mainnet equivalents at launch.

• A snapshot taken on September 1 determines eligible wallets for early access.

• The launch marks a major step for 0G’s decentralized AI ecosystem ahead of its mainnet.

AIverse: The “OpenSea for iNFTs”

Dubbed “The OpenSea for iNFTs,” AIverse is designed as the go-to marketplace for tokenized intelligence. The platform enables minting, trading, and collecting of iNFTs, setting the stage for what 0G calls the “agent economy.”

The marketplace is powered by 0G, a modular and infinitely scalable Layer 1 blockchain built for decentralized AI. Its integration of compute, storage, and data availability makes it an ideal foundation for applications that merge Web3 and AI.

Source: 0G

Exclusive Access for One Gravity Holders

One Gravity, which launched in March, is more than just another NFT collection—it’s the gateway to 0G’s broader decentralized AI ecosystem. Its 1,888 holders now get a front-row seat to AIverse, with their NFTs serving as access passes to mint some of the very first iNFTs on the Galileo testnet.

All iNFTs will be tradable within AIverse using testnet tokens that carry no monetary value. This provision allows participants to explore the marketplace’s core features, experiment with intelligent NFTs, and position themselves for potential rewards and ecosystem incentives once 0G’s mainnet officially goes live.

First-Mover Advantage in the iNFT Economy

The first iNFT minted on AIverse during the testnet phase will also be exchangeable for a mainnet version once 0G officially launches. This provides One Gravity holders with a strong first-mover advantage in shaping the AI-driven agent economy.

Michael Heinrich, CEO of 0G Labs, said:

“AIverse is going to power 0G’s agent economy and it’s only right that the One Gravity community should be first in line to onboard, mint an exclusive iNFT and reap the rewards that come from being early.”

Why This Matters for Web3 and AI

The launch of AIverse highlights a growing trend where AI and blockchain merge to create new forms of digital ownership. Unlike static NFTs, iNFTs embody dynamic, intelligent agents that can evolve, interact, and generate value within decentralized systems.

Minting and trading iNFTs gives users a way to engage directly with AI onchain, moving beyond static digital collectibles. Communities can test how intelligent NFTs function in practice and explore their potential role in emerging markets.

For 0G, the launch of AIverse is a practical step toward its broader goal of running AI workloads in a decentralized way, rather than leaving control in the hands of centralized providers.

Trusted Editorial content, reviewed by leading industry experts and seasoned editors. Ad Disclosure

An XRP Ledger (XRPL) developer building under the pseudonym “Vincent Van Code” says an MVP testnet for an “immutable forever file storage” service could arrive “likely 2 months” from now, after the idea evolved from simple document notarization to a compliance-oriented, globally mirrored archive that anchors control to popular wallets.

First XRP Ledger Based File Storage

In an initial post on August 18, 2025, the developer described the original scope as notarization on XRPL with on-chain hashing and a signing layer bound to legal documentation. “I am working on a new startup that will bring notarized documents to the XRPL,” he wrote. “Basically, you have a document you want an official record to say existed at a point in time. The doc is loaded in our servers, the hash of the file is sent to the XRPL, and I also provide a unique crypto based signing system to verify parties have signed. I also provide bundled relevant legal documents and affidavits to allow you to provide full evidence in court.”

He framed the go-to-market around enterprise users before a broader push to everyday records: “To be used initially mainly by companies and law firms, but later expanding to anything, from medical reports, tax receipts, you name it.” Pricing, he added, would be stratified: “Will be multi-tiered, where tier 0 is free and goes all the way to tier 4 which includes KYC signatories. All on our dear XRP Ledger. I would welcome everyone’s opinion on this.”

Today, the developer said the team had started writing code and, in the process, expanded the ambition from notarization to long-term preservation with explicit compliance targets and a wallet-centric control model. “Update: we have started coding… What we landed on is quite different to what we set out to do, and it is now a far more meaningful problem we are solving,” he said.

“Immutable, compliant (SOC2t2/ISO27001/SEC) 100yr storage. Built on XRPL, with files stored on multiple mirrors globally. Pay once depending on retention, store your file. And it’s not that expensive. All files fully linked and controlled by your wallet, either Xaman (formerlly XUMM) or a custodian provider (enterprise grade). Our journey has begun. I will keep you updated. Will have an MVP TESTNET hopefully in the next 2 of 3 weeks. You will be able to use a test wallet to upload files (of course files won’t be immutable in test, and will delete each week). Thanks all for your feedback, lot of it actually helped.”

He then characterized the effort in more sweeping terms while reiterating the testnet window. “We have started to build the world’s first XRPL powered immutable forever file storage. This is a game changer. I would love your feedback and suggestions. MVP TESTNET ETA likely 2 months.”

Taken together, the statements outline a two-phase path: a near-term test environment where users can upload via a test wallet with ephemeral files, followed by a broader MVP testnet rollout tied to XRPL-linked identity and signatures, and a commercial model that promises a single, retention-based payment for multi-mirror, 100-year storage.

At press time, XRP traded at $2.90.

Featured image created with DALL.E, chart from TradingView.com

Editorial Process for bitcoinist is centered on delivering thoroughly researched, accurate, and unbiased content. We uphold strict sourcing standards, and each page undergoes diligent review by our team of top technology experts and seasoned editors. This process ensures the integrity, relevance, and value of our content for our readers.

I am a developer working on blockchain applications and need a ton of testnet coins (ETH, Solana, Tron, etc.) for testing. Faucets usually only offer small quantities, but not enough for large-scale testing.

I already have some Bitcoin Testnet Coins (TestNet4). Are there any exchanges or services (BTC TestNet4→ETH TestNet, or other testnet currency) that allow you to exchange TestNet coins? Or is it the only way to get a ton of Testnet Coins through a specific developer program or private faucet?

My question is about the bitcoin.conf file.

We will explain the steps used to install it.

I used this command to create the start testnet.bat file.
start “” bitcoin -qt.exe -calculated -datadir =. /data_calculated/ -prune = 550

You will now find this bitcoin.conf file in the “data_testnet” folder. But the thing is empty.

And I’m new to this so I’d like to know that I should make any changes to the bitcoin.conf file or leave it as is.

And another question now, I’m not closing my wallet for fear of losing the sync it took so long, so next time I want to access the wallet you can start directly Start testnet.bat file? ?

operating system: Windows 10 (x64 bit)

Bitcoin Core Version: 0.16.3

thank you:)

I have made many forwarding to the addresses shown in the following example:

Also, my history has these transfers and is marked as successful. For reference, I have transferred it from my wallet to an address linked to the wallet.

It is also connected to a test network.

As shown, the wallet has everything, everything is fine, but when I try to check the info at my address, there is nothing.

Here we have checked the address through a special website.

I wrote a small program to check the address, balance history, but nothing appears there.

Connecting to Electrum server...
Successfully connected to Electrum server.
Address: tb1qc7j5j80s02gupl0qa3svg5kr99smjdq9a7yezd
ScriptHash: bb72dcabbea723d56aa49cd29575e53aaabf832f9dbdb45f251b56e187ce915a
Raw history response: ()
Fetching transaction history...
Found 0 transactions.
Total balance for tb1qc7j5j80s02gupl0qa3svg5kr99smjdq9a7yezd: 0 satoshis (0 BTC)
Current block height: 900621
Disconnected from Electrum server.

Here is the code for the program itself:

import * as bitcoin from 'bitcoinjs-lib';
import { ElectrumClient, ElectrumClientEvents } from '@electrum-cash/network';

const ELECTRUM_HOST = 'blackie.c3-soft.com';
const ADDRESS = 'tb1qc7j5j80s02gupl0qa3svg5kr99smjdq9a7yezd';
const NETWORK = bitcoin.networks.testnet;

function addressToElectrumScriptHash(address: string, network: bitcoin.Network): string | null {
  try {
    const outputScript = bitcoin.address.toOutputScript(address, network);
    const hash = bitcoin.crypto.sha256(outputScript);
    return Buffer.from(hash.reverse()).toString('hex');
  } catch (e) {
    console.error(`Failed to convert address ${address} to scripthash: ${e.message}`);
    return null;
  }
}

async function debugScripthashHistory(client: ElectrumClient<ElectrumClientEvents>, scriptHash: string) {
  try {
    const history = await client.request('blockchain.scripthash.get_history', scriptHash);
    console.log('Raw history response:', JSON.stringify(history, null, 2));
  } catch (error) {
    console.error('Error fetching raw history:', error.message);
  }
}

async function checkAddress() {
  const client = new ElectrumClient(
    'Address Checker',
    '1.4.1',
    ELECTRUM_HOST,
  );

  try {
    console.log('Connecting to Electrum server...');
    await client.connect();
    console.log('Successfully connected to Electrum server.');

    const scriptHash = addressToElectrumScriptHash(ADDRESS, NETWORK);
    if (!scriptHash) {
      console.error('Failed to generate scripthash for address.');
      return;
    }
    console.log(`Address: ${ADDRESS}`);
    console.log(`ScriptHash: ${scriptHash}`);
    await debugScripthashHistory(client, scriptHash);

    console.log('Fetching transaction history...');
    const historyResult = await client.request('blockchain.scripthash.get_history', scriptHash);
    if (historyResult instanceof Error) {
      console.error(`Error fetching history: ${historyResult.message}`);
      return;
    }
    if (!Array.isArray(historyResult)) {
      console.error('Unexpected history response:', historyResult);
      return;
    }

    const history = historyResult as { tx_hash: string; height: number }();
    console.log(`Found ${history.length} transactions.`);

    let totalBalance = 0;
    for (const tx of history) {
      const txHash = tx.tx_hash;
      console.log(`Processing transaction: ${txHash} (Block height: ${tx.height})`);

      const txDataResult = await client.request('blockchain.transaction.get', txHash, true);
      if (txDataResult instanceof Error) {
        console.error(`Error fetching transaction ${txHash}: ${txDataResult.message}`);
        continue;
      }
      if (!txDataResult || typeof txDataResult !== 'object') {
        console.error(`Invalid transaction data for ${txHash}`);
        continue;
      }

      const txData = txDataResult as { vout: { value: string; scriptPubKey: { hex: string } }() };
      const outputScriptHex = bitcoin.address.toOutputScript(ADDRESS, NETWORK).toString('hex');

      for (const vout of txData.vout) {
        if (vout.scriptPubKey.hex === outputScriptHex) {
          const amount = Math.round(parseFloat(vout.value) * 1e8); // Конвертация BTC в сатоши
          totalBalance += amount;
          console.log(`Found output to address: ${amount} satoshis`);
        }
      }
    }

    console.log(`Total balance for ${ADDRESS}: ${totalBalance} satoshis (${totalBalance / 1e8} BTC)`);

    const blockHeightResponse = await client.request('blockchain.headers.subscribe');
    if (blockHeightResponse && typeof blockHeightResponse === 'object' && 'height' in blockHeightResponse) {
      console.log(`Current block height: ${blockHeightResponse.height}`);
    }

  } catch (error) {
    console.error('Error during address check:', error.message);
  } finally {
    try {
      await client.disconnect();
      console.log('Disconnected from Electrum server.');
    } catch (e) {
      console.error('Error during disconnection:', e.message);
    }
  }
}

checkAddress().catch(console.error);

Since returning from the Amphora merge workshop, client teams have been hard at work implementing the latest versions of merge specifications and testing them on devnets.

After four ephemeral devnets, Kintsugi , a longer-lived public testnet, is now live!

Although client development and UX continue to be refined, we encourage the community to start using Kintsugi to familiarize themselves with Ethereum in a post-merge context. For application developers, as previously explained, not much will change. Tooling which only interacts with either the consensus or execution layer is also largely unaffected. Infrastructure which depends on both layers is most likely to need to adapt to support The Merge.

We recommend most projects begin testing and prototyping on Kintsugi to surface any potential issues soon. This way, changes can more easily be incorporated in future client and specification versions.

Using Kintsugi

Check out the Kintsugi landing page for information about interacting with the Kintsugi network. You’ll find network settings, a faucet, a block explorer and a JSON-RPC endpoint, along with documentation updated to reflect supported consensus <> execution layer client combinations.

As a reminder, post-merge, a full Ethereum client is comprised of both a Beacon / Consensus node and an Execution engine (handled by an existing “Eth1” client). Both layers maintain independent API endpoints and peer connections to handle their respective role. For a full overview of Ethereum’s post-merge architecture, see this post.

Support & Feedback

The EthStaker community is available to provide Kintsugi support. If you have questions, encounter errors or need clarifications, they are happy to provide assistance in the #testingthemerge channel of their Discord server.

With the launch of Kintsugi, we hope the community gets involved #TestingTheMerge. Check ou this list of test scenarios for ideas on how to bring your testing to the next level.

If you identify bugs or issues with the specification, the best place to raise these is in the #merge-general channel of the Ethereum R&D Discord server. If you’d rather not use Discord, other venues to raise such issues are the specification repositories (consensus, execution, APIs), and Ethereum Magicians .

Next Steps

The Kintsugi testnet provides the community an opportunity to experiment with post-merge Ethereum and begin to identify any issues. Once feedback has been incorporated into the client sofware and the specifications, a final series of testnets will be launched. In parallel, testing efforts will continue ramping up.

After this, existing long-lived testnets will run through The Merge. Once these have upgraded and are stable, next up is Ethereum mainnet’s transition to proof of stake .

For those eager to follow the progress at a more granular level, a mainnet readiness checklist is publicly available and regularly updated.

See you on Kintsugi !