CRYPTO NEWS

Polygon Network Increases Unique Addresses By 12% In Q2 2022

Polygon network has been resilient despite the relative downtown in the crypto market. The notable rise in bridge aggregators is an indication that there is a possible wave of user migration from Ethereum to Polygon. Although Ethereum is still the network to beat, other platforms like Polygon are covering the cap faster than anticipated.

Polygon Recorded Impressive Growth In Q2 2022

The network’s Q2 report shows that the platform saw steady growth when it comes to transaction volume and the number of network addresses. This comes despite a wider market selloff during the same period.

Polygon is regarded as a sidechain scaling solution for the Ethereum Network, which has been criticized for its traffic congestion and high transaction fees.

The polygon network is seen as a much cheaper alternative, with the average transaction cost in Q2 2022 being $0.018. This represents a 49% drop from the previous quarter.

Buy Polygon Now

Your capital is at risk.

Additionally, Polygon has also attracted more users over the past few months. The total unique address on the network is 5.34 million, representing a 12% increase from Q1 2022. The total transaction on the platform during the quarter stood at $284 million, which represents a 4% surge compared to the previous quarter.

It’s important to note that the number of developers working within an ecosystem is an indication of a blockchain protocol’s attempt to challenge the status quo. Ethereum is regarded as the giant and juggernaut in the industry, and several protocols are struggling to match the level of transaction and popularity the network is wielding.

But Polygon has already recorded impressive strides. The network’s growth in the second quarter of the year has been very impressive, with more than 90,000 developers publishing their first contract during the period.

MATIC Gains Popularity Amidst Ethereum’s High Fees

The growth of Polygon is also indicated in its decentralized finance (DeFi) protocols. It has been attracting users that are feeling ripped off by the high fees with Ethereum. This means that decentralized exchanges and bridge aggregators are benefiting from the emerging wave f migration.

The network has also recorded progress when it comes to its expansion in NFTs. The total number of Polygon-based wallets on OpenSEa surged to 1.51 million in Q2, representing a 47% increase from the previous quarter.

Read more:

Battle Infinity – New Crypto Presale

Our Rating

Battle Infinity
  • Presale Until October 2022 – 16500 BNB Hard Cap
  • First Fantasy Sports Metaverse Game
  • Play to Earn Utility – IBAT Token
  • Powered By Unreal Engine
  • CoinSniper Verified, Solid Proof Audited
  • Roadmap & Whitepaper at battleinfinity.io

Battle Infinity

Truffle test: Error: expected event argument ‘_ids’ to have value 1 but got 1

I wrote an ERC1155 Nft whith this following function: contract Nft is ERC1155{ using Counters for Counters.Counter; Counters.Counter private id; event MintBatch(address indexed _to, uint256[] _ids, uint256[] _amounts); function mintBatch( address _to, uint256[] memory _amounts, address[][] memory _recipients, uint256[][] memory _values, ) external { uint256 _id; uint256[] memory _ids = new uint256[](_amounts.length); for (uint256 i;::Listen

I wrote an ERC1155 Nft whith this following function:

contract Nft is ERC1155{     using Counters for Counters.Counter;     Counters.Counter private id;      event MintBatch(address indexed _to, uint256[] _ids, uint256[] _amounts);      function mintBatch(             address _to,             uint256[] memory _amounts,             address[][] memory _recipients,             uint256[][] memory _values,         ) external {            uint256 _id;            uint256[] memory _ids = new uint256[](_amounts.length);             for (uint256 i; i < _amounts.length; i++){                 id.increment();                 _id = id.current();                 _ids[i]= _id;             }                          _mintBatch(_to, _ids, _amounts, '');             emit MintBatch(_to, _ids, _amounts);          } } 

And when I run the test to check the content of the event emitted :

const { expectRevert, expectEvent, BN } = require('@openzeppelin/test-helpers'); const { web3 } = require('@openzeppelin/test-helpers/src/setup'); const { expect, should } = require('chai');  it('mintBatch: Event', async function () {         let receipt = await this.NftInstance.mintBatch(user1, [2], [[]], [[]]);                  expectEvent(receipt, "MintBatch", {             _to: user1,             _ids: [web3.utils.toBN(1)],             _amounts: [2],         });      }); 

I get the error:

expected event argument '_ids' to have value 1 but got 1 

The failed test shows me the events emitted during it and specifically this one:

    Nft.MintBatch(       _to: <indexed> <user1 address> (type: address),       _ids: [ 1 ] (type: uint256[]),       _amounts: [ 2 ] (type: uint256[])     ) 

I tried to change from web3.utils.toBN to just 1, or to define a variable with new BN(1) and it doesn’t change anything.

Thank you for reading šŸ™‚

Polygon Network Increases Unique Addresses By 12% In Q2 2022

Shopping cart
There are no products in the cart!
Continue shopping
0