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)

Is my p2p server set up correctly? When will I see inbound connections on 8333?

I’ve had a Windows host up at 23.23.246.5 for both Bitcoin and Namecoin and I’d like to make sure its configured correctly.

So far when I run a netstat I see the services below and a few things bother me:

  • Why is Bitcoind listening on port 80?

  • Why are there no inbound connections to Bitcoin (Prod or Test) or Namecoin? When will I see them?

  • Is the target host 92.243.23.21:6667 running IRC? If so what is that for?

  • Are there any questionable connections here?


More Information:


Bitcoin Launch Parameters

  • bitcoind -debug -server -detachdb -printtodebugger -printtoconsole

bitcoin.conf:

#noirc=0
server=0
rpcuser=Ulysseys
rpcpassword=YourSuperGreatPasswordNumber_DO_NOT_USE_THIS_OR_YOU_WILL_GET_ROBBED
#rpctimeout=30
rpcallowip=x.x.x.x  <-- my trusted IP set
rpcallowip=x.x.x.x  <-- my trusted IP set #2
rpcallowip=x.x.x.x  <-- my trusted IP set #3
rpcport=8332
#rpcconnect=127.0.0.1
#rpcssl=1
#rpcsslciphers=TLSv1+HIGH:!SSLv2:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
#rpcsslcertificatechainfile=server.cert
#rpcsslprivatekeyfile=server.pem
#allowreceivebyip=1

Namecoin Launch Parameters

  • namecoind -debug -server -detachdb -printtodebugger -printtoconsole

bitcoin.conf

server=1
rpcuser=asdf
rpcpassword=asdf
#rpctimeout=30
#rpcport=8336
#rpcconnect=127.0.0.1
#rpcssl=1 

Bitcoin Testnet Launch Parameters

  • bitcoind -debug -server -detachdb -printtodebugger -printtoconsole -testnet -rpcport=18332

NOTE: No bitcoin.conf is present in C:\Users\me\AppData\Roaming\Bitcoin\testnet3 directory assuming it is using \.. parent directory

Output

C:\Users\Administrator>netstat   -a -n -b -s

  Proto  Local Address          Foreign Address        State           PID
  TCP    0.0.0.0:8332           0.0.0.0:0              LISTENING       2624
 [bitcoind.exe]
  TCP    0.0.0.0:8333           0.0.0.0:0              LISTENING       2624
 [bitcoind.exe]
  TCP    0.0.0.0:8334           0.0.0.0:0              LISTENING       2928
 [namecoind.exe]
  TCP    0.0.0.0:8336           0.0.0.0:0              LISTENING       2928
 [namecoind.exe]
  TCP    0.0.0.0:18332          0.0.0.0:0              LISTENING       2660
 [bitcoind.exe]
  TCP    0.0.0.0:18333          0.0.0.0:0              LISTENING       2660
 [bitcoind.exe]
  TCP    10.193.55.114:49163    92.243.23.21:6667      ESTABLISHED     2660
 [bitcoind.exe]
  TCP    10.193.55.114:49164    69.64.46.74:18333      ESTABLISHED     2660
 [bitcoind.exe]
  TCP    10.193.55.114:49167    96.241.176.56:18333    ESTABLISHED     2660
 [bitcoind.exe]
  TCP    10.193.55.114:49170    94.23.34.31:18333      ESTABLISHED     2660
 [bitcoind.exe]
  TCP    10.193.55.114:49181    97.107.137.243:8334    ESTABLISHED     2928
 [namecoind.exe]
  TCP    10.193.55.114:49182    46.254.14.136:8334     ESTABLISHED     2928
 [namecoind.exe]
  TCP    10.193.55.114:49183    176.36.33.121:8334     ESTABLISHED     2928
 [namecoind.exe]
  TCP    10.193.55.114:49186    12.23.127.175:8334     ESTABLISHED     2928
 [namecoind.exe]
  TCP    10.193.55.114:49193    176.31.128.16:8334     ESTABLISHED     2928
 [namecoind.exe]
  TCP    10.193.55.114:49194    96.127.133.36:8334     ESTABLISHED     2928
 [namecoind.exe]
  TCP    10.193.55.114:49220    54.243.38.85:18333     ESTABLISHED     2660
 [bitcoind.exe]
  TCP    10.193.55.114:49304    178.63.48.141:18333    ESTABLISHED     2660
 [bitcoind.exe]
  TCP    10.193.55.114:50504    193.107.204.81:6667    ESTABLISHED     2928
 [namecoind.exe]
  TCP    10.193.55.114:53098    173.208.219.162:18333  ESTABLISHED     2660
 [bitcoind.exe]
  TCP    10.193.55.114:53537    99.230.227.73:8333     ESTABLISHED     2624
 [bitcoind.exe]
  TCP    10.193.55.114:55713    94.236.165.24:8333     ESTABLISHED     2624
 [bitcoind.exe]
  TCP    10.193.55.114:55716    74.196.224.251:8333    ESTABLISHED     2624
 [bitcoind.exe]
  TCP    10.193.55.114:56470    195.182.5.221:8334     ESTABLISHED     2928
 [namecoind.exe]
  TCP    10.193.55.114:57000    96.60.218.202:8333     ESTABLISHED     2624
 [bitcoind.exe]
  TCP    10.193.55.114:57083    91.121.174.223:8334    ESTABLISHED     2928
 [namecoind.exe]
  TCP    10.193.55.114:59585    173.167.113.73:8333    ESTABLISHED     2624
 [bitcoind.exe]
  TCP    10.193.55.114:60574    77.232.139.69:8333     ESTABLISHED     2624
 [bitcoind.exe]
  TCP    10.193.55.114:63469    89.79.247.234:8333     ESTABLISHED     2624
 [bitcoind.exe]
  TCP    10.193.55.114:63916    92.241.227.145:8333    ESTABLISHED     2624
 [bitcoind.exe]
  TCP    [::]:8332              [::]:0                 LISTENING       2624
 [bitcoind.exe]
  TCP    [::]:8333              [::]:0                 LISTENING       2624
 [bitcoind.exe]
  TCP    [::]:18332             [::]:0                 LISTENING       2660
 [bitcoind.exe]
  TCP    [::]:18333             [::]:0                 LISTENING       2660
 [bitcoind.exe]

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.