Quote from: bytemaster on December 06, 2015, 11:05:41 pm

Bounty is all yours, where do you want the BitUSD sent?

you can send it all to "xeroc" .. I'll share a cut with @abit

Thanks  my account is "abit"

Quote from: fuzzy on December 07, 2015, 05:17:44 pm

Opinions and facts must be tested.  How are the alternatives being tested?

I tend to agree with proposal to test bitAssets which pay premium or interest to holders. Setting positive interest would motivate holders and demotivate borrowers, increasing demand and reducing supply which would push the price up. Setting negative interest would reduce  demand and increase supply which would push the price down.  This could give an efficient way to keep the asset close to peg.

Why not fork a chain and test if impossible to test by a private MPA?

Now that I'm voted out I can share a secret 

Graphene has been so rock-solid that I was able to scale back my infrastructure to running a single t2.micro (plus a physical machine at home and another t2 ready to spin up in seconds).
Even on this low-end setup CPU utilization is close to zero, RAM is safely at around 60% and no latency issues.
During the two-months I've only had 33 missed blocks, all before the vesting-pay-bug fix. I now only scale up the machines during build.

Now, some witnesses are maintaining several four-core, 8GB machines, and you might think that it's somehow more secure, stable or scalable but the thing is, they have to dump their earned BTS to pay the bill. Meanwhile, I've never sold any BTS and am still able to easily scale up if/when blockchain usage picks up.

Graphene has exceeded expectations in terms of stability and footprint so much, that we ended up overpaying the witnesses. We can easily have twice as many witnesses or slash witness pay by half. And if the Blockchain starts demanding more resources we can always reevaluate.

Just a note, while the block chain is growing fast, the witness_node consumes much more memory than the beginning.

这样看来，bts死定了啊。
锚定不了的话，失败归零；锚定了又没法拉盘。

唉，一点都不激动。
问题多多，价格低迷。

now we have 17 witness, about 11 witness published price at 0.02, but the mdedian price is still 0.0216,
because there are almost 13 wintess don't update price over 1 hour
some of them are voted out, so they can't publish price any more
so you'd better use the price published in 1 hour, or exclude the unactive witness's price

Technically it can be done with a committee proposal. Here are options in bitasset_data:
    "options": {
      "feed_lifetime_sec": 86400,
      "minimum_feeds": 7,
      "force_settlement_delay_sec": 86400,
      "force_settlement_offset_percent": 0,
      "maximum_force_settlement_volume": 200,
      "short_backing_asset": "1.3.0",
      "extensions": [

      ]
    },
It seems that current setting is 24 hours.

@xeroc I'm using your latest script with this config:
...
                   "CNY" : {
                       "metric" : "weighted",
                       "sources" : ["btc38",
                                    "yunbi",
                                    "huobi",
                                    "btcchina",
                                    "okcoin",
                                   ]
                   }
...
feedSources["yunbi"]    = feedsources.Yunbi(allowFailure=True,scaleVolumeBy=0.3)
feedSources["btc38"]    = feedsources.Btc38(allowFailure=True)
feedSources["btcchina"] = feedsources.BtcChina(allowFailure=True,scaleVolumeBy=0.2)
feedSources["okcoin"]   = feedsources.Okcoin(allowFailure=True,scaleVolumeBy=0.2)
feedSources["huobi"]    = feedsources.Huobi(allowFailure=True,scaleVolumeBy=0.2)
But the price of BTS/CNY is usually 5% higher than normal (e.g. result=0.023, should be 0.022)
After I disabled bts/btc pairs of btc38 and yunbi, then the result looks fine.

Since volumes of bts/btc on btc38 and yunbi are far less than those of bts/cny (about 1:1000), I don't know why the weighted result is so far from the bts/cny price only (even though price of bts/btc is somehow higher).

据说， obit 在英文里一般用作 obituary 的简写。