Latest API Releases

Hello xWorld!

• Fixed a rustc compatibility issue when building contracts. The meta crate looks at the rustc version when generating the wasm crate code.
• Initial version of the contract template tool in multiversx-sc-meta.
• The Rust debugger is now thread safe.
• Removed the `big-float` feature of multiversx-sc, because the functionality is already available on mainnet.
• CLI fixes in multiversx-sc-meta: arguments `--target-dir-wasm`, `--target-dir-meta`, and `--target-dir-all` in the `multiversx-sc-meta`
• Fixed an issue with contract calls and ESDT transfers in the `StaticApi` environment.

And many many other goodies. Check the detailed description of this release and join us on Discord, where you can connect with fellow builders and developers, share your feedback, ask for details, contribute with constructive ideas. And starting last week we have the monthly live dev sessions where you can meet us and discuss in detail every characteristic and detail.

• Multi-endpoints in multi-contracts:
• It is now possible to have multiple versions of the same endpoint in different multi-contract variants.
• We can also have multiple versions of the constructor.
• Major architectural redesign of the debugger:
• The VM executor interface inserted between the smart contract API objects and the Rust VM. A new VMHooksApi is used to connect on the smart contract side. A VMHooksDispatcher object and VMHooksHandler interface provide the connection on the VM side.
• The VMHooksApi comes in several flavors (backends):
• The old DebugApi is now only used at runtime, on the VM context stack;
• A new StaticApi provides support for managed types in a regular context, without needing to be initialized;
• An additional SingleTxApi is useful for unit tests. Aside managed types, it also allows some basic context for tx inputs, results, storage and block info.
• Removed almost all of the legacy functionality from the smart contract APIs.
• System SC mock.
• It is now possible to issue tokens (fungible, SFT, NFT) in integration tests.
• Setting roles is modeled.
• It is, however, not fully mocked.

And many many other goodies. Check the detailed description of this release and join us on Discord, where you can connect with fellow builders and developers, share your feedback, ask for details, contribute with constructive ideas.

Hello xWorld!

This is a hotfix release, there will be more substantial changes to these mappers in the next minor release:

• Fixed an edge case for the token storage mappers (FungibleTokenMapper, NonFungibleTokenMapper);

Send us feedback and let's get in touch if you have any improvement ideas. Become a maintainer!

Hello xWorld!

A short summary of the release:

• Fixed compatibility with rustc v1.71.0.
• Allocator system:
• Contracts can now choose their own allocator. This works in multi-contract contexts.
• New allocators: `fail` (default), `static64k`, `leaking`.
• Removed dependency to `wee_alloc`, but using it is still possible if the contract references it directly.
• Contract call stack size is now configurable in `multicontract.toml`.
• The 'panic with message' system now relies on managed buffers instead of on an allocator.
• Fixed BigUint bitwise operations in the debugger.
• When building contracts, an additional `.mxsc.json` file is created, which packs both the contract binary, the ABI, and some additional metadata.
• Refactor: reorganized the meta crate.
• Deprecated some legacy methods in the API wrappers.

Send us feedback and let's get in touch if you have any improvement ideas. Become a contributor!

Hello xWorld!

This release brings:

• Building contracts also triggers an EI check, which verifies compatibility with various VM versions. It currently only issues warnings.
• ManagedVecItem implementation for arrays.

Send us feedback and let's get in touch if you have any improvement ideas. Become a maintainer!

Hello xWorld!

This release is minor, rather than a hotfix, because it is not fully backwards compatible, but in spirit it is closer to a hotfix.

What we fixed:

• [BUG] Caching of call_value().egld_value() breaks thing
  

Send us feedback and let's get in touch if you have any improvement ideas. Become a maintainer!