Forem: xmrrabbitx

Retrieve Top 10 selling Nfts Using PHP and Infura

xmrrabbitx — Fri, 14 Apr 2023 10:58:17 +0000

If you have read my previous articles, you will notice that the previous version of the NFT history logs library didnt support the top-selling built-in function to retrieve these kinds of logs. but in the latest update, we can now retrieve as many top-selling NFT tokens from a specific contract address as we want in just one line of code.

You will retrieve the top 10 selling NFTs in five stages:

sign up on the infura website
setup the provider for the nft history logs library
retrieve the top 10 selling NFT in one line of code.

So, why Infura? Infura is a good option to start with that supports 100K free requests per day. And yes, it has premium plans, but its free plan is enough for us.

First of all, sign up for free in Infura:

then create a new API key:

Choose Web3 API and name your project:

Copy the url of Ethereum's mainnet. Do not share the API key with anyone.

Now it's time to use the real magic. Install the latest version of the NFT history logs library:

composer require nfthistory/nfthistorylogs dev-master

Then import it like this:

<?php

require 'vendor/autoload.php'

use Nft\History\nftHistory;

Then, insert the contract address you want and paste the provider URL that you copied from the Infura website:

$contractAddress = '0x00B3e138c6e4b233e5DDed8CfeD200f0c82B536c';
$provider = 'https://mainnet.infura.io/v3/<YOUR API KEY>';

In this step, create an instance of the nftHistory object:

$nfthistory = new nftHistory($contractAdress, $provider);

Now call the topSellNfts() function to retrieve as many top-selling nft tokens as you want:

$NftHistory->topSellNfts("multiThread", 10);

In the code above, we retrieve the top-selling NFT tokens of a contract address in one single code. We set the mode on multiTread to decrease the time for retrieving. Also, we set 10, which means retrieve the top 10 selling NFT tokens of a contract address. This option can be different based on your needs.

The output is:

array(10) {
  [0]=>
  string(4) "0.40"
  [1]=>
  string(4) "0.25"
  [2]=>
  string(4) "0.21"
  [3]=>
  string(4) "0.19"
  [4]=>
  string(4) "0.15"
  [5]=>
  string(4) "0.12"
  [6]=>
  string(4) "0.11"
  [7]=>
  string(4) "0.11"
  [8]=>
  string(4) "0.10"
  [9]=>
  string(4) "0.09"
}

As you can see, we successfully retrieved the top 10 out of 83 NFT token sale logs with a single code. Just remember, the bulk request (multiThread) may lead to a rate limit with some providers. Fortunately, Infura is more resilient than that. use carefully.

The rest of the functions are here

I hope this is helpful to you. ^__^

How to Rank Top-Selling NFTs Using PHP

xmrrabbitx — Wed, 22 Mar 2023 01:10:11 +0000

Well, we know that NFTs are transactions with special token IDs in the Ethereum logs.

But, what exactly does that mean

It means every token id includes a “Transfer” transaction, which includes special information in the smart contract. Every “Transfer” transaction includes a set of logs and special events. In fact, the whole of the Ethereum logs concept is a multidimensional array, which we can access to subset information.

One of these pieces of information is the “value” of a transaction. This value is in WEI format, which you could convert to Ether.

For more convenient access, we could use the NFT History Logs library.

Let’s get started!

First, install it via this command:

 composer require nfthistory/nfthistorylogs v0.0.1

Then import it like this:

<?php

require 'vendor/autoload.php'

use Nft\History\nftHistory;

Then, insert the contract address and set the provider:

$contractAddress = '0x00B3e138c6e4b233e5DDed8CfeD200f0c82B536c';
$provider = 'https://cloudflare-eth.com';

I used this contract address, 0x00B3e138c6e4b233e5DDed8CfeD200f0c82B536c, which belongs to The Boy who lost his mind Open Edition by Boss Logic. It is a collection of 82 NFTs at this smart contract address.

In this article, I want to list the top sales of NFTs using this contract address as a sample.

I used the free Cloudflare provider, but you could use your desired provider with an API key.

In this step, create an instance of the nftHistory object:

