Topic: [BTC-TC] Virtual Community Exchange [CLOSED] - page 70. (Read 316534 times)

It's been a day or so since I've posted in here and some may be wondering where BTC-TC stands with things.

- BTC-TC will not be closing it's doors to US citizens.  US citizens using the site are not doing anything wrong and the issues around investing in assets from the various issuers is better addressed on a per-issuer basis.  For instance, a fully registered and compliant issuer should be able to have unfettered access to the entire US population, whereas an issuer that has not properly registered their company puts themselves at risk and thus we would hope would close off access to the riskier markets.  (note that this registration takes many forms depending on where you are located.)
- BTC-TC will be adapting it's ToS and wording on the site to be clearer and to avoid words that imply regulation where there is not.  For example, calling something a stock implies a share of a regulated, registered company, when in fact that may not truly be the case.  These changes will be made over time as we work things out with the help of legal representation.
- BTC-TC will be building a set of tools to assist issuers in maintaining compliance with securities law internationally.  Initially this means that we will be giving issuers the ability to solicit (or not solicit) investment on a per-country basis.  Eventually we could also facilitate validation and filtering of accredited investors versus non-accredited investors.

Cheers.

Maybe open this in a narrow side-window?

https://btct.co/realtimeTrades

I think we went through the options and decided that most of them had some pretty sticky flaws.  The other alternatives I can think of, like giving out a one-time reset code when you register are all completely pointless when you consider that it'd require writing the code down and keeping it safe.  You can already do exactly that with your PIN and gAuth secret...

We offered other options, but it seems burnside will stick with this insane method.

So I really screwed up today and was adding security to my MT.gox account via Google Auth. 

Well i overwrote my auth code for BTC TC.  I submitted a reset request but is this really 30 days?  Is there anything I can do to prove i'm not a hacker and get help with this quicker?  I totally understand the security measures but surely there is a faster option to fix this?

Hey burnside, the realtime chart on the left is a really great addition.

Would it be possible to have a breakaway option for realtime? Like a dedicated page only for realtime that I can have open without having to open the entire rest of the page?

Today I added support to CryptFolio (thread) for premium users to view all of their securities (BTC-TC, Litecoin Global, Cryptostocks, Havelock Investments) on a single page along with their current market value:

Thank you！

Read the details tab of the ASICMINER PassThrough: https://btct.co/security/ASICMINER-PT#tab6

How can put the direct shares of AsicMiner into the btct.co?
does anybody know?

Your right should have highlighted some parts but it is an interesting thanks for giving it a read

.

At some point you run into a maximum number of digits.

They are significant numbers, not digits.

Sorry, I was talking about the entries in the order book. I noticed one entry with 8 digits after the comma (0.00000100) and was wondering if thats also applicable for the API (depending on stock price). Last time I checked the limits were 6 digits (after comma) for BTCT and 4 on LTC-Global.

Working as intended, there was an update to BTCT that rounds all orders to 4 significant digits.

@Burnside: Your algorithm gives identical results to mine. I don't see any real reason to prefer one over the other, since it's not really a high-performance scenario. As always with web-services, validation of user input will be the biggest potential issue.

Burnside, there is a bug, when I set a sell 0.010288, it saved to 0.010290
This is on LTC-ATF.B2.

The 7d field doesn't have to show zero, it could simply say N/A for assets that don't have a div posted in the last 7 days.

I just don't like that some people are seeing 200% yield on the PMBs and buying blindly. It's their own fault, but this yield data certainly makes it easier to act ignorantly.

Indeed.  I thought you meant 7 digits, not 7 day.    (been too focused on digits!)

Edit: Expanding on this.  It already uses the 7d value of the security for the calculations, thus the calculations you see should reflect price drops fairly quickly, though not quickly enough for some, and not slowly enough for others I'm sure.  Adding a 7d yield for most issues would (best case) only take into account the most recent weekly div and (worst case) show zero yield 3/4 of the month on issues that only have monthly divs.  The only ones it really works for are those with daily divs, and most of those are stable enough that a 30d is a better picture anyway.

Am I missing anything?


LTC-GLOBAL has the same code as BTC-TC for the most part.

I don't think the div yield numbers are available via API.  They're kind of an interpreted value that you're better off calculating yourself using your own preferred inputs if you can.  (And I suspect you can if you're up to using the API.)

Cheers.

Thats also available through the API? Whats the maximum digitcount for LTC-Global? Still 4 or did it also increase?