2017 27th International Telecommunication Networks and Applications Conference (ITNAC) 2017
DOI: 10.1109/atnac.2017.8215367
|View full text |Cite
|
Sign up to set email alerts
|

Increased block size and Bitcoin blockchain dynamics

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
35
0

Year Published

2019
2019
2024
2024

Publication Types

Select...
6
3
1

Relationship

0
10

Authors

Journals

citations
Cited by 71 publications
(39 citation statements)
references
References 3 publications
0
35
0
Order By: Relevance
“…On the other hand, reducing difficulty will reduce the block time but it will increase the number of orphaned blocks in the system and the overall size of the Blockchain. At the time of writing this paper, Bitcoin and Ethereum Blockchain size was recorded to be 162 GB and 450 GB, respectively [146]. Saad et al [33] proposed fee-based and age-based countermeasures to prevent DDoS attack on Blockchain mempools.…”
Section: H Countering Peer-to-peer Attacksmentioning
confidence: 99%
“…On the other hand, reducing difficulty will reduce the block time but it will increase the number of orphaned blocks in the system and the overall size of the Blockchain. At the time of writing this paper, Bitcoin and Ethereum Blockchain size was recorded to be 162 GB and 450 GB, respectively [146]. Saad et al [33] proposed fee-based and age-based countermeasures to prevent DDoS attack on Blockchain mempools.…”
Section: H Countering Peer-to-peer Attacksmentioning
confidence: 99%
“…Another method is to reduce the size of the block, although the speed of the node synchronization data can be increased, but this will make the capacity that was not enough to be smaller. These two solutions are like fighting in the left and right hands [28].…”
Section: System Structurementioning
confidence: 99%
“…We removed eight DLT characteristics that did not comply with the relevance criteria, leading to a final set of 20 relevant DLT characteristics for the comparison process. For example, block creation interval was excluded because it is expressed in throughput and stale block rate [27], which can be directly mapped to application requirements.…”
Section: Scalabilitymentioning
confidence: 99%