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 ... 12 13 14 15 16 17 18 [19] 20 21 22 23 24 25 26 ... 102
271
Technical Support / Re: Memo maximum field size?
« on: November 26, 2017, 09:32:13 am »
There is no limit, AFAIK, but you pay an additional fee per kb.

(Technically there is a limit, of course, like max block size etc.).

272
Technical Support / Re: What is virtual transaction / operation?
« on: November 23, 2017, 10:24:42 pm »
What is a transaction, that has "virtual" in the place of it's ID?

The account history log is based on operations. Most events are directly triggered by user operations - for example, if user A sends funds to user B, user A creates a transfer_operation with the amount to send and the IDs of users A and B as parameters.
Some events are not directly triggered by user operations, though, or the connection between operation and event is not obvious. Such events are represented by virtual operations. For example, when an order is filled, a virtual fill_order_operation is created by the blockchain logic.

273
Stakeholder Proposals / Re: Poll: BSIP 26 & 27
« on: November 23, 2017, 08:01:26 pm »
Thanks for bringing this up, @abit!

tl;dr:

BSIP-26 will change how the refunding of limit order creation fee works when the order is cancelled. Currently, the refund always returns the fee in BTS, even if it was originally paid in some other asset through the asset's fee pool. The motivation for this change is that this behaviour has more than once been abused to "sell" an asset for BTS.

BSIP-27 is meant to solve a problem that is created through BSIP-26. Currently, half of the asset creation fee is deposited into the fee pool - and there is no way to get these funds out again. The fee refund mentioned above could be used as a workaround for this, but that will no longer be possible after BSIP-26 has been implemented.

----

I think BSIP-26 is a good idea and I support it.

I think BSIP-27 is unnecessary and can be replaced by a simple change of the asset creation logic - i. e. the asset creation fee should be reduced, and the automatic funding of the fee pool upon creation should be removed.

274
General Discussion / Re: Newbie question about BitUSD peg
« on: November 17, 2017, 06:43:02 pm »
So here is my question: what happens if the market gaps when volatility becomes extreme? Isn't there a chance that pegs such as BitUSD break in the event of a black swan?

A black swan *is* the situation when a bitasset becomes undercollateralized. When that happens, the settlement guarantee that defines the peg is replaced by a fixed exchange rate bitasset -> BTS, so essentially the bitasset is pegged to a fixed amount of BTS instead of its "real" counterpart.

This has already happened to some bitassets, like SEK, RUB, KRW, and more recently GOLD and SILVER. We are currently deploying a method to re-collateralize bitassets after a black swan to make them usable again.

275
Technical Support / Re: Avoid forking
« on: November 17, 2017, 06:37:39 pm »
So we tried what you proposes, and in order to make it, we had to start a first node with the property to true, otherwise, it doesn't start.
then, we added two nodes with enable-stale-production with false, and we restarted the first node, changing the param from true to false as well.

Good, keep it like that.

Then, we tested again, disconnect the network, reconnect the network, and we had the same effect as before.

I think you must also set the "required-participation" parameter so that a single node notices that it's on a minority chain. I. e. if you have three nodes, required-participation should be > 33% on each.

276
Technical Support / Re: Avoid forking
« on: November 17, 2017, 02:07:35 pm »
Make sure "enable-stale-production = false" is set in your config.ini (on all nodes).

277
General Discussion / Re: DPOS Resilience From Government Censorship
« on: November 16, 2017, 04:53:47 pm »
What protects the anonymity of the witness nodes?  What's to prevent an attacker from finding the replacements quickly? 

Well, it's not like the nodes (i. e. the actual servers) are advertising themselves as witnesses. How would you find a witness server?

To find out the location of a witness server, an attacker could attempt to measure at what time nodes become aware of blocks signed by a certain witness. But a witness node does not (or at least should not) have an open p2p port for everyone to connect, which makes it close to impossible for an attacker to find the actual IP address. At least for an attacker with reasonable power. Witnesses can put additional protective layers around their nodes, like connecting only to trusted relay nodes, and hiding their own traffic in IPSEC.

Similarly, the witnesses themselves (i. e. the owners of the blockchain accounts), can hide themselves by using different nodes to publish their own transactions, connecting only via TOR, and so on.

278
I think our bitCNY problem is caused by people in China moving from CNY into (other) cryptos, using bitCNY and BTS as intermediates. I. e. CNY -> (via magicwallet) -> bitCNY -> (via forced settlement) -> BTS -> BTC (or other cryptos).

That would explain why CNY:bitCNY is trading above the peg, while at the same time BTS:bitCNY is trading below - if there was real demand for bitCNY, people would buy it on the DEX. In reality, people are dumping bitCNY for BTS either on the DEX or via forced settlement.
I think changing the settlement offset will not change this situation - it would only continue on a different level. (It seems the proposal has been accepted by now - we will see if it helps.)

