Contact Sales

Connected Accounts

Some widgets show your own data, such as your pool earnings or your miners. To get it, they need a token (a code a service gives you to use instead of your password) or a login. On the Deck you save that secret once as an account, then pick the account in each widget that needs it.

Most widgets need no account at all. You only need this page for:

WidgetAccount it needs
Braiins PoolA Braiins Pool account with your pool's API token
Fleet ManagementA Username & password account per miner family: one for Braiins OS miners, one for Forge Firmware miners. AxeOS miners need none.

Add an Account

  1. Open the web interface and choose Connected Accounts in the menu.
  2. Choose Add New Account.
  3. Pick the Type: Braiins Pool, Username & password, or Token for other services. Ignore Local file token; the Deck has no use for it.
  4. Type an Account Name you will recognize, such as "Garage miners".
  5. Fill in the token or the login. Secret fields are hidden while you type.
  6. Choose Add New Account.

The Deck never shows the secret again. To change it, edit the account and enter a new one. You cannot change an account's type later.

Then open the widget's settings on Display Widgets and choose the account in its account field. One account can serve as many widgets as you like.

Braiins Pool

The Braiins Pool widget needs an API token from Braiins Pool with Read-only access.

  1. Sign in to Braiins Pool and open Access Profiles.
  2. Pick an access profile with Read-only access, or create a new one. Limited read-only access is not enough. Do not use a profile with full access: the Deck only reads data.
  3. Turn on Allow access to web APIs.
  4. Choose Generate New token, save the profile and copy the token. This is the token the Deck needs.
  5. On the Deck, add a Braiins Pool account and paste the token into API token. The Deck checks the token with Braiins Pool before it saves it, so Braiins Pool must be reachable: if it is not, the save is refused even with a good token. "Invalid API key" means the pool rejected the token, either because it is wrong or because it lacks access.
  6. In the Braiins Pool widget's settings, choose the account under Pool account.

The Deck sends a Braiins Pool token only to Braiins. If the widget says "Access denied", the token cannot read your pool data: create a new one with Read-only access as above.

Miner Logins

For Fleet Management, add a Username & password account with your miners' login. For Braiins OS the user is always root, with the password you set on the miner. Fleet Management uses one login for all miners of a family, so give your Braiins OS miners the same password.

Miners receive this password unencrypted, over plain HTTP. To keep it on your home network, fill in Allowed destinations with your network range. For most home networks, that is your router's address with the last number replaced by 0/24:

192.168.1.0/24

The Deck then refuses to send this login anywhere else. You can list several entries, one per line: single addresses, address ranges, host names, or wildcards such as *.example.com. Addresses and host names can end with a :port; address ranges cannot. A wildcard matches exactly one name part: *.example.com matches a.example.com but not a.b.example.com. An address range matches only addresses typed as numbers: if a widget reaches a miner by name, such as miner.local, list that name too. If you leave the field empty, the Deck sends the login wherever the widget asks.

Change or Remove an Account

  • Edit an account to change its name, secret or allowed destinations. Leave the secret fields empty to keep the saved values; to change a password, type the username again too. Widgets that use it get the change at once, with nothing to restart. This is how you replace a token that leaked.
  • Delete an account you no longer need. If widgets still use it, the Deck names them before you confirm. Those widgets then behave as if they never had an account.

How Your Secrets Are Protected

  • The Deck uses the secret on the widget's behalf. The widget's code never reads it, only the account's name.
  • A token tied to a service, such as a Braiins Pool token, can only be sent to that service.
  • A Token or Username & password account goes wherever the widget sends it. The widgets that ship with the Deck send it only where it belongs, but a widget you install yourself decides on its own. Fill in Allowed destinations for every account such a widget uses.
  • Secrets never appear in the Deck's logs, and support archives leave them out.
Under the hood

There are four account types: Token (a single API token or bearer secret), Username & password, Braiins Pool (sent only to api.braiins.com), and Local file token, whose value the device reads from a file another service writes. Local file tokens exist for displays built into miners, where a widget reads the miner's own API; on the Deck you do not need them.

Credentials are stored unencrypted, in a file only the device's administrator (root) can read. They are protected by file permissions and by being kept out of logs and support archives, not by encryption. Anyone with administrator access to the Deck can read them.

For WebAssembly widgets, the secret is never handed to the widget's code in any form. The widget puts a placeholder in a request and chooses the destination; the runtime fills in the secret as the request leaves. If Allowed destinations is filled in, the runtime refuses requests to any other destination. If it is empty, nothing is restricted. Native widgets are part of the firmware and are trusted like the rest of it.


Was this helpful?