@clout, this is what worked for me.

1) Create blind account "bacc1"
2) Create blind account "bacc2"

get_blind_accounts
[[
    "bacc1",
    "GPH7EsV61saKFYh5kQwxTtd7h92BtJP51YL32EEsMeUWhZjkY4NVv"
  ],[
    "bacc2",
    "GPH824HUDikZtpP8U26aGWNddGrBCcJSFQkQ41HRSqjCZFhZJfTCA"
  ]
]

3)  transfer_to_blind nathan CORE [["GPH7EsV61saKFYh5kQwxTtd7h92BtJP51YL32EEsMeUWhZjkY4NVv", 555]] true

4) get_blind_balances bacc1
555 CORE

5) blind_transfer bacc1 GPH824HUDikZtpP8U26aGWNddGrBCcJSFQkQ41HRSqjCZFhZJfTCA 45 CORE true

6) get_blind_balances bacc2
45 CORE

7) get_blind_balances bacc1
495 CORE

[15 CORE fee!]

@ElMato

I'm in

I have my witness node running.
Need some votes.

elmato

--disclaimer: not an expert talking--

I think we will have a robust system when 2.0 is out and running.

- Clear and defined governance model
- Ability to (de)centralize at will
- Aligned economic incentives
- A good degree of privacy

Among other excellents features such as smartcoins, transaction speed, scalability, copay-on-protocol, etc, etc, etc.

Looking at MakerDao, one of the things that sounds interesting is the actions their planned to mitigate the effects of a blackswan.

I know that "printing" more BTS is a sensible subject in the community, but i think in an scenario like this.

Supose that 2 years have passed from now and the marketcap of bitUSD is 100M USD, basically a lot of people is using it as a medium of exchange etc etc. Suddenly a black swan event ocurrs, the rainy-day pool is not enough to cover all, and we declare the bitUSD market dead and everyone gets their bitUSD swaped by (what is left) BTS.

Bad publicity and difficult to restart confidence in the sysmtem again.

Should we as stake holders take the losse on it in order to keep the business running?

Deposit / Withdraw using bitcoin is down for the moment.

iOS Version
iOS version is ready to test, please PM you email to add you to testflight!

Great work , and is there Chinese version?

Chinese localization is on the TODO (top prio)