1.2.52

This release:

1. adds support for KV Storage in Rust WASM contracts (#330)
2. fixes an issue for inner contract writes for WASM contracts
3. fixes an issue with error handling for Rust WASM contracts
4. updates the arweave-js library to latest version
5. reduces the web bundle size (#347)

What's Changed

• fix: error handling from wasm by @ppedziwiatr in #344
• fix: fixing deps to arweave-js by @ppedziwiatr in #347

Full Changelog: 1.2.51...1.2.52

Source type in contract manifest

This release adds an option to define interactions source type in a contract manifest.
More details: https://academy.warp.cc/docs/sdk/advanced/manifest#sourcetype-evaluation-option

What's Changed

• fix: readStatefor fixes by @ppedziwiatr in #336
• chore: replace redstone-isomorphic with warp-isomorphic by @asiaziola in #340
• feat: contract evaluation manifest #264 - source type by @Tadeuchi in #334
• fix: dryRuns should not commit changes to the KV storage #335 by @Tadeuchi in #341
• fix: register and deployBundled error handling fix by @asiaziola in #342

Full Changelog: 1.2.49...v1.2.50

v1.2.50 Broken release, do not use!

v1.2.50

1.2.49

This PR introduces the uncommitted state feature - #290 - an enhancement and refactor of how inner contract calls (reads and writes) are handled.

What's Changed

• Ppe/uncommitted state by @ppedziwiatr in #311

Full Changelog: 1.2.48...1.2.49

KV Storage for contracts

This release introduces key-value storage for SmartWeave contracts - an alternative, more efficient way of storing and accessing contracts' state.
More details in: #310

This releases also fixes bindings for viewContractState calls for Rust contracts.

What's Changed

• fix: move smartweave extension condition to HandlerExecutorFactory by @asiaziola in #319
• feat: kv storage for contracts by @ppedziwiatr in #300
• feat: expose viewContractState to rust contract code by @rpiszczatowski in #329

New Contributors

• @rpiszczatowski made their first contribution in #329

Full Changelog: v1.2.47...1.2.48

Fix for setting Arweave effective caller when in strict mode

This release fixes v1.2.43 release. When strict mode is set to true and signature type is arweave - arweave.wallets.ownerToAddress(caller) method should be used to determine effective caller's address from the wallet public key.

What's Changed

• fix: incorrect effective caller when in strict mode by @asiaziola in #324

Full Changelog: 1.2.46...v1.2.47

1.2.46

This issue upgrades the wasm-json-toolkit library, which has the previously missing WASM opcodes added (see warp-contracts/warp-wasm-json-toolkit#1):

'i32.extend8_s': 0xc0,
'i32.extend16_s': 0xc1,
'i64.extend8_s': 0xc2,
'i64.extend16_s': 0xc3,
'i64.extend32_s': 0xc4

Close caches

The release adds a close() method to the warp instance, which allows to close underlying database (e.g. leveldb or lmdb).

What's Changed

• docs: smartweave global by @asiaziola in #308
• feat: allow closing cache connections by @janekolszak in #313

Full Changelog: v1.2.43...1.2.44

Fix for assigning effective caller in strict mode

This release fixes how effective caller is assigned when in strict mode. Thanks to that, signing transactions with Metamask now works correctly also when the strict mode is set totrue.

What's Changed

• fix: reading owner of tx in strict mode by @koonopek in #306

New Contributors

• @koonopek made their first contribution in #306

Full Changelog: v1.2.42...v1.2.43

Custom SmartWeave extension plugin - fix

This release fixes 1.2.42 by extending WarpPluginType with WarpPluginPartialType.

Full Changelog: v1.2.41...v1.2.42