Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - sschiessl

Pages: 1 ... 7 8 9 10 11 12 13 [14] 15 16 17 18 19 20 21 ... 45
196
Before talking about this worker, please wrap up the DevCon worker by itself. It is not clear how this deficit came to be since the funds of the DevCon worker are not accounted for, or at least I don't understand how yet.

Now on this worker:
It is a good example of reporting and escrow intent gone wrong.

There is no public information available how much funds have been spent on what. Just looking on the blockchain, BTS with an equivalent value (at the time of transfers) of 130k bitUSD have been paid out, which exceeds the asked for budget. This has been done with no clarification on the increased spendings whatsoever, or even reporting what the money has been spent on. On top of that, the escrow that was publicly communicated was only for show. The worker owner still had access to the owner key of the escrow account, and made use of it.

I don't see at the moment how funds of this worker can be re-used without calling a vote of the community. If funds are to be returned, return it by burning and not to committee.

197
Can you post a summary of this worker in here as well please? If possible with links and references of media and social media coverage
https://bitsharestalk.org/index.php?topic=25196.15

I am confused by the way you have setup the table there. You mention incoming and outgoing payments, and I can't identify where this workers own budget comes in. My questions:
  • How much funds have been collected through this worker?
  • Where are those funds shown in the table of https://bitsharestalk.org/index.php?topic=25196.15?
  • Is there anything left over that will be returned?
  • Can you please clarify what "market fee for huodongxing" and "safeguard service" is?

Please summarize and finalize this worker before tapping into funds of another worker.

198
Thanks, sounds reasonable to me, and also aligns with how I understood it.

199
General Discussion / Re: System requirements for automatic trading
« on: July 24, 2019, 06:02:14 am »
Have a look at dexbot and extinctionevent first. Market making and ta trading bot.

200
We have curated publications done through the worker under

https://github.com/bitshares/marketing

and we intend to add other worker funded publications as well. For Visbility, we are tracking the communcations transparently under

https://github.com/bitshares/marketing/issues

Please feel free to add links to this repository and it will get action. In light of another worker being funded and the possible impact we have decided to re-define the optional article of this worker to be the production of short 10sec video clips promoting BitShares. Other ongoings are attempts to get feature articles out (e.g. Direct Debit), unfortunately first drafts are lacking quality and will likely need to be completely redone.

201
General Discussion / Re: New BSIP:GS protection via core code
« on: July 19, 2019, 03:59:23 pm »
Followed abit's style and added a 6th option to https://github.com/bitshares/bsips/issues/179#issuecomment-513269772

202
General Discussion / Re: New BSIP:GS protection via core code
« on: July 19, 2019, 10:16:14 am »
then bitUSD holders begin to exploit debt position owners with force settlement.

even worse, the last bitUSD balance cannot do force settlement, it can only fill the settlement orders with higher price.

I don't understand how that exploit works. If I force settle while there are positions with CR < 1 are present, I settle for BTS that are worth less then 1 USD, accepting the undercollaterization. This also closes out the bad margin position, but that is of course the risk of running a undercollaterized position (it's a loss-loss scenario so I expect this is not an exploit for you). In my scenario force settlement still eats the margin position with least CR. There will of course be margin call orders with a price different than the feed price, but that does not force the traders to deviate from the peg. Can you please make another example please?

203
General Discussion / Re: New BSIP:GS protection via core code
« on: July 19, 2019, 09:09:52 am »
Let's assume we want to explicitly allow undercollaterization. In my opinion, a more suitable way would be to implement a bitasset parameter "prevent global settlement", which then can be turned on by committee, and leave the price feed as is. Then the undercollaterization is transparent.

What are your thoughts on that?

what does bad debt mean? which means the debt in the position cannot be fully paid by selling the collateral with margin call/force settlement referencing the market price.

then you choose to disable margin call and force settlement while bad debt appears? or you allow the existence of a debt position with pure debt and 0 BTS?

Margin call price would need to be adjusted. If CR is less than MSSR, adjust the price such that the full debt would be bought (which is essentially their global settlement price). If CR is higher, use existing rules. Force settlement would still eat the least collaterized positions first, in that sense the punishment goes to holders that decide to force settle instead of sell on the market. Incentivization would be possible by adjusting the force settlement price if it settle a margin position with CR < MCR (the force settlement offset could then be MSSR (punishment for margin position holder)).

For the bitasset holders it is similar as compared to being in global settlement state.

With "prevent global settlement flag":
 - bitasset holder can sell into the margin calls which is equal or even better compared to global settlement price instead of force settling
 - bitasset holder can force settle, accepting the undercollaterization
 - margin position holder can recollaterize
 - new margin positions can be created
 - margin positions with CR < 1 receive a bit of protection that is shifted to bitasset holders iff they are using force settlement, on the other hand force settling is incentivized if applied to a margin position that is currently being called

204
General Discussion / Re: New BSIP:GS protection via core code
« on: July 19, 2019, 07:12:25 am »
Let's assume we want to explicitly allow undercollaterization. In my opinion, a more suitable way would be to implement a bitasset parameter "prevent global settlement", which then can be turned on by committee, and leave the price feed as is. Then the undercollaterization is transparent.

What are your thoughts on that?

206
Technical Support / Re: how to withdraw the market fee sharing?
« on: July 18, 2019, 12:29:47 pm »
Latest development can be found under develop.bitshares.org, might contain unstable nightly builds.

207
Voted, directly on the site :)

208
Thanks for the initiative in the indian market!

Questions:
 - Will they be creating all marketing content themselves, or are we needed to create it?
 - Do they have statistics available for the last 3 or 6 months? What they have posted is quite old
 - I personally find 4 BTC quite expensive, is that their final offer?

Cheers,
  Stefan

209
General Discussion / Re: Cleaned out!
« on: July 12, 2019, 08:54:10 pm »
I say it again this is the UI team's fault
they got many payment but continue give us a shit.
I don't known why anybody can be shown as a receiver in the form, even filled automaticly.
I don't known why anybody create a prosposal can be shown in your wallets
when we use a traditional financial app, we known we should only trade to the one in whitelist.

Please have a look how the UI renders the proposal scam at this point. I'd say it is impossible to accidently approve it.

@kurtduncan
You must have been using an old version that did not show you the warning. I checked your history, at the moment you approved the proposal your account was handed over to the attacker. There were 4 proposals showing in your account at this point in time. Unfortunately there is not much that can be done, if you are lucky the gateway can mitigate by blocking quick enough.

210
i would be happy to help there. best channels sould be tg/wechat or some other live messenger. let me know if interested.

Pages: 1 ... 7 8 9 10 11 12 13 [14] 15 16 17 18 19 20 21 ... 45