> For the complete documentation index, see [llms.txt](https://dev-docs.dcentwallet.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev-docs.dcentwallet.com/dcent-biometric-wallet-for-mobile/dcent-biometric-sdk-android/near.md).

# Near

## **getNearSignedTransaction**

**This function for :**

* `NEAR`(NEAR)
* `NEAR_TOKEN`
* `NEAR_TESTNET`(NEARt)

### **Parameters**

| Parameter   | Type                                      | Description                  |
| ----------- | ----------------------------------------- | ---------------------------- |
| coinType    | `CoinType`                                | near coin type.              |
| transaction | [NearTransaction](#class-neartransaction) | near transaction parameters. |

#### **class** NearTransaction

<table><thead><tr><th width="158.33333333333331">Name</th><th width="157">Type</th><th>Description</th></tr></thead><tbody><tr><td>hdKeyPath</td><td><code>Bip44KeyPath</code></td><td>sign key path for near transaction</td></tr><tr><td>sigHash</td><td><code>String</code></td><td>transaction that has not been signed of near transaction</td></tr><tr><td>decimals</td><td><code>int</code></td><td>transaction decimals of near transaction</td></tr><tr><td>symbol</td><td><code>String</code></td><td>transaction symbol of near transaction</td></tr><tr><td>fee</td><td><code>String</code></td><td>transaction fee of near transaction<br>* Fee value is configured in near(NEAR) unit.</td></tr><tr><td>nonce</td><td><code>String</code></td><td>(optional)transaction nonce of near transaction</td></tr><tr><td>optionParam</td><td><code>String</code></td><td>(optional)hexadecimal value of the token method type is used only in near token.<br>- '02' : Function call(ft_transfer)<br>- '<del>04' : Stake</del> (<strong>The method will be supported later.)</strong><br>- <del>'08' : Delegate</del> (<strong>The method will be supported later)</strong></td></tr></tbody></table>

### **Returns**

`String` - signed transaction.

### **Requirements**

* D'CENT Biometric Wallet version 2.24.0 or higher is required.
  * (for near-token): 2.27.1 or higher is required.

**Example**

```java
String keyPath = "m/44'/397'/0'";
NearTransaction nearTransaction;

nearTransaction = new NearTransaction.Builder()
                    .keyPath(Bip44KeyPath.valueOf(keyPath))
                    .sigHash("4000000033666164666339326631633631643261303138626166333738383566376633363331313439616331356163303438613263303137316566316661356139633366003fadfc92f1c61d2a018baf37885f7f3631149ac15ac048a2c0171ef1fa5a9c3f41b15753844300004000000033666164666339326631633631643261303138626166333738383566376633363331313439616331356163303438613263303137316566316661356139633366d5e91d9515257370e4763c0da089ca544c1292bd188ad3fee466e17024e941f40100000003000000a1edccce1bc2d3000000000000")
                    .fee("0.000860039223625")
                    .decimals(24)
                    .symbol("NEAR")
                    .build();


String response = mDcentmanager.getNearSignedTransaction(CoinType.NEAR, nearTransaction);
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://dev-docs.dcentwallet.com/dcent-biometric-wallet-for-mobile/dcent-biometric-sdk-android/near.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.