Version 1.11.0 released
https://github.com/byteball/byteball/releasesIt adds the ability to create single-address wallets. These wallets have only one address and the change always returns to the same address.

For many users, the concept of the change going to a new address after each transaction was confusing, and with single-address wallets they get more familiar experience, even though this comes at the expense of privacy.
But the main motivation to add single-address wallets is to support applications that require a stable identity.
Starting with this version, you can use single-address wallets to run a manual oracle, right from your wallet, without having to run a node on a server. This allows you to run a prediction market for a future event, enable users to make contracts (bets) referencing your address as an oracle, and when the outcome of the event is known, you post its result from your wallet:

In this version, you can also manually attest other users and post arbitrary data into Byteball DAG. We'll use this data-posting functionality to assign human readable names to tokens issued on Byteball (now they are shown as cryptic hashes).
In the future, we'll see even more applications that require stable identity provided by single-address wallets.
Also in his release:
* Fixed an issue that caused new full clients to crash when starting to sync
* Fixed an issue that didn't allow to unlock a smart contract when it was created from a multisig address and unlock attempted from a device different from the one used to create the contract
* Fixed an issue when private payloads spent from a contract whose party is a multisig address were not forwarded to other members of a multisig address
* Multiple visual fixes
* Improved translations