2. Contributor Device Usage Guide

2.1 Introduction

MetaEdge supports multiple device access methods (official):

Access MethodSupported PlatformsPrerequisite
Terminal CLI (meta-edge)Windows / macOS / LinuxStable network connection
Browser ExtensionChrome / EdgeBrowser installed
Developer SDKApps & devicesEmbed the SDK

Official note: Providers join with one click through a browser extension, while developers can embed the SDK into apps and devices.

Security & Privacy:

  • End-to-end TLS 1.3 encryption
  • Isolated sandbox execution environment
  • Full autonomy over what is shared
  • Zero file access — never touches your photos, passwords, or browsing history
  • Only uses idle capacity you explicitly choose to share

The official site further summarizes this as "Privacy-first by architecture" with four principles:

PrincipleDescription
Opt-in & user-controlledProviders decide what to share, when and how much
Encrypted trafficAll connections are end-to-end encrypted in transit
No access to personal filesSandboxed execution. Zero access to user data
Transparent usageReal-time dashboards for both providers and customers

For Individuals (official Turn your home devices into edge capacity):

  • One-click browser extension, or embed the SDK as a developer
  • Convert idle devices into ongoing rewards, sharing only the resources you choose
  • Opt-in, user-controlled, and transparent
  • Automatic digital-asset rewards

2.2 Quick Start

Choose either deployment path:

Document Source: This document is compiled from the MetaEdge official website (https://metaedge.xyz/), API documentation (https://edge-doc.vercel.app/), and CLI README. Content marked [TBD] is pending further information or confirmation from the MetaEdge team. Introductory copy and data follow the current official website.