Pages:
Author

Topic: GLBSE 2.0 release delayed again! (Read 4289 times)

sr. member
Activity: 462
Merit: 250
March 25, 2012, 01:33:47 PM
#47
actually the exchange 2.0 was launched on weekend.
now it alternates between "up&running" and "teething problems"

to claim your account from 1.0 in the new version please log in once again to the old version
https://glbse.com/client/glbse/index.html and copy the code (it pops up all the time now in 1.0 version)

and once you have it, create an account in 2.0 and enter the claim code.
https://sourceforge.net/p/glbseguide/wiki/Home/

p.s. the 1.0 site works even while 2.0 gives the error message ; )
member
Activity: 64
Merit: 10
March 22, 2012, 10:59:35 AM
#46
Take your time dude, just remove the "** Launching Monday 18 March **" from the front page :p
sr. member
Activity: 462
Merit: 250
March 20, 2012, 03:53:33 AM
#45
I realize that GLBSE 2.0 is in beta and I'm trying to play around with my fake 1,000 BTC.  None of my orders executed so far, but I'm not sure how many orders really exist or are functioning at this time.

hi, welcome and try to visit following links
http://dev.glbse.com/asset/view/TICK
http://dev.glbse.com/asset/view/SYN1
http://dev.glbse.com/asset/view/MUMRAH

and place orders at 1, 2, 3, 5, 10 to see if you buy something.

I see an issue with closed orders not being purged from the interface, this might be indeed confusing
but I created sell orders at various prices in all 3 assets listed above

try to imagine that the upper 50-90% of the table of sell orders have been already executed/paired and should have been removed (at least this is how it worked in 1.0 and that it will be addressed in the coming days). nevertheless set higher buy price (recommended above as well) to see what you can buy and that you can buy.

with the entries at the bottom of the "sell orders" table you have higher chance that they are open and can be bought.
what I created for you

known sell orders at the time of writing
MUMRAH    1.0    5    2012-03-20 08:41:28    Cancel
MUMRAH    2.0    5    2012-03-20 08:41:35    Cancel
MUMRAH    3.0    5    2012-03-20 08:41:43    Cancel
MUMRAH    4.0    5    2012-03-20 08:42:15    Cancel
MUMRAH    10.0    5    2012-03-20 08:42:24    Cancel
SYN1    10.0    99    2012-03-20 08:42:33    Cancel
TICK    2.3333333    300    2012-03-20 08:42:53    Cancel
TICK    2.0    500    2012-03-20 08:52:01    Cancel
SYN2    5.0    200    2012-03-20 08:52:11    Cancel

it's play money, play with it and once you run out of the 1000 btc welcome credit, create new account and play further
legendary
Activity: 2114
Merit: 1031
March 20, 2012, 03:02:53 AM
#44
I'm new here and trying to get up to speed with GLBSE.

I realize that GLBSE 2.0 is in beta and I'm trying to play around with my fake 1,000 BTC.  None of my orders executed so far, but I'm not sure how many orders really exist or are functioning at this time.

The only bug I found is that I couldn't view a message that I sent.  I got the following error when clicking on the message subject in my outbox:

