Rutile weekly news #3
🖥 Rutile Virtual Machine
Added support for more EWASM methods. The biggest one is the new call method. This allows web applications to call each other and react to the data that has been received by another WASM function. Currently only call is supported but it lays the foundation for supporting callCode callDelegate and callStatic .
With this, it includes progress for system functions. Our first system function will be the keccak256 method. We need this for our Proof of Stake implementation to generate seeds for selecting random sets of validators.
We’ve also introduced two new methods that go with the call methods:
returnDataCopy— allows you to read the data that was returned by the call methodgetReturnDataSize— returns the size of the data that was returned by the call method.printString— prints a string out to the console.
🔌 AssemblyScript API
We continued our development of our easy to use API for AssemblyScript users. Since Rutile only has an key -> value storage it can be difficult to store arrays and mappings. This is why we are building a new API that allows you to use arrays and storing them in the Rutile storage. This would only be possible with the new call method that was developed.
👨💻 New member
We are proud to add a new member to the Rutile team: Masanori Sawahata. Masanori will help get Rutile more exposure and get Rutile to the next level.
We are currently at 5 members. Are you interested in joining? Please contact us with the email: f.waller@rutile.io
📦 Wrapping up
All these changes were in the spirit of implementing Proof of Stake. We will continue this week with developing it.
Always feel free to ask questions on any of the social media:
Reddit: https://www.reddit.com/r/rutile
Twitter: https://twitter.com/Rutile_io
Telegram: https://t.me/Rutileio
See ya next week!
