- Who called the method
- How much money is attached to the call
- How many computational resources are available
- The current timestamp
- Helper functions for Public Key derivation, for example
Environment Variables
- 🦀 Rust
- 🌐 JavaScript
- 🐍 Python
- 🐹 GO
Who is Calling? Who am I?
The environment gives you access to 3 important users: thecurrent_account, the predecessor, and the signer.
Current Account
Thecurrent_account contains the address in which your contract is deployed. This is very useful to implement ownership, e.g. making a public method only callable by the contract itself.
Predecessor and Signer
Thepredecessor is the account that called the method in the contract. Meanwhile, the signer is the account that signed the initial transaction.
During a simple transaction (no cross-contract calls) the predecessor is the same as the signer. For example, if alice.near calls contract.near, from the contract’s perspective, alice.near is both the signer and the predecessor. However, if contract.near creates a cross-contract call, then the predecessor changes down the line. In the example below, when pool.near executes, it would see contract.near as the predecessor and alice.near as the signer.
You can access information about the users interacting with your smart contract
Balances and Attached NEAR
The environment gives you access to 3 token-related parameters, all expressed in yoctoNEAR (1 Ⓝ = 1024yⓃ):Attached Deposit
attached_deposit represents the amount of yoctoNEAR the predecessor attached to the call.
This amount is already deposited in your contract’s account, and is automatically returned to the predecessor if your method panics.
Account Balance
account_balance represents the balance of your contract (current_account).
It includes the attached_deposit, since it was deposited when the method execution started.
If the contract has any locked $NEAR, it will appear in account_locked_balance.
Storage Used
storage_used represents the amount of storage that is currently being used by your contract.
Telling the Time
The environment exposes three different ways to tell the pass of time, each representing a different dimension of the underlying blockchain.Timestamp
Thetimestamp attribute represents the approximated UNIX timestamp in nanoseconds at which this call was executed. It quantifies time passing in a human way, enabling us to check if a specific date has passed or not.
Current Epoch
The NEAR blockchain groups blocks in Epochs. Thecurrent_epoch attribute measures how many epochs have passed so far. It is very useful to coordinate with other contracts that measure time in epochs, such as the validators.
Block Index
Theblock_index represents the index of the block in which this transaction will be added to the blockchain.
Gas
Your contract has a limited number of computational resources to use on each call. Such resources are measured in Gas. Gas can be thought of as wall time, where 1 PetaGas (1_000 TGas) is ~1 second of compute time. Each code instruction costs a certain amount of Gas, and if you run out of it, the execution halts with the error messageExceeded the prepaid gas.
The environment gives you access to two gas-related arguments: prepaid_gas and used_gas.
Prepaid Gas
prepaid_gas represents the amount of Gas the predecessor attached to this call. It cannot exceed the limit 300TGas (300 * 1012 Gas).
Used Gas
used_gas contains the amount of Gas that has been used so far. It is useful to estimate the Gas cost of running a method.
Environment Functions
Besides environmental variables, the SDK also exposes some functions to perform basic cryptographic operations- 🦀 Rust
- 🌐 JavaScript
- 🐍 Python
- 🐹 GO
In the JS SDK,
throw new Error("message") mimics the behavior of Rust’s env::panic_str("message").