chore(release): prepare the repo for a public 0.1.0

CHANGELOG.md

@@ -0,0 +1,54 @@
+# Changelog
+
+All notable changes to `bitsafe-token` are recorded here. The format follows
+[Keep a Changelog](https://keepachangelog.com/en/1.1.0/), and the project
+follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## [0.1.0] - 2026-10-06
+
+The first release. `bitsafe-token` replaces `cbtc-lib` and adds BETH.
+
+### Added
+
+- `tokens::cbtc` and `tokens::beth`: the mint and burn flows of both assets,
+  with one API shape. Each module maps a `Network` to its own registrar.
+- `tokens::beth::mint::deposit_call`: builds the `depositETH` transaction
+  for a deposit account. It checks the network, the account id, the amount,
+  the wei unit and the account limits. It sends nothing.
+- `check_dars`: compares one asset's DAR set under `dars/` with a
+  participant.
+- `dars/`: the DAR packages for CBTC and BETH, and `dars/upload_dars.sh
+  <asset>`, which uploads them and stops at the first failed upload.
+- Examples for both assets, a localnet integration suite and a contract test
+  of the live BitSafe API.
+
+### Changed from `cbtc-lib`
+
+- The crate is `bitsafe-token` (`bitsafe_token` in code), not `cbtc`.
+- The CBTC flows move from `mint_redeem` to `tokens::cbtc::{mint, redeem}`,
+  and `CBTC_TICKER` is now `tokens::cbtc::TICKER`.
+- The DAR folder `cbtc-dars/` is now `dars/`. `upload_dars.sh` takes the
+  asset as its argument, and reads `jwt_token` and `canton_admin_api_url`
+  from the environment.
+- The crate uses `canton-lib` 0.10.0 instead of 0.9.0. Its active-contract
+  queries and update streams send `eventFormat` and `updateFormat`, which
+  Canton 3.6.1 requires. The `ledger` re-export no longer has
+  `submit::wait_for_transaction_tree` or `common::TransactionFilter`.
+- The dependency DAR set changed: `splice-amulet` 0.1.16 instead of 0.1.17,
+  `splice-util` 0.1.4 instead of 0.1.5, and newer Canton Network Utility
+  versions.
+- The `check_dars` example reads `ASSET`, as every Token Standard example
+  does.
+- The `cbtc_redeem_flow` example requires `DESTINATION_BTC_ADDRESS`, and
+  reuses only a withdraw account with that destination.
+
+### Removed from `cbtc-lib`
+
+- The template-id constants of `mint_redeem::constants`, such as
+  `DEPOSIT_ACCOUNT_TEMPLATE_ID`.
+- `mint_redeem::attestor::get_token_standard_contracts`.
+- The deprecated `issuer_credential` of the BitSafe API. The burn sends an
+  empty `issuer-credentials` list.
+- `cbtc-tui`, the terminal UI.

Cargo.toml

@@ -3,7 +3,7 @@ name = "bitsafe-token"
 version = "0.1.0"
 edition = "2024"
 description = "Client library for BitSafe bridged assets on Canton: CBTC, BETH"
-license = "Apache-2.0"
+license = "MIT"
 repository = "https://github.com/DLC-link/bitsafe-token-lib"
 publish = false
 autoexamples = false

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Bitsafe
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.