Quote from: alt on October 16, 2015, 03:48:56 pm

the question is , how much we can set  short_squeeze_ratio to?
which is better? which is bad?
if witness set it to 1000%, all short position will force margin call, and sell at 10% price. I think it's bad.
if 500% is bad? if 200% is bad? if 150% is bad? what's the rule? do we need to set a hard code limit? what's the value?
will you short bitUSD if there is no limit?
in my opnion, 110% should be the hard code limit, if we don't protect short position, nobody dare to short, bitUSD die.

I don't think there is one economically "correct" answer since it depends on collateralization. Well collateralized markets  can have it set much higher than lower collateralized markets. At this point, you have to go by "feel" and adjust accordingly. Or we can use the price feed script to publish a squeeze ratio that is a function of SWAN or average collateralization for each market.

Maybe 1.25xSWAN is a good number? That means:
1.25xSWAN_PRICE = FEED/SQR
SQR= (FEED/SWAN_PRICE) X .8

Quote from: spartako on October 14, 2015, 12:32:24 pm

Quote from: fav on October 14, 2015, 11:53:18 am

Quote from: spartako on October 14, 2015, 08:47:12 am

Quote from: fav on October 14, 2015, 07:11:28 am

80% of that never reached my account. that's what I wanted to say. seems like life time membership is bugged

It seems ok on backend side: You have 97 BTS as cashback

Code: [Select]

get_account fav
{
...
"cashback_vb": "1.13.52"
}

get_object 1.13.52
[{ 
    "id": "1.13.52",
    "owner": "1.2.21106",
    "balance": {
      "amount": 9729843,
      "asset_id": "1.3.0"
    },
    "policy": [
      1,{
        "vesting_seconds": 7776000,
        "start_claim": "1970-01-01T00:00:00",
        "coin_seconds_earned": "75659259168000",
        "coin_seconds_earned_last_update": "2015-10-14T08:00:00"
      }
    ]
  }
]


But my balance does not update?

you should give this command:

Code: [Select]

withdraw_vesting "1.13.52" 97 BTS true


Is that possible in the win lightwallet or OpenLedger?

Quote from: xeroc on October 14, 2015, 02:46:59 am

Yup ... 7 blocks pending means they will be IRREVERSIBLE after 7 blocks

You can reverse transactions? If so, why only some?

Quote from: Troglodactyl on October 11, 2015, 02:30:19 pm

Quote from: jakub on October 11, 2015, 01:53:43 pm

Quote from: svk on October 11, 2015, 01:22:56 pm

Quote from: jakub on October 11, 2015, 12:10:29 pm

Quote from: svk on October 11, 2015, 11:40:26 am

The functionality was only added a few days ago, we just need to figure out the kinks. I'll see if I can add access to it in the connection failure screen.
It's stored in localStorage so you can clear it by clearing that, in Chrome its under resources in the dev tools.

In the online version (i.e. in the GUI accessed by https://graphene.bitshares.org) - what possible reason would I have to want to change it??
I think it should be completely removed (or disabled) in the online version.

No, it can be useful, say you're on OpenLedger but their backend servers go down, you could switch it to another api provider, like BunkerDEX or Banx, or even one you provide yourself.

I see. So you can have the html/js served by domain A and at the same time have the blockchain support (i.e. wss) served by domain B.
OK, that makes sense and it's great.

But this definitely requires a fool-proof implementation in the GUI so that people do not become cut off when they mess it up.
Maybe a drop-down offering a choice of available wss domains plus and advanced option to add your own wss URL.

The connection failure page should list the web socket connection information and allow the user to alter it before retrying, possibly buried behind an "Advanced" expander.

Yea I've gone and added this, I also refactored the whole thing so you now choose the websocket using a dropdown menu. In the settings you can add AND remove websockets to the list, while on the init-error page you can choose from the list, or add a new one then pick it.

Quote from: svk on October 11, 2015, 01:22:56 pm

Quote from: jakub on October 11, 2015, 12:10:29 pm

Quote from: svk on October 11, 2015, 11:40:26 am

The functionality was only added a few days ago, we just need to figure out the kinks. I'll see if I can add access to it in the connection failure screen.
It's stored in localStorage so you can clear it by clearing that, in Chrome its under resources in the dev tools.

In the online version (i.e. in the GUI accessed by https://graphene.bitshares.org) - what possible reason would I have to want to change it??
I think it should be completely removed (or disabled) in the online version.

No, it can be useful, say you're on OpenLedger but their backend servers go down, you could switch it to another api provider, like BunkerDEX or Banx, or even one you provide yourself.

I see. So you can have the html/js served by domain A and at the same time have the blockchain support (i.e. wss) served by domain B.
OK, that makes sense and it's great.

But this definitely requires a fool-proof implementation in the GUI so that people do not become cut off when they mess it up.
Maybe a drop-down offering a choice of available wss domains plus and advanced option to add your own wss URL.

Quote from: cylonmaker2053 on October 09, 2015, 03:41:16 pm

Quote from: bytemaster on October 09, 2015, 03:27:41 pm

Cryptsy failed to honor the PTS snapshot and lost the support of many in the community.

still, there's only value to be gained by working with them to incorporate BTS 2.0. the more liquidity channels we have, the better.

No, there isnt value in having some people buy BTS on a scam exchange and then have it get stolen from them by the exchange and dumped elsewhere.