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

Pages: 1 2 3 4 5 [6] 7 8 9 10 11 12 13 ... 57
76
Muse / Will NOTE snapshot include active DEX orders?
« on: October 06, 2015, 07:04:43 pm »
I have a couple orders on the DEX to sell some NOTEs - will the snapshot capture those, or do I need to cancel the orders before hand? Thinking more about it, I'll probably cancel them anyway just to avoid any weird disappointments, but I thought I'd ask anyway.

77
General Discussion / Re: Announcing Brownie Points (BROWNIE.PTS)
« on: July 03, 2015, 06:28:59 pm »
Major shout-out to CLains for PMing me and alerting me to this Brownie.PTS thing. Fun idea.

I've been pretty quiet in the community lately, but in the past year-and-a-half I've participated in many forum discussions and hopefully been a helpful voice on stuff.

I ran a private, custom market-maker bot for BitUSD/BTC on Bter with several hundred dollars. It's been shut down since the Bter BTC-theft debacle.

I wrote significant portions of the BitShares FAQ commissioned by Brian Page, most of which can be found here: http://wiki.bitshares.org/index.php/FAQs#DACs

I've done some helping-out of newbies. There were a couple months when my main goal on the forums was to clean up after tonyk's attempts to scare new people away.

Um... not sure if this is a plus or a minus (lol), but I engaged with the RandPaulCoin guy back when he was around, trying to help him work out his BTS clone.

I used to go to the Nxt forum pretty frequently and preach about bitshares.

If you want hours, I've probably done between 10 and 100 hours of productive work for BitShares.

78
BitShares PTS / Re: what do i do with my pts @ cryptsy
« on: June 10, 2015, 11:23:50 pm »
Cryptsy has been ignoring snapshots for a long time now. If you can convince them to honor this one you'll be succeeding where many before you have failed. Good luck.

Sent from my LGL34C using Tapatalk


79
Technical Support / Re: Announcing BitShares 2.0
« on: June 08, 2015, 11:32:43 pm »
Also, it seems the new client is not the same codebase as 0.9.x.

Is TITAN also baked in the new codebase? Will we have privacy built-in by default?
No, no TITAN. This is a good thing! TITAN wasn't really very effective for privacy, but it gave the illusion of privacy. Also, TITAN was one of the reasons the client was so unbelievably slow.

Sent from my LGL34C using Tapatalk


80
General Discussion / Re: [ANN] Questions for TODAY @ 4:00pm EST
« on: June 08, 2015, 07:57:14 pm »
A possibly-naive question from someone who hasn't looked too closely at either voting system yet:

Have you studied NuShares's voting model when creating the voting model for approving code changes? I know there will be some major structural differences (perhaps the foremost of which is that in BitShares, you can't directly buy a delegate position), but there may be some lessons to learn. 

81
Technical Support / Re: Announcing BitShares 2.0
« on: June 08, 2015, 07:05:33 pm »
mmmm, transferable accounts. You people are beautiful. :)

82
It would be neat if this license-if-sharedropped  worked, but how would you ever enforce it? The old PTS social consensus wasn't exactly overwhelmingly adopted...

83
Sparkle was originally intended to be PoW, not DPOS. That was the whole point: bitshares functionality on a PoW chain.

84
General Discussion / The market engine is not matching shorts properly
« on: April 10, 2015, 10:35:01 pm »
Right now, there are bids for BitUSD above the feed price. The feed price is about 211, the highest bid is 225. To test the market, I shorted BitUSD with 1000 BTS of collateral, and was able to borrow 2.3637 BitUSD. Now in my margin order it says I have about 1500 BTS, which means the proceeds of my short order were about 500 BTS. THAT IS THE WRONG AMOUNT!! I should have been matched with the highest bid and gotten the 225 price, but as you can calculate (500/2.3637), I only got the 211 price. I'm guessing I matched one of the many expired shorts.

I know the devs aren't allowed to talk to us anymore or some such insane bullshit, but is there anybody out there who knows how to get a fix for this in the pipeline? Thanks.

85
Muse / NOTE Price discussion
« on: March 26, 2015, 03:17:59 pm »
Has anybody done any ROI calculations for NOTEs from the pre-sale? I can't recall my ballpark figures exactly, but it seems like the pre-sale was implying a market cap around $2MM, which isn't far from where NOTEs are trading now. Anybody care to give actual numbers?

86
Stakeholder Proposals / Re: BitSuperLab please fix your feeds
« on: March 17, 2015, 01:31:43 am »
I guess I should just go design a feed-prediction attack and make money myself, since people seem so hard to convince.

At the very least, feed scripts should randomize update times. I'll leave it at that until I can give a better argument.

87
Stakeholder Proposals / Re: BitSuperLab please fix your feeds
« on: March 16, 2015, 03:03:27 pm »
@Gentso- do you believe there is any such thing as a perfectly accurate price? What's the spread at btc38? 1%? 0.5%? Which price is the price you think is "correct?" The bid or ask? The price of the last trade? I think you'll agree with me that none of those are quite right; you'd almost always be more interested in something between the bid and ask. So what do you pick? The average? A recent moving average of market prices? Those sound better, but they're still only estimates. Maybe I'm being long-winded, but I'm trying to make the point that there isn't ever 1 price and the best you can ever do is estimate it. So adding in 0.2% noise will still give an accurate price feed, especially if everybody is doing it and all the noise averages out.

@Xeroc, I haven't actually designed a manipulation algorithm to exploit feed price prediction, but isn't it obvious that a noisy feed would be better than a predictable one? I'm working from this principle: if I can execute trades on btc38 and predict exactly what that will do to the price feed, then I can make money moving the price feed around. Probably a fraction of a percent per trade, but the fact is I'll be taking money from the system without providing any benefit. Doesn't that sound like something we should try to prevent?

maybe we can find a compromise and have a randomness in-line with the lowest spread of your exchanges .. if btc38 says 1% you may add randomness with a spread of less than 1% with confidence >90% or so ..
Yeah, that's more or less what I had in mind.

Another way to do it halfway is to randomize update times. Update every 20 minutes plus or minus 5.

Also there should be no hard triggers that push a new price with 100% certainty, because those could be pretty easily exploitable. Again, based on the principle that a deterministic price feed is exploitable.

88
Stakeholder Proposals / Re: BitSuperLab please fix your feeds
« on: March 16, 2015, 02:21:32 pm »
@Gentso- do you believe there is any such thing as a perfectly accurate price? What's the spread at btc38? 1%? 0.5%? Which price is the price you think is "correct?" The bid or ask? The price of the last trade? I think you'll agree with me that none of those are quite right; you'd almost always be more interested in something between the bid and ask. So what do you pick? The average? A recent moving average of market prices? Those sound better, but they're still only estimates. Maybe I'm being long-winded, but I'm trying to make the point that there isn't ever 1 price and the best you can ever do is estimate it. So adding in 0.2% noise will still give an accurate price feed, especially if everybody is doing it and all the noise averages out.

@Xeroc, I haven't actually designed a manipulation algorithm to exploit feed price prediction, but isn't it obvious that a noisy feed would be better than a predictable one? I'm working from this principle: if I can execute trades on btc38 and predict exactly what that will do to the price feed, then I can make money moving the price feed around. Probably a fraction of a percent per trade, but the fact is I'll be taking money from the system without providing any benefit. Doesn't that sound like something we should try to prevent?

89
Stakeholder Proposals / Re: BitSuperLab please fix your feeds
« on: March 16, 2015, 03:15:00 am »
One more fairly obvious item you should add to the list is:

Always multiply your published price by a random number that is close to 1; maybe within a quarter percent of one. It's an easy step that makes the price feed that much less predictable and improves security against precision market manipulation.

90
General Discussion / Re: An attack on DevShares
« on: February 09, 2015, 07:21:13 pm »
I like this. Gonna go get some popcorn.

Sent from my SCH-S720C using Tapatalk 2


Pages: 1 2 3 4 5 [6] 7 8 9 10 11 12 13 ... 57