BTS has been in an uptrend during the past couple of days. It is normal that during a BTS uptrend bitassets trade below the peg, because the settlement delay means that the bitasset is actually pegged to the expected price one day in the future.

Some people are arguing that the price feed is off, because the indirect price CNY->bitCNY->BTS doesn't match the feed price. I think that argument is invalid because of the abovementioned dependency between the bitCNY->BTS price as seen on the DEX and the feed price. The feed price must not be calculated as a function of the internal trade price, because that would create a feedback loop, and feedback loops are inherently unstable.​

279
General Discussion / Re: DPOS Resilience From Government Censorship
« on: November 15, 2017, 04:04:29 pm »
If the witnesses come under attack they can be replaced with anonymous users in no time. It might be difficult to track down the nodes, too - you can only attack the datacenter if you know where a witness node is located.

280
Good news, but please note that bitKRW is currently in global settlement. After the next hardfork (planned for Dec 08), witnesses can publish a price feed for KRW again, which should revive the asset.

281
most of witnesses aren't doing the job well, as they have been failed to report for days.

Hm... what if all witnesses stop feeding a price for bitCNY until the markets are aligned correctly? That would prevent forced settlement for the time being.

282
I am a big shorter, how can I scam the DEX users?

1. You sell bitCNY and promise that holders can settle their bitCNY for an equivalent amount of BTS within 24 hours.
2. After selling, you use your voting power to change the settlement offset, depriving bitCNY owners of 5% of their holdings.

But we've had that discussion before, and I guess neither one of us will change their position.

Instead we should try to find a fair solution.

The real problem is a disparity of markets. You are quoting an outside market (magicwallet), which pays more than 1 CNY for a bitCNY. On the DEX, we see (right now) a trading price of 1.76 BTS/bitCNY and a feed price of 1.84 BTS/CNY, from which we can calculate that on the DEX you can buy at .956 CNY/bitCNY.

In order to realign the markets, trading must occur.
For example, someone could buy cheap bitCNY on the DEX and sell it on magicwallet for a profit. Or (which is what shorters should be doing), buy cheap bitCNY on the DEX, and close their position with a profit while at the same time pushing the DEX price up towards the feed price.

Why is that not happening?

according to your logic, now I should sell BTS in DEX to lower the price as feeded?

the problem is:
1. after I doing this, I have no way to buy BTS back at the feeded price, I am at risk if the BTS price goes up.
2. as a big shorter it's not easy to avoid being settlement by reducing debt,  even I avoid, some other shorters will be settled, as committee we need to find a solution to make sure any shorters won't be settled unfairly!

You don't have to buy BTS back, you can reduce your collateral as well as your debt.

listen, there is no low or high bitCNY price, bitCNY price are stable, there's only high or low BTS price,

That doesn't even make sense. Prices are always relative to something. The price of bitassets is expected to be unstable, because there is no fixed peg - it's a Market-Pegged Asset, and the market needs some space to move. The mechanism of MPAs encourages trading that moves the price towards the peg, that's how it works. This trading is currently not happening, which is at least partially responsible for both the market disparity and the current "speculators" who buy cheap and force-settle.

http://docs.bitshares.eu/_downloads/bitshares-financial-platform.pdf - section 2.

283
We've had a lengthy discussion on the subject before, and back then we were arguing about 1%, not 5.

I think the settlement offset is a blatant violation of the settlement guarantee. Raising the offset means ripping off the holders of bitCNY, which will further serve to destroy the credibility of bitAssets as a concept.

It is especially unfair to those who have already requested forced settlement, because they cannot undo their settlement requests. They will simply receive another 4% less than what they were supposed to receive.

Once again the largest shorters of bitCNY are abusing their power to scam the users of our DEX.

284
Great move!

285
II think that your earnings are someone else's loses so all backed BTC should be able to pay all earnings, am i wrong ?

In the grand scheme of things it's correct but irrelevant. Your gains on the dex can be completely independent of your trading. You can just hold your coins there and the price can suddenly surge - who's loss is it? Some guys from China? How do you track it?
The trading-related gains are indeed losses for someone else, but again, how do you track it?

Your original point was this:
If I understand it correctly, the solution of having bitshares-controlled btc wallet won't work in the scenario of depositing btc to the dex, then gaining profit from trading and then withdrawing. The wallet will have only the btc that is deposited there, so you won't be able to withdraw all your newly found money.

There are two different kinds of profit to look at here:
1. You deposit BTC, BTC goes up in value, you withdraw you BTC and you are richer than before. This is not a problem for the gateway, because the gateway holds the exact amount that you deposited and will return that to you upon withdrawal.
2. You deposit x BTC, someone else deposits y BTC. After some trading you own x+y BTC. You withdraw x+y BTC for a profit of y BTC. This is not a problem for the gateway either - x+y BTC have been deposited, and x+y BTC will be withdrawn.

Pages: 1 ... 12 13 14 15 16 17 18 [19] 20 21 22 23 24 25 26 ... 102