Network verification processes

  1. Possession of a particular onion address (activity)
    • Method: actively online, ranking of a fraction (successes / tries)
    • replay-proxy attacks possible
  2. Possession of a public key (signed challenge)
    • Method: send challenge nounce, request it be signed, validate
    • Shor's Algorithm / RSA Factorization
    • Could swap to ECC, then it has its own ECDL
  3. Proof of Stake (ownership of a vote / issue / poll datum)
    • request proof that a transaction came from that node?
    • Could lead to favoritism
  4. Chain of Trust (you trust your introductory nodes more)
    • method: ranking out from a trusted node, halving, small fraction alloted to un-trusted nodes
    • leads to coordinated-synchronization (half sybil) attacks (bots all have same data)
  5. Sync Tests (they have what you need when you need it)
    • method: rank query-bounce of a node (successes / tries)
    • vulnerable to coordinated-syncrhonization (half sybil)
  6. Hash/Scrypt Tests (GPU/Memory based)
    • difficulty goals generated by the network (fudge factor)
  7. Limited resources (ownership of an IP address?)
    • impossible re: feasible to make new Tor nodes