Based on the geekcode (
http://www.geekcode.com/geek.html) I think it's time to start a Bitcoin code.
I suggest the following format.
<BTC_Code> = <BTC_Start> <BTC_Code_List> <EOL>
<BTC_Start> = BTC:
<BTC_Code_List> = <BTC_Code> { <BTC_Code> }
<BTC_Code> = <BTC_Code_Tag> { <BTC_Code_Modifier> }
<BTC_Code_Tag> = <Letter> { <Character> }
<BTC_Code_Modifier> = {<Character>}
<Character> = <Letter> | <Number> | <Symbol>
In the case of commercial enterprises, I propose the following.
<Company_Tag> = <Company_Shorthand> { <Company_Alignment> }
<Company_Shorthand> = BFL | BTCFPGA | ZTEX | <Character> { Character }
<Company_Alignment> = <Company_Employee> | <Company_Fanboi> | <Company_Advocate> | <Company_Optimist> | <Company_Neutral> | <Company_Pessimist> | <Company_Opponent> | <Company_Hater> | <Company_Agitator>
<Company_Employee> = $
<Company_Fanboi> = <3
<Company_Advocate> = ++
<Company_Optimist> = +
<Company_Neutral> = <Empty>
<Company_Pessimist> = -
<Company_Opponent> = --
<Company_Hater> =
<Company_Agitator> = ●～*
A person can have multiple alignments. For example, I like the BFL FPGAs but am pessimistic or skeptical about upcoming products. I also like the modminers from BTCFPGA. My code would be BTC:BFL++-BTCFPGA++.
Inaba would possibly be BTC:BFL$ and Goat would be BTC:GLBSE●～* or BTC:GLBSE:(.
Now, this only gets interesting when there are a number of attribute values. I've kicked off one area out of scratching my own itch, but I leave this thread for suggestions. I will reserve the second post for updates but I will also leave a copy at
https://github.com/arttaylor/bitcoincode. Fork and issue pull requests as you like.
Let's get it started:
Butterfly Labs:
BFL$ = shill/employee
BFL<3 = fanboy
BFL++ = advocate
BFL+ = optimist
BFL = neutral
BFL- = pessimist
BFL-- = opponent
BFL:( = hater
BFL●～* = agitator
Miner:
MASIC = ASIC Miner
MFPGA = FPGA Miner
MGPU = GPU Miner
MCPU = CPU Miner
M3t = 3 THash/sec
M2g = 2 GHash/sec
Mm = 1 MHash/sec
Mk = 1 KHash/sec
(Examples: MASICt, MFPGA55g, MCPU12k, M100t)
