Appendix: Netrabrick Nodes

Mike Tango Bravo · Updated 2024-08-09

Appendix: Netrabrick
1. A decentralized node for blockchain, storage, IoT, web2, and local services.
2. Why the world needs the Netrabrick
  1. The centralized/ decentralized problem
  2. 80’s, 90’s, 2000’s
3. But what does this bring to OpenVino?
  1. No dependency on Infura for web3 and IPFS
    1. Cost savings
    2. NFT and BioDigitalCert storage
    3. Reduced MnM attack potential
  2. IoT anchor for wineries
    1. Proof-of-position
    2. LoRa gateway
  3. No dependency on web2 hosting
    1. Distributed availability
    2. Endless bandwith
    3. Optimized energy footprint
    4. Resilience on DDoS attacks
    5. On-prem anchor for OpenVino service providers
4. The challenge decentralized nodes present
  1. Availability
    1. Sugapi + PiKVM
    2. UPS
    3. Network
  2. Maintainability
    1. Managed by OpenVino
    2. 1:100 sysadmin Scalability
    3. Independent of winery networks
  3. Costs
    1. Hardware
    2. Networking
    3. Power
    4. Savings
      1. Hosting
      2. Pinning
      3. Web3 endpoints
    5. Inputs
      1. HOPR
      2. AI
      3. On-prem services
        
        Security cams
        
        ERP