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 - pc

Pages: 1 [2] 3 4 5 6 7 8 9 ... 102
16
General Discussion / Re: D*Match betting in chain
« on: October 23, 2019, 05:25:45 pm »
Is a prediction asset can be reusable ?
It's too expensive to create one for every NBA match for example !!

Unfortunately they aren't. This is a known problem.

17
General Discussion / Re: D*Match betting in chain
« on: October 21, 2019, 04:55:42 pm »
I wish to experiment how long can i reach in develop a betting app with BitShares prediction markets.
[...]
* The second project (monotoken (smartasset wallet)) failed for not being according to locals laws.

Erm, did you check that betting apps are in line with your local laws?


 i don't have nor the hardware neither the ability to operate a node,

You don't *have* to run a node yourself. You should start on testnet. I'm sure someone has a public API node there.

The idea is to bring a new interpretation of the blockchain data rather than modify the protocol to adapt to this use case.

Keep in mind that the chain and the original interpretation are still there. In particular, your assets can be traded, which should be aligned with your new interpretation.

18
General Discussion / Re: Committee Fund Operation Review
« on: October 20, 2019, 12:13:59 pm »
> but now, we have threshold feed price, which remove the problem, and now we can borrow with margin call price < threshold feed price without worrying margin call.

The threshold price is not set for eternity. See e. g. this proposal: https://github.com/bitshares/bsips/issues/244
If this gets accepted the committee debt posiition would instantly be margin called. Also note that the external price for BTS is less than 0.19 CNY whereas when selling CNY on the DEX you have to pay 0.202 CNY/BTS. In other words, the committee would lose more than 6% with this deal, even without BTS going down.

19
It's not quite so simple, but possible. See BSIP-17 for some details.

20
General Discussion / Re: I come from the cn-vote
« on: October 19, 2019, 04:09:48 pm »
Ok.Nobody is "blocking" the proposal. Actually I think it's much better than BSIP-76.

There is discussion going on because people want to understand it better. It was inaccurate in some respects, and it presented no explanation as to why the proposed changes would solve the problems nor why certain constants are set the way they are.

21
I didn't say that MSSR = 10% and GS were *sufficient* incentives. But at least there *were* incentives. Now there are none.

22
The problem is solved if Joe is allowed to pay his debt in an asset other than BitUSD.

No it isn't. How should it work?

1. Ana still has 500 bitUSD and relies on the settlement guarantee, i. e. she expects to be paid $500 worth of BTS whenever she wants to cash out.
2. The blockchain has created the bitUSD from thin air. It can only destroy them when they are paid back. If Joe pays his debt in BTC, then the blockchain can't burn the BTC, and even if it did the bitUSD would continue to exist.

I agree with your analysis that with many people sticking to their bitAssets instead of trading them the system can't work if the collateral is in a downtrend. However, BitAssets come with the promise of stable value. With that promise, it is only natural (and perfectly acceptable IMO) that people buy and hold BitAssets when BTS is in a downtrend.

What's missing is an appropriate incentive for BitAsset holders to sell their holdings, thus reducing the debt. The original design of BitAssets came with two such incentives, both of which have been effectively scrapped by now:

1. MSSR - a large MSSR rewards holders for selling into margin calls. Because this mechanism leads to a premium on the market price (and because it is expensive for debt holders), MSSR has been reduced further and further, which has improved the peg but also removed the incentive to sell into margin calls.

2. Global settlement aka Black Swan - global settlement is like a Damocles' sword pending above both BitAsset holders and debt holders. It sets a limit to the promise of stable value, and thus provides another incentive for BitAsset holders to sell their holdings, because if they stick to them for too long they will start losing value. Thanks to Global Settlement Protection, this threat has been muddied and partially removed.

23
General Discussion / Re: I come from the cn-vote
« on: October 18, 2019, 06:29:17 pm »
Are you talking about this? https://github.com/bitshares/bsips/issues/244

24
according to the community's consensus.

There is no consensus wrt the price feed. A decision was made by a majority of stake.

25
Excellent, thanks George!

26
I created 2 committee proposals to remove the "witness_fed_asset" flag from bitCNY and bitUSD.

https://cryptofresh.com/p/1.10.50330
https://cryptofresh.com/p/1.10.50333

Thanks @abit . I support this.

I like very much the idea from Dan Notenstein aka blocktrades to use BitShares Decentralized Exchange (DEX) market for BitUSD and BitCNY pricefeeds.

I have often pointed out that this will create a feedback loop, because the feed price already affects trading activity on the DEX. Feedback loops are inherently unstable and dangerous, and should be avoided.

27
Stakeholder Proposals / Re: [Poll] BSIP76:Set bitUSD feed threshold
« on: October 15, 2019, 11:34:42 am »
Sapiens has a point. Bsip76 is effectively taking a Globally Traded and long term marketed as stable asset and creating an artificial difference in its price, and that is being done in order to benefit a specific group of people.

Out of the top of my head I can think of at least 5 different reasons why this can make for a legal investigation.

I agree, absolutely.

28
I suppose you mean this:

{
          "amount": {
            "amount": "38611393904",
            "asset_id": "1.3.0"
          },
          "extensions": [],
          "fee": {
            "amount": 47737,
            "asset_id": "1.3.0"
          },
          "from": "1.2.90162",
          "memo": {
            "from": "BTS8BbZqGbPVjHkYtswX92QbJwgAKovnwkRddW4Qq3zvyLYWKCD88",
            "message": "aec3266640276c866e87de1a891441c6",
            "nonce": "401396210379214",
            "to": "BTS7N3Y2ozxLvnRk5z2bQXHoTY431aLnizi1KhjcU1CreYtXrZM8C"
          },
          "to": "1.2.444403"
        }


"BTS7N3Y2ozxLvnRk5z2bQXHoTY431aLnizi1KhjcU1CreYtXrZM8C" is the memo key of the recipient. The recipient *account* has ID "1.2.444403", the sending account has ID "1.2.90162".

It seems that the explorer is out of sync. Other explorers show the transaction, e. g. https://bitsharescan.com/account/joeboomofo, and it's also in your account history on https://wallet.bitshares.org/#/account/joeboomofo .

29
General Discussion / Re: BitSharestalk.org - now fast again
« on: October 07, 2019, 04:32:03 pm »
Thanks @xeroc!

30
Technical Support / Re: Private testnet questions
« on: October 07, 2019, 06:06:16 am »
Then I don't understand your question. If you've done your own gateway you should be the one who knows how it works.
What does your gateway do if not the points I listed above?

Pages: 1 [2] 3 4 5 6 7 8 9 ... 102