> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dfns.co/llms.txt
> Use this file to discover all available pages before exploring further.

# NEAR

> Network-specific features and requirements for NEAR wallets

NEAR is a sharded, proof-of-stake blockchain. This guide covers NEAR-specific features when using Dfns wallets.

## Sharded architecture

NEAR uses **sharding** to scale the network. Each account lives on a specific shard, and transactions are processed on the shard where the sender's account resides.

### Finding transactions

To locate a transaction on NEAR, you need both:

* The transaction hash
* The sender's account ID (to identify the correct shard)

Dfns handles this automatically when indexing transactions.

<Note>
  Dfns uses the main shard for wallet operations.
</Note>

## Transfers

Use the [Transfer Asset](/api-reference/wallets/transfer-asset) endpoint for NEAR transfers:

* **Native NEAR**: Use `kind: Native` with amount in yoctoNEAR (1 NEAR = 10^24 yoctoNEAR)
* **NEP-141 tokens**: Use the appropriate kind with the token contract

## SDK integration

For full transaction control, use the Dfns SDK with [near-api-js](https://docs.near.org/tools/near-api). See the [NEAR integration example](https://github.com/dfns/dfns-sdk-ts/blob/m/examples/libs/near/basic-tx/main.ts).

## Related resources

* [NEAR broadcast examples](/api-reference/broadcast/near)
* [NEAR signing examples](/api-reference/sign/near)
* [Supported networks](/networks)
* [NEAR documentation](https://docs.near.org/)