PLEASE SEE THE OVERVIEWS OF EACH OF THE IDEAS BELOW, BEFORE YOU VOTE! THANKS!
- Numsgil's idea: To make codules of the form "[xmutation_rate] ...protected BPs... [/xmutation_rate]"
-
2 (20%)
- Ericl's idea: To make a new instruction, of the form "number_of_lines_to_protect .protect store"
-
2 (20%)
- Bacillus' original idea: To make mutation immunity have a cost based on the amount of DNA protected and time
-
3 (30%)
- A hybrid algorithm, combining features of 1, 2, or 3 above, such as the MPPI instruction (see the DB3 topic, and please post your idea if it hasn't been mentioned before)
-
1 (10%)
- Bacillus' updated idea: To make mutation protection be implemented as metadata, like in idea 1, and have a cost associated with it too, like idea 3.
- 0 (0%)
- Ikke's DNA comparison idea: To have two or more copies of the DBot's genome, and if the DNA in one mutates, replace it with the DNA from one of it's copies. Check for mutations by comparing the DNA line-for-line.
- 0 (0%)
- Ikke's hash comparison idea: To have two or more copies of the DBot's genome, and if the DNA in one mutates, replace it with the DNA from one of it's copies. Check for mutations by comparing the Hash-values of the different genomes.
- 0 (0%)
- Something totally different (Please post your new idea)
-
2 (20%)
Total Members Voted: 8