> For the complete documentation index, see [llms.txt](https://docs.catfee.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.catfee.io/en/getting-started/seamless-energy/wallet-settings.md).

# Wallet Settings

For wallets or applications, Seamless Energy behaves like a configurable TRON broadcast node. Usually, you only need to replace the broadcast domain and do not need to change the local signing flow.

## Applicable scenarios

* Wallets that support custom TRON nodes or broadcast nodes.
* Applications that need to forward signed transactions through a backend.
* Wallet teams that need a unified integration method across multiple clients.

## First identify your scenario

* You use TronLink and plan to fill in the node manually: read [TronLink Setup](/en/getting-started/seamless-energy/wallet-settings/tronlink-setup.md).
* You use another wallet that supports custom nodes: read [Other Wallets and Apps](/en/getting-started/seamless-energy/wallet-settings/other-wallets-and-apps.md).
* Your wallet does not provide a custom node entry: this wallet configuration section does not apply for now. You usually need to wait for official wallet support or switch to backend-controlled broadcasting.
* You plan to control broadcasting through your backend: read [Application Integration](/en/getting-started/seamless-energy/application-integration.md) first.

## How to choose a configuration method

### TronLink setup

Suitable for wallets that support custom nodes and allow users to configure the node directly inside the wallet.

Read [TronLink Setup](/en/getting-started/seamless-energy/wallet-settings/tronlink-setup.md).

### Other wallets and apps

Suitable for other wallets that support custom nodes, DApps, self-built backends, and gRPC clients.

Read [Other Wallets and Apps](/en/getting-started/seamless-energy/wallet-settings/other-wallets-and-apps.md).

## Authentication recommendations

* Backend services or wallet platforms should prefer API KEY. Requests must carry `CF-NODE-KEY: {AccessKey}`, and the value must match the 41-character random `AccessKey` stored for the node.
* Ordinary wallet users should prefer bound address. The owner address of the first transaction in the request must be bound to the node.
* No authentication is only suitable for temporary testing.

## Next steps

* First-time integration: [Quick Start](/en/getting-started/seamless-energy/quick-start.md).
* Server-side development: [Application Integration](/en/getting-started/seamless-energy/application-integration.md).
* AI-assisted refactoring: [AI-Assisted Integration](/en/getting-started/seamless-energy/ai-assisted-integration.md).
* Risk boundaries: [Security](/en/getting-started/seamless-energy/security.md).


---

# 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://docs.catfee.io/en/getting-started/seamless-energy/wallet-settings.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.