Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Just a Spoonful of Ceptr

Presentation elements for MIT/KIT Webinar call scheduled on April 2nd 2015 (by Arthur Brock and Eric Harris-Braun, MetaCurrency Project)
by

Arthur Brock

on 7 October 2015

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Just a Spoonful of Ceptr

In Ceptr, Everything
is stored as Semantic Trees
Semtrex:
General Pattern Parser
Sem
antic
T
ree
R
egular
EX
pressions
H.O.P.E.
Marc took receptor and membrane based computing in some very cool directions
Self-Describing Protocol Stack
Compository
Q & A
http://Ceptr.org
http://MetaCurrency.org
http://github.com/zippy/ceptr
http://HigherOrderProgramming.com
http://artbrock.com/blog
Just a Spoonful of Ceptr
Arthur Brock
Eric Harris-Braun
Marc Clifton
MIT/KIT Webinar
April 2, 2015
For more information, visit http://www.Ceptr.org
Presented by:
Why Ceptr?
Roots in MetaCurrency Project -- we needed radically different infrastructure for our tools
Distributed & Decentralized
Interoperable & Resilient
Composable & Semantic
Way beyond block-chain, APIs or RDF !
Context
Breakthroughs
Composability
Receptivity
Agency
Some design breakthroughs gave us courage to tackle a major overhaul of computing stack.
Low-Level Rewrite
Today we'll look at Ceptr approach to:
Structure of Data
Organization of Processing
Communication Protocols
Code Sharing

Built in C for speed and portability
(browser demo: JavaScript rendering of sys internals)
Coherence
2. Receptors receive (and send) signals
3. Receptors are lightweight VMs
In sum, receptors
Higher Order Programing Environment
Ceptr Receptors
Composable units for
computing and communication
1. Receptors have membranes,
and are organized fractally
Big:
VMhost that all receptors on a machine run in
Small:
like a function call (what-is-my-location, filter-list, etc.)
And everything in between
Bound to external carrier(s)
upon instantiation
(like lock & key in hormones)
A Virtual Machine wed to a slice
of a data engine for persistence
Manage Coherence
Sync with their other instances (holographic storage & distributed byzantine fault tolerance)
Carrier
Signal
Protocol
In computing, we're always serializing then
"re-hydrating" data. Ceptr keeps meaning in the structure at the base level.
Data
Process
Cannot instantiate meaningless data
Data always carries its semantics, structure and context
VM uses RunTrees not bytecode - self-eating, reducing trees
A RunTree functions like a semantic stack, which already carries its "debug" info
/%<HTTP_REQUEST_PATH_SEGMENTS: HTTP_REQUEST_PATH_SEGMENTS, HTTP_REQUEST_PATH_FILE>
Semtrex Expression:
(rendered in ASCII format)
Match results
highlighted in red
Expectations
Similar to rules in Prolog, receptors contain series of Expectations in the following form:
on
<carrier>
expect
<semtrex_pattern>
do
<action>
Listeners are structured this same way (subscriptions)
Carrier
Signal
Protocol
3. Ability to install the protocol to “understand”
(process) a signal
CeptrNet
Imagine the Internet with a built-in github that's distributed like a bittorrent DHT.
Questions & Answers
More Resources
Ceptr
gets it's name from being built out of re
cept
o
r
s
Manage their membranes ( in / out / transforms )
Store their state (memory & persistent)
Transform their state (by running code)
Scape data (index collections, compute relationships)
Suitable for parallel processing
Expectations can be nested
May trigger a cascade of changes from other expectations
Basic Requirements:
1. Listen on a general carrier (Ceptr messages)
2. Identify protocol (and its semantics/ structure)
Ceptr protocols are pluggable / fully functional
ON
<carrier>
EXPECT
<semtrex_pattern>
DO
<action>
Defining a Pluggable Protocol
Address space for protocols/semantics/structures
Receptor packages are like sharable apps
Publish via triangulation...
Author + Reviewer sign to generate a CompositionID
Versions in sub-branches
Networking via back-end synchronization
DHT, sharded into hashed segments + selections
Learns physical network topology
CeptrNet is just another receptor
Spoonful
Just a
of
Ceptr
Full transcript