The Law Offices of NEAR

    Questions


    This article is written to answer the following questions

    • Provide your best assessment of the number of contracts deployed on NEAR and clearly outline your methodology

      \

    • Visualize the number of new smart contracts deployed over time over a time period of your choosing. What are the top 5 new smart contracts interacted in that period of your choosing?

    Approaches


    • We use data from the table near.core.fact_transactions

    • The column tx_receiver indicates the contract or receiver wallet that tx interacts with

    • To filter only Tx that interact with smart contracts, we inner join the table

      near.core.fact_actions_events_function_call because only Tx interacting with smart contracts will have FunctionCall action. Now, tx_receiver are only smart contracts.

    • We find the first date that each contract is deployed by using min(block_timestamp::date) and group by tx_receiver

    • Now, we have the table containing column of tx_receiver and its min_date (the date that the contract is first deployed)

    • Then, we count(tx_receiver) and group by min_date, to count how many contracts are first deployed on each date.

    • Limitation of this work is that we can query Tx only after 1 Sep 2021. Hence, there may be mistake about deploying date of contracts, we will explain again in conclusions section.

    Loading...
    Loading...
    Loading...

    Overall statistic


    We plotted Daily and Accumulated number of new contracts deployed in the below graph.

    We can see there are a lot of contracts deployed in the early period (in beginning of September), exceeding 500 on some days. We think this is because some contracts are deployed long time ago, but we can query data of the first time the contracts are called only since 1 Sep 2021. After that, Daily new contracts drop to around 50-100 per day until now.

    Total number of contracts deployed is about 22.4k, and average per day is about 67.1.

    Loading...
    Loading...
    Loading...
    Loading...

    Top 5 of all time


    1.) aurora

    2.) app.nearcrowd.near

    3.) v2.nearapps.near

    4.) v2.ref-finance.near

    5.) priceoracle.near

    Top 5 in last 180 days


    1.) v2.nearapps.near

    2.) analytics.nearapps.near

    3.) usn

    4.) zomland.near

    5.) utopia.secretskelliessociety.near

    Even v2.nearapps.near is deployed in last 180 days, but it is also in Top 5 of all time

    Top 5 in last 90 days


    1.) zomland.near

    2.) v1.orderbook.near

    3.) lightstar.near

    4.) fpo.opfilabs.near

    5.) undead.secretskelliessociety.near

    Even zomland.near is deployed in last 90 days, but it is also in Top 5 of last 180 days

    Top 5 in last 30 days


    1.) v1.pembrock.near

    2.) nearmailbot.near

    3.) laboratory.secretskelliessociety.near

    4.) tdt2022.near

    5.) neartribes-nft.near

    In short time period (30 days and 90 days), we cannot find contract that dominate “Other” (other than Top 5 contracts combined).

    > We may define this contract as dominating contract, which is a contract that gains very large amount of Tx volume among others.

    We start to see in last 180 days, v2.nearapps.near is number one contract and is a dominating contract.

    Of all time, aurora and app.nearcrowd.near is number one and number two, and they are dominating contracts.

    Conclusions


    • Total number of contracts is about 22.4k. In average, 67.1 new contracts are deployed per day.

      \

    • In early days, number of new contracts is large, exceeding 500 in some days.

      • We think this is because some contracts are deployed long time ago, but we can query data only since 1 Sep 2021.

      • After that is about 50-100 contracts/day.

        \

    • Another approach of this work is to look for Tx that has DeployContract action from near.core.fact_actions_events. However, we found that some contracts exist without being deployed and some contracts are deployed long time ago before 1 Sep 2021.

      • We think looking for FunctionCall action is the better way to collect existing contracts, even there may be some slight mistake of the date deploying contracts.

      • Our approach cannot collect contracts that are deployed and never being called before 1 Sep 2021.

        \

    • Mostly, Top 5 contracts of each time period are deployed on that time period, except

      • v2.nearapps.near is deployed in last 180 days, but it is also in Top 5 of all time.

      • zomland.near is deployed in last 90 days, but it is also in Top 5 of last 180 days.

        \

    • In short time period (30 days and 90 days), we cannot find dominating contract.

      • In last 180 days, v2.nearapps.near is only one dominating contract.
      • Of all time, aurora and app.nearcrowd.near are dominating contracts.

    Top 5 new contracts


    We find Top 5 new contracts that have highest Tx volume over periods of time; 30 days, 90 days, 180 days, and of all time.

    For clarification, when we find Top 5 contracts in last 30 days,

    • We find set of contracts that are first deployed within last 30 days.
    • Then, we count number of Tx interacting with that set of contracts over time and compare the fraction.
    • Top 5 contracts are shown (in the right graphs), remaining contracts in the set are put in “Other”.