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

Pages: 1 [2] 3 4 5 6 7 8 9 ... 45
16
General Discussion / Re: Help me Identify the Top 10 most harmful laws!
« on: December 05, 2015, 09:25:06 pm »
Just don't register to vote and you never get called in the first place.

it's a little harder.
Don't register to vote, don't register a vehicle or get a driver's license, don't have a job that requires a W4 (don't pay taxes), and don't receive any federal or state assistance (unemployment benefits)

17
General Discussion / Re: Network Stability Under Graphene
« on: December 05, 2015, 09:05:35 pm »
I don't really think that running the very backbone of bitshares in a t2micro is a good practice at all, even if it seems to run "fine".

Witnesses should always be ready and able to deal with sudden increases in resources required by the network, and this is not possible with a t2micro.
What happens if a spam attack strike on bts? That low-end server will not be able to bear the attack.
What if all the witnesses run on a t2micro? Bitshares network dies.

And you can not even assume a priori that you will be always ready to manage your instance in time to mitigate an attack.
What if you are outside and can not connect to your servers or server's hosting? What if you are just sleeping?

Witnesses should always look at what could be the next required resources and their servers should always be capable of sustain a lot more requests that the current ones.
...
So no, the witness pay should not be only barely enough to pay the server's rent.
It should be high, to put more weight and responsability to the witnesses and to push them to do an exellent job.
+5%
witnesses need to be able to scale, and this can't be a hobby if it will succeed long term. If things go well, I anticipate witnesses actually being professional operations (like miners are really now large companies). And they must be paid accordingly well. We will hire/fire companies based on performance.

18
General Discussion / Re: CCEDK Trading Team
« on: December 04, 2015, 03:13:01 pm »
Here are some strategies
https://cryptotrader.org/strategies

https://tradewave.net/help/trading
(Moving Average Crossover
Bollinger Band Mean Reversion
Honey Badger Ice Float
Breakout w/ Mathews Drop
OBV Lite 1.4
6 SAR Harmonica)

http://www.mathworks.com/matlabcentral/fileexchange/?term=trading
http://www.mathworks.com/support/books/book58750.html?category=4&language=1&view=category

There isn't one "right" solution, and there is always a chance you will lose. I'd suggest starting there, then discussing details of strategies as you learn them.

19
General Discussion / Re: feed price should expired over 1 hour
« on: December 04, 2015, 03:05:10 pm »
sorry about that, just turned it on for the first time last night (see other post) and the cron job didn't run while I was asleep. fixed now

20
General Discussion / Re: Incentivising Liquidity
« on: December 04, 2015, 02:39:10 am »
I keep saying it and will say it again.

We need relative orders that allow orders to be placed in relation to the feed price and then move with it.

If you had a script that did that, but you had to pay a transaction fee when the price drifted by some value from the original, would you use it?

It can be implemented using your own server (I'd make a worker to write the tool and split it with xeroc for using his library). But without a hardfork and some serious coding, it isn't immediately implementable on the chain.

I'm against this because put a lot of trust in the publishing feeds and risk on the system since witness could easily manipulate the feed and run with a lot of money. Also this can easily be work around using third part tools or bots.

I'm actually talking about making a third party tool or bot to do what jonny's asking since you can't do it on the chain.

That's a fair concern about relying on someone else's data. You could use your own feed so it doesn't rely on anyone else.

21
General Discussion / Re: Incentivising Liquidity
« on: December 04, 2015, 01:56:55 am »
I keep saying it and will say it again.

We need relative orders that allow orders to be placed in relation to the feed price and then move with it.

If you had a script that did that, but you had to pay a transaction fee when the price drifted by some value from the original, would you use it?

It can be implemented using your own server (I'd make a worker to write the tool and split it with xeroc for using his library). But without a hardfork and some serious coding, it isn't immediately implementable on the chain.

22
Stakeholder Proposals / Re: Is maqifrnswa active?
« on: December 04, 2015, 01:45:35 am »
ok, publishing

for the record I am on both sides of many markets and am publishing feeds. if someone has a problem in the future, don't hesitate to speak up

23
Stakeholder Proposals / Re: Is maqifrnswa active?
« on: December 03, 2015, 08:04:24 pm »
I haven't have any communication with him, and he haven't published any feeds. What status now? @maqifrnswa

i'm quite active ;-)

There is a slight conflict of interest with me publishing feeds. By measurement of trading fees paid, I'm the most active trader by far. Since I've been making trades based on forced settlement and feeds, it appears to be a conflict of interest setting the feeds that I directly profit from.

I really would prefer being a worker and maintaining linux distribution of bitshares (and raspberry pi nodes/wallets), but there doesn't seem to be an interest in funding that. So, for now, I've been justifying running https://launchpad.net/~bitshares/+archive/ubuntu/bitshares (ppa:bitshares/bitshares) and the preliminary page at http://162.243.185.205/ off of witness pay. I've also kept the market maker "maqifrnswa.bot" running with witness pay, which might also be something for a worker.

Since the start, I only want to be a witness for as long as I am useful. If I'm no longer useful without feeds, please cut me out

24
General Discussion / Re: so disappoint for this community
« on: December 03, 2015, 12:17:01 am »
Keep fighting,  I personally want independent thinking committee members with diverse opinions that can come up with their own conclusions, and back those conclusions with evidence.

"I disapprove of what you say, but I will defend to the death your right to say it."

Committee members should try to change minds, be open to have their minds changed, and stand against the flow for what they think is right.

25
Stakeholder Proposals / Re: witness, please add 2% for settlement price
« on: December 02, 2015, 03:28:03 pm »
I'd suggest everyone review some of the discussion and analysis that took place 7 months ago on these topics. 

https://bitsharestalk.org/index.php/topic,16143.msg206715.html#msg206715

There's a good bit of valuable information there.

excellent post, thank you for re-finding it!

26
Technical Support / Re: Number of Witnesses
« on: December 02, 2015, 03:25:22 pm »
because witnesses have to pay for servers and so on. more witnesses = less money for them.
Almost .. All witnesses are paid a fixed amount of BTS.
More witnesses means more costs for the DAC.

I don't think it works like that, each witness gets the same pay per block -- so more witnesses doesn't effect DAC expenses but reduces witness daily pay since each witness gets fewer blocks.

27
Stakeholder Proposals / Re: witness, please add 2% for settlement price
« on: December 02, 2015, 03:12:49 pm »
I agree with the concept, but I want to ask if this is the correct technical and organizational way of handling this.

1) Should changing the behavior of the system be a committee decision, not a witness decision?

2) Is the "correct" technical way of implementing this is to change
"force_settlement_offset_percent": 0
to
"force_settlement_offset_percent": 200

rather than messing with the feed? Adding a feed offset might complicate something else in the system, but there is a parameter that can be tweaked to do exactly what you want: charge settlers a premium for settling, and the premium goes to the shorter.

Code: [Select]
locked >>> get_object 1.3.120
get_object 1.3.120
[{
    "id": "1.3.120",
    "symbol": "EUR",
    "precision": 4,
    "issuer": "1.2.0",
    "options": {
      "max_supply": "1000000000000000",
      "market_fee_percent": 0,
      "max_market_fee": "1000000000000000",
      "issuer_permissions": 511,
      "flags": 128,
      "core_exchange_rate": {
        "base": {
          "amount": 12,
          "asset_id": "1.3.120"
        },
        "quote": {
          "amount": 37854,
          "asset_id": "1.3.0"
        }
      },
      "whitelist_authorities": [],
      "blacklist_authorities": [],
      "whitelist_markets": [],
      "blacklist_markets": [],
      "description": "1 euro",
      "extensions": []
    },
    "dynamic_asset_data_id": "2.3.120",
    "bitasset_data_id": "2.4.20"
  }
]

Code: [Select]
locked >>> get_object 2.4.20
...
"current_feed": {
      "settlement_price": {
        "base": {
          "amount": 6,
          "asset_id": "1.3.120"
        },
        "quote": {
          "amount": 19867,
          "asset_id": "1.3.0"
        }
      },
      "maintenance_collateral_ratio": 1750,
      "maximum_short_squeeze_ratio": 1100,
      "core_exchange_rate": {
        "base": {
          "amount": 12,
          "asset_id": "1.3.120"
        },
        "quote": {
          "amount": 37854,
          "asset_id": "1.3.0"
        }
      }
    },
    "current_feed_publication_time": "2015-12-02T04:35:06",
    "options": {
      "feed_lifetime_sec": 86400,
      "minimum_feeds": 7,
      "force_settlement_delay_sec": 86400,
      "force_settlement_offset_percent": 0,
      "maximum_force_settlement_volume": 2000,
      "short_backing_asset": "1.3.0",
      "extensions": []
    },
    "force_settled_volume": 0,
    "is_prediction_market": false,
    "settlement_price": {
      "base": {
        "amount": 0,
        "asset_id": "1.3.0"
      },
      "quote": {
        "amount": 0,
        "asset_id": "1.3.0"
      }
    },
    "settlement_fund": 0
  }
]

