Introducing the linkdrop contract we can use

To Share and +4 nLEARNs

import createMainnetAccount from ‘’;
import createTestnetAccount from ‘’;

The linkdrop contract

We’re going to take a small detour to talk about the linkdrop smart contract. It’s best that we understand this contract and it’s purpose, then discuss calling a method on this contract.

The linkdrop contract is deployed to the accounts testnet and near, which are known as the top-level accounts of the testnet and mainnet network, respectively.


There’s ✌️nothing special✌️ about these accounts.

When a user signs up for a testnet account on NEAR Wallet, they’ll see this:

Let’s discuss how this testnet account gets created.

Notice the new account will end in .testnet. This is because the account testnet will create a subaccount (like we learned about earlier in this tutorial) called vacant-name.testnet.

There are two ways to create this subaccount:

  1. Use a full-access key for the account testnet to sign a transaction with the CreateAccount Action.
  2. Have a smart contract deployed to the testnet account that has a Promise executing the CreateAccount Action. (More info about writing a CreateAccount Promise.)

We could also use NEAR CLI to create a new account, as we’ll show next.


On mainnet, the account near also has the linkdrop contract deployed to it.

Using NEAR CLI, a person can create a mainnet account by calling the linkdrop contract, like shown below:

The above command calls the create_account method on the account near, and would create aloha.near if it’s available, funding it with 15 Ⓝ.

We’ll want to write a smart contract that calls that same method. However, things get interesting because it’s possible aloha.near is already taken, so we’ll need to learn how to handle that.

A simple callback

The create_account method

Here, we’ll show the implementation of the create_account method. Note the #[payable] macro, which allows this function to accept an attached deposit. (Remember in the CLI command we were attaching 15 Ⓝ.)

The most important part of the snippet above is around the middle where there’s:

This translates to, "we’re going to attempt to perform an Action, and when we’re done, please call myself at the method on_account_created so we can see how that went."

::caution This doesn’t work

Not infrequently, developers will attempt to do this in a smart contract:

let creation_result = Promise::new("aloha.mike.near")

// Check creation_result variable (can't do it!)
if creation_result {...}
In other programming languages promises might work like this, but we must use callbacks instead.

The callback

Now let’s look at the callback:

This calls the private helper method is_promise_success, which basically checks to see that there was only one promise result, because we only attempted one Promise:

Note that the callback returns a boolean. This means when we modify our crossword puzzle to call the linkdrop contract on testnet, we’ll be able to determine if the account creation succeeded or failed.

And that’s it! Now we’ve seen a method and a callback in action for a simple contract.

::tip This is important
Understanding cross-contract calls and callbacks is quite important in smart contract development.

Since NEAR’s transactions are asynchronous, the use of callbacks may be a new paradigm shift for smart contract developers from other ecosystems.

Feel free to dig into the linkdrop contract and play with the ideas presented in this section.

There are two additional examples that are helpful to look at:

  1. High-level cross-contract calls — this is similar what we’ve seen in the linkdrop contract.
  2. Low-level cross-contract calls — a different approach where you don’t use the traits we mentioned.

Next we’ll modify the crossword puzzle contract to check for the signer’s public key, which is how we now determine if they solved the puzzle correctly.

Generate comment with AI 2 nL
Scroll to Top
Report a bug👀