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

Pages: 1 ... 10 11 12 13 14 15 16 [17] 18 19 20 21 22 23 24 ... 64
241
In the past 3 months the dev team has produced more than the 9 months before it and this work will be made public in a few weeks.
This is the secert sauce? :o
really hope this time will not delay or just a empty promise.
I don't think it's an empty promise.  I'm pretty convinced they're really working on something big and that they're really excited about it.  The question is whether community will share that excitement.

Personally I think the dev team is getting stronger, and they started out pretty good, so I expect what they're all so excited about is quite worthwhile.

242
We also got some great news!
Factom and bitsapphire teamed up to create an Identity Management System for the Moonstone Wallet.
"Bitsapphire will be creating a new level of KYC for their Moonstone crypto wallet. It will allow users to transfer and trade among Bitcoin, BitAssets, User-Issued Assets, and other tokens. It will be available in the next 6-12 months with customer identification via the Factom protocol."
You can check this link for more information: http://blog.factom.org/post/118735295389/fun-new-things-happening-at-factom

That is indeed great news...for factom that is.

It was not enough that peertracks are ripping the benefits of moonstone and not paying a dime, but now we have a new project that is milking Bitshares. Very nice thank you!

Do you have other project interested in bitshares money? I am hearing the left arm of factom - mastercoin is not doing so great? Don't they want to milk of BTS as well. Why the wait? Bring them on. I am sure they can think of feature that moonstone can provide for them...all paid using BTS delegate dilution! How can they say 'No'?

Indeed. if that depends on the success of the moonstone wallet, why won't those projects fund the $130,000 you need? It's in their best interest to do so.

Might aswell add a powered by BitShares mark on Factom since it's squeezing BTS funds

I don't know what this fuss is about. This is what the blog post says:
Quote
They are now building an identity management system backed up by Factom’s API for Moonstone.
Looks like Bitsapphire has chosen Factom’s technology to enhance the new Moonstone wallet - what's wrong with that? Factom is not a competitor for us.
I assume that Factom customers will not be using the wallet - but even if they do, it might be beneficial for us in the long term.
And Bitsapphire is not using BTS funds, they are just fund raising using the tools we have created for this purpose: BitShares UIA. Again, what's wrong with that?
(and it just happens that the cause of their fundraising, i.e. their new wallet, might be good for us)

Last I heard, BitShares is going to support whitelisting for UIAs natively, and BitSapphire wasn't particularly working with the core devs to make anything compatible.  Funding, making, and marketing a new wallet that relies on a tangle of other blockchains to support the basic features of our blockchain seems inefficient, at best.

243
General Discussion / Re: Wrong short amounts displayed in the GUI
« on: May 13, 2015, 12:54:40 pm »
See also https://github.com/BitShares/bitshares/issues/1541

Thanks, I was just about to link that.

The weird part to me is that collateral is determined at time of order placement based on the price feed, but the quantity of BitAsset is determined at time of execution based on sale price.  It seems to me that choosing to overcollateralize your short should be a separate issue from setting a premium on its price.  Minimum collateral should be feed * margin call ratio, and starting collateral should be 2 * feed + sale price, instead of 3x sale price as it is now.

This may not be worth dealing with depending on the plans for replacing BitAssets.

244
Muse/SoundDAC / Re: NOTES are listed ar CMC
« on: May 12, 2015, 07:27:58 pm »
Last I heard, PeerTracks is a closed source, privately managed front-end to the open source BitShares Music blockchain.

245
Random Discussion / Re: An "arbitrary data" bug in the blockchain?
« on: May 11, 2015, 12:38:15 pm »
Does anyone here know how to code a simple trap for this? There's now a 40,000 BTS bounty for you. ::)
this shouldn't be an issue.

For me, that's not good enough. If someone downloads a client that WILL, then we all have a big big problem. We do not want to be on the end of that stick.
 
Does anyone here know how to code a simple trap for this? There's now a 40,000 BTS bounty for you. ::)

If someone writes a malicious client that executes arbitrary data from the blockchain, they might as well include malicious code in the client itself.  Our blockchain cannot protect people from downloading malicious software.

