I confirm after cancelling buy order the reserve is correctly updated

It is also correctly updated the total reserve after first buy order is created
(even if on form load it showed 0 reserved and an existing buy order, which was expected after the account reserve was reset)

can be closed. also my other tests with reserved btc succeeded
edit: except for btc kept in reserve if buy order price > actual buy price

can't reproduce the dividend bug

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

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

he's joking. english teacher would not make such grammatical errors ...

@Nefario you could still switch to 2.0 fast enough to jump on the IPO train for a good part of the sales and fees from that
my question was 'R you willing to bribe?

to potential stock buyers, please bear with us for a moment this is is important. no more hijacking and off topic after 4 am. I promise

edit: and ofc it's only teasing and pointing out interesting moments in time.

dear community, I would like to file a progress report on the new language support I started 4 weeks ago.

there was absolutely no progress on the 90+ % ready new language.
I posted a question with fairly reasonable question how to treat the special characters in the translation strings back then (things like n% d% and stuff) and what other noob catches are there that I needed to get answer to finish that job.

I am dissapoint from the roaring silence but also kind of relieved from dropping this commitment to finish the translation.
maybe next time. sorry for giving up so quickly.

Loan has been repaid on time and in full amount.

silly joke but here is the thread of thoughts to follow
- if the new fee structure would be in place, successfull IPO of this asset would net BitcoinGlobal 25 btc as fees from the 2500 btc raised here
- if there would be less bugs reported, the 2.0 glbse could be already in prod or at least not delayed for published reasons
- having 25 btc vs not having 25 btc makes a difference (having 25 btc is the preferred option)
- from above assumptions I concluded that I contributed to the loss of 25 btc to BitcoinGlobal

smiling now? wink

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

yes, that sucks. it would net 25 btc in fees from sale/trade
but if the IPO lasts substantially longer, BG gets it's share
I'm willing to stop testing for a bribe and fast 2.0 deployment wink

that was me (+1 counter). I sold tygr bank 5@0.102999 to buy 1 share here
i did not want to wait for 6 confirmations

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

dividends (after fees) are wrong

10 btc dividends result in 8.93712 btc paid to shareholders.

affected release 18/Mar (guess who forgot to increment counter? wink)

btw if you want to pay dividends visit the asset view page .../asset/view/TICKER
& click pay dividends

the only option to pay dividends is "how much you gonna spend on this?"
easy (and slightly not working)



edit: either fixed or can't be reproduced
not an issue 20/Mar

New asset fee:   8.0 BTC
Dividends fee rate:   0.50 %
Trade fee rate, paid by seller:   1.00 %

sooo, where's the COGNITIVE or Cognitive asset?
I searched the glbse's asset list (list of contracts) and tried to find it via the Asset page but no success.

can confirm both:
- trading between accounts works fine
- blocking bitcoins as reserved for purchase after closed transaction remains.

but that should not prevent us from further testing.

edit: connecting glbse to testnet is not that important after all. since we never manage the bitcoins like we would in a proper web wallet implementation (& glbse is kind of mixing service ) the 'only' benefit of connecting it to test net would be to verify deposit/withdrawal (because all other bitcoin transactions are glbse internal db records; all fees, dividends and trades exist independent from blockchain and we have no way of knowing which coins would be used for withdrawal ...)

@Nefario big Thank you! ... for fixes & delayed deployment in prod

@all testers & curious folks a note about testnet coins, where to get them and how to use testnet

- start your client with the "-testnet" switch/parameter; it will create a subdir called 'testnet' in your bitcoin client working directory, create testnet wallet and download the testnet chain. last time I checked it was only about 50k blocks and since there are far less transactions, blocks are smaller and download _much_ faster.
- google for "bitcoin faucet +testnet" to get 50 testcoins from Gavin or PM me with testnet address and I'll send 10 coins per request to first 8 users who'll ask for them (allow some 8-12 hrs processing time ...)
- make sure you use testnet (addresses do not start with 1, that's a safe indication)

I did not check if dev.glbse is already connected to testnet but if it is or when it will be, we probably will no longer have the luxury of a funded account after registration and this extra step would be necessary (and the sleep deprived admin could have missed something in the process so it might not work out (deja-vu?))

If this gets enough attention and good will, we might get some test coins donated from the old boys so some kind of funding testers accounts might be automated (careful with this expectation, this is my private rumbling only) but not sure if worth the extra effort. getting testnet coins afaik is easy and straightforward.

if not sure how to start your client with the -testnet parameter (each OS handles it differently), try & you'll succeed eventually. if tried for half an hour and still not there, PM me or post here.

edit: dev.glbse works with dummy bitcoins for now, happy testing!

bitte benutze html tags in dem Vetrag damit es gut liesbar ist und nimm dir Zeit ..
die http://dev.glbse.com ist die richtige Spielwiese dafuer

verbleibe MfG

can we have 'a week' of glbse 2.0 running with testnet coins?

I'd side with users who want a later deployment of the new version

I can't retest my list of known issues before later tonight and I did only basic testing.
the bug when buy orders at lower price cause blocking btc balance is IMO serious enough to wait for a new version
and allow at least 24h for testing

@nefario don't be. it's more or less friendly teasing.

my worries are
- untested interface to bitcoin (we did nothing with testnet bitcoins, only dev.glbse which uses dummy coins)
- short testing of the 'final' release, some nasty bugs still inside might be hiding
- unannounced changes (trading fees?)
- really nefarious transition from 1.0 to 2.0

this will affect all shareholders that's why I post it here and don't think it would be completely off topic in TyGrr's thread, since he has 2 big products on the exchange.
I really like what you do (both, goat and nefario) and just bitch a bit about how unreasonably fast deployment of glbse 2.0 might spoil something.

It's a valid use case when I as issuer need to buy stock back.
It works with 2 accounts but that is a different use case.