The "make money" idea might have seemed a "spoof" back in the days before BiTCoin came along, but once bitcoin came along wow it became totally true, minting money.
Do you know what the "make" command is? The idea was to use that "make" command.
So it would build/compile the file named money, whose dependencies would include bitcoind, (the bitcoin daemon), so it would build/compile bitcoind and run it...
But wait, go deeper.... it would actually build/compile ("make") wallet.dat, whose dependencies would include bitcoind, so it would first "make" bitcoind...
But to "make" wallet.dat it needs to not only make bitcoind but also run it, since it is running it that makes the wallet.dat file.
But wait, deeper still... we need actually mining the coins to be part of it, so lets put a miner program in there too as a dependency, so it builds the coin and a miner for it and runs the miner...
"make" is based on making (building/compiling) files, checking they are at least as new as all their dependencies; so if wallet.dat is older than any of the things it depends on, it will need to run the miner until the wallet is newer than the other files...
...But transactions other than mining can touch the wallet, so maybe go a little deeper still, something to actually check whether the last change to the wallet is incoming...
...Or maybe even write a "balance" file and a "previous balance" file and if the balance is not higher than the previous balance make a "needmoremoney" file so that "needmoremoney" will be newer than current or previous balance, thus leading to having to run the miner again...
...But the miner won't be the only way of "make"ing money, so maybe a random or biased-random pick of ways to "make" the "gotenoughmoney" file be newer than the "needmoremoney" file...
So a "case" loop...
In the "case" that the dice roll X, "make" didmethodX;
In the "case" that the dice roll Y, "make" didmethodY;
etcetera etcetera etcetera, as "the king" might say to "I"...
-MarkM-