.

[PatrickHarnett]

The amount of capital held in PPT will always be greater than 25% of the face value of all outstanding bonds.

25% of the face value of the bonds from the capital reserves of PPT (0.32 BTC per bond)

There are 3000.A+3000.B+3000.C+6000.E = 15 000 bonds.
The face value of them is 15 000 * 0.32 = 4800
Total PPT vol is 3960
3960 < 4800
What is wrong with my math?

Nothing - the problem was with the double sale of PPT.E.  Rather than screw up the whole shareholding structure, the six members of PPT agreed to personally (jointly and severally) underwrite the difference if a default occurred.  We have personally pre-paid nearly 4000 coins into PPT, and the remainder (a contingent liability) is unpaid.

The insurance is designed to pay out 3840 coins based on 25% of 12,000 bonds at a value of 1.28 per bond on issue at any one time.  This is similar to how agreed value insurance works - no gimmick, a simply payoff.  While some people like to play the part of detractors, PPT bonds remain one of the higher value Pirate Pass Through products in the bitcoin market place.

(as a real life example, I have an insurance value on my car (currently $14k) so if it is stolen, I get an agreed value.  However, it is actually worth more than that (possibly double), and I've actually spent much more than that - so I pay a premium to my insurance company and in the event of claim, I get a small percentage back.  I do not get to see the cash the company holds to pay my claim, nor do I think it is a gimmick that a company is offering insurance)

[stochastic]

This week's zero coupon bond is now open for bidding at https://glbse.com/asset/view/PPT.D

Are you still pushing buttons to release the bonds for sale?

[stochastic]

This week's zero coupon bond is now open for bidding at https://glbse.com/asset/view/PPT.D

Are you still pushing buttons to release the bonds for sale?

Yes.  But, I do have someone working on a script to do this for us in the near future.

When is the estimated completion of that?

[BurtW]

This week's zero coupon bond is now open for bidding at https://glbse.com/asset/view/PPT.D

Are you still pushing buttons to release the bonds for sale?

Yes.  But, I do have someone working on a script to do this for us in the near future.

When is the estimated completion of that?

Maybe by next week,  week after that for sure.  But Patrick is doing it and he seems to be pretty good at getting it done within a few seconds.

[PatrickHarnett]

Sounds like I'm up to push someone's buttons again tomorrow.

[piotr_n]

Isn't it just as simple, as using curl to post quantity=3000&price=100000000&ticker=PPT.D to https://glbse.com/api/market/buy/API-ID/API-KEY ?

[stochastic]

Isn't it just as simple, as using curl to post quantity=3000&price=100000000&ticker=PPT.D to https://glbse.com/api/market/buy/API-ID/API-KEY ?

That is part of it.

1.  Get selling criteria (What bond ticker to sell and how many of them to sell.)
2.  Verify connection
3.  Synchronize clock with GLBSE.
4.  Time to sell? If not then go to 3.  If yes, curl to post quantity=3000&price=100000000&ticker=PPT.D to https://glbse.com/api/market/buy/API-ID/API-KEY
5.  Sell bonds.
6.  Evaluate results (save bond sale history, email whoever)
7.  End

[piotr_n]

Isn't it just as simple, as using curl to post quantity=3000&price=100000000&ticker=PPT.D to https://glbse.com/api/market/buy/API-ID/API-KEY ?

That is part of it.

1.  Get selling criteria (What bond ticker to sell and how many of them to sell.)
2.  Verify connection
3.  Synchronize clock with GLBSE.
4.  Time to sell? If not then go to 3.  If yes, curl to post quantity=3000&price=100000000&ticker=PPT.D to https://glbse.com/api/market/buy/API-ID/API-KEY
5.  Sell bonds.
6.  Evaluate results (save bond sale history, email whoever)
7.  End

Neee.. You can just use runat or put the command into cron or windows scheduler, if you prefer.

And the GLBSE clock is pretty well synchronized - just synchronize yours to some NTP server.
Besides in the past, except for the last time, you were +/- 2 min accurate.

6. Evaluating results - it's obviously a different task, though number 7 - the end - this one seems quite trivial 
Guys, if you need a genius to solve such a challenges, I'm here for you

[PatrickHarnett]

I don't use APIs - I could probably learn, but the effort (cost) outweighs the benefit.  Just like I could improve my web authoring skills, learn some new programming languages and a whole lot of other stuff.

It's easy for me to set the sell and wait for the clock to get to 2:00:00

[stochastic]

Isn't it just as simple, as using curl to post quantity=3000&price=100000000&ticker=PPT.D to https://glbse.com/api/market/buy/API-ID/API-KEY ?

That is part of it.

1.  Get selling criteria (What bond ticker to sell and how many of them to sell.)
2.  Verify connection
3.  Synchronize clock with GLBSE.
4.  Time to sell? If not then go to 3.  If yes, curl to post quantity=3000&price=100000000&ticker=PPT.D to https://glbse.com/api/market/buy/API-ID/API-KEY
5.  Sell bonds.
6.  Evaluate results (save bond sale history, email whoever)
7.  End

Neee.. You can just use runat or put the command into cron or windows scheduler, if you prefer.

And the GLBSE clock is pretty well synchronized - just synchronize yours to some NTP server.

6. Evaluating results - it's obviously a different task.
Though number 7 - the end - this one seems quite simple

No, The program should be synchronized with the host server where the selling will be done and have a countdown to the sell time.  If chron is set up to sell at 01:00:00 UTC then the sale will probably occur at 01:00:05 to 01:00:15 UTC.

I thought the idea was to sell exactly at the right second.

Also, what would happen if GLBSE was down right at the sale time? A connection needs to be verified beforehand, so then the connection to GLBSE should be made before the actual sale occurs to make sure GLBSE is not down or slow.  Synchronization and verification of GLBSE working could be done with one step.  That means the program needs a trigger to sell.  Since a connection to GLBSE was made and its server time was collected, a countdown would be the best way to trigger a sale.

[piotr_n]

I don't use APIs - I could probably learn

It's really trivial - I tell you.

You can test it first - just enable the API key and then run:

Code:

curl -d "quantity=3000&price=100000000&ticker=PPT.D" "https://glbse.com/api/market/sell/AAA/BBBBBBBBBBBBBBBBBBBBBBBBBB"

(replacing AAA with "API ID" and BBBBB with "API Key")

You can test it up front, using a different ticker and some high price - then you will see the order going to your "Sell Orders" - means it worked.

[stochastic]

I don't use APIs - I could probably learn, but the effort (cost) outweighs the benefit.  Just like I could improve my web authoring skills, learn some new programming languages and a whole lot of other stuff.

It's easy for me to set the sell and wait for the clock to get to 2:00:00

[piotr_n]

I thought the idea was to sell exactly at the right second.

Maybe that was the idea, but it hasn't been realized

Just look at the last sell of PPT.B - the time stamps are from GLBS decoded to my local time (they all should be 04:00:00)

Code:

2012-06-02 03:59:06   250 1.30000000
2012-06-02 03:59:06     1 1.06100000
2012-06-02 03:59:06     2 1.05100000
2012-06-02 03:59:06     2 1.05033000
2012-06-02 03:59:07     1 1.05030000
2012-06-02 03:59:07   490 1.05021000
2012-06-02 03:59:07   200 1.05020000
2012-06-02 03:59:08   100 1.05010000
2012-06-02 03:59:08   180 1.04800000
2012-06-02 03:59:08    13 1.04701000
2012-06-02 03:59:08    15 1.04652000
2012-06-02 03:59:08    25 1.04620000
2012-06-02 03:59:09    20 1.04601000
2012-06-02 03:59:09    15 1.04600010
2012-06-02 03:59:09   200 1.04570000
2012-06-02 03:59:09   120 1.04561000
2012-06-02 03:59:09    15 1.04560000
2012-06-02 03:59:09    10 1.04500000
2012-06-02 03:59:10   200 1.04500000
2012-06-02 03:59:10    47 1.04400001
2012-06-02 03:59:10    27 1.04350000
2012-06-02 03:59:10    33 1.04333330
2012-06-02 03:59:10    81 1.04300000
2012-06-02 03:59:10    29 1.04261110
2012-06-02 03:59:10    26 1.04230000
2012-06-02 03:59:10     1 1.04200000
2012-06-02 03:59:11   100 1.04120000
2012-06-02 03:59:11    64 1.04100005
2012-06-02 03:59:11     1 1.04100000
2012-06-02 03:59:11    90 1.04100000
2012-06-02 03:59:11     1 1.04100000
2012-06-02 03:59:11     3 1.04030000
2012-06-02 03:59:12   101 1.04020001
2012-06-02 03:59:12   200 1.04020000
2012-06-02 03:59:12    10 1.04010001
2012-06-02 03:59:12   100 1.04010000
2012-06-02 03:59:12     1 1.04000000
2012-06-02 03:59:12     5 1.03800001
2012-06-02 03:59:12   221 1.03800000

And the last PPT.A:

Code:

2012-05-26 04:00:19    15 1.13000000
2012-05-26 04:00:19    15 1.12000000
2012-05-26 04:00:19     2 1.12000000
2012-05-26 04:00:19    15 1.11000000
2012-05-26 04:00:19     2 1.11000000
2012-05-26 04:00:19     2 1.10300000
2012-05-26 04:00:20    15 1.10100000
2012-05-26 04:00:20     1 1.10000000
2012-05-26 04:00:20     2 1.10000000
2012-05-26 04:00:20    20 1.10000000
2012-05-26 04:00:20     1 1.09800000
2012-05-26 04:00:20     1 1.09600000
2012-05-26 04:00:20     1 1.09500000
2012-05-26 04:00:20    14 1.09500000
2012-05-26 04:00:20     1 1.09110000
2012-05-26 04:00:20     1 1.09100000
2012-05-26 04:00:20    15 1.09100000
2012-05-26 04:00:21     2 1.09000000
2012-05-26 04:00:21     6 1.09000000
2012-05-26 04:00:21     2 1.09000000
2012-05-26 04:00:21     1 1.08910000
2012-05-26 04:00:21     1 1.08880000
2012-05-26 04:00:21     1 1.08800000
2012-05-26 04:00:21     1 1.08700000
2012-05-26 04:00:21     1 1.08500000
2012-05-26 04:00:21    33 1.08260000
2012-05-26 04:00:21     1 1.08100000
2012-05-26 04:00:21   100 1.08000000
2012-05-26 04:00:22     2 1.08000000
2012-05-26 04:00:22     1 1.07810000
2012-05-26 04:00:22     1 1.07800000
2012-05-26 04:00:22     1 1.07500000
2012-05-26 04:00:22    30 1.07260000
2012-05-26 04:00:22     1 1.07100000
2012-05-26 04:00:22     2 1.07100000
2012-05-26 04:00:22     1 1.07010000
2012-05-26 04:00:22   100 1.07000000
2012-05-26 04:00:22     6 1.07000000
2012-05-26 04:00:22     2 1.07000000
2012-05-26 04:00:23     1 1.06910000
2012-05-26 04:00:23     1 1.06900000
2012-05-26 04:00:23    27 1.06820000
2012-05-26 04:00:23     1 1.06800000
2012-05-26 04:00:23     1 1.06660000
2012-05-26 04:00:23     1 1.06600000
2012-05-26 04:00:23     1 1.06510000
2012-05-26 04:00:23     3 1.06500000
2012-05-26 04:00:23   100 1.06110000
2012-05-26 04:00:23     1 1.06100000
2012-05-26 04:00:24   100 1.06000000
2012-05-26 04:00:24     1 1.05800000
2012-05-26 04:00:24     1 1.05550000
2012-05-26 04:00:24     1 1.05510000
2012-05-26 04:00:24    15 1.05500000
2012-05-26 04:00:24     1 1.05100000
2012-05-26 04:00:24   100 1.05010000
2012-05-26 04:00:24     5 1.05000001
2012-05-26 04:00:24     1 1.05000000
2012-05-26 04:00:25   100 1.05000000
2012-05-26 04:00:25    17 1.05000000
2012-05-26 04:00:25   476 1.05000000
2012-05-26 04:00:25     5 1.05000000
2012-05-26 04:00:25     1 1.04900000
2012-05-26 04:00:25     1 1.04800000
2012-05-26 04:00:25     1 1.04510000
2012-05-26 04:00:25     1 1.04500000
2012-05-26 04:00:25     1 1.04100000
2012-05-26 04:00:25    10 1.04100000
2012-05-26 04:00:25     1 1.04000000
2012-05-26 04:00:26   100 1.04000000
2012-05-26 04:00:26     8 1.04000000
2012-05-26 04:00:26    96 1.04000000
2012-05-26 04:00:26     1 1.03800000
2012-05-26 04:00:26     1 1.03500000
2012-05-26 04:00:26     1 1.03500000
2012-05-26 04:00:26     1 1.03110000
2012-05-26 04:00:26     1 1.03100000
2012-05-26 04:00:27     1 1.03100000
2012-05-26 04:00:27   101 1.03010000
2012-05-26 04:00:27     1 1.03000002
2012-05-26 04:00:27   100 1.03000001
2012-05-26 04:00:27     1 1.03000000
2012-05-26 04:00:27     1 1.02510000
2012-05-26 04:00:27     5 1.02500002
2012-05-26 04:00:27   100 1.02500001
2012-05-26 04:00:28     1 1.02500000
2012-05-26 04:00:28     1 1.02300000
2012-05-26 04:00:28   100 1.02200001
2012-05-26 04:00:28   100 1.02100001
2012-05-26 04:00:28   100 1.02000001
2012-05-26 04:00:28     1 1.02000000
2012-05-26 04:00:28     1 1.02000000
2012-05-26 04:00:28    10 1.02000000
2012-05-26 04:00:28   100 1.02000000
2012-05-26 04:00:28     5 1.01500000
2012-05-26 04:00:29     1 1.01500000
2012-05-26 04:00:29    75 1.01111000
2012-05-26 04:00:29     5 1.01010101
2012-05-26 04:00:29     5 1.01000001
2012-05-26 04:00:29     1 1.01000000
2012-05-26 04:00:29     5 1.01000000
2012-05-26 04:00:29     1 1.01000000
2012-05-26 04:00:29     1 1.00500000
2012-05-26 04:00:29    48 1.00000100
2012-05-26 04:00:30    42 1.00000100
2012-05-26 04:00:30    33 1.00000003
2012-05-26 04:00:30   450 1.00000002

[PatrickHarnett]

I don't use APIs - I could probably learn

It's really trivial - I tell you.

You can test it first - just enable the API key and then run:

Code:

curl -d "quantity=3000&price=100000000&ticker=PPT.D" "https://glbse.com/api/market/sell/AAA/BBBBBBBBBBBBBBBBBBBBBBBBBB"

(replacing AAA with "API ID" and BBBBB with "API Key")

You can test it up front, using a different ticker and some high price - then you will see the order going to your "Sell Orders" - means it worked.

and "curl" is linux?

Actually, my lecturers in Compsci did their stuff in the 50's and 60's and I originally learnt programming around 1980, and by the time I got to my undergrad degree we had a mix of main-frames and networked terminals to use (the Burroughs 48 bit processor was something else).  IBM XTs were just making their presence felt.  MS Word 3.0 would fit nicely on a 360kb floppy allowing you to save your work on the second drive (woo hoo).

[stochastic]

I thought the idea was to sell exactly at the right second.

Maybe that was the idea, but it hasn't been realized

Just look at the last sell of PPT.B - the time stamps are from GLBS decoded to my local time (they all should be 04:00:00)

Code:

2012-06-02 03:59:06   250 1.30000000
2012-06-02 03:59:06     1 1.06100000
2012-06-02 03:59:06     2 1.05100000
2012-06-02 03:59:06     2 1.05033000
2012-06-02 03:59:07     1 1.05030000
2012-06-02 03:59:07   490 1.05021000
2012-06-02 03:59:07   200 1.05020000
2012-06-02 03:59:08   100 1.05010000
2012-06-02 03:59:08   180 1.04800000
2012-06-02 03:59:08    13 1.04701000
2012-06-02 03:59:08    15 1.04652000
2012-06-02 03:59:08    25 1.04620000
2012-06-02 03:59:09    20 1.04601000
2012-06-02 03:59:09    15 1.04600010
2012-06-02 03:59:09   200 1.04570000
2012-06-02 03:59:09   120 1.04561000
2012-06-02 03:59:09    15 1.04560000
2012-06-02 03:59:09    10 1.04500000
2012-06-02 03:59:10   200 1.04500000
2012-06-02 03:59:10    47 1.04400001
2012-06-02 03:59:10    27 1.04350000
2012-06-02 03:59:10    33 1.04333330
2012-06-02 03:59:10    81 1.04300000
2012-06-02 03:59:10    29 1.04261110
2012-06-02 03:59:10    26 1.04230000
2012-06-02 03:59:10     1 1.04200000
2012-06-02 03:59:11   100 1.04120000
2012-06-02 03:59:11    64 1.04100005
2012-06-02 03:59:11     1 1.04100000
2012-06-02 03:59:11    90 1.04100000
2012-06-02 03:59:11     1 1.04100000
2012-06-02 03:59:11     3 1.04030000
2012-06-02 03:59:12   101 1.04020001
2012-06-02 03:59:12   200 1.04020000
2012-06-02 03:59:12    10 1.04010001
2012-06-02 03:59:12   100 1.04010000
2012-06-02 03:59:12     1 1.04000000
2012-06-02 03:59:12     5 1.03800001
2012-06-02 03:59:12   221 1.03800000

This is why synchronization is important.  The synchronization would increase in frequency as the countdown reaches 0.  After that, the sales happen in order until they are all filled so it depends on the speed of the GLBSE servers.

[Sukrim]

Just google it, curl is a command line program (there are also Windows versions) that is used to interact with webservers. You can then (with Windows) put the line posted above in a batch file and have the task scheduler call the batch file at exactly the time you specify. If you learned how to use computers back then, this should anyways be kinda familiar...

To find out about lag, you can try to put up test orders at 99999 BTC or so and check how long it takes until they show up (maybe 1-2 seconds I guess?) so you can then issue the sell order at xx:59:59 to have it at exactly yy:00:00

[stochastic]

Just google it, curl is a command line program (there are also Windows versions) that is used to interact with webservers. You can then (with Windows) put the line posted above in a batch file and have the task scheduler call the batch file at exactly the time you specify. If you learned how to use computers back then, this should anyways be kinda familiar...

To find out about lag, you can try to put up test orders at 99999 BTC or so and check how long it takes until they show up (maybe 1-2 seconds I guess?) so you can then issue the sell order at xx:59:59 to have it at exactly yy:00:00

What happens when the lag changes?

[piotr_n]

I don't use APIs - I could probably learn

It's really trivial - I tell you.

You can test it first - just enable the API key and then run:

Code:

curl -d "quantity=3000&price=100000000&ticker=PPT.D" "https://glbse.com/api/market/sell/AAA/BBBBBBBBBBBBBBBBBBBBBBBBBB"

(replacing AAA with "API ID" and BBBBB with "API Key")

You can test it up front, using a different ticker and some high price - then you will see the order going to your "Sell Orders" - means it worked.

and "curl" is linux?

Actually, my lecturers in Compsci did their stuff in the 50's and 60's and I originally learnt programming around 1980, and by the time I got to my undergrad degree we had a mix of main-frames and networked terminals to use (the Burroughs 48 bit processor was something else).  IBM XTs were just making their presence felt.  MS Word 3.0 would fit nicely on a 360kb floppy allowing you to save your work on the second drive (woo hoo).

Well... and I thought I was old

curl is basically available on any platform - you can find a windows build as well.
In fact it's a part of many different packages - i.e. if you install Git, you will also find curl.exe in its bin folder.

And, what I didn't mention, since GLBSE uses SSL, you will probably need to add the command line switch to ignore the certificate checking.
If you run it the first time and it fails, it will give you a hint of what the switch is called - I don't remember now, I have it in some curlrc file which I cannot find now

[imsaguy]

or he can just get the buy button ready, watch his computer tick, and click.

[stochastic]

or he can just get the buy button ready, watch his computer tick, and click.

Wasn't it stated earlier that missing a bus because it is late is worse than waiting a for a late bus?