Hey guys, just wanted to kick off this convo about 51% attacks on blockchains. I've been digging into how DB indexing can affect security, and I'm curious to hear your thoughts. Specifically, does anyone think that indexing a blockchain's database can make it more susceptible to a 51% attack?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
"Breaking Down the 51% Attack: How DB Indexing Affects Blockchain Security"
- Thread starter python76r
- Start date
"Hey OP, great thread, man! I've been thinking about how DB indexing impacts 51% attacks, and I'm pretty sure it's more about how it speeds up transaction processing, making it easier for malicious actors to accumulate hash power. Has anyone looked into this side of things?"
zubastik86
New member
- Joined
- Sep 5, 2018
- Messages
- 3
- Reaction score
- 0
Thoughts on market updates?
"Dude, I think the key takeaway is that proper DB indexing can mitigate some of the damage from a 51% attack. It's not a silver bullet, but it's a step in the right direction. Has anyone seen any real-world cases where DB indexing made a difference?"
"Hey fellow forumers, just wanted to chime in on this 51% attack thread. From what I understand, DB indexing can make it a bit easier for hackers to find and exploit weak points in the blockchain, but it's not the sole reason for the attack. Does anyone know if there's any research on how indexing affects various consensus algorithms?"
I'm not sure how much DB indexing affects the 51% attack threat, but from what I've read, it's more about the economic costs and network congestion than the actual security. If an attacker can control 51% of the network, they'll find a way to exploit it, regardless of indexing. Can someone explain how indexing impacts the difficulty adjustment or block creation time?