Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Molecular assembler
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
==Self-replication== "Molecular assemblers" have been confused with self-replicating machines. To produce a practical quantity of a desired product, the nanoscale size of a typical science fiction universal molecular assembler requires an extremely large number of such devices. However, a single such theoretical molecular assembler might be programmed to [[self replication|self-replicate]], constructing many copies of itself. This would allow an exponential rate of production. Then, after sufficient quantities of the molecular assemblers were available, they would then be re-programmed for production of the desired product. However, if self-replication of molecular assemblers were not restrained then it might lead to competition with naturally occurring organisms. This has been called [[ecophagy]] or the [[grey goo]] problem.<ref>{{cite web|url=http://www.crnano.org/BD-Goo.htm|title=Nanotechnology: Grey Goo is a Small Issue|access-date=2007-08-21|archive-url=https://web.archive.org/web/20140829204949/http://www.crnano.org/BD-Goo.htm|archive-date=2014-08-29|url-status=dead}}</ref> One method of building molecular assemblers is to mimic evolutionary processes employed by biological systems. Biological evolution proceeds by random variation combined with culling of the less-successful variants and reproduction of the more-successful variants. Production of complex molecular assemblers might be evolved from simpler systems since "A [[complex system]] that works is invariably found to have evolved from a simple system that worked. . . . A complex system designed from scratch never works and can not be patched up to make it work. You have to start over, beginning with a system that works."<ref name="JohGall">{{Cite book |last=Gall |first=John |url=https://archive.org/details/systemantics00john/page/80/ |title=Systemantics: How Systems Work and Especially How They Fail |publisher=Pocket Books |year=1978 |isbn=9780671819101 |edition=1st |location=New York |pages=80β81 |author-link=John Gall (author) |via=[[Archive.org]]}}</ref> However, most published safety guidelines include "recommendations against developing ... replicator designs which permit surviving mutation or undergoing evolution".<ref>{{cite web|url=http://www.foresight.org/guidelines/current.html|title=Foresight Guidelines on Molecular Nanotechnology}}</ref> Most assembler designs keep the "source code" external to the physical assembler. At each step of a manufacturing process, that step is read from an ordinary computer file and "broadcast" to all the assemblers. If any assembler gets out of range of that computer, or when the link between that computer and the assemblers is broken, or when that computer is unplugged, the assemblers stop replicating. Such a "broadcast architecture" is one of the safety features recommended by the "Foresight Guidelines on Molecular Nanotechnology", and a map of the 137-dimensional replicator design space<ref>{{cite web|url=http://www.MolecularAssembler.com/KSRM/5.1.9.htm|title=Kinematic Self-Replicating Machines}}</ref> recently published by Freitas and Merkle provides numerous practical methods by which replicators can be safely controlled by good design.
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)