How the Expload Platform Has Evolved Since November

Changelog

Hello everyone! In November, we focused on making Expload SDK easy-to-use for developers, as well as on fixing bugs. Pravda programs (smart contracts) have become simpler and more intuitive to develop. Their behavior has been further approximated to that of the original .NET-machine.

To this effect, the following has been implemented:

1. Documentation is now available here → click
2. Rapid project deployment through the dotnet new command has been enabled → click
3. A transactionId field has been added in response to the VM call → click, click
4. The DApp API has received a no-confirmation blockchain data read method → click
5. Internal errors have been fixed and the overall system stability has been improved.
6. Changes in the C# translator:

• Block number and block hash opcodes have been added → click
• Errors tweaked: incorrect operator behavior (or, and, xor), string concatenation (there’s no longer the need to create getters/setters), properties initiation with default values.
• The use of non-private fields in programs has been prohibited, with the aim to better correlate Pravda program semantics with C# class instances.
• The Mapping interface has been changed → click
• A method for calling common classes (including constructors) from other files has been added.
• Access has been enabled to the XCoin into С# transfer and ptransfer methods → click
• Unsigned primitives (uint*, byte, ushort, etc.) have been removed from the virtual machine and Pravda.cs interfaces, with int64 type and long support enabled in C#.

We’re just about ready to start closed beta testing for the Expload platform, so the next changelog promises to be even more insightful :) Stay tuned!