Beta GLBSE stock market Open for trading

[S3052]

After installing all the programs from setup as described, I tried to run the market
with blackmarket.py

Then I got the error:

"Traceback <most recent call last>:
 File "C....\blackmarket.py, line 10, in <module>
   from M2Crypto.util import passphrase_callback as prompt_password
Import Error: No module named M2Crypto.util"

can anyone help?

you nedd M2crypto: http://chandlerproject.org/Projects/MeTooCrypto#Downloads

kokjo,
I went to the link, which one should I install?
thanks for the help in advance

[kokjo]

After installing all the programs from setup as described, I tried to run the market
with blackmarket.py

Then I got the error:

"Traceback <most recent call last>:
 File "C....\blackmarket.py, line 10, in <module>
   from M2Crypto.util import passphrase_callback as prompt_password
Import Error: No module named M2Crypto.util"

can anyone help?

you nedd M2crypto: http://chandlerproject.org/Projects/MeTooCrypto#Downloads

kokjo,
I went to the link, which one should I install?
thanks for the help in advance

it depends of what version of python you are using. and what OS you are using.
so if you are using python 2.7 and windows 32 bit(vista, xp...) you should download: http://chandlerproject.org/pub/Projects/MeTooCrypto/M2Crypto-0.21.1.win32-py2.7.msi

but thats maybe not the case... you could be using python 2.6 or MacOSX or Linux, or whatever...

[markm]

I use Fedora Core 14, so I just needed to do "yum install m2crypto".

-MarkM-

[S3052]

After installing all the programs from setup as described, I tried to run the market
with blackmarket.py

Then I got the error:

"Traceback <most recent call last>:
 File "C....\blackmarket.py, line 10, in <module>
   from M2Crypto.util import passphrase_callback as prompt_password
Import Error: No module named M2Crypto.util"

can anyone help?

you nedd M2crypto: http://chandlerproject.org/Projects/MeTooCrypto#Downloads

kokjo,
I went to the link, which one should I install?
thanks for the help in advance

it depends of what version of python you are using. and what OS you are using.
so if you are using python 2.7 and windows 32 bit(vista, xp...) you should download: http://chandlerproject.org/pub/Projects/MeTooCrypto/M2Crypto-0.21.1.win32-py2.7.msi

but thats maybe not the case... you could be using python 2.6 or MacOSX or Linux, or whatever...

Thanks for the efforts.
I have windows 64bit and installed python 2.7
The key issue is that no OpenSSl can be installed on this machine. I tried already 5 different versions. I would love to see whats wrong.

[Nefario]

$ python2.6 bmc.py balance
Enter passphrase:
 
balance --:-- 25000000
$ python2.6 bmc.py withdraw 25000000 MYADDRESS
Enter passphrase:

balance --:-- balance_error
result --:-- True

$ python2.6 bmc.py balance
Enter passphrase:
Problem: Your account doesn't balance, you may have deposited funds, please try again in a few minutes,if this problem continues please inform the administrator

Even after two confirmations.

Best regards,
Casper

With regards inputing numbers to the client (and what it prints out) I'll change that to mBTC (e.g. 0.75btc=750mBTC).

Your account should be working now.

[Nefario]

Market down for bug fixing.

[Nefario]

Open again, will go down for an hour or two tomorrow.

[Ryland R. Taylor-Almanza]

Open again, will go down for an hour or two tomorrow.

^1000th post. Congratulations!

[FooDSt4mP]