NoMethodError at /user/mail/read/1
undefined method `body' for nil:NilClass
file: mail.rb location: block (2 levels) in line: 74

Hope this helps a little.

Looking forward to buying some of those IPOs!
sr. member
Activity: 462
Merit: 250
March 19, 2012, 11:02:31 PM
#43
@brendio I updated my post with detailed description if interested.

@Nefario interesting update on dividend bug, I could pay correct dividends of 99.5% of debited amount and could not reproduce the wrong and silly numbers reported earlier. it was a flawed testcase and the lack of bitcoin history (equivalent to 1.0 bitcoin history).

solution: not an issue. the dividends were paid properly (verified several times since test case updated). I was reading the wrong parts of the screen when looking for written traces of the payment.
the field Dividend history was changed after each payment but it was not dividend paid but dividend received.
from the account of asset manager on page /portfolio in table fees paid is always the right amount calculated (0.5%)
and from the account of asset manager on page /asset/view/TICKER in field Dividend payments all entries are correct (show data like)
2012-03-20 00:37   6.965   668   0.01042664
2012-03-20 02:22   9.95   668   0.0148952
2012-03-20 03:39   9.95   668   0.0148952
2012-03-20 03:43   9.95   1001   0.00994005

probably I should sleep as well a bit more. I wondered already if a payment of dividends can be cross-manageable across assets.
now I go and properly cancel the bug note in previous posts.

in the meantime I drafted this piece of howto https://sourceforge.net/p/glbseguide/blog/2012/03/user-20-how-to-register--transfer-account-from-10/
hero member
Activity: 518
Merit: 500
March 19, 2012, 10:24:07 PM
#42
will you keep fixing 1.0 bugs in the meantime?
or rather not Wink but you might want to notice we have TyGrr-Bank situation where ask=bid=.103 and orders are not paired


I saw that. I wonder whether the bid is actually 0.10299999? The web client rounds to 7 decimal places, but the order matching still uses the full 8.
sr. member
Activity: 462
Merit: 250
March 19, 2012, 08:27:08 PM
#41
will you keep fixing 1.0 bugs in the meantime?
or rather not Wink but you might want to notice we have TyGrr-Bank situation where ask=bid=.103 and orders are not paired


It's really odd. All I can say for this is to cancel the order and try again.

Nefario.


It's not my order. I had one for 5 shares at .103 and could see in the asset view 2 sell orders at that price, one from goat and mine.
at the same time a buy order at .103 was visible at the same page. after no pair of buy/sell would not pair I sold another 5 shares at .102999 instead, that worked. cancelled my [email protected] order afterwards.

on the db level you should be able to see also cancelled transactions for that asset if you're into that. or just note it as interesting and won't be fixed. this is harmless ... and soon to be history/open source and problem of somebody else wink

I excluded the 8th decimal place theory as a duplicate of this as goat sells at .10300000 and any buy order visible up to 7 decimal places would be equal or higher and should match in all cases when it is created. fact that it was in the buy/sell table while stock was for sale at that price, that's interesting
hero member
Activity: 602
Merit: 513
GLBSE Support [email protected]
March 19, 2012, 08:23:50 PM
#40
will you keep fixing 1.0 bugs in the meantime?
or rather not Wink but you might want to notice we have TyGrr-Bank situation where ask=bid=.103 and orders are not paired


It's really odd. All I can say for this is to cancel the order and try again.

Nefario.
sr. member
Activity: 462
Merit: 250
March 19, 2012, 08:03:59 PM
#39
will you keep fixing 1.0 bugs in the meantime?
or rather not Wink but you might want to notice we have TyGrr-Bank situation where ask=bid=.103 and orders are not paired
hero member
Activity: 602
Merit: 513
GLBSE Support [email protected]
March 19, 2012, 01:10:56 PM
#38
Will we be having fewer sql database lockups in the new version?

We shouldn't have any.
Didn't you already answer that?

 Huh I think I need more sleep.
hero member
Activity: 812
Merit: 510
March 19, 2012, 12:42:33 PM
#37
Will we be having fewer sql database lockups in the new version?

We shouldn't have any.
Didn't you already answer that?
hero member
Activity: 602
Merit: 513
GLBSE Support [email protected]
March 19, 2012, 12:40:38 PM
#36
Will we be having fewer sql database lockups in the new version?

We shouldn't have any.
hero member
Activity: 812
Merit: 510
March 19, 2012, 11:32:58 AM
#35
Yes, sleep, get everything worked out how it should be then come let it out.

Even if everything was ready right now, people would still be asking questions, and you'd be too burnt out to answer.
donator
Activity: 4760
Merit: 4323
Leading Crypto Sports Betting & Casino Platform
March 19, 2012, 09:24:57 AM
#34
Take your time.  Get some sleep.
hero member
Activity: 602
Merit: 513
GLBSE Support [email protected]
hero member
Activity: 812
Merit: 510
March 03, 2012, 05:37:31 PM
#32
Mmmmk...makes sense.
hero member
Activity: 602
Merit: 513
GLBSE Support [email protected]
March 03, 2012, 05:28:52 PM
#31
I'm apparently going to keep going here...

Can't sell any assets...

NameError at /trade/process_sell/JLP-BMDT
uninitialized constant AssetAccount::Not_assets
file: module.rb location: const_missing line: 36

Have you checked to see if you have any assets in your account to sell?

I have a feeling that your balance is probably 0

This is because of the IPO, when you create a new asset it makes an IPO, when the IPO reaches the launch date it will deposit the specified amount of assets into your account.

Before the IPO launches people can make buy orders.

I'm going to have to remove the sell link if your balance is 0.

If you want to test selling assets, create a new one and put the IPO date in the past, it should pretty much just deposit the shares into the account right away then (but without a public IPO page).

Nefario.
hero member
Activity: 812
Merit: 510
March 03, 2012, 05:20:50 PM
#30
I'm apparently going to keep going here...

Can't sell any assets...

NameError at /trade/process_sell/JLP-BMDT
uninitialized constant AssetAccount::Not_assets
file: module.rb location: const_missing line: 36
hero member
Activity: 602
Merit: 513
GLBSE Support [email protected]
March 03, 2012, 05:17:25 PM
#29
More bugs...

When issuing additional shares I get this.

Sinatra doesn’t know this ditty.


Try this:
get '/asset/issue/JLP-BMDT' do
  "Hello World"
end
Oh, yeah that. actually I was supposed to remove that link.

I'm getting rid of the simple issue and sell shares, in the future, when you want to issue shares it's going to be put to motion. That won't be available at launch though.

Thanks for finding that though.
hero member
Activity: 812
Merit: 510
March 03, 2012, 04:45:33 PM
#28
More bugs...

When issuing additional shares I get this.

Sinatra doesn’t know this ditty.


Try this:
get '/asset/issue/JLP-BMDT' do
  "Hello World"
end
Pages:
Jump to: