To get the 0.1 BTC prize money, do the following:

1. Download the game client from Smartmonsters.org and read the "How to play" page.
   This is a blockchain game (game client == wallet).

2. Optional but recommended: send PM with a coin address to get 1000 coins
   (on a best efford basis).

3. Wait until block 2000, then make a new player character. Or several. But only one can win.
   ***Only characters created after block 2000 can win***

4. Optional but recommended: make a move every 2000 blocks. (about once per day, but it may vary)
   Winner is the richest player character on testnet block 26000.

5. type in Debug Window:
   

Code:

name_update Alice {\"msg_comment\":\"1BitcoinEaterAddressDontSendf59kuE\"}

   (replace "Alice" with your character name, and the eater address with your BTC address)


Additional rules:

1.) If block 26000 happens before 12:00GMT on Oct 16, then the competition continues 'til next full 1000 blocks after 12:00GMT on Oct 16.

2.) The winner must be alive and not a monster when the competition ends. If it has multiplied, coins of all its descendants count too (if they're alive and not a monster). Output of game client (column "voting coins" in stats_voting.html) is used to determine the winner.

3.) In case of a critical bug, the competition may be paused and then restarted.


I'll try to answer questions about the game here in this thread.

[Part 1: The Oracle (half finished and ready for testing, see below):]

This is about adding a new feature (embedded bet exchange) to a very old coin (Fairbrix).


Source:         https://github.com/wiggi/fairbrix-0.8-coincontrol
win32 binaries: https://mega.co.nz/#!6Q00TJ5Q!PhbhsRrlbJQbt0ZUuxikIXXoEw5MpCaydNVGcIsZRhA


Part 1: The Oracle (half finished and ready for testing, see below):

When it comes to settlement of bets, I think that ideas like "let nodes google automatically" are not that great.
Someone trustworthy is needed to decide the outcome, sign that data and put it in the blockchain
for the node's reading pleasure. The coin holders in their entirety are trustworthy because it's in their self interest.

- The oracle's answers is about the value of ticker symbols like 'BTCUSD', at specific points of time.
  Not about the exact value but always 1 out of 8 predefined answers like "">250", ">200 <=250" etc.
  The purpose is to settle bets, after all.

- Everyone with coins can vote for the oracle's answer (kinda Proof of Stake but no coin age required
  and votes are retractable until a final deadline)

- all data is stored in the blockchain encoded in regular transactions


Part 2: How to store orders for the prediction market (half finished):

- This is done *not* as contracts as described in bitcoin wiki but as balances held by addresses hard coded into the client.
  (i.e. a specific bet like ">75% probability that Bitcoin is worth more than 10000 Ripples on Dec 31, 2014" will have an address assigned to it)

- for a minimalist implementation:
 - quarterly expiration with one rollover month
 - up to 6 markets like the aforementioned BTCUSD
 - 5% minimum price tick
 - 7 order books per currency pair (because there are 8 possible oracle answers)
 - *2 for bid and ask
 - *2 for the rollover month
 these are 3192 addresses. (recycled after 1/2 year)

- Orders can be transmitted by sending coins to these addresses.
  Orders can be canceled by sending coins back to the originating address.
  Every node maintains all order books (and lists of matched and unmatched orders, per address) updated with every block.

- Now here comes the heretical part: the private keys of these addresses will be public.
  Nodes will scan every block before accepting it and reject blocks that try to send coins from special addresses unless
  - it's an unmatched order and coins go back to originating address.
  - it's a winning bet (after expiration) and coins go to originating address of the winner.
  the same way they already reject blocks for insufficient PoW, failed checkpoint tests or generally not following the rules.


Part 3-???, TODO list:

- Command line functions to build lists of unmatched orders and lists of matched orders
  and display the order books (custom time frame for testing)

- Implement cache system, all oracles's answers must be available immediately as they are
  needed to validate transactions and blocks

- Command line functions to trade (buy, sell, find active markets etc)

- Extend voting system to allow everyone (with coins) to list/delist ticker symbols for trading

- Implement custom "time in force" (encoded in least significant digits of satoshi amount) to
  automatically cancel orders, and auto sending of profits (after expiration).

- Allow the voting system to control essential features of the the coin itself


Notes:

- Trading will only work after supermajority of miners use a new - yet unreleased - client version.

- It's a soft fork, old client versions will remain functional.

- No partial fills. This is due to the nature of bitcoin transactions,
  so locked and crossed markets are possible (==arbitrage opportunities for everyone)


*** If you have coins, vote for the oracle's answer: ***

- Vanitygen is required: https://bitcointalk.org/index.php?topic=25804.0

- In Fairbrix debug window|console type: "svlistvotings"

Code:

"index" : 2
"maturity date" : "close of Oct 31, 2013"
"vanitygen command" : "vanitygen -X95 fa5nwd"

  make an address using the vanitygen command, import the private key of the address in a wallet,
  no rescan required ("importprivkey <fairbrixprivkey> <label> false") and restart client to see the new address

- Read voting instructions (i.e. "command for help: svlistpairs 2")

- Check historical prices (e.g. bitcoincharts.com, www.ltc-charts.com, bitcoinaverage.com)

- Backup wallet(s), then vote by sending coins to the new address (IMHO according to output of "svlistpairs 2"
  the amount sent should be xxxx.xxxxx733, or xxxx.xxxxx734 if using btc-e prices only)

- Type "svgetoracle 2" to see your vote included (after tx is included in a block)

- Keep the coins in the new address until 30 days after Oct 31, 2013 16.00 EST, 'svgetoracle' will show

Code:

"maturity" : "close of Oct 31, 2013"
"voting closed" : "the results are final"

Please try to "cheat" (like voting twice with the same coins) and report bugs

Many alt-coin/modded/patched clients are very interesting but less than fully trustworthy,
and VirtualBox has no good GPU support.

So, for solo mining the miner should run on the physical host machine and connect to the client
in the virtual machine, via "virtual box port forwarding".
Expert level manuals are easy to find, but is there a simple step-by-step howto for beginners?


Very short version would be like:

-Miner: connect to localhost 127.0.0.1 and to some unused port xxxx.

-VBox network settings (for this virtual machine): networking mode: NAT (default)
                                            port forwarding: host IP <empty>
                                                                    host port <the unused port xxxx>
                                                                    guest IP <empty>
                                                                    guest port <the actual rpc port>

-in config file for client in guest machine: rpcallowip=*

This should do it. Guest firewall (in its default state, tested on Linux mint and Win7) is mostly harmless.