Well, I knew it was 1500 then I saw 2000 on the GBLSE listing and second-guessed myself...then I revised my bid down to reflect my estimated buy line. So I missed it. Live and learn. Congrats to all who got some and the cartel underwriting this thing. Cool stuff. 
Topic: . - page 30. (Read 67479 times)
Oops, I thought it was 2000 shares Well, I knew it was 1500 then I saw 2000 on the GBLSE listing and second-guessed myself...then I revised my bid down to reflect my estimated buy line. So I missed it. Live and learn. Congrats to all who got some and the cartel underwriting this thing. Cool stuff.
Well, I knew it was 1500 then I saw 2000 on the GBLSE listing and second-guessed myself...then I revised my bid down to reflect my estimated buy line. So I missed it. Live and learn. Congrats to all who got some and the cartel underwriting this thing. Cool stuff. 
Interestingly a few people have now sold off their shares immediately for a quick <4 Bitcent profit over the chance of a <21 Bitcent profit in 4 weeks per share.
...anyways, 1.12 is still a 14.29% profit (if pirate delivers that is...)
Unfortunately the table with real percentages was removed, so here's a new one:
...anyways, 1.12 is still a 14.29% profit (if pirate delivers that is...)
Unfortunately the table with real percentages was removed, so here's a new one:
Code:
1 28,00% 1,28
1,01 26,73% 1,28
1,02 25,49% 1,28
1,03 24,27% 1,28
1,04 23,08% 1,28
1,05 21,90% 1,28
1,06 20,75% 1,28
1,07 19,63% 1,28
1,08 18,52% 1,28
1,09 17,43% 1,28
1,1 16,36% 1,28
1,11 15,32% 1,28
1,12 14,29% 1,28
1,13 13,27% 1,28
1,14 12,28% 1,28
1,15 11,30% 1,28
1,16 10,34% 1,28
1,17 9,40% 1,28
1,18 8,47% 1,28
1,19 7,56% 1,28
1,2 6,67% 1,28
1,21 5,79% 1,28
1,22 4,92% 1,28
1,23 4,07% 1,28
1,24 3,23% 1,28
1,25 2,40% 1,28
1,26 1,59% 1,28
1,27 0,79% 1,28
1,28 0,00% 1,28
I was capturing the order book at one minute intervals up to the trigger (my last scrape about 5 seconds before the issue). Yes, the 500 bid at 1.07 came in the last two minutes.
With four minutes to go, total bids were around 2850 before going to 3500 and then 4174. At the close it fell to 3585 and could be due to re-bidding.
Similarly, the cut-off increased from 1.055 to 1.06, 1.07 and then dipped to 1.068.
With four minutes to go, total bids were around 2850 before going to 3500 and then 4174. At the close it fell to 3585 and could be due to re-bidding.
Similarly, the cut-off increased from 1.055 to 1.06, 1.07 and then dipped to 1.068.
Excellent, now I don't have to feel like I left anything on the table at a bit over 1.07. What clock did you go by?
I'm linked to internet time servers, and I would expect glbse to be the same. Allowed for the request lag and refresh, then a simple bit of analysis formulas to look at all the bids.
At least next week's bond issue will not take so much work.
I was capturing the order book at one minute intervals up to the trigger (my last scrape about 5 seconds before the issue). Yes, the 500 bid at 1.07 came in the last two minutes.
With four minutes to go, total bids were around 2850 before going to 3500 and then 4174. At the close it fell to 3585 and could be due to re-bidding.
Similarly, the cut-off increased from 1.055 to 1.06, 1.07 and then dipped to 1.068.
I got the same information. With four minutes to go, total bids were around 2850 before going to 3500 and then 4174. At the close it fell to 3585 and could be due to re-bidding.
Similarly, the cut-off increased from 1.055 to 1.06, 1.07 and then dipped to 1.068.
I was capturing the order book at one minute intervals up to the trigger (my last scrape about 5 seconds before the issue). Yes, the 500 bid at 1.07 came in the last two minutes.
With four minutes to go, total bids were around 2850 before going to 3500 and then 4174. At the close it fell to 3585 and could be due to re-bidding.
Similarly, the cut-off increased from 1.055 to 1.06, 1.07 and then dipped to 1.068.
With four minutes to go, total bids were around 2850 before going to 3500 and then 4174. At the close it fell to 3585 and could be due to re-bidding.
Similarly, the cut-off increased from 1.055 to 1.06, 1.07 and then dipped to 1.068.
Excellent, now I don't have to feel like I left anything on the table at a bit over 1.07. What clock did you go by?
I was capturing the order book at one minute intervals up to the trigger (my last scrape about 5 seconds before the issue). Yes, the 500 bid at 1.07 came in the last two minutes.
With four minutes to go, total bids were around 2850 before going to 3500 and then 4174. At the close it fell to 3585 and could be due to re-bidding.
Similarly, the cut-off increased from 1.055 to 1.06, 1.07 and then dipped to 1.068.
With four minutes to go, total bids were around 2850 before going to 3500 and then 4174. At the close it fell to 3585 and could be due to re-bidding.
Similarly, the cut-off increased from 1.055 to 1.06, 1.07 and then dipped to 1.068.
Looks like it's currently yielding around 14%. It will be interesting to watch this.
14% for a month is pretty good, but of course it all depends on how likely you think Pirate is to default.
WTF?! 
I'd love to have an API to see orders + an orderbook snapshot of that trade... according to my calculations it should have gone down until 1.06 at least, there must have been some hefty snipes in the end!
I'd love to have an API to see orders + an orderbook snapshot of that trade... according to my calculations it should have gone down until 1.06 at least, there must have been some hefty snipes in the end!
you didnt refresh soon enough. 2 minutes~ before the deadline the bottom was at 1.07
This looks like a pure HYIP to me, but there are many very smart traders betting against a default, so I was convinced. WTF?!
I'd love to have an API to see orders + an orderbook snapshot of that trade... according to my calculations it should have gone down until 1.06 at least, there must have been some hefty snipes in the end!
I'd love to have an API to see orders + an orderbook snapshot of that trade... according to my calculations it should have gone down until 1.06 at least, there must have been some hefty snipes in the end!
There was one for 500 at a little over 1.07; a third of the bonds right there.
WTF?!
I'd love to have an API to see orders + an orderbook snapshot of that trade... according to my calculations it should have gone down until 1.06 at least, there must have been some hefty snipes in the end!
I'd love to have an API to see orders + an orderbook snapshot of that trade... according to my calculations it should have gone down until 1.06 at least, there must have been some hefty snipes in the end!
The GLBSE twitter account has the entire record.
:\ had to change my bid b/c it was to low and didnt come through in time. oh well. didnt have a chance to get my coins in from my wallet either.
seems that happened to a few people. I have to move my price over 1.7 to get in but I see some shares sold below that mark so a bunch of coins got stuck out.
seems that happened to a few people. I have to move my price over 1.7 to get in but I see some shares sold below that mark so a bunch of coins got stuck out.
Just to keep everyone informed ,there was an issue with deposits not being processed for a period of about an hour.
This has now been fixed, the normal wait is for 6 confirmations, anyone who has been waiting longer please check your account, it should be there now.
Sorry about the delay.
Nefario.
This has now been fixed, the normal wait is for 6 confirmations, anyone who has been waiting longer please check your account, it should be there now.
Sorry about the delay.
Nefario.
Thanks, I got hit by this and I was starting to get paranoid.
Thanks again !
Just to keep everyone informed ,there was an issue with deposits not being processed for a period of about an hour.
This has now been fixed, the normal wait is for 6 confirmations, anyone who has been waiting longer please check your account, it should be there now.
Sorry about the delay.
Nefario.
This has now been fixed, the normal wait is for 6 confirmations, anyone who has been waiting longer please check your account, it should be there now.
Sorry about the delay.
Nefario.
Jump to: