Repository navigation
Releases
bitsafe-token 0.5.0
This release updates the shared EVM deposit event for BETH and CHYPE.
The bridge change is evm-asset-bridge#68.
Breaking change
Deposit gains uint256 prevDepositBlock as its last field.
Both tokens::beth::mint and tokens::chype::mint export this type.
Callers that construct or decode a Deposit must handle the new field.
The field identifies the previous deposit block for the same account.
A zero value means that no earlier deposit exists since deployment or the upgrade that adds the field.
DEPOSIT_EVENT_TOPIC now matches only Deposit(bytes32,bytes,address,uint256,uint256):
0xf3ca88974ec5963addc617fe6c0c359d7196759e318be6ab0cade940986e30e2
Migration
Callers that read historical logs must also filter on the old topic:
0xacaea730ea841fae3326f72a7ff746b6e06c646840526bcaf5dabee5fd887ef8
Declare the old four-field event in a separate sol! block to decode those logs.
The new Deposit decoder rejects logs with the old topic.
Decoding old data without checking its topic can silently produce an incorrect prevDepositBlock value.
Compatibility
CBTC has no API changes in this release.
The library retains canton-lib v0.12.0 and canton-api-client 3.6.1-0.1.0.
The DAR bundle remains unchanged.
Integrators install this release with the Git tag v0.5.0; the crate is not published to crates.io.
Known warning
Cargo Deny reports RUSTSEC-2026-0543 because chrono is unmaintained.
This release retains the dependency versions from 0.4.1.
Issue #20 tracks remediation separately.
The maintainer accepts this warning for the compatibility release.
bitsafe-token 0.4.1
This documentation release keeps README guidance independent of deployment state.
Documentation
- The main README and examples README describe library behavior without temporary network availability, endpoint failures, or mutable bridge limits.
- The README identifies network mappings as library configuration and explains how to check bridge conditions at runtime.
AGENTS.mdrequires general documentation and places operational observations in separate verification records.
Compatibility
The library code, public API, dependencies, and DAR bundle are unchanged from 0.4.0. Existing callers need no migration.
bitsafe-token 0.4.0
This release adds CHYPE, which bridges HYPE from HyperEVM to Canton.
Added
- The
tokens::chypemodule provides network configuration, credentials, deposit accounts, mint builders, and redemption flows. - Devnet and Testnet use HyperEVM testnet (chain 998). Mainnet uses HyperEVM mainnet (chain 999).
- CHYPE validates withdrawal destinations during account creation and before burning holdings. It rejects zero addresses, HyperEVM system addresses, and CHYPE bridge proxies.
- The DAR bundle includes
chype-0.1.0.dar. - The examples include
chype_credentials,chype_mint_flow, andchype_redeem_flow. Token Standard examples acceptASSET=chype.
Changed
- BETH and CHYPE share internal EVM mint builders. Existing BETH public paths remain unchanged.
.env.exampleleavesDEPOSIT_AMOUNT_WEIandWITHDRAW_AMOUNTunset so each example uses its own defaults.- The localnet suite covers CHYPE with sandbox image
cbtc-6689a6a.
Compatibility and availability
The release retains canton-lib v0.12.0 and canton-api-client 3.6.1-0.1.0. Existing BETH and CBTC callers need no migration.
Live CHYPE transaction validation covers Devnet only. Testnet API requests redirect to Swagger. Mainnet account rules remain unavailable, which prevents new account creation.
Validation
The merged release matches the tested candidate. CI passes formatting, Clippy, unit tests, documentation tests, the localnet suite, and dependency checks.
The library remains a Git dependency; this release does not publish a crates.io package.
bitsafe-token 0.3.0
Fixed
credentials::accept_credential_offerexercises the UserService by the
package-name template id, throughcanton-lib0.12.0. The participant then
picks a package version that every host vets. With 0.2.0, the accept used
the package version that the UserService was created with. A participant
that did not vet that version rejected the accept with
INVALID_PRESCRIBED_SYNCHRONIZER_ID.
Changed — breaking
AcceptCredentialOfferParamsloses itsuser_service_template_idfield.
Drop it at the call site; thecredentialsexamples show the new shape.- The crate uses
canton-lib0.12.0 instead of 0.11.0. A project that also
depends on acanton-libcrate must pinv0.12.0. Two different pins make
Cargo build two copies of the shared types, and then the types do not
match.
Security
- The lockfile moves
rustlsto 0.23.46. This closes RUSTSEC-2026-0346 to
RUSTSEC-2026-0349. canton-lib0.12.0 moveszipto 9.0.5. This closes RUSTSEC-2026-0367 to
RUSTSEC-2026-0369.- The lockfile moves
rustls-webpkito 0.103.16, which closes
RUSTSEC-2026-0382. It moveswebpki-root-certsto 1.0.10, which closes
RUSTSEC-2026-0383.
bitsafe-token 0.2.0
Changed
- The crate uses
canton-lib0.11.0 instead of 0.10.0.canton-libnow
usescanton-api-client3.6.1 instead of 3.6.0. - A project that also depends on a
canton-libcrate must pinv0.11.0.
With av0.10.0pin, Cargo cannot resolvecanton-api-clientand the
build fails. A directcanton-api-clientdependency must be
3.6.1-0.1.0for the same reason. - The re-exported
active_contracts::getreturns the Ledger API error when
the participant rejects the request. With 0.10.0 it returned an empty
list, so a rejected balance query reported 0.
bitsafe-token 0.1.0
The first release. bitsafe-token replaces cbtc-lib and adds BETH.
Added
tokens::cbtcandtokens::beth: the mint and burn flows of both assets,
with one API shape. Each module maps aNetworkto its own registrar.tokens::beth::mint::deposit_call: builds thedepositETHtransaction
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 underdars/with a
participant.dars/: the DAR packages for CBTC and BETH, anddars/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_tokenin code), notcbtc. - The CBTC flows move from
mint_redeemtotokens::cbtc::{mint, redeem},
andCBTC_TICKERis nowtokens::cbtc::TICKER. - The DAR folder
cbtc-dars/is nowdars/.upload_dars.shtakes the
asset as its argument, and readsjwt_tokenandcanton_admin_api_url
from the environment. - The crate uses
canton-lib0.10.0 instead of 0.9.0. Its active-contract
queries and update streams sendeventFormatandupdateFormat, which
Canton 3.6.1 requires. Theledgerre-export no longer has
submit::wait_for_transaction_treeorcommon::TransactionFilter. - The dependency DAR set changed:
splice-amulet0.1.16 instead of 0.1.17,
splice-util0.1.4 instead of 0.1.5, and newer Canton Network Utility
versions. - The
check_darsexample readsASSET, as every Token Standard example
does. - The
cbtc_redeem_flowexample requiresDESTINATION_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_credentialof the BitSafe API. The burn sends an
emptyissuer-credentialslist. cbtc-tui, the terminal UI.