BCM » Historial » Revisió 6
Revisió 5 (Anònim, 07-11-2017 21:02) → Revisió 6/8 (Anònim, 07-11-2017 22:18)
h1. BCM h2. 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) h2. Questions - who is challenging the randomly selected node? - how is a node randomly selected? - h2. Block Chain Consensus * PoV > * Order of recursion depth > * Instance particularity > * Identity mapping/control h2. 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) h2. Challenges * QoS Reservation * Path changes * Clustering * Transaction recording traffic * Roaming * Multi-path h2. * User-Data encryption h2. 2-years objective * 30k nodes mesh scalability * Transaction support * Multi-protocol, Multi-Architecture support from scratch * Convergence performance (mobile/vehicle nodes) * Roaming? * IPV6! IPv4? h2. Long term objective * Multi-path