The point is that he's not going to get burnt because it's not his coins he's playing with.

I'm not clear - does smoothie have the option to buy at $11 at the end of October, or the obligation to do so?  i.e. can he elect to just pay the 25% and not take the coins without breaking terms of the contract?

In this picture:



both lines are higher than all the prices in all 14 time periods.  How can that be, given that one of the lines is a 10 period EMA?  The average shouldn't be higher than all 10 of the preceeding highs should it?

Do you have a 'suppressions' file from when you ran it before?  There are usually a bunch of memory read/write errors in the libraries you link with which need suppressing before you can notice the errors in your own code.

My player didn't like the m3u link, but this worked for me:

  http://radio.donkdown.com:8000/radio

Point your audio player there if you can't listen any other way.

I carried on listening and found out what 'itgrowsbackfast' was a reference to.  And wished I hadn't...

Something seems to be going wrong with the blockchain.info database.

Searching for transaction 32c43975286013906f49f76f9403788616fc36cfcb0f6542449d93f7eac5a96f shows me a page saying that it was "Included in blocks   189704 (2012-07-18 21:16:19 +2 minutes)" but has "Confirmations:   0 confirmations".  The transaction was to my gox account, and showed up there hours ago.  Gox requires 6 confirmations.

http://blockchain.info/search?search=32c43975286013906f49f76f9403788616fc36cfcb0f6542449d93f7eac5a96f

I took a screenshot showing the incorrect page, along with recent block numbers.  Notice the weird "recent transaction" with a time thousands of hours ago.

Do you have an email address for him?  He's not replying to any of the ones I have.

On the hourly chart it's hours.  On the daily chart it's days.

Can you guess what it is on the 15 minute chart? 

Despite increasing the maximum bets far in excess of safe levels, SatoshiDice appears to be prospering:

Got mine too.  Withdrawals never took more than an hour I don't think.

You don't need the original private key to spend payments to a bitcoin address.  Any private key with the same bitcoin address will work.

We can see this by looking at the script on a random recent transaction.  In order to spend the 50 BTC output of that transaction, we need to provide an input such that this script is satisfied:

OP_DUP OP_HASH160 f88b720031b65505f853bce809d4f4641744d2ae OP_EQUALVERIFY OP_CHECKSIG

ie. we need to put two values on the stack, one of which is a public key which has a hash160 of f88b720031b65505f853bce809d4f4641744d2ae, and the other of which is the signature obtained when signing the spending transaction with the corresponding private key.

At no point is there anything to distinguish the sender's private key - all we can see is the 160 bit hash of the sender's public key and so any suitable private key will do.

Incidentally, when I modified the Makefile in cppForSwig/ my editor complained that lines 23 and 73 were "suspicious".  Both those lines contain only a single tab character.  Tab is significant in Makefiles, so it's probably better to delete those two tabs.

I've just been doing "gdb python" then "run sample_armory_code.py".  That should be enough, right?  gdb's "run" command takes arguments and passes them to the process it's debugging - in this case "python".

As predicted the crash is no longer happening of course...

When I get my faster laptop back from having it repaired I'll try running it using valgrind.  That usually finds the source of intermittent crashes.

Is this the right thread for discussing blockchain.info's wallet service?

I was just trying to answer [uri=http://bitcoin.stackexchange.com/questions/4198/how-can-i-retrieve-my-bitcoins-when-the-client-crashes-as-soon-as-it-begins-sync]this question[/url] by suggesting that they sign up for blockchain.info's wallet service, add the address as a 'watch only' address, and then when they want to spend from it, it will prompt for the private key.

In writing the answer I wanted to give step-by-step signup instructions, so I signed up for a new wallet to see how that works these days.  I tried 3 or 4 times and every time I got stuck at the "proceed to login" button that appears after typing the password and captcha, and optionally typing an email address and nickname.  I would click the "proceed to login" button and nothing would happen.  I tried in chromium and firefox and got the same result every time.  I just tried again now, and it's working again.

Hmmm.

So it's possible that this is MtGox's 'hot wallet'.

The reason I said I seemed to be many wallets mixed together is that it contains at least 5 of the addresses which receive interest from BS&T each week.  But it's quite possible that those 5 people have given MtGox deposit addresses as their BS&T interest payment address.

Just don't win too much or report too many bugs in the software or you might be abused by the owner and banned from the site.

I ran my modified copy of sample_armory_code.py twice today.  Both times it failed with "Segmentation fault".  I've not modified the C++ code at all.

I'm now running it in gdb to hopefully get a stack trace for you, though in my experience running it in gdb is often enough to stop the crash from happening.

Thanks for the code znort - I'm impressed by how fast it is.

I notice that 1113qRXdSA3Sdioib76mGSv9cfUYTY3xn is in a cluster of 191939 addresses.  It seems to be the combination of many different wallets.  Are you aware of a mixing service which would cause this to happen?

It sounds like you're saying you want more than 6.9% on the uninsured part of your deposit.

In order to pay you that, payb.tc would have to invest the insured part with pirate as well, and then may not be able to pay you in the case of a pirate default.  Unless he has other funds he's willing to risk.  But in that case it would be more cost effective to stop offering insurance and put those other funds with pirate rather than holding them somewhere safer so he can be sure to be able to pay out insurance claims.

Insurance companies are able to make a profit because not everybody's house burns down on the same day.  The ones who don't suffer a disaster pay for the ones who do to rebuild their house.  With BS&T it's different - if it defaults, it defaults for everyone.