Тёмный

10. PoW Recap, Other Fork Types 

MIT OpenCourseWare
Подписаться 5 млн
Просмотров 9 тыс.
50% 1

Опубликовано:

 

21 окт 2024

Поделиться:

Ссылка:

Скачать:

Готовим ссылку...

Добавить в:

Мой плейлист
Посмотреть позже
Комментарии : 13   
@potatopotatopotatotomato9035
@potatopotatopotatotomato9035 2 года назад
cryptodaddy loves a good forking is what i heard
@shymaaarafat1342
@shymaaarafat1342 3 года назад
1-Also the part about including the Merkle root of another block (evil forks, min40 I think) is similar to what Catena lecture7 said they might do sometimes to attach another Merkle Tree of TXs to this block by writing the Merkle root in the OP-Return part . 2- I wonder was the same about transaction replay attack applies to EIP-1559; ie some replay protection must have been applied otherwise people could use an old EIP to get an equivalent amount of ETH after EIP-1559?
@PedroOjeda
@PedroOjeda 3 года назад
Are some classes missing? Lecture 9 for example
@mitocw
@mitocw 3 года назад
Yes, some classes are missing. Lectures 9, 19, 20, and 21 are not available. Those were guest lecturers... most likely we were unable to get permission from them. See ocw.mit.edu/MAS-S62S18 for more info and materials.
@andso7068
@andso7068 2 года назад
@@mitocw That sucks... I enjoy the lectures and material, nonetheless.
@Torterra_ghahhyhiHd
@Torterra_ghahhyhiHd 2 года назад
@@mitocw why are not avaible? pls whould like to complete are there some problems?
@PaulFidika
@PaulFidika Год назад
@@mitocw Darn, I wish they were all on here. Thanks for answering though.
@shymaaarafat1342
@shymaaarafat1342 3 года назад
So it's the coordination of (like voting on) CHECKSEQUENCEVERIFY that happened thru the fork coordination protocol introduced in BIP-9 (min49:17 in here I think), not the implementation of the operation itself that was introduced in BIP-112 I think, why didn't you guys clarify it in lec8 comments instead of deleting my reply? (Or after deleting it if u must, I'll still be grateful for the free material u offer)
@JamesBlacklock
@JamesBlacklock 2 года назад
Could the "evil fork" be solved simply by upgrading nodes to reject all blocks that do not contain enough txs with respect to the size of the mempool? I've often thought this would be a good idea anyway. Prevents tx censorship. You could even penalize miners who are ignoring transactions that have been in the mempool a long time. Thoughts, anyone?
@MrCoreyTexas
@MrCoreyTexas Год назад
I've always thought 1 transaction blocks was weird too, but every block you add to the blockchain increases the security of the transactions, as it becomes harder to rewrite history. The problem with transaction censorship is, the mining pools create the blocks (deciding which transactions are or are not in the block), *not* the miners who use the pools. So theoretically you could find the top 3 mining pool owners which control over 50% of the hashpower and coerce them with a gun to their head. People will say, oh, but the miners will switch to another pool - maybe they will, maybe they won't, but in that case you could just put a gun to the heads of the top 10 mining pools, and now you have coerced 90% of the hashpower. I think they are trying to change this, to where individual miners can choose the transactions they put in a block, but inertia is making that hard. It doesn't seem like Bitcoin is enough of a threat to the powers that be yet for them to do this coercion scenario, and whatever else people (Bitcoin religious fanatics) tell you, I think that's a vulnerability in Bitcoin.
@战忽局保洁阿姨
@战忽局保洁阿姨 4 года назад
很棒的视频!
@SsuchiChen
@SsuchiChen 4 года назад
牛批!!!
@MK-rk4no
@MK-rk4no 2 года назад
Pow doesn't scale.