EDIT
Changing feed Params is like a country revaluing its currency.  Bad idea.  Instant 2% loss to everyone who was playing by the rules.
this is true, another reason why I think this should be done through committee as it has to weigh the pros and cons of the change

28
@merivercap  -- I actually agree with your points, thanks for articulating them

1)The concept of BitUSD is unusual to someone that is used to just showing up on polo (or where ever) and knowing that they bought/sold in USD. The concept that USD trades for more in the DEX than on polo does sound weird, and can make inter-exchange arbitrage harder to do (or will make you lose money if you do it blindly). The plus side is that if you accumulate $10 million USD on polo, good look trying to get that out in one shot. If you accumulate $10 million in bitUSD, the blockchain will happily cash you out whenever you ask for it. Maybe you're right, maybe marketing bitUSD as "premium" USD or USD++ will be a better indicator to new users that something is different about them, and what the benefits of having them are so they are willing to pay a premium for them (especially since it's possible they will cash them out for more than 1 USD at the end as well)

2) I do agree that incentives to go short aren't as clear. I wrote a post before bitshares 2 was released: "Why would anyone short in BitShares 2.0?" I seriously asked the question, because I couldn't figure out the answer mathematically right away. It comes down to the requirement that bitshares is profitable and will gain in value of the smartcoin in the long term. You short for long-term gain... also kind of counter intuitive, and also risky

29
General Discussion / Re: my plan to adjust SQP
« on: December 02, 2015, 03:04:40 am »

Benefit: Margin calls should be avoided unless absolutely necessary since it takes smartcoins out of circulation when the market is too thin to begin with. The most accurate/liquid market should be used to establish when a market call occurs, and at this moment the feed is a best. Feed is 100% SQP.


If you want to avoid margin calls, why not just reduce the margin call limit?  Instead of triggering at 175% collateralization, trigger at 150% or lower.

Its my understanding that SQP is on its way out, so perhaps we shouldn't be designing around it.  But in any event I think this SQP limit should not be reduced to 1000.  If smartcoins are designed to trade at a premium,  selling the smartcoin at the feed is the worst deal you should ever expect to get.  Margin call orders, as they approach <100% collateralization are the most urgently needed to fill.   You don't put the most urgent need at the least desirable price.  It may never get filled. 

I'd suggested elsewhere having margin call only trigger if the feed crosses your limit. Like BTS-0.9  Only then would it reach out and try to fill the order, but it's restricted by a limit, again like BTS-0.9  ;  As the feed moves beyond your margin call limit, the urgency to fill the order is greater.  The limit could start at 0% of the feed once triggered, and slowly extend out, up to 10% or more as it approaches black swan <100% collateralization.

I deleted my post after thinking a bit more, sorry for the noise. (I was hoping it would be deleted before anyone saw it!)

I agree with you that SQP shouldn't be used to avoid margin calls. It also shouldn't be 100% for the reason you give: those calls urgently need to be filled, and they won't at 100% SQP.

I didn't know SQP was going to be removed; but I did know that margin calls will only be triggered if the feed crosses your margin call limit:
https://github.com/cryptonomex/graphene/issues/436
https://github.com/cryptonomex/graphene/compare/436-fork-feed-protect

Even with this change you probably need some SQP to protect shorts and prevent margin calls from accidentally triggering a blackswan in a thin market.

Given that margin calls will only be triggered if the feed crosses your margin limit:
--In a normal market where bid/ask is within 10% of the feed (see current bitUSD:BTS), SQP doesn't really do much except protect shorts from being "ripped off." Shorts see this as a penalty, but the bitUSD has to come from somewhere and SQP limits how big the penalty will be. In a liquid market, you shouldn't even need SQP as there should be enough for sale at market rates. SQP can't be 0, because they have to be cleared from somewhere otherwise margin calls and collateral are meaningless.

--In a broken market where bid/ask is greater than 10% from the feed (see current bitBTC:BTS), SQP creates an invisible buy wall that slows the market from converging to the peg. Someone's going to have to bite the bullet and short to clear out all the margin calls, otherwise price will linger at feed+10%.

SQP also helps me price risk - if the biggest penalty I can pay is 10%, I know that anything I short greater than 10% should be immune to risk associated with bitASSET:ASSET spread.

30
General Discussion / Re: Liquidity has a Price -> Adding Maker / Taker
« on: December 02, 2015, 12:44:37 am »
I wasn't attempting to propose any particular solution, merely to point out that if you want a to encourage liquidity it must be paid for by someone.

Furthermore, I am contemplating a solution to this that doesn't involve dilution.  Think about sharing a cut of all future BitUSD fees with those who provide liquidity in that market early on. 

The early participants to the market are the ones who give it life, the late comers don't benefit from the fees.  In other words, make BitUSD a "profit center" where the profits go to those who make it a successful business.

I don't see that as being a viable solution. You talk about revenue from fees as if it were substantial enough to encourage participation. They simply aren't. Bitshares is too small, and its prospects are meager at best.

I think he's talking about future fees, which may or may not be big.

I'm in favor of using accumulated fees to jump-start the system directly and as simply as possible - what about using the fee pool to set up sell walls or use a worker to buy?

We could fund a worker where some % goes to the operators as a "fee," the rest goes to short walls at feed +5% (or something else). Proceeds from the short wall sales go straight back in to collateral. Whenever the community is happy, the worker can stop and the multisig account can just be sitting short. That account can sit short indefinitely, essentially another reserve account. It can be margin called or force settled, it's fine and doesn't matter -- its roll was to generate smartcoins and any remaining BTS is out of circulation. Another worker proposal can allow the trustees of the account to close out the debt and refund remaining BTS to the reserve account (or fund jumpstarting another market).

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