※ 본 게시물의 목적, 취지, 이력에 대해선 맨 밑의 비고를 참조(Please go to the bottom to see the purpose, intention, and prior history of this typed reproduction of an original contribution by the MetaCurrency Project).
Foster Coherence and Follow Convergence
Rooted in these principles (‘Learn from Nature’ and ‘Make it open and peered’), some very interesting patterns started to emerge. We discovered there were connections that wanted to be made to complete the picture, and it turns out they're not so hard to build.
For example, we didn't set out to build a semantic system, but because our Ceptr needed self-describing protocols, and because we preserve coherence contexts for each receptor, it ends up being a fairly small step to build semantics in at the very base level. From doing so, we got a huge leap in the power of our system. We knew we were going to need to build some sort of generalized protocol parser to be able to work with self-describing protocols, and once we added semantics, it turned out to be pretty easy. We expanded the idea of regular expressions and built Semtrex(SEMantic Tree Regular EXpressions) which provide lexical and syntactic parsing at all layers of a protocol stack.
We have only begun to fathom the magnitude of possibilities for collective sense-making that adding semantics has enabled, and it was a fairly small technical cost for us to include. The trick was in discovering this connection wanting to happen, even though it wasn't a problem we had originally intended to solve.
We understand that patterns in technology adoption could warn us away from changing too many things too fast. There are numerous examples of social adoption of new things veering toward inferior technical solutions rather than embracing something less familiar. However, we began to see that putting certain things in place created a kind of elegant simplicity where a few significant changes at the outset, solved numerous other problems that we hadn't even start to focus on.
This kind of whole systems design is what has led us to the current design of Ceptr. We've had a chance to learn from numerous attempts (by ourselves and others) at assembling a solution. There are hundreds of projects trying to solve these problems. Typically, each one is trying to solve their part in relative isolation of the other parts, building their solution on a flawed underlying architecture. Assembling all these solutions together creates massive complexity and brittle interdepencies.
We're not claiming our team has more expertise than all the people working on these solutions, nor that we could accomplish the same work of all those projects are doing. Howevr, we have discovered that stepping back and altering some underlying assumptions about how to structure computing and protocols create an enormous convergence of the solutions which makes them all more readily achievable.
Some Domains that Ceptr Addresses:
DISTRIBUTED COMPUTING
- validation of data integrity (no matter who possesses it)
- byzantine fault tolerance
- decentralizing control of shared rules / activities / data / projects for groups
- embodied contracts / “code as law”
- power balances between groups and individuals
IDENTITY & TRUST
- open identity
- personal ownership (and control) of data
- domain name squatting / namespace competition
- authentication (of almost everything)
- decentralized social networking
- transparency and accountability
- trust networks and authority for certification
PROGRAMMING & DEVELOPMENT
- reusability of code and data
- modularization / separation of concerns
- coherence management
- signing of code and apps
- deprecation of outdated tools
- version management of updated tools
- language flexibility / independece
- native preservation of syntax / structure
- UI for non-tech programmers using flow visualization tools (future)
NETWORKING INFRASTRUCTURE
- P2P / mesh networking
- Workarounds to ensure net neutrality
- network resilience (no off switch)
- decentralized networking architecture (no central addressing / naming authority)
- privacy, surveillance, and sousveillace
- evolution and replacement of protocols
SCALABILITY FIDELITY
- privacy and encryption
- transportability of live systems
- redundancy / resilience / mirroring
- sharding / segmentation of large distributed systems
ENABLING NEW COMPUTING PLATFORMS
- Parallel processing
- Analog computing
- Interface with analog communication protocols?
BUILDING & SHARING MEANING
- semantic web / semantic computing
- open and customizable communication protocols
- common data structures and world models
- knowledge building and sharing
- collective sense making
- distributed autonomous corporations
BUILDING & SHARING VALUE
- decentralized currencies
- new economic infrastructure
- reputation currencies
- custom transactions
- infrastructure accounting
- mutual (& fractal) sovereignty
- DHT / distributed file sharing (like torrents)
Still to write / expand: 앞으로 더 작성하고 확장해야 할 부분들 (생략).
※ 여기까지가 제2절 “How Was Ceptr Designed?”
※ 다음에 살펴볼 제3절:
What Makes Ceptr Work?
( ... ... )
※ 비고: 메타커런시 프로젝트(MetaCurrency Project)의 개념과 역사에 대해 탐색해 가면서 아울러 현재와 미래에 걸쳐 동반 탐색자의 출현을 기대하는 공개적인 탐구용 게시물(A personal exploration to learn about something related to the ideas of the MetaCurrency Project and its history, having some hope to find some people interested esp. in Korea though).
- 추적 문서의 위치: The MetaCurrency Project(Ceptr) > Ceptr Revelation(자료 형태: 구글문서)
- 최초 탐색: '메타커런시 프로젝트'를 찾아서(1): '보이지 않는 대학 연맹'에 집결된 자료들
- 직전 탐색: 메타커런시 프로젝트를 찾아서 (4)
- 다음 탐색: 메타커런시 프로젝트를 찾아서 6, Ceptr Revelation 읽기