> For the complete documentation index, see [llms.txt](https://docs.bitsafe.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bitsafe.finance/beth/guides/integrating-beth.md). # Integrating BETH Integrate BETH into a Canton wallet, DEX, or protocol. Use the same asset identifiers and registry URLs for each integration. Minting and redemption are separate workflows. ### Asset information Use the fields for the intended environment. In Canton Token Standard calls, use the Registrar as `InstrumentId.admin` and `BETH` as `InstrumentId.id`. Do not use the Operator as the instrument administrator. Confirm current configuration before production use. Fields marked “Confirm with BitSafe” need confirmation before publication. #### DevNet * **ID:** `BETH` * **Operator:** `auth0_007c65f857f1c3d599cb6df73775::1220d2d732d042c281cee80f483ab80f3cbaa4782860ed5f4dc228ab03dedd2ee8f9` * **Provider:** `beth-network::12207547956b2fbcc5c7b85ee3eeb13705b641e233fb17cebb4057d14e1a3f81bea6` * **Registrar:** `beth-network::12207547956b2fbcc5c7b85ee3eeb13705b641e233fb17cebb4057d14e1a3f81bea6` Registry URL: `https://api.utilities.digitalasset-dev.com` #### TestNet * **ID:** `BETH` * **Operator:** `DigitalAsset-UtilityOperator::12202679f2bbe57d8cba9ef3cee847ac8239df0877105ab1f01a77d47477fdce1204` * **Provider:** `beth-network::122027d91679105c721435c6f08f8d0cd684e6679f385731f5b3691cb9bf93cd126e` * **Registrar:** `beth-network::122027d91679105c721435c6f08f8d0cd684e6679f385731f5b3691cb9bf93cd126e` Registry URL: `https://api.utilities.digitalasset-staging.com` #### MainNet * **ID:** `BETH` * **Operator:** `auth0_007c6643538f2eadd3e573dd05b9::12205bcc106efa0eaa7f18dc491e5c6f5fb9b0cc68dc110ae66f4ed6467475d7c78e` * **Provider:** `beth-network::1220704c3cebc23916785557ebe79a5c7f68d034890a5b15690ea7ce050c7d463075` * **Registrar:** `beth-network::1220704c3cebc23916785557ebe79a5c7f68d034890a5b15690ea7ce050c7d463075` Registry URL: `https://api.utilities.digitalasset.com` ### Test the integration [Open the BitSafe faucet](https://cbtc-faucet.bitsafe.finance/?network=devnet\&token=cbtc). The faucet supports CBTC and BETH on DevNet and TestNet. The link opens with DevNet and CBTC selected. 1. Select the intended network. 2. Select BETH. 3. Enter the recipient's Canton party ID. 4. Request test tokens. 5. Accept the faucet transfer as the recipient. 6. Check the recipient's BETH balance. The recipient node must have the DA Utility Registry installed. Faucet tokens are not MainNet assets. Test sending and receiving with the [Transfer and receive BETH guide](https://docs.bitsafe.finance/beth/guides/transfer-and-receive-beth). Support both pending offers and completed transfers. A completed transfer does not require acceptance. ### DEX and protocol integrations DEXs and protocols use the same BETH instrument ID and administrator listed above. The additional work depends on the application's workflow. | Integration | Additional work | | ------------------------- | ------------------------------------------------------------------------ | | Wallet | Display balances and support sending and receiving tokens. | | DEX or trading venue | Connect asset transfers to the venue's trade-settlement workflow. | | Lending or other protocol | Define how the application manages deposits, positions, and withdrawals. | For a trade that exchanges two assets, an ordinary transfer does not link the two legs. Canton Token Standard allocations support delivery-versus-payment settlement: both legs settle together or neither does. Confirm supported APIs and the required settlement permissions before using this workflow. For lending, confirm the price source and collateral, borrowing, and liquidation rules before enabling the asset. Token support alone does not configure those rules. See the [Canton Token Standard documentation](https://docs.dev.sync.global/app_dev/token_standard/index.html) for allocation and application integration details. [Minting information](/beth/guides/mint-beth.md) can be found here. ### Technical resources * [`bitsafe-token-lib`](https://github.com/DLC-link/bitsafe-token-lib) * [`canton-lib`](https://github.com/DLC-link/canton-lib) ### Artwork and support Use approved asset artwork from the [BitSafe brand kit](https://bitsafe.finance/brand-kit). Contact BitSafe if the required artwork is unavailable. For additional party fields or configuration questions, [contact BitSafe](https://bitsafe.typeform.com/helloBitSafe). ## Reach out to BitSafe Integrating one of our assets? Reach out to the team on Slack or to to coordinate go-lives, marketing, and liquidity. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.bitsafe.finance/beth/guides/integrating-beth.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.