Releases: CharmsDev/charms
v12.0.0
What's Changed
- fix(charms-app-runner): Do not crash if Charms app Wasm is missing the entry point by @imikushin in #160
- Remove outdated example projects by @imikushin in #163
- feat(cardano): support spending from Charms app contracts on Cardano by @imikushin in #162
- Update dependencies and enhance Cardano support for version 12 by @imikushin in #164
Full Changelog: v11.0.1...v12.0.0
v11.0.1
What's Changed
- fix(charms-lib): enable getrandom with wasm_js for wasm feature by @imikushin in #159
Full Changelog: v11.0.0...v11.0.1
v11.0.0
What's Changed
- Add support for Cardano transaction finality proof by @imikushin in #152
- Handle beamed-out outputs for Cardano multi-asset transactions by @imikushin in #153
- Refactor and enhance spell outputs on Cardano by @imikushin in #154
- Introduce
BeamSourcestruct and update build documentation by @imikushin in #155 - Add Cardano NativeOutput content by @imikushin in #156
- Add
util destsubcommand by @imikushin in #157 - Add deterministic PRNG to Charms Wasm app runtime by @imikushin in #158
Full Changelog: v0.12.0...v11.0.0
v0.11.1
Full Changelog: v0.10.0...v0.11.1
v0.10.0
Charms v0.10.0 brings native coins visibility to app contracts. Combined with Scrolls this enables smart contracts on Bitcoin that can lock and unlock BTC.
This release also completes the ground work necessary for Charms being represented on Cardano as CNTs.
Also, Charms can now be securely beamed from Bitcoin to... currently only Bitcoin (but also any other chains, when we add support for them). Great news is: now adding support for Bitcoin clones is straightforward, so now Litecoin and Dogecoin can be added almost trivially.
What's Changed
- Native coin handling in spells by @imikushin in #127
- Prepare v0.10 release by @imikushin in #133
Full Changelog: v0.9.3...v0.10.0
v0.9.1 - Improve Reliability
New
- Charms protocol current version to use in spells:
version: 7
Improved
- charms-lib Wasm module for use both in browser and server JS runtimes
- Proving speed
- Improved reliability across the board
Full Changelog
v0.8.0 - Proper mocks
What's New
- Charms protocol version 6 is now the current version
- charms-lib Wasm module for use both in browser and backend runtimes like Node.js and Deno
- Find
charms_lib.wasmin this release's artifacts - Generate JS bindings for it using
wasm-bindgen --out-dir target/wasm-bindgen-nodejs --target nodejs ./charms_lib.wasm
- Find
- Proper mocks:
- Use
--mockflag in charms CLI commands to generate and verify mock proofs mock: boolparam in charms-lib'sextractAndVerifySpell(tx, mock)
- Use
Full Changelog: v0.7.0...v0.8.0
v0.7.0 - Wasm app contracts
What's New
- Charms apps compile to Wasm modules (using WASI Preview 1 spec, with
--target=wasm32-wasip1).charms app buildbuilds prints the Wasm module file name to stdout.charms app vknow simply computes SHA-256 hash of the Wasm module and thus no longer depends on the underlying zkVM.
What's Changed
charms_data::Transactionnow lists inputs asVec<(UtxoId, Charms)>(vsBTreeMap<UtxoId, Charms>before v0.7.0)
Full Changelog
v0.6.3: Improve the prover
Prover speed and reliability improvements.