Trust layer
Safety is a product requirement, not a blog badge
Home infrastructure is intimate. Anyone asking to place software on that infrastructure owes a plain account of consent, encryption, isolation, workload policy and kill switches. MetaEdge names those controls: opt-in, pause or disconnect without penalty, encrypted enterprise traffic, no access to personal files, public-web workloads only.
Naming controls is step one. Proof is step two. This site reports the design claims as claims, and gives readers a checklist that still works if the final software changes.
Checklist
Questions that should have written answers
If a vendor cannot answer these before install day, wait. Authority is patience with other people’s networks.
- Is participation explicitly opt-in, and can it be stopped immediately?
- Are workloads limited to lawful public-web use, with abuse monitoring?
- Is traffic encrypted in transit?
- Is the node isolated from files, credentials, cameras and local devices?
- Are rewards described as variable, with costs and ISP risks disclosed?
- Is there an age floor (18+) and a way to keep children off the node?
- Will independent security review be published?
| Stated control | What the deck provides | What you should still request |
|---|---|---|
| Opt-in / pause | Design principle | In-product screens and logs |
| Encryption | Company assertion | Protocol details |
| No file access | Isolation claim | Architecture diagram / audit |
| Public-web only | Positioning | Acceptable-use policy |
Parents & beginners
Default to no until the off switch is obvious
Beginners and parents should not start with earnings calculators. Start with who can turn the software off, what happens on a guest Wi-Fi, and whether a teenager’s laptop is an appropriate node. Curiosity about unused bandwidth is healthy. Installing first and reading later is how trust gets burned across this whole category.
FAQ
Questions, answered
Can clients see my files?+
MetaEdge says no: requests go to the public web, and personal files, history and local storage stay isolated. The deck does not include an independent audit.
Is it safe for a family network?+
Only if every adult agrees, children are not the operators, and you can pause the node. A shared router is a shared risk surface.
What if my ISP forbids resale of connectivity?+
Then you should not participate until terms are clear. Residential sharing can conflict with some consumer contracts.
Related topics