try to import WIF private key:
5KJJNfiSyzsbHoVb81WkHHjaX2vZVQ1Fqq5wE5ro8HWXe6qNFyQ

view the page from account:  announce

there are long memo in this page, the UI become very slow

currently, all fees earned by the network belong to this account 'committee-account'
this account is controled by 11 committee
but the committes don't have enough authority, the money don't belong to them.

I suggest two changes to privated BTS:
1. all fees earned should belong to committees, seperate by the vote weight.
2. 1 BTS can only vote for 1 committee.

after the change, big capital can got chance to get profit from BTS, they will buy BTS to become the committee,
they will hired pro group to maintain the business, hired more programer to help develop

public ownership is the most evil system.

https://bitsharestalk.org/index.php/topic,20835.msg269215.html#msg269215
I have redesign the whole architecture, now we can provide trading robot service
This trading robot is used to provide market making services.
1. get source from each exchange,  got a basic bid/ask price.
2. according to each asset's weights and some parameters, we got another premium.
3. Finally, according to the additional premium individual local settings, and the additional price peg parameter, we got the last price

During the test, it is suggested keep a small balance at the  account.

use it with follow step :
1. run a cli wallet, and import your trade account.
2. install the btsbots client
pip3 install btsbots --upgrade
edit config.json, reference:
https://github.com/pch957/btsbots/blob/master/config-example.json
3. run the trade bots, you can see some output from the console
btsbots --config config.json run_trade
4. you need to recharge for the service,  now it's 1USD/per day for each market.
we will not  charge  fees for filled order during test period.
accept all peg assets for recharge.
run command at a new console, and you can see infomation from last console
btsbots --config config.json recharge 1 USD
5. after recharge, you can upload your profile.json for the trade
reference:
https://github.com/pch957/btsbots/blob/master/profile-example.json
run command to upload profile
btsbots --config config.json --profile profile.json update_profile
after the profile upload success, you can see output from the 1st console, and the trade will begin.
we support all peg asset, and BOTSCNY,  TRADE.BTC, OPENBTC, METAEX.BTC now


for now, account exchange.btsbots is test this bots at market BOTSCNY/BTS
you can visit the bot's orders. and here is the config.json profile.json used now
config.json
{
    "account": "exchange.btsbots",
    "cli_wallet": {
        "host" : "localhost",
        "port" : 9092,
        "rpc_user" : "",
        "rpc_passwd" : "",
        "wallet_unlock" : ""
    },
    "addition_spread": 0.01,
    "threshold": 0.01,
    "price_factor": {
        "CNY": 1.0,
        "BTS": 1.00,
        "USD": 1.05
    }
}profile.json
{
    "quota_in_usd": 50,
    "market": [
        ["BTS", "BOTSCNY"]
        ],
    "asset": {
        "BTS": {
            "weight": 8.0,
            "spread": [0.007, 0.12]
        },
        "BOTSCNY": {
            "weight": 4.0,
            "spread": [0.005, 0.1]
        },
        "CNY": {
            "weight": 2.0,
            "spread": [0.005, 0.1]
        },
        "USD": {
            "weight": 2.0,
            "spread": [0.005, 0.1]
        },
        "GOLD": {
            "weight": 1.0,
            "spread": [0.005, 0.1]
        },
        "SILVER": {
            "weight": 1.0,
            "spread": [0.005, 0.1]
        }
    }
}


If I got a transaction like this:
{'expiration': '2015-12-21T09:33:30',
 'extensions': [],
 'operations': [[1,
                 {'amount_to_sell': {'amount': 900000000,
                                     'asset_id': '1.3.0'},
                  'expiration': '1969-12-31T23:59:59',
                  'extensions': [],
                  'fee': {'amount': 500000, 'asset_id': '1.3.0'},
                  'fill_or_kill': False,
                  'min_to_receive': {'amount': 1900000,
                                     'asset_id': '1.3.1'},
                  'seller': '1.2.18'}],
                [1,
                 {'amount_to_sell': {'amount': 2000000,
                                     'asset_id': '1.3.1'},
                  'expiration': '1969-12-31T23:59:59',
                  'extensions': [],
                  'fee': {'amount': 500000, 'asset_id': '1.3.0'},
                  'fill_or_kill': False,
                  'min_to_receive': {'amount': 1100000000,
                                     'asset_id': '1.3.0'},
                  'seller': '1.2.18'}]],
 'ref_block_num': 30631,
 'ref_block_prefix': 2405814624,
 'signatures': []}
how to signature it with a private key from python? thanks

#edit: seems xeroc have provid this tools, but don't know how to use it
https://github.com/xeroc/python-graphenelib/blob/master/graphenebase/transactions.py

bts price is 0.0245CNY/BTS from about 13 hours ago, but now, the feed price for CNY is still 0.0236CNY/bts
many witness publish a wrong price

now, don't know why, several witness publish feed price double
for CNY, the normal price is 0.025, but some witness publish 0.049.

this can be a very serious security problem.
if more witness give wrong price, we will get a final feed price at 0.049,
users can borrow CNY at price 0.049, the collatereal is not enough,  a black swan will happe.

I don't want to talk about why they give a wrong feed price, maybe it's a bug of feed script,
maybe an exchange return a wrong price

the more important thing is we should  avoid this happen even if the witness give a wrong feed price.
so I ask for a new limit at the borrow logic

currently when we borrow from the wallet, the collatereal's price is the feed price.
we should get it from min(feed price, highest bid price)

I am testing for private MPA which  collateral with non BTS(bitCNY) now
some issue about this will post at this thread.

with api update_asset, I can remove a permission, but can't add a permission.
from the source code asset_evaluator.cpp, seems don't allow add permission
270    // new issuer_permissions must be subset of old issuer permissions                                                                                               
271    FC_ASSERT(!(o.new_options.issuer_permissions & ~a.options.issuer_permissions),
272              "Cannot reinstate previously revoked issuer permissions on an asset.");
273
so how should I do if I want to add a permission for my private asset?