cyrano

Thanks for everything! You did a great job! You've contributed a lot more than many other witnesses. I'm glad you'll stay around. :-)

Minor nit: the worker payout is not capped at 21k per hour, instead the cap is a fraction of of the total budget reserve (the factor is 3600*17/(2^32) ).

The reason for the halt is this much more severe problem:

Not sure if I can make it, but I'd like to report on today's testnet hardfork.

Flagged for spamming

Hi, we're currently planning for a hardfork in BitShares, and there's the possibility that your account could be resurrected. You should join the discussion at . The github issue related to your problem

Permission granted, as long as you keep the link back to my original.

I would think that placing a limit order at about 10% above the settlement price would be sufficient. That might require some calculations on your own, I'm not really familiar with the UI, sorry.

Precisely.

first blockchain buy should put my in the safe position, but this didn't happend. Why? The word "safe" in "Alice's position is safe again" is only from the POV of the blockchain. It

As the value of the collateral continues to go down, the maximum short squeeze price moves through the market. If the market does not provide sufficient liquidity to settle the full debt, at some point

The blockchain will only buy up to the maximum short squeeze price. If there are no orders left in that range, nothing else happens.

Good point. The word "safe" in "Alice's position is safe again" is only from the POV of the blockchain. It is true that Alice will remain in margin call territory until either the price

I'd like to speak about BSIP-0018 and the worker proposal published by the BitShares Foundation on my behalf.

Then what are you doing here?

Don't panic. This here: "worker": [ 0,{ "total_burned": "13172141776315" } ], means that it's a refund worker. The '0' above refers to the worker type, and as you can see

without it how would we prevent users from buying immediately before the scheduled dividend then selling immediately after? I wouldn't even try to prevent that. Happens all the time in traditional stock

You spammed me offline. I've removed the flag, because you seem to have understood.

Flagged for spamming

I don't see how that's a security flaw. Steemit is about freedom of expression, IMO. That includes comments on other people's posts. While the ability to "delete" posts (note that you cannot