Is there a listing of strange or unusual scripts found in transactions?

I’m studying scripts and am looking for strange or unusual scripts that have appeared in any of the *coin networks..(outside the standard ones listed on this page)

  • Is any one person, or website listing non-standard transactions that are not generated by the default client?

Ideally there would be an analysis of the script and what’s going on, but I’m not picky. I’d even settle for a command line method to extract this data and discover it myself.

My goal is to learn what contracts are occurring in each network and determine the frequency of each. (How popular is multi-sig tx over time)

Alternatively, I can use this as a tool to learn how people are using the scripting language.

What are orphaned and stale blocks?

If I understand it right, a stale block is a block for which an earlier confirmation has been found and was accepted by majority of people. This block is considered invalid and is later never used.

But what is a orphaned block. How is it created? How is it verified that it is orphaned and what is done to the orphaned block?

Unlocking wallet, recovering password

I want to send bitcoins, but cannot unlock my wallet. The rpc password located in \AppData\Roaming does not work. How can I unlock my wallet? Deleting the wallet.dat erases all my bitcoins, which I would like to keep.

How do I optimize my usage of oclvanitygen?

I’d like to extract the most performance possible from oclvanitygen. Can anyone tell me what the best practices are with this tool?

Examples may include:

  • Use operating system X, or video card Y
  • Ensure that the file specified with the -F option has more than 7 characters per row
  • Ensure that there are no more than Z quantity of lines in the file
  • Set a custom grid size with the -g option (what is this?)
  • How many work items per thread ( -w option)
  • What custom options should I use (-d option)

Need a random seed for vanitygen; where can I obtain one?

Vanitygen has the option for a file to contain random numbers as an alternative to the built-in random number generator.

What is the correct way to generate this file on Windows, OSX? (and Linux)

What is the range of each number (upper and lower bound)?

What is the correct format of the file (CRLF, LF only)?

How do you perform double-SHA-256 encoding?

The Bitcoin Protocol-specification gives an example of double-SHA-256 encoding.

hello
2cf24dba5fb0a30e26e83b2ac5b9e29e1b161e5c1fa7425e73043362938b9824 (first round of sha-256)
9595c9df90075148eb06860365df33584b75bff782a510c6cd4883a419833d50 (second round of sha-256)

I’ve tried various SHA256 calculators and the first encoding matches no problem, but the second always resolves to

d7914fe546b684688bb95f4f888a92dfc680603a75f23eb823658031fff766d9

I’ve also tried UPPERCASE and swapping the byte endianness.

How can I combine all the tiny amounts I’ve received to minimise transaction fees, and do I need to?

Important parts in bold, for those who don’t want to read the detail!

I’ve received lots of tiny transactions, in amounts sometimes as low as 0.000003BTC.
Even though I’ve also received (relatively) larger amounts, I’m worried that when I want to spend my bitcoins the transaction fees may be very high thanks to the large number of “input” transactions needed to make up the output transaction.

As I understand it, the network has an algorithm for determining minimum transaction fees, and the relationship between number of inputs and required transaction fee is non-linear. This means there is likely some optimum way to combine my inputs. This has already been discussed here and here, but neither question asks how it can be done, and how bad the consequences can be.

It might be best to somehow include as many tiny inputs with a larger input each time I spend a moderate amount, or perhaps it would be better to somehow combine all the tiny inputs in individual batches of some optimum size and send them to myself to prevent future problems.

If I were to combine the tiny amounts, I’d be happy to wait for the newly combined bitcoins to age, so additional fees which would be required by spending young bitcoins won’t be a problem.

In most, but not all, cases, my tiny amounts have been received to a dedicated tony-amount address.

For the sake of the question, let’s assume I’ve received 1000 tiny transactions of 0.001BTC each, and another 100 transactions of 0.1BTC each, all in the same wallet. This would give a total balance of 11BTC. Assume all amounts were received 6 months ago.

If I wanted to spend the entire 11BTC at once (with 1100 transaction inputs), how high might the fee be?

If I only spent 1BTC at a time, how high might the fee be?

How can I actually combine the tiny amounts without affecting the larger ones?

I’m running the standard (Satoshi) client, but other clients could be an option.