EDIT: If for some strange reason the attacker was determined to get the destructive payload from the blockchain, any traps could be avoided by disguising the payload and adding code to the client to convert it back into executable form.

246
Random Discussion / Re: An "arbitrary data" bug in the blockchain?
« on: May 11, 2015, 12:29:15 pm »
Does anyone here know how to code a simple trap for this? There's now a 40,000 BTS bounty for you. ::)

A trap in what exactly?  The client should not attempt to execute arbitrary data from the blockchain anyway, so this shouldn't be an issue.

247
Random Discussion / Re: An "arbitrary data" bug in the blockchain?
« on: May 10, 2015, 10:31:36 pm »
I think you people are missing the point...

This post contains a destructive virus.  You can execute it by following these malicious instructions:

Code: [Select]
Smash your computer with a hammer.
I could also burn these instructions onto a wall in the BitShares blockchain, but that wouldn't give me any way to make people execute it.

248
This article is from January.  Has anyone heard anything from the play team recently?

249
The market is far from saturated.  Once we have solid light wallets, I think end to end encrypted messaging using chain registered names for key distribution would be a great add on feature.

250
DAC PLAY / Re: Why does no exchanges list PLAY?
« on: May 09, 2015, 05:24:01 am »
FYI: https://www.btsbots.com/gateway?asset=PLS

Not much liquidity yet, but at least there seems to be one gateway so PLS IOUs can be traded on the BitShares exchange.

...So go make those markets liquid, people.  :P

251
General Discussion / Re: Counter Party Risk
« on: May 08, 2015, 05:24:56 pm »
Thanks. How do we know a node won't cheat on the market engine if its not checked by the delegates?
It is checked by the delegates, in that the delegates should never include invalid transactions in a block.  If a delegate does include invalid transactions created by someone cheating, all other full nodes should reject and ignore that block.

Checking block validity isn't a special role exclusive to delegates, it's performed by all full nodes. The delegates just bundle groups of pending transactions into blocks and sign them.

252
General Discussion / Re: Why no one is shorting bitassets?
« on: May 04, 2015, 12:45:59 pm »
Yes. I don't have a problem with it for margin calls, but enabling it for expirations is pretty bad.

Why should it even happen for margin calls? The whole point of putting down a certain amount of collateral is to keep you covered up to a certain market price. Once that point is reach you just unwind. The participant has already lost pretty bad at that point so I can't see any trading strategy that depends on that setup.

If a margin call happens in a rapid BTS dip, the feed may be trailing the market price, so in that scenario force covering only at the feed could be more of a black swan risk resulting in undercollateralized BitAssets.

253
General Discussion / Re: BitAssets 2.0 (formally 3.0)
« on: May 03, 2015, 10:44:25 pm »
...
The main floor on the value of BitAssets is formed by the value to shorters of freeing their collateral.  Forced settling by either expiration or other systems forms another floor at the value in BTS at which the longs expect to be able to force settlement.  With sufficient liquidity, this secondary floor should be unnecessary, but if it is considered necessary it should be at the targeted peg value, not an offset from that.

If the longs are able to cancel settlement, that defeats the purpose of the 24 hour delay I think.  In that case they might as well constantly request settlement and constantly cancel unless settlement is going to occur on a spike in their favour.  If price feed volatility is an issue, they could trigger 24 hour delayed settlement at the average feed price over those 24 hours.  Again, I think forced settling is less than ideal anyway.  The real floor should be the value that BitAssets have to shorters who need them in order to recover their collateral.

While your main point might be correct you are just declaring how this should be rather than suggesting way to do it so!

That and I have no Idea what you  mean by:
"The main floor on the value of BitAssets is formed by the value to shorters of freeing their collateral."
Clarification would be appreciated!
Let me point why I ask - The value of recovering the collateral for 'Would be shorter" is 0, so in this regard the value of the bitAsset is also 0?

To create 1 BitUSD currently at the feed, a shorter must lock up at least 2USD worth of BTS collateral, plus 1 USD worth of BTS from the buyer.  To retrieve that collateral, the shorter must provide 1 BitUSD.  The break even position is for the shorter to buy back 1 BitUSD for 1 USD (or 1 USD worth of something) and use it to claim all 3 USD worth of BTS.  The more liquid the market, the lower the margins, and the nearer to break even you can expect to find trades happening at any given moment.  This establishes the price floor: 1 BitUSD is worth 1 USD to shorters because that's what they can pay for it and break even.

Given that such a price floor exists, we can expect price of BitUSD to follow that floor with spread determined by liquidity unless a higher floor supersedes it.  Currently this higher floor is created by the knowledge that shorters are required to cover at feed + 10% when shorts expire, which they've been doing with some regularity.  As long as BitUSD holders expect regular expirations, we should have a peg at about $1.10 instead of $1.

Given that the lower floor should track the peg we actually want, either eliminating expirations completely or forcing them to cover at the feed rather than at feed + 10% should solve this problem.

254
General Discussion / Re: BitAssets 2.0 (formally 3.0)
« on: May 03, 2015, 07:40:34 pm »
What I mean is you are saying that "$1.00/bitUSD should be the floor, and fail in explaining why it will be the floor. [Actually I believe that about $0.99 will be the floor and that if you set the settlement at 0.99 and all (not only 5% or whatever % can settle in 24h]

Here is one of the main points where it all goes wrong.
The real underlying demand that drives BitUSD:USD to 1:1 is from arbitrage bots and speculators buying BitUSD first as a means to buy the BTS more cheaply than via alternative channels.    This means that buying 1 BitUSD for $1.00 should always be the most cost effective means to purchase the underlying crypto-currency, BTS.   This realization has many implications for the design goals of BitAssets 2.0.
Actually it does not mean that   buying 1 BitUSD for $1.00 should always be the most cost effective means to purchase the underlying crypto-currency, BTS.  That means that buying for as little as possible should be the best price for them! So buying for $0.95 will be better!

Now we come to the next point - is there gonna be conditions at which there will be sellers at $0.95?

The answer is generally 'Yes' - At bull market times it is feasible to short below 1:1 and still profit [*1]

The question then becomes how much below $1.00/bitUSD will such shorting  still be profitable?
In the proposed system "0.99*feed price settlement with no restriction on the % of bitUSD longs that can request a settlement" the answer is about 0.99 adjusted for 1day volatility.


So in other words the bitAsset 2.0 will effectively put the floor on bitUSD on a number directly proportional to the chosen settlement price compared to the feed price [other factors such as - margin requirements, % of all longs that can request settlement, as well as all other market rules that shift the risks for the short/longs - will also influence the exact floor of the bitUSD]

[*1] There is a very simple  explanation why it is so. Will try to explain if anybody interested.
Yea, forced conversion at 99% seems random to me, may as well just make it convertible at 100% if you are going to do it, although I'm generally not a big fan of bitAssets 2.0 formally (formerly?) 3.0.

Should we let people who are force settling at the feed place a limit on what price feed they would accept at the time of settlement?  i.e.  Some news is announced and someone with bitUSD decides BTS is cheap and they request force settlement but by the time 24hrs is over the price has moved so much they don't want to settle at that price.  Or maybe just preventing someone from being completely screwed by a momentary price feed error like a script goes awry.

The main floor on the value of BitAssets is formed by the value to shorters of freeing their collateral.  Forced settling by either expiration or other systems forms another floor at the value in BTS at which the longs expect to be able to force settlement.  With sufficient liquidity, this secondary floor should be unnecessary, but if it is considered necessary it should be at the targeted peg value, not an offset from that.

If the longs are able to cancel settlement, that defeats the purpose of the 24 hour delay I think.  In that case they might as well constantly request settlement and constantly cancel unless settlement is going to occur on a spike in their favour.  If price feed volatility is an issue, they could trigger 24 hour delayed settlement at the average feed price over those 24 hours.  Again, I think forced settling is less than ideal anyway.  The real floor should be the value that BitAssets have to shorters who need them in order to recover their collateral.

255
General Discussion / Re: Why no one is shorting bitassets?
« on: May 03, 2015, 02:36:43 pm »
10% above buyback rule is arbitrary and distorts the market, good thing it was identified for the next BTA iteration
Yes. I don't have a problem with it for margin calls, but enabling it for expirations is pretty bad.

Pages: 1 ... 10 11 12 13 14 15 16 [17] 18 19 20 21 22 23 24 ... 64