22 Matching Annotations
  1. Mar 2021
  2. Dec 2020
  3. ieeexplore.ieee.org ieeexplore.ieee.org
    -
    18
    1. can be forced to broadcast the generated block

      Doesn't prevent DoS attacks of the network layer. How do you distinguish between "not finished yet" and network outage?

    2. Moreover, as obtaining 51% of the stake in PoS is much easier than obtaining 51% of the computing power in PoW

      Ethereum 2.0 people would probably strongly disagree with this. Collusion of mining pools is easy to imagine; obtaining 51% of ETH market cap is not!

    3. the TC enclave will contact the data source via HTTPS to obtain the requested data

      You just said "the enclave lacks direct network access"?! The paper shows it going through the relay (Figure 1). Guess that's what the 2nd half of the sentence means.

    4. The node that first completes the waiting process will obtain the right to create the new block and receive the reward

      Why is waiting needed? Why didn't they skip straight to PoLK below to take the lowest number?

    5. To relieve this problem, PoUW designs a statistical analysis scheme to test whether the mining time of the submitted blocks is different from the expected value.

      What is the "mining time"? How is the expected value obtained? Why can't this be spoofed?

    6. but it still faces several vulnerabilities, e.g., nothing at stake attack, long-range attack

      The cited paper lists mitigations and references older Ethereum papers, but is from 2018 so unclear whether recent Ethereum 2.0 research mitigates further.