Bitcoin Forum

UPDATE!

Once again we're going to delay the release of GLBSE2.0

You can see the progress that has been made at http://dev.glbse.com, but there are still some bugs to work out and a couple of crucial things to add (like bitcoin deposits/withdrawals lol).

I've been working on this non-stop since Friday, taking a little time of only to work on something else, during this time I've not slept.

I'm quite sure if I was to try to stick with today as the release date two things:
1) It wouldn't be ready, and everyone would be unhappy
2) The stress would most probably kill me.

What was meant to be 2-3 days has become a lot longer, I'm sorry for the delay.

Nefario.

I'm logged in but getting nothing but balance sitting at retrieving, and trying to click on bitcoin/assets/market history just sticks at refreshing.

I've logged in and out a few times over the last few hours, but still the same.

marked

Thank m, fixed that.

Nefario.

many thanks. Logged in now.

Out of interest this is the third week in a row that it's gone down monday that I know of in this manner.

Is this due to all the dividends being paid out Sunday/Monday?

marked

Nefario, 3 questions.

1) When GLBSE 2.0 gets pushed, how will account owners transfer their information into the new system, or how will we have to prove our ownership of accounts in the new system if everything is automatically migrated?

2) Will all asset contracts held by an account be moved into the new system?

3) Will we finally be able to edit contracts? I have plans for the original JLP but I'd obviously have to edit the contract to something that made sense.

Thanks

I'm not sure as to the reason why it's happening on Mondays. my experience is that it usually happens just as my net connect goes down, like today for example.

JL, when 2.0 launches, I'll freeze 1.0, and move the most active assets over(at first).

The next step will be to log into you 1.0 account and it will give you a code, enter that into 2.0 and it will transfer everything.

Yes we'll finally be able to edit contracts, however not right away. Contract edits will be put to a vote, if passed then the edit becomes the contract.

Nefario.

Thank you much sir. This should be exciting, I'm liking how the new system looks an functions so far. (At least on the dev site).

It should really improve things, easier to use, more functionality, and we'll have more users (and liquidity) as a result.

Looking forward to it...

marked

Go to dev.glbse.com (http://dev.glbse.com), check out how it's going to look. I believe it will add much more usability to the site, and be much more user-friendly than the current version.

Web keys were a good idea, the problem was that users didn't understand how they worked, and that they needed to back them up.

Take as much time as you need. I vastly prefer the safe approach.

Good decision to postphone the upgrade. No point in deploying software that's not finished.

Thanks for the work, Nefario! Looking forward to release!

Still delayed I take it?

Id like to gather sample contracts together to give people an idea on how to construct their own. Is there a way to view them all without having to go into each companies page ?

Yeah, I've just finished a presentation at TEDx in Leeds (which went terrible), and I'm off to bed, I'll kick off development in the morning and aim to have all the features for the release (with loads of bugs) up on the demo site for bug hunting and feedback.

Mila's found a ton of bugs in the current demo that I've not fixed yet, I've been racing to get release features done and dealing with tons of non GLBSE2.0 stuff that's held me back.

Nefario.

I'm anxiously awaiting this. I've waited to pull the trigger on some shares because I'm utterly confused by the process. Hopefully this will help.

As much as I hate to say it, as long as there aren't any security holes, just push it how it looks on the dev...it can be a constantly evolving project. This vs trying to push it all out at once.

Certain functionality is needed, IPO's haven't been done yet, etc.

Will we be having fewer sql database lockups in the new version?

0 is the expected number of DB lockups in the new version.

Just an update on where I'm currently at, the demo site will be updated in a couple of hours, hacking away, wired up to my eyeballs on Rockstar XDurance(think RedBull but strong, bigger can, and cheaper).

I've updated the test site, added loads of functionality and introduced loads of bugs.

It's ugly, but it just about works.

Go to http://dev.glbse.com

Feedback welcome

I got an ArgumentError at /asset/create...when trying to ...well you know...even though it still shows up?

But when you click on the asset you get a lovely NoMethodError at /asset/view/JLP-BMDT

Then when I choose an asset account, I can't change back to my BTC accounts.

Thanks, fixed the first bug, is the second one (not being able to switch back to BTC account) still happening?

Yep, can't switch away from JLP-BMDT

Brilliant, thanks for that, it was a bug, fixed now.

Yes it is. Thanks

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.

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.

Mmmmk...makes sense.

Delayed again, see op

https://bitcointalk.org/index.php?topic=66505.msg771771#msg771771

Take your time.  Get some sleep.

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.

We shouldn't have any.

Didn't you already answer that?

 ??? I think I need more sleep.

will you keep fixing 1.0 bugs in the meantime?
or rather not ;) 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 5@.103 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

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.

@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/

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 <top (required)> line: 74

Hope this helps a little.

Looking forward to buying some of those IPOs!

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

Take your time dude, just remove the "** Launching Monday 18 March **" from the front page :p

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 ; )