451
General Discussion / Re: BitShares February Newsletter
« on: March 14, 2015, 07:35:07 pm »march letter anywhere?Should be out pretty soon, they were collecting input from people this week.
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.
march letter anywhere?Should be out pretty soon, they were collecting input from people this week.
Hello,Hi Armilo,
I think this might be of interest for you:
Yesterday afternoon (CET) we have made a test transfer of 0.1 BTC via BlockTrades*) for exchange in BTS and to credit our account "armin39" at BitShares. It took over 20 hours until that amount was credited to the account.
A similar test transfer via Metaexchange was done in less than half an hour.
*) The email address 'support@blocktrades.us' shown on the BlockTrades website does not work!
Best regards,
armilo
Any opinion from core devs on the matter? This has been going on for more than 48 hours now...I looked at my devshares delegate on Linux and also at my devshares GUI client, and they seem to be operating within normal parameters (both are less loaded as to cpu/memory usage than my respective bitshares clients). My devshares delegate is consuming around 800MB, my bitshares delegate is consuming around 1GB.
Open source please ... Bytemaster asked others to do it before he vote them, not you?Our site is a service, not software development that we're creating for everyone to use. I'm much more comfortable running a service than handles customer money operating off closed-source that is not as vulnerable to exposure of potential weaknesses, especially during it's early development, although I don't want to get into a big debate of security of open- and closed-source. I've heard all the arguments over the years I think, and I'm reasonably confident this is a safer way to operate now. It's quite possible we will release it as open-source in the future, but I don't think it's a good idea now.
Sent from my ALCATEL ONE TOUCH 997D
Can you integrate this into the wallet.bitshares.org? We need everything consolidated and made to look and feel like a centralized exchange.We can certainly do it, but it needs to be something open, so that competing services could be offered I think.
Thanks for the replies, I now understand part one of trading at face value.Dealing in an IOU asset lets an exchange avoid the speculation of holding a market position, especially if they plan to do market matching of their own. These blockchain-visible IOUs can substitute for the "internal quantities" that exchanges use today for order-matching purposes. As far as BTS visibility goes in the trading process, right now it tends to serve as a convenient base currency for quoting other assets in, similar to what BTC provides on many exchanges.
My next thoughts and questions revolve around the market itself:
-Why not have the market deal with BitAssets instead of BitShares? In the example if it is primarily a USD gateway why not for the simplicity of numbers do a 1 for 1 with BitUSD? 1 IOU = 1 BitUSD? Only downside I is if dealing with international customer's with different currency, thus requiring an exchange rate. As far as operating with BTS in the markets, there's no absolute need for it to be visible to the users, it's just a convenient "base currency" for quoting other assets in, similar to the way BTC works on many exchanges.
-In the beginning with low liquidity wouldn't the gateway need to play both sides of the market? Buyer Joe sends the gateway fiat and the gateway issues the IOU. Joe now wants to trade the IOU for BitUSD however there are no buyers, thus wouldn't the gateway need to buy their own IOU back in this case? Perhaps the gateway would require a market bot to automate this process?What happens in the beginning depends a lot on what state of "startup" the gateway itself is at. If it's an existing exchange, it can convert it's existing accounting system to using user issued assets (IOUs) and liquidity should already exist. For a true startup, like http://blocktrades.us, we need to offer initial liquidity for our IOUs, so we're working to get market maker bots running for that now.
Ok, thanks for update, I"ll grab it after design meeting today.Hey dan,i recenrly added yunbi and make use of the python-bitsharesrpc package also available in bitshares-pytools as a submodule ..ok, I've updated to the new version of the script (except the url to bter wasn't correct, so I had to remove the "data." from it).
maybe I should start tagging stuff
I just pushed another slight update to the feed script .. it seems yahoo has changed the api interface and now returns a "\n" instead of "\r" for my queries ..
i recenrly added yunbi and make use of the python-bitsharesrpc package also available in bitshares-pytools as a submodule ..ok, I've updated to the new version of the script (except the url to bter wasn't correct, so I had to remove the "data." from it).
maybe I should start tagging stuff
It's certainly not "on purpose", we're just running one of the available feed scripts (looks like Xeroc's). The only change I see to it is we changed the URL for bter after it went down and came back up. Maybe there's been later changes that we haven't merged in?I really hope I am doing something wrong when calculating theses percentages:Code: [Select]+-----------------------------------------+-----+----------+--------------------------------------+
| delegate | top | numFeeds | asset |
+-----------------------------------------+-----+----------+--------------------------------------+
| | | | |
| delegate-dev2.btsnow | 21 | 18 | BTC, 0.00004237 (med +17.976%) |
| | | | |
| delegate-dev1.btsnow | 30 | 18 | BTC, 0.00004237 (med +17.976%) |
| | | | |
| delegate-dev3.btsnow | 31 | 18 | BTC, 0.00004237 (med +17.976%) |
| | | | |
| dac.bts500 | 34 | 19 | HKD, 0.07703945 (med +1.599%) |
| | | | CNY, 0.06219399 (med +1.562%) |
| | | | USD, 0.00992958 (med +1.579%) |
| | | | |
| delegate.btsnow | 37 | 18 | BTC, 0.00004237 (med +17.976%) |
| | | | |
| delegate-dev4.btsnow | 49 | 18 | BTC, 0.00004237 (med +17.976%) |
| | | | |
| delegate.cgafeng | 75 | 6 | BTC, 0.00003654 (med +1.756%) |
| | | | SILVER, 0.00063002 (med +1.737%) |
| | | | GOLD, 0.00000894 (med +6.945%) |
| | | | CNY, 0.06225258 (med +1.657%) |
| | | | EUR, 0.00916409 (med +1.660%) |
| | | | USD, 0.00993720 (med +1.657%) |
| | | | |
| delegate.bitder | 100 | 19 | BTC, 0.00003781 (med +5.287%) |
| | | | |
+-----------------------------------------+-----+----------+--------------------------------------+
I don't think so, I get similar results:
http://bitsharesblocks.com/delegate/feeds?name=delegate-dev1.btsnow
I added percent devaitions from the median a few days ago.
How come for BTSNOW most feeds are ok .. but not BTC which is of more than 15%???
Is this on purpose?
I really don't know if we'll open source it or not, it's a decision for another day.is your code public?No, it's not open source, we're using our own code repositories.
you will open source it later? just curious, because you are also funded via delagte position like we are.
is your code public?No, it's not open source, we're using our own code repositories.
The conversion rate in that picture is very, very off.The site quotes conversions as a function of the pricing and volume of the markets involved. The price the site offers is basically a function of whatever price you could get by placing a series of market orders to fulfill the quantity you wish to purchase. So in a low liquidity market, the conversion price can go up rapidly for larger quantity orders as orders close to the market feed price get consumed. In the case in question above, there's apparently not any offers to sell BitBTC close to the market feed price (I checked with my wallet's exchange display to confirm this was the case).
This looks awesome provided we can get the conversion rate correct / spread down to a reasonable amount.
In markets with low volume maybe a warning should be displayed.Yes, it's not a bad idea. We show the conversion, but of course it might not be that obvious to someone when they're exchanging between two distinctly different coin types. I'll try to think of a good metric to identify this condition.
How about bitUSD => BTC ?It's coming relatively soon. It's possible we may have BTC output in another week, depending on what other tasks pop up.