Next issues are front running (you pay more for feeds that are closer to real time). 

Also pricing errors (even happens to MSN), transactions are not reversible.

There is the stock split too.   It is actually a real challenge/expense to get the detailed dividend and split data required without having rounding errors (which compound over time) or violating someone's terms of service.   It is as if we have the new technology and that it is better if we support companies that upgrade.

Did you children sell your bitcoins a few years ago when they went down from $30 to less than $2?

I didn't.

I bought more.

And I sold them later at $800 each (to buy BTS)

And I am buying more BTS now.

I call this value investing. Well done!

This is Fun....  I program BitShares web wallets.   : slim180

But we should always keep the ability to have and control our own.

2 of 4 active...  You can still have the owner or owners which typically are cold wallet keys..

I would like to see the transfer transaction have an optional account name "to" field.  Because the transfer transaction can also have an account id, it should also be provided and validated when ever possible.

Bytemaster (in github) noticed a few other operations where this might be useful.  I looked into and, well, lets say it started expanding into a lot of other what-ifs...  So, that is getting complicated.  Lets remember we can do things off-chain...   

One case jumps out at me, btercom vrs bter.  This is a real loss.  The BTER exchange registered "btercom" but some other entity registered the shorter name bter.  Sure enough, a user sent money to the wrong address.  It was not good, this user was just getting into BitShares and this was there initial investment. 

So, here is the new hypothetical story...  Example.com creates there new account "examplecom".  When they do, their wallet hashes that name adding 3 base58 encoded characters to the end.  Now, there safe name would look like this:

exampllecom_8d8

Also, assuming this is not a cold-wallet, the wallet will also grab examplecom's account id which is say 37,521 (current registered accounts on BitShares).  Finally, 3 more chars are added which is a check for both examplecom and the encoded account id.  Note, this is the actual length with fake checksums:

examplecom_8d8_6rzDCojw9e9

This becomes useful in anyplace where we use an account ID (for example: active and owner signature authorities).  If the ID is not known a shorter version may be used (just examplecom_8d8).  It should still be possible in every case to simply use examplecom.

The identicon should remain unchanged on the account name, this gives the cold wallet the ability to show a matching identicon even though it can't lookup the account number.

I used an _ because that most often lets one double-click and select the entire name.  An underscore is not allowed in a BTS account name.

btw: did you notice, I really typed two 'l's in the example .. complete accident I promise...  If only exampllecom_8d8 was provided, the computer would catch the mistake in all but 1 case in every 190K cases).

Quote from: nz on May 12, 2015, 07:36:30 pm

Question: is there a way to select my own Recovery Key rather than the random one thats automatically generated?

I'm sure there is, i just dont see it.

Thanks
M

it's only possible with the console version of the client:
wallet_create <wallet_name> <new_passphrase> [brain_key] [new_passphrase_verify]                     


but I would not recommend using a brain_key unless you REALLY REALLY REALLY know what you are doing!!

Just use "Recover Wallet" and type anything you want.. yes, you really should limit funds if you start doing that or better yet run some numbers and share.  I use simple keys for my test accounts which will be transferable to a stronger key later in Graphene.   At least the wallet gives us a hint what the a proper strength should be (we did some math and compared it to the industry standard)...  Of course, keep in mind, this is a server hosting js files that creates the key.  We really have to do better than this; we just need that key created in a format where the source code can be frozen or ran in cold storage.  So, you can at least see what a retirement strength key should look like..