BCM¶

Architecture Components¶

• Block Chain Node
• SOHO Node (cheap wireless router, smartphones,...)
• Internet GW Node
• Client Node
• AP-client links
• Mesh links
• Tunnel links
• DAO Server (distributed)
  - Hosted by Etherium platform
  - May run in Ammbr HW

• Identity proving instance
• Digital Autonomous Organization (DAO): | > agreement on code or smart contract (Not on central authority) | > Voting on code changes
• Consensus based on PoET
• PoV used for
• 100 000 000 million round recursions takes 1ms vs 5secs
• sha(sha(sha(....)))
• 3 chip functions
  - PK functionality, Identity generation
  - PoET (consensus)
  - PoV (Identity Validation)

Questions
- who is challenging the randomly selected node?
- how is a node randomly selected?¶

Block Chain Consensus¶

• PoV

• Order of recursion depth
• Instance particularity
• Identity mapping/control

BMX7 / Semtor features¶

• Self signed identies
• Signed node Profiles

• Public key
• List of trusted nodes
• List of supported nodes
• Path metric function and parametrization
• Tunnel announcements

• Identity proven addresses (CGA)
• Trusted paths set (destination address driven)
• DH based shared key agreement (for links and tunnels)

Challenges¶

• QoS Reservation
• Path changes
• Clustering
• Transaction recording traffic
• Roaming
• Multi-path
• User-Data encryption

2-years objective¶

• 30k nodes mesh scalability
• Transaction support
• Multi-protocol, Multi-Architecture support from scratch
• Convergence performance (mobile/vehicle nodes)
• Roaming?
• IPV6! IPv4?

Long term objective¶

• Multi-path