1. Help Center
  2. Version Releases


May 8, 2019


  • New Dashboard
    • A completely newly designed dashboard that provides better user experience and performance
    • Organization-Based Management Dashboard
    • Better Application Configuration Wizard
    • Improved Application Method Call UI
    • Quick Access bar for application related functions
    • Wallets support mutiple accounts
    • New UI for managing contracts
    • Changeable Theme Colors
  • Support for Stellar
    • Stellar is a platform that connects banks, payment systems, and people
    • Integrate to move money quickly, reliably, and at almost no cost
    • Stellar Application with SIMBA API
    • Stellar Public Network
    • Stellar Test Network
    • Stellar Local Wallet
    • Stellar Contract Builder


  • Complete rewrite of our blockchain interaction code providing
    • Enhanced reliability
    • Better error handling and validation
    • Improved fault recovery
    • Optimized build processes to improve bugfix response times
    • Streamlined process of adding new blockchains and filesystems
  • Support for the Stellar blockchain
    • Completely new backend adapter allowing the use of the Stellar blockchain from within the SIMBA Chain ecosystem
    • New form auto-generated API to allow calling Stellar contracts
    • Support for Stellar Main and Testnet
  • Improved support for Ethereum and Quorum
    • More reliable transaction template generation for method calls
    • More reliable transaction submission
    • Better error reporting on failed transaction
  • Support for Tahoe-LAFS
    • Allows storing off-chain data to a Tahoe LAFS deployment (please contact support for access to this feature).
  • Improved full-stack error reporting, allowing the Dashboard to provide clearer and more useful errors if needed.
  • Improved contract and method call validation, along with much improved reporting of validation failures to aid users in tracking down bad values in their requests.

Potentially breaking changes:
When sending a “bytes” argument to a method, you will be required to pad the value to the appropriate size. For example, a bytes32 should be 0x, followed by 64 characters (0-9 A-F a-f). This change has been made as there was undefined and unexpected behaviour when automatically padding on our side that could lead to bytes values not being parsed as expected. This way passes full control of the process to the user.