Transaction

j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMV<div class="post">So I'm writing a little tool that dissects the Bitcoin wallet.dat, mainly because I want to understand better exactly how Bitcoin works.<br/><br/>And I see that the outputs of transactions have a value (number of bitcoins) and a bunch of bytes that are run through the little Forth-like scripting language built in to bitcoin.&nbsp; E.g.:<br/>['TxOut: value: 100.00 Script: DUP HASH160 6fad...ab90 EQUALVERIFY CHECKSIG']<br/><br/>First: it make me a little nervous that bitcoin has a scripting language in it, even though it is a really simple scripting language (no loops, no pointers, nothing but math and crypto).&nbsp; It makes me nervous because it is more complicated, and complication is the enemy of security.&nbsp; It also makes it harder to create a second, compatible implementation.&nbsp; But I think I can get over that.<br/><br/>Looking at the code, new transactions are verified by pushing the signature an then public key on the interpreter's stack and then running the TxOut script (did I get that right?).<br/><br/>Could I write code to create transactions with any valid script in the TxOut?<br/>E.g. could I create a TxOut with a script of:&nbsp; &nbsp;OP_2DROP OP_TRUE<br/>... to create a coin that could be spent by anybody?<br/><br/>And is flexibility in the types of coins created the reason it is coded this way?<br/></div> text/html