Allowing people to place multiple bids with the same BTC results in lots of what I see as spam orders, it's happened every time I've allowed it.
The only way to improve liquidity is to have more BTC on there, either in the form of peoples own BTC or margin.
Actually, at the bitcoin conference Meni was telling me that margin also performs the same functionality more or less as options. I didn't quite understand it at the time (I was pretty tired) but this is one of Meni's strengths.
Topic: GLBSE - request for next features - page 2. (Read 27744 times)
There are two ways liquidity could be improved, either Nefario gets it to work so people can place multiple bids with the same bitcoin, or people add more bitcoin and place more bids.
I often see great deals due to the low liquidity, the huge spreads on many assets. There are a couple assets I have been making like 5-10% per week buying and selling (but very low volumes), but I just don't have enough bitcoins to place bids on everything at once. There have been a few times somebody dumps shares and I say to myself I wish I had known they were going to sell, I would have bid much higher than they got.
I often see great deals due to the low liquidity, the huge spreads on many assets. There are a couple assets I have been making like 5-10% per week buying and selling (but very low volumes), but I just don't have enough bitcoins to place bids on everything at once. There have been a few times somebody dumps shares and I say to myself I wish I had known they were going to sell, I would have bid much higher than they got.
Would more liquidity appear if trading fees were shared on glbse ? For example if someone buys shares the seller splits the cost of the fees 50/50 rather than just one side paying all the fees.
How would that improve liquidity? That would remove one of the benefits of leaving an open order on the exchange. I think it would have a negative effect on liquidity and result in more volatility and destabilization of assets.
Would more liquidity appear if trading fees were shared on glbse ? For example if someone buys shares the seller splits the cost of the fees 50/50 rather than just one side paying all the fees.
Mark security issuers Buy and Sell orders with a different color in the order book.
I also like to add this one:
Highlight users bid/ask in the order book (btc-e has it well implemented).
I am going to bring this on up once more because we need more transparency to issuers actions and I think this is valuable for the investors too.
Wouldnt they just use sock puppet accounts ?
Mark security issuers Buy and Sell orders with a different color in the order book.
I also like to add this one:
Highlight users bid/ask in the order book (btc-e has it well implemented).
I am going to bring this on up once more because we need more transparency to issuers actions and I think this is valuable for the investors too.
I think this is a good idea. The user's own orders could be highlighted yellow (and maybe have a cancel option on the asset page, so we don't have to go back to the portfolio to cancel, and then back to the asset page to replace the order when moving the price). The asset issuer's orders could be highlighted orange or something like that.
Mark security issuers Buy and Sell orders with a different color in the order book.
I also like to add this one:
Highlight users bid/ask in the order book (btc-e has it well implemented).
I am going to bring this on up once more because we need more transparency to issuers actions and I think this is valuable for the investors too.
How about being able to open a demo account to have a play around before using real coin??
I would love it if you got a second chance to log in before having to do a captcha. I realize it's a balance between security and ease of use, but nearly every time I fail the login I end up doing the captcha between 5 and 10 times before I can get back in 
Also, the ability to establish a PGP key just in case we are unable to log in would be useful as a backup. We could simple sign a message to you proving our ownership of the account if necessary.
Also, the ability to establish a PGP key just in case we are unable to log in would be useful as a backup. We could simple sign a message to you proving our ownership of the account if necessary.
So you are suggesting GLBSE holds onto a database of the public keys corresponding to account emails?
Correct. Just an idea though.
It would definitely be nice if you could tie your ownership of shares to a GPG key.
With much thanks to LWCoder, I've added the GLBSE android client to the front page (you'll need to log out to see).
I've also ordered yubikeys, so will begin to add them as a 2fa method when they arrive.
I've also ordered yubikeys, so will begin to add them as a 2fa method when they arrive.
I would love some way to easily reply to and keep track of personal transfers.
Currently, they are just listed in the transfers in / out. It would be nice if it told me the account they were coming from / going to.
I believe someone else (on a whole other thread) found this information inside the full account CVS download. Though not the most direct way to get it.Currently, they are just listed in the transfers in / out. It would be nice if it told me the account they were coming from / going to.
Yes, I lost some time too before figuring it out.
I would love some way to easily reply to and keep track of personal transfers.
Currently, they are just listed in the transfers in / out. It would be nice if it told me the account they were coming from / going to.
I believe someone else (on a whole other thread) found this information inside the full account CVS download. Though not the most direct way to get it. Currently, they are just listed in the transfers in / out. It would be nice if it told me the account they were coming from / going to.
I would love it if you got a second chance to log in before having to do a captcha. I realize it's a balance between security and ease of use, but nearly every time I fail the login I end up doing the captcha between 5 and 10 times before I can get back in
Also, the ability to establish a PGP key just in case we are unable to log in would be useful as a backup. We could simple sign a message to you proving our ownership of the account if necessary.
Also, the ability to establish a PGP key just in case we are unable to log in would be useful as a backup. We could simple sign a message to you proving our ownership of the account if necessary.
So you are suggesting GLBSE holds onto a database of the public keys corresponding to account emails?
Correct. Just an idea though.
I would love it if you got a second chance to log in before having to do a captcha. I realize it's a balance between security and ease of use, but nearly every time I fail the login I end up doing the captcha between 5 and 10 times before I can get back in
Also, the ability to establish a PGP key just in case we are unable to log in would be useful as a backup. We could simple sign a message to you proving our ownership of the account if necessary.
Also, the ability to establish a PGP key just in case we are unable to log in would be useful as a backup. We could simple sign a message to you proving our ownership of the account if necessary.
So you are suggesting GLBSE holds onto a database of the public keys corresponding to account emails?
I would love it if you got a second chance to log in before having to do a captcha. I realize it's a balance between security and ease of use, but nearly every time I fail the login I end up doing the captcha between 5 and 10 times before I can get back in
Also, the ability to establish a PGP key just in case we are unable to log in would be useful as a backup. We could simple sign a message to you proving our ownership of the account if necessary.
Also, the ability to establish a PGP key just in case we are unable to log in would be useful as a backup. We could simple sign a message to you proving our ownership of the account if necessary.
A recent topic seems to be moving contracts out of GLBSE for security reasons, and another is being able to prove you actually possess shares. I'm sure this has been discussed somewhere, but both can be accomplished by an option to lock a certain number of owned shares (or all of it if easier) in your account for a specified number of days.
The locking process can provide a signed certificate of ownership that expires at a certain date. The lock should optionally get updated everyday. This way I will be certain that there is time delay in case my account gets compromised, and I'll get an e-mail notice when the locked shares get unlocked. It might also serve proof of ownership in an outage or an odd case of data corruption at GLBSE (assuming the keys aren't leaked, though they probably can be kept in a separate location).
Another functionality could be sending shares with a temporary lock, which would help making off-market transactions easier. If the receiving party doesn't pay, you'd have time to contest.
The locking process can provide a signed certificate of ownership that expires at a certain date. The lock should optionally get updated everyday. This way I will be certain that there is time delay in case my account gets compromised, and I'll get an e-mail notice when the locked shares get unlocked. It might also serve proof of ownership in an outage or an odd case of data corruption at GLBSE (assuming the keys aren't leaked, though they probably can be kept in a separate location).
Another functionality could be sending shares with a temporary lock, which would help making off-market transactions easier. If the receiving party doesn't pay, you'd have time to contest.
+1 with backups outside of glbse infrastructure/controle
A recent topic seems to be moving contracts out of GLBSE for security reasons, and another is being able to prove you actually possess shares. I'm sure this has been discussed somewhere, but both can be accomplished by an option to lock a certain number of owned shares (or all of it if easier) in your account for a specified number of days.
The locking process can provide a signed certificate of ownership that expires at a certain date. The lock should optionally get updated everyday. This way I will be certain that there is time delay in case my account gets compromised, and I'll get an e-mail notice when the locked shares get unlocked. It might also serve proof of ownership in an outage or an odd case of data corruption at GLBSE (assuming the keys aren't leaked, though they probably can be kept in a separate location).
Another functionality could be sending shares with a temporary lock, which would help making off-market transactions easier. If the receiving party doesn't pay, you'd have time to contest.
The locking process can provide a signed certificate of ownership that expires at a certain date. The lock should optionally get updated everyday. This way I will be certain that there is time delay in case my account gets compromised, and I'll get an e-mail notice when the locked shares get unlocked. It might also serve proof of ownership in an outage or an odd case of data corruption at GLBSE (assuming the keys aren't leaked, though they probably can be kept in a separate location).
Another functionality could be sending shares with a temporary lock, which would help making off-market transactions easier. If the receiving party doesn't pay, you'd have time to contest.
s/freenet/freenode/ ? 
well spotted. my fault. s/freenet/freenodecould go via gribble say/msg
Quote
I guess it would be fairly easy on any platform. I suggested e-mail (although it's not optimal for me) because everyone knows how to deal with that and it's pretty much decentralized. I'd create a new e-mail account for this, which I'll only access through my smartphone, yet I can still easily access from any other device if I need to.
2nd email address - for 2 factor auth email could be just fine
I couldn't manage to add GLBSE to my two-factor authentication with Google (I guess it doesn't work over SMS?), and I wasn't very eager anyway. Will you implement other authentication schemes? A jabber message would be good enough for me, though any generic protocol that's easy to setup with an external device should be fine. I guess e-mail would be the most generic one.
or pairing glbse account with freenet irc accounts, or wot at http://bitcoin-otc.com/
could you write that in ruby?
s/freenet/freenode/ ?
I guess it would be fairly easy on any platform. I suggested e-mail (although it's not optimal for me) because everyone knows how to deal with that and it's pretty much decentralized. I'd create a new e-mail account for this, which I'll only access through my smartphone, yet I can still easily access from any other device if I need to.
I couldn't manage to add GLBSE to my two-factor authentication with Google (I guess it doesn't work over SMS?), and I wasn't very eager anyway. Will you implement other authentication schemes? A jabber message would be good enough for me, though any generic protocol that's easy to setup with an external device should be fine. I guess e-mail would be the most generic one.
or pairing glbse account with freenet irc accounts, or wot at http://bitcoin-otc.com/
could you write that in ruby?
Jump to: