I also added the JSON Endpoints for those who want to GET the data lists to process them with their own script:
https://weexadd.firebaseio.com/add_deposit.json
https://weexadd.firebaseio.com/add_withdrawal_original.json
https://weexadd.firebaseio.com/add_withdrawal_portal.json

I also added the JSON Endpoints for those who want to GET the data lists to process them with their own script:
https://weexadd.firebaseio.com/add_deposit.json
https://weexadd.firebaseio.com/add_withdrawal_original.json
https://weexadd.firebaseio.com/add_withdrawal_portal.json

So I put together a quick site where we can collect all the addresses in one place...
http://www.jspmedia.net/weexadd/

You can add your address anonymously and quickly. Anyone can go there and view the addresses collected so far. It updates autonomously using Firebase.

So I put together a quick site where we can collect all the addresses in one place...
http://www.jspmedia.net/weexadd/

You can add your address anonymously and quickly. Anyone can go there and view the addresses collected so far. It updates autonomously using Firebase.

Here is my guess and I could be completely wrong...

1) There originally, really was a bitcoind issue.
2) Someone was involved to assist with this issue, either doing something with bitcoind or migrating to a different software.
3) A security hole/weakness was discovered in the (beta) Weex site and a majority of the coins were stolen, causing the withdrawals to fail. (Maybe the vulnerability was something originally negligible because the beta-Weex was ultimately going to be abandoned and a new Weex was going to be built, hence the new Weex site talk and mention.)
4) Since then, (and while we wait in oblivion), Jon had been racing to secure the remaining coins before the security hole could be exploited anymore. This may be the reason for secrecy.
5) Then, Danny became involved to help Jon write new code to facilitate a new secure way to initiate transfers on Weex (2.0) (maybe using some of the same techniques the bank-like Neo-Bee systems use).

* This would explain why "...revealing too much information could result in a decreased chance of getting those coins back..." They may now be finished with the new Weex, but before Monday they need to run the tests and the final "...precaution of making sure the remaining funds don't go missing too!"

Wondering why dividends dropped from ฿0.00000765 to ฿0.00000745 per share on 9/3? Is difficulty no longer 65,750,060?


Difficulty used for the past nine dividend calc was 65,750,060
(1*25/65750060) * (60*60*24 * 65535 * 10^6 / 2^48) = ฿0.00000765

For it to be ฿0.00000745 now, that would mean the difficulty used to calculate was 67,504,230 (below the next estimated difficulty increase).
(1*25/67504230) * (60*60*24 * 65535 * 10^6 / 2^48) = ฿0.00000745


Thanks for the explanation in advance.

How does your house code generate randomness? No where on your site explains it. I really hope you are not using pseudorandom functions... however, I am not familiar with HTML5 to know if random is based off of some real physical phenomena.

I think visitors would feel more confident in playing in your casino games if you disclose that you are seeds are based off of random number generators that measure some sort of a physical phenomena.

For those other forum members who are not familiar with what I'm talking about: http://www.random.org/randomness/

Thanks in advance!

I agree. Thanks.

Thanks, Ukyo!

Yes, this has happened to me constantly. After I cancel an order, I have to reload a fresh page in Chrome, then I will be able to post another order. Some bug here.



Also, I have requested that server time be posted somewhere on the top of the page, or users are given an option to set times to display in their local timezones...


hopefully these suggestions help =)

I actually dont even have the graph turned on because it is slow loading in my browser and just looking at the trade histories tells you much more... though a bit slower to assimlate, it is more detailed an accurate...

I calculated (figuring difficulty) that it was worth getting the several months of good dividends at the price I bought the shares at. Honestly, I think we have several good months left on this. You can do the math yourself for the current price (BTC0.00365, I think)...

According to profile on bitfunder...

D is the current difficulty
H is your hash rate in Mhash/s = 1 MH
B is the current block reward in BTC = 25 btc
(H*B/D) * (60*60*24 * 65535 * 10^6 / 2^48)

(1*25/26162875.68257) * (60*60*24 * 65535 * 10000000 / 281474976710656)

This thing pays daily, DAILY!

Even as difficulty increases, at it's current price (BTC0.00369/share) with the current DAILY dividend payment (BTC0.00001922/share), that's over 0.5% return EACH DAY! %15 return EACH MONTH! and somewhere around 100% return for the year (granted the difficulty doesn't increase too much)... still it's a good buy now!

I just put in over 40 BTC into this and should see somewhere around BTC0.25 return for each of the next few days.

There is still a good chunk at a reasonable low price, below the initial IPO, but if you look at the dividends page, you see the proof of how is undervalued compared to other investments!

https://bitfunder.com/asset/TAT.VIRTUALMINE

Issue was resolved. It was a server side issue. Thanks!

Hi,

For now, is it possible to have the current server time listed somewhere on the top where the menu is on each page?

I live in a different time zone and often want to analyze when the last trade actually happen. It would be even better if on our settings page, we can save a setting to display time in our own time zones. But the first will suffice in the meantime so we can compare when things were posted.

Thanks,
Joe

Does anyone know who is in charge of BitFunder here? Thanks. I have an issue logging in. I have sent an email already. I do have 2-factor enabled.

Thanks for any info in advance!