# Sovryn Onboard

Sovryn-onboard is a wallet connection library that when integrated into a dapp, allows users to connect their Web3 wallets to sign messages and transactions. It's modular so each part can be easily changed, with a split between core and connector packages.

Modules are forked from and therefore compatible with [web3-onboard](https://github.com/blocknative/web3-onboard). Most changes are to add additional features required by Sovryn.

Core packages are required for library to work seamlessly and connectors are optional.

#### Core

| package                     | description                                                 |
| --------------------------- | ----------------------------------------------------------- |
| `@sovryn/onboard-core`      | core package, required to use sovryn onboard                |
| `@sovryn/onboard-common`    | common Web3 provider logic and typings                      |
| `@sovryn/onboard-hw-common` | common provider logic for Hardware wallets (Trezor, Ledger) |
| `@sovryn/onboard-react`     | React UI component                                          |

#### Connectors

At least one connector is required to use sovryn onboard

| package                         | description                          |
| ------------------------------- | ------------------------------------ |
| `@sovryn/onboard-injected`      | connector for injected Web3 wallets  |
| `@sovryn/onboard-walletconnect` | connector for WalletConnect          |
| `@sovryn/onboard-ledger`        | connector for Ledger Hardware wallet |
| `@sovryn/onboard-trezor`        | connector for Trezor Hardware wallet |


---

# Agent Instructions: 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:

```
GET https://build.sovryn.com/builder-portal/sovryn-sdk/sovryn-onboard.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.