0x1
  • About
  • Mobile Security
    • Android Security
    • Android Security Findings
    • IOS App Sec Pentest
    • IOS App Sec Best Practices
    • Tools
  • Web App Security
    • Q&A
    • Tools
  • Security Reports
    • Web Apps
    • Mobile Apps
  • Library
    • Links
    • Soft-Link
  • SmartContract
    • Tools
    • Saving gas
    • Security Research
    • Smart Contract Audit
    • Other findings
    • Writing a safe smart contract
  • NEO Smart Contract
    • DoS Vulnerability
    • NEP-5 Tokens
  • Buffer Overflow
    • BOF-01 (Basic)
    • BOF-02 (Basic)
    • BOF-03 (Basic)
Powered by GitBook
On this page

Was this helpful?

  1. SmartContract

Other findings

PreviousSmart Contract AuditNextWriting a safe smart contract

Last updated 6 years ago

Was this helpful?

Nodes do not need to care about how many confirmations a block has. A confirmation is a term which is useful only to someone who accepts Ether as payments: if a transaction has 5 confirmations it typically means there are 5 blocks mined on top of the block which includes the transaction. 5 confirmations is quite much already, but it's up to the Ether receiver to decide what number of confirmations is enough to be "sure" that the transaction won't be reverted.

There actually is no such thing as "51% confirmations". The percentage 51% is only used when talked about different attack vectors against the EVM: you would need 51% of the network's hashing (computing) power to be able to attack the network with double-spend attacks.

Furthermore, mining is confirming. When a block is successfully mined it means the block is confirmed and added to the (thought-to-be) canonical chain. But yes, mining (confirming) a block means all the transactions within it are confirmed.

How does an Ethereum node understand that 51% confirmations have been obtained?