$nfthistory = new nftHistory($contractAdress, $provider);

Next, call the getAllTransferTrxHashAndIds() function:

$trxHash = $nfthistory->getAllTransferTrxHashAndIds();

The above function will give us a list of “Transfer” transaction hashes based on every token id.

The output of the function is something like this:

var_dump($trxHash);

// output:
array(82) {
   [19400010233]=>
       array(2) {
               [0]=>
              string(66) 
               '0x3982a65f77b8896c19722b8ee2314f2224c767fef25035ba968f57e0cb4a8c8e'

Now we have a set of token ids that includes “Transfer” hashes of specific NFTs. The number 19400010233 is the token id, and the string value with the length of 66 in hexadecimal format is the transaction hash. by using this transaction hash, we could access the value of that transaction.

So, let’s filter this array:

$filterData = array_map(function($log) use($nfthistory){

             return array_map(function($logs) use($nfthistory){

                    $result = $nfthistory->getTrxByHash($logs);

                     if($result['value'] !== '0x0'){

                                 $logs = $result['value'];
                                 return $logs;

                                 }
             },$log);

},$trxHash);

In the above code, we used array_map() to iterate over the array in order to filter it out. In this loop, we iterate again, using another array_map() to access every transaction hash. Then, using NFT History Logs , we call the getTrxHash() function to access the value of the transaction in trade.

The output of this function is a multidimensional array. The “value” index is important to us because it is the hexadecimal value of trade in WEI format. We put in a statement to remove the “0x0”, which means removing zero values.

In this step, you must have an array like this:

array(82){
[19400010074]=>
 array(4) {
    [0]=>
    NULL
    [1]=>
    NULL
    [2]=>
    NULL
    [3]=>
    string(17) '0x12dfb0cb5e88000'
  }
  [19400010323]=>
  array(2) {
    [0]=>
   NULL
    [1]=>
    NULL
  }
}

As you can see, the keys of the above array are the token ids that we preserved, and the values of the array are the prices of every transaction. Those whose values are NULL mean there was no sale or the transfer event was equal to zero Ether.

Now we filter this array out again:

$res = array_map(function($log) use($nfthistory){

        $sum = array_sum(array_map('hexdec',$log));

                $nftSumPrice = $nfthistory->weiToEther($sum);

                return $nftSumPrice;

},$filterData);

In the above code, we sum the prices of every token id that includes more than one price. Then, using the weiToEther() function, we convert the price in WEI format to Ether format and finally return the result.

The output must look like this:

// output:

array(82) {
  [19400010233]=>
  string(4) '0.00'
  [19400010322]=>
  string(4) '0.00'
  [19400010042]=>
  string(4) '0.00'
 [19400010113]=>
  string(4) '0.00'
  [19400010074]=>
  string(4) '0.08'
}

Now we have the sum prices as well as the other ones, which are NULL. We could remove NULL values, but I intentionally kept them to make the comparison better.

Sort the array in descending order like this:

arsort($res);

Then the output be like this:

array(82) {
  [19400010142]=>
  string(4) '0.40'
  [19400010060]=>
  string(4) '0.25'
  [19400010127]=>
  string(4) '0.21'
  [19400010159]=>
  string(4) '0.19'
  [19400010303]=>
  string(4) '0.15'
  [19400010055]=>
  string(4) '0.12'
  [19400010429]=>
  string(4) '0.11'
  [19400010236]=>
  string(4) '0.11'
  [19400010400]=>
  string(4) '0.10'
 [19400010136]=>
 string(4) '0.09'
}

The above output is the list of the top 10 selling NFTs. in order to be sure about these numbers, first go to this page to search for the first token id (19400010142). Put this number in the search section to access the transaction list of this token id.

As you can see, this token ID is transferred twice. If you click on every transaction hash and go to the “value” section, you can see the price of the trade. The first one is 0.4 Ether, and the second one is 0.

I will try to add these functions as built-in functions to the library. At this moment, you can use it as is.

The rest of the functions are here.

If you have any questions, I will respond to you in the comment section. ^__^

How to Fetch NFT Transaction Logs Using PHP

xmrrabbitx — Thu, 16 Mar 2023 02:24:53 +0000

You may have experienced entering an NFT market and wanting to find out the number of people who have transferred a specific NFT. Some markets put the transaction history information of each NFT on the website, but some do not. Perhaps one of the reasons is the high volume of transactions made on each smart contract.

If the latter is the case, then the second option in front of you is the Etherscan.io website. This website makes it easier for us to track NFT smart contracts. It is a very powerful tool, but it is not enough. When you want to check an NFT with a specific ID, you will have a problem, although it provides the possibility of filtering transactions based on specific event signatures such as transfer or approval but not more detailed filtering! Especially if you are in the web development space and need non-graphical tools.

The third way is to use the Web3 library. Unfortunately, most web3 php libraries are not stable and do not have features as good as web3js.

With your options laid out, You are definitely looking for a way to get Ethereum logs more easily and filter their information in more detail. The Nft History Logs library allows you to use the eth_getLogs method with the help of endpoints such as alchemy, infura, or any network where you want to receive the logs of a specific smart contract address according to the event signature.

You may ask why we should not use an SDK like SDK Alchemy instead of this library. There are several specific reasons:

Most of these SDKs are written by JavaScript
These SDKs only work with their own dedicated network; for example, the alchemy SDK only works with the alchemy network, which may not be your choice and actually takes away your free will.
Most Web3 PHP libraries are not stable and have many problems!

To start using this library, type the following command to install it:

composer require nfthistory/nfthistorylogs v0.0.1

Now import the library and create a new instance:

<?php

require 'vendor/autoload.php'

use Nft\History\nftHistory;

$contractAdress = '0x7F0159D3A639a035797e92861d9F414246735568'

$provider = 'https://cloudflare-eth.com'

$NftHistory = new nftHistory($contractAdress, $provider);

As you can see, this class must receive two default variables during construction: one is the address of the NFT smart contract you want, and the other is the provider or endpoint you want to use. Both must be of the string type.

Here I used Kuddle Koala smart contract #6466. Its smart contract address is 0x7F0159D3A639a035797e92861d9F414246735568 and its token ID is 6466.

This token has actually been transferred between two people (two addresses), and the meaning of this transfer is nothing more than the sale of an NFT to another person. We know that NFTs are unique entities, so we have one Kuddle Koala token with ID 6466; the rest of the NFTs have different IDs.

By using our instance, we call the transferTrxById() function:

Well, as you can see, the output of this instance was a multidimensional array with 3 transactions, including the NFT mint transaction and the next two transactions of our NFT transfer, which were transferred between 3 people.

You can access any of the properties of these transactions and analyze them. For example, the data section contains the amount of ether transferred between two addresses during NFT transfer, which is 0x, which means zero, which means no ether was transferred. Be aware that this number is in WEI format, and you need to convert it to Ether. Of course, there are other functions for the convenience of receiving the amount of transferred ether, for example:

$transactionHash = '0x62f59782cc17e5156fda51e27b121d5e9562b4f0d5455c5f04720aeb0a79eb07';

$eventName = 'OrdersMatched';

$etherAmount = $NftHistory->nftTrxWei($transactionHash, $eventName);

var_dump($etherAmount);

//output
array(1) {

  ['value']=>

  array(1) {

    [0]=>

    array(3) {

      ['buyHash']=>

      string(66) '0x0000000000000000000000000000000000000000000000000000000000000000'

      ['sellHash']=>

      string(66) '0243b8854fe6a9b124e13caed266c59d3cacc1ca4c3246a3cad5a094c53f6d0900'

      ['price']=>

      string(62) '0000000000000000000000000000000000000000000000009869529cdd4000'
    }
 }
}

Well, as shown in the code above, based on the hash value of the transaction, we obtained the sale information for this NFT. Note that the $eventName variable is optional. In fact, instead of receiving all the ether values made on this transaction, we returned only its sale value information.

Likewise, you can work with the rest of its functions to achieve your desired results more easily.

You can access other functions of the NFT History Logs library here.

if you have any questions, feel free to ask me in the comment section ^__^