Hello,
       MagicWallet team is ready for new api source for price feed. As you know , we have the faitCNY/bitCNY deposit/withdraw gateway (p2p), so can provide some data to witnesses now. But this data is not for public. As a witness, if you are interesting to use this source, please use one of the following methods to apply your api key:

1 . reply this topic, comment your email address and your witness account
2.  send a mail to pluswave@magicwallet.io

the provided data is a array of accumulated deposit/withdraw transactions:


{  depositBitCNY: '0.0000',
    depositFiatCNY: '0.0000',
    depositCount: 0,
    withdrawBitCNY: '0.0000',
    withdrawFiatCNY: '0.0000',
    withdrawCount: 0,
    startdate: '2018-03-15T02:50:00.000Z',
    datelength: 1,
    datatype: '1m'
 },

the data is updated every minutes. you can get most recent data for:

1min
5min
15min
30min
1h
2h
4h
6h
12h
24h

Would you be interested in publishing price feeds for the Hertz Algorithm Based Asset on the Bitshares DEX? https://bitsharestalk.org/index.php?topic=26013.0

Yes, we are doing research about alt's btsprice script and forks. will add Hertz later.

Hi all,
       MagicWallet Team is testing witness. Please vote magicwallet-witness in testnet. Thank you for your support.

中文版： 关于多签的一些问题

proposed_transaction 手续费应该由多签帐号来出。

1. 只能选BTS ?
2. 如果满足条件，执行时费用不足怎么办？又充值够了怎么办？

proposal_create/propsal_update

1. proposal_create/proposal_update 如果由一个多签的一个公钥来执行，还需要这个公钥完全控制的另一个帐号来出手续费(或者由另一个帐号/密钥签名出手续费),不能用多签帐号自己来出？
1. proposal_create/proposal_update 可以用非BTS资产吧？

-----------------------------------------------------

English Version: Some questions about multisig and fee:

for proposed_transaction,   fee should be payed by multisig account

1. The fee asset can only be BTS ?
2. if it has been approved (up the threshold approval ), but can't be executed because of fee, how about the proposal ? And if the account get more asset after that time ?

proposal_create/proposal_update

1. if proposal_create/proposal_update are executed by one publickey, can the multisig account itself pay for the fee ?

2. proposal_create/proposal_update can be paid by other assets instead of BTS ?

是否有账户密码泄漏的风险？

除非您的手机中了木马或者病毒。

In this stage, we don't want to open source the app. If you consider any security issue, please don't use it. If any developer want to review the code for security issue, please contact me. I will send you the source code , but you can use it only for review.

I am the leader developer of ICOWallet team. From my point of view,  the ChainStore part of bitsharesjs is poorly designed so we need to replace with our own. The points are:

1 The return value of APIs of the form getXXXX  is a 'try and guess correct' thing (sync one), which should be replaced with  ( same form of ) promise apis.
2. The tests are incomplete and the code is hard to argue and review.
3. For the cache thing, we need some carefully designed mechanism to reduce the network throughput  . IMHO, if a fully api node can reduce the memory usage, then in theory , a smart phone is capable for a "reduced full api node" which is used only with concerned accounts. That is a big thing. But for now, we plan to do some small improvements: market data / account history with diff data on wire .  BitsharesUI has some code for diff data on wire for market data, it should be  in bitsharesjs. Also, we plan to use HTML5 storage like localstorage / indexedDB to save persistent data from blockchain. (For compatible with Nodejs, that is another story.)

And yes, I think there are two ways to improve the architecture which is more valuable now:

1. use and improve alt's backend, drop many components in bitsharesjs.
2. do something like the discussion in this post above to improve the bitsharejs lib to make it a better one.

with any direction done, we can then do a better UI but I think it will be much easier.

we don't plan to open-source the UI part for ICOWallet in the near future( but maybe 1 or 2 years later), but once we have improved the bitsharesjs lib , we will make it opensource. @bitcrab suggested us to apply a worker for this part, but I don't think we need so much work to apply a worker (I think the community will see a better lib in two months, however as we have some other works, it could be incomplete for a whole UI but it should be a good reference for community to work on). If anyone can do some "block to object generating" like in C++ part in javascript, that is a valuable worker proposal (the big thing mentioned above).

In short, we need a better API lib layer to talk to backend first, then it is valuable to do a better reference UI .