Due to wrestling with accounting problems caused by premature usage of the exchange we will be launching in about 4 hours(I've got meatspace things to attend to first).

Can you please use floating point numbers for currency like all other Bitcoin clients rather than the very confusing huge integers?

E.g. 0.75 rather than 75000000.

750 mBTC would be fine too IMO.

Best regards,
Casper

No, no, no, no, no.  Never using floating point when dealing with anything of value.  Every floating point number is an approximation, and errors quickly pile up.  Use fixed point.  However, I would hope Nefario already knows this.

[xf2_org]

No, no, no, no, no.  Never using floating point when dealing with anything of value.  Every floating point number is an approximation, and errors quickly pile up.  Use fixed point.  However, I would hope Nefario already knows this.

The presence of a decimal does not necessarily imply floating point.  SQL and all the major programming languages support fixed point decimals, and these types are widely used in banking and finance to store money.

[FooDSt4mP]

No, no, no, no, no.  Never using floating point when dealing with anything of value.  Every floating point number is an approximation, and errors quickly pile up.  Use fixed point.  However, I would hope Nefario already knows this.

The presence of a decimal does not necessarily imply floating point.  SQL and all the major programming languages support fixed point decimals, and these types are widely used in banking and finance to store money.

I know this.  Look at what I quoted.  He specifically says "floating point".  I said use fixed point.

[Nefario]

No, no, no, no, no.  Never using floating point when dealing with anything of value.  Every floating point number is an approximation, and errors quickly pile up.  Use fixed point.  However, I would hope Nefario already knows this.

I think I'm vaguely aware of it...you know....because it's all done in 64bit integers.

I would like to move to a fixed point decimal representation on the client only(input/output, easier on the eyes), on the market feed (http://twitter.com/#!/GLBSE) it will remain 64bit integers, and internally it will be represented as 64bit integers.

I even had to re-write the json parsing library to deal with the return values from bitcoind's json, the library was converting them to floating point numbers, rewrote it to convert straight into fixed point decimal, and then 64bit integers.

[cuddlefish]

I would like to move to a fixed point decimal representation on the client only(input/output, easier on the eyes), on the market feed (http://twitter.com/#!/GLBSE) it will remain 64bit integers, and internally it will be represented as 64bit integers.

If you're using Django for the server, check out contrib.humanize. It's awesome and basically made for this.

[Nefario]

I would like to move to a fixed point decimal representation on the client only(input/output, easier on the eyes), on the market feed (http://twitter.com/#!/GLBSE) it will remain 64bit integers, and internally it will be represented as 64bit integers.

If you're using Django for the server, check out contrib.humanize. It's awesome and basically made for this.

Servers in ruby 

[Nefario]

Voting has now been added to GLBSE

Get the latest client code from gitorious(git users git://gitorious.org/black-market/black-market-client.git),everyone without git can get it here as a gzip file.

As the issuer of an asset you must:

FILE is the text of what you will have your shareholders vote on(your motion), and save it as a textfile(example, motion.txt).

ASSET-ID is either the full asset id or it's ticker symbol

DATE is the day that you want the voting to finish (that is the date it stops, not one day after), it's format is dd-mm-yy dd being day, mm being month, yy being year.


bmc.py new-vote ASSET-ID FILE DATE

You can see the id's of all the open motions of assets you posses with:

bmc.py motions

You can get the details of any motion by using the motions id:

bmc.py motion MOTION-ID

You can vote on a motion with:

bmc.py vote MOTION-ID CHOICE

where choice is either the words yes or no, you can change your vote as many times as you like before the motion closes.

You can get the status of a motions vote with:

bmc.py tally MOTION-ID

Transfering or selling shares and voting

If you have an asset where you have voted on a motion, and you then sell or transfer those assets, the corresponding votes will be removed, and the new owner will now have the voting ability.

If you experience any problems (errors for example) please let me know either on this thread, by pm'ing me or emailing me (doctor.nefario@gmail.com)

Please be patient if you don't recieve a quick reply, I'm probably sleeping (I'm on Beijing time).

Nefario.

[codemojo]

Hey, are you guys still looking for coders?

[Nefario]

Hey, are you guys still looking for coders?

Yes and no.

No as in not right now, we've got enough coders.

But yes as in we still have a number of projects that are rolling out, begining to or will begin shortly.

What's your skillset?(everything not just programming).

[codemojo]

What's your skillset?(everything not just programming).

Please see the email I've sent.

[Nefario]

What's your skillset?(everything not just programming).

Please see the email I've sent.

Got it, will reply tomorrow. It's late here.