Quote from: bytemaster on October 13, 2015, 08:14:31 PM
BitShares.org/wallet now has a copy of the light wallet sources.   

Behind the scenes it still uses OpenLedger to register accounts and serve blockchain data. 

In theory you can use https://bitshares.org/wallet to point at your own full node in the cloud.  It also serves as a basic block explorer.

Very cool Bytemaster. Congratulations to you and the team. Smooth and appealing. Good luck!

 +5%

Quote from: pseudoscops on December 03, 2014, 08:33:58 PM
Not a huge amount of funds (2634.1766BTS) but just realized today that the funds sent below never turned up. Today I'm wanting to send 1BTC to BTER so I can invest a little in the Music pre-sale. I'm worried about the funds not turning up again if I do. I remember reading of at least one other who's funds did not turn up at BTER.



Anyone got any advice. As far as I know their support is in Chinese :(

Pseudo I'm pretty sure off the top of my head the BTS depost address for BTR is btercom not BTER. You should always verify the image is the same when sending BTS

Quote from: clayop on November 11, 2014, 01:13:10 AM

Quote from: JWF on November 11, 2014, 01:04:44 AM
I'm pretty sure you need to do 6 decimal places to the above...  At least that looked right for my balances. And each of the instances of the address would be different snapshots I'm presuming.

8 decimal I think.

Toast can we get a clear answer on this? What are we dividing numbers by

If we will pool funds for some kind of promotional give away. I would be willing to donate. I'll match the 10K BTS

Quote from: Riverhead on November 05, 2014, 02:19:29 AM
BTSX doesn't have a vesting period but if you leave it on an exchange you're trusting them to, "Do the right thing".

Sent from my SM-G900T using Tapatalk

I take it those holding BitUSD are missing out on the airdrop ?

@Bytemaster, Are you guys just going to hardfork the current BTSX blockchain or launch a brand new BTS genesis blockchain off the snapshot essentially leaving all BTSX worthless after the snapshot?

Quote from: bytemaster on September 23, 2014, 08:36:21 AM
Yes we have identified and fixed this discrepancy. 

Your bitUsd yield is about to increase.

I don't understand the yield. Even when I'm holding substantial BitUSD my estimated yield is always 0? Is this a bug or ?

Quote from: bytemaster on September 22, 2014, 09:21:34 PM
Yes, laddies and gentlemen, the BTSX supply is over 2 billion as a result of multiple bugs identified and fixed weeks ago.  The surplus supply will be burned from our own funds to return it to the proper supply.  We didn't want to spook people until we had the burn operation implemented so that we could correct it.

So where did this extra supply end up going?

1) Mostly to the delegates... our calculation of delegate pay was off and thus we miscalculated the running supply.   We stated earlier our intent to compensate delegates for the extra hard work they were doing, this particular bug just helped us do what we were planning on anyway.  Delegates running at a discount didn't have their pay burned like it was supposed to be.

2) Some white hat individuals who identified bugs and reported them to us privately after they exploited them.  We were able to fix the bugs without much being created.

can i step up and take public glory now?  ;) lol

Quote from: Riverhead on August 30, 2014, 01:19:29 PM
We seem to be on the rise again. I don't see any of the big contenders going down so I wonder if this is "new" money coming into the crypto ecosystem.

Market depth isn't significant enough to mean anything. If someone wanted to offload 200K btsx it would bring the price down to yesterday's midday levels (EST time)

Quote from: Empirical1 on August 29, 2014, 03:31:33 PM
I know for future reference though that the words 'KEEP CALM' actually mean it's time to 'PANIC SELL'. I'm a long term holder but should have trusted my gut and sold a bit so I could add to my BTSX position.

Emprical you should of just moved into BitUSD on the downward move. No need to sell into BTC. I've increased my position of BTSx holding by 85% through BitUSD

Quote from: toast on August 29, 2014, 01:07:53 AM
GUI is broken, you can see order book with blockchain_market_order_book USD BTSX

I think it would be a great idea to link that feed "blockchain_market_order_book" in a more user friendly format to somewhere on the website. It'll help traders check prices when they don't have access to their wallets and give the market more public exposure. @bytemaster

Has this been discussed amongst devs yet? I know you guys have bigger fish to fry but i definitely think a web based feed like that would be great

Quote from: TheOnion on August 28, 2014, 12:41:12 AM

Quote from: liondani on August 28, 2014, 12:34:37 AM
same bid and ask/short orders...
even it seems they exist the bid order for bitUSD I couldn't sell my bitUSDs in that price so I canceled the order  :(

have you fixed that?

There is an order before yours which eats up the opposing order. i.e your order is actually the second

[Edit] What needs fixing is the  'display bug' - what I mean by this is - after the two orders are matched the bid order will disappear but the amount in the short (in this case) will stay the same '600' bitUSD.

Yes, that is one issue. However the order that he is referring to sat at the top of the list for a solid 2 hours. It just cleared now.

Noticed the same thing Liondani. Seems the order is stuck there. I tried to clear it a few times

Quote from: bytemaster on August 27, 2014, 09:17:59 PM
We have identified and fixed an issue with the market execution that will require all users to upgrade.  A DAC Sun Limited is preparing a release.

This update has addressed some critical issues:
1) The 1hr moving average could get "stuck" if the price moves too fast and no trades occur to trigger an update.  We have adjusted it so that if no trades occur the average will gradually adjust on its own over 6 hours. 

2) We fixed the bug that generate the Assert exception during market execution.

3) We have fixed a bug that would cause seed nodes or locked wallets to get stuck on a fork.

4) Many other small fixes.

Still left to be resolved:
1) random crash on closing a connection.
    - work arounds: 
        - seed nodes, auto relaunch with shell script
        - delegates:  don't allow incoming connections
    - Dan & Eric have made great progress on solving this bug, but the source of the bug is "deep & involved"

eta?