NEAR Overview

---

Transactions can be sent asynchronously from a contract through a Promise. Like Promises in many programming languages, these will cause code to be executed in the future. In the case of NEAR, this "in the future" means a transaction to be executed in the next block (or thereabouts), rather than in the same block as the original function call.

You can implement any cross-contract workflow using Promises; they inhabit a middle-ground between the high-level and low-level approaches discussed in the last section. See the full Promise docs, linked above, for details.

However, there are a few situations where Promises are uniquely capable, since these situations don't involve making function calls:

• Sending $NEAR
• Creating accounts
• Deploying contracts

Reference : NEAR Docs

Methodology

---

In this dashboard, the main focus is on NEAR contract deployment and usage. I only consider those contracts deployed since 1st September 2022. While for in-depth analysis only consider the usage in Year 2023.

NEAR network does not have contract_address itself ; so, I have to identify the tx_receiver using near.core.dim_address_labels which exclude the cex addresses and only include those protocols and projects contracts.

While to determine the usage I just obtain the data from near.core.fact_transactions. I have also used near.core.fact_prices with the symbol of wNEAR to obtain the token price to calculate the transactions fee in USD value as the representation of volume move across the contracts.

The analysis split into 2 parts :

1. Contracts deployment vs Contracts Used

2. In-depth Analysis on Contracts Used