Thanks, and Yes, I watched all the videos about it, but I still don’t understand
What part of segwit is confusing to you? The basis is that the witness data or the unlocking script has been moved to a new data structure and is not part of the transaction hashing. The hash of the transaction is the transaction ID and by moving the witness data the attacker cannot change the txid anymore. 
Hi Ivan on Tech fam,
This part of the course isn’t working for me. Only videos #2 and #6 load, the other videos don’t, so I can’t watch them. I’ve tried different browsers, tried yesterday and again today but still have the same problem. The videos just won’t load. I don’t have any problems with any other sites or streaming videos elsewhere. Any ideas how I can watch these videos??
Thanks all.
I tried and all videos opened fine for me. Can you try again? If you still encounter the issue, please report it to [email protected]
I will try again @Alko89. I noticed that one of the videos did load after about 20 minutes. I will use the support email you’ve given. Thanks !
So Segwit was not clear until after the reading, the discussion questions and the implementation video. But now it completely makes since regarding how it was implemented as a soft fork!
1 Like
How Is Segwit a part of multi-signature account set ups?
What do you mean? Multisig has been part of Bitcoin script before Segwit. The only difference is that the script has been moved out of the block structure.
My courses are not updating showing that I have completed them. When I mark complete it simply goes back the the same course. I have to click the next course to continue.
I noticed my photo is no longer visible as well.
Wasn’t the signature added to the original bitcoin protocol at some point?
Looking forward to getting started on the programming languages. Great courses and great instructors.
2 Likes
Currently on lesson #3. Does this sound right?
- Changing signatures = changes the proof that the participating parties were involved in the transaction
- With the changed signature, the transaction will still happen because the nodes will verify that the right amount of money is being sent
- Changing signatures also changes the transaction ID, and Alice won’t be able to prove that she made the transaction
----- § From the other nodes’ perspective - this looks like a regular transaction ID generated by the transaction
----- § From Alice’s perspective - this was not the transaction ID of her transaction so she is not part of this transaction
----- From Bob’s perspective - I’ve altered the original signature, and will ask for the transaction again to make more money
If Alice performs the transaction again and she does not have enough input, the transaction will get canceled by the blockchain and Alice will discover that her previous transaction got tampered with.
Yes, if Alice doesn’t check her balance and only rely on the txid she would think the tx simply didn’t go through.
1 Like
Yeah i have a same problem. I basically watch videos and answer questions in laptop and in my phone KAJABI app i mark them completed. I didnt get any weekly points also for completing tasks.
How can they match the inputs with the signatures with Segwit if it wasn’t hash with it in the first place?
Its just not part of the tx hash, that doesn’t mean its not there. You can decode a raw tx where it will be part of the txinwitness field.
1 Like
Does anyone have clarification on whether SegWit was a hard or soft fork? Both arguments seem to be floating about online. I understand that it was proposed as a soft fork but can also see that it resulted in a hard fork, Bitcoin Cash. It doesn’t appear that the update made previous blocks invalid as block size didn’t change and the split to Bitcoin Cash was the result of choosing not to adopt the TX consensus protocol. Thoughts appreciated. Cheers.
Segwit was a soft fork because it didn’t really change the structure of the block, just how some transactions are interpreted. Both nodes will accept these txs as valid, but old nodes won’t be able to spend them.
1 Like
Hi @filip,
I think I’m stuck in understanding if SegWit is a fork. It is obviously no hard fork but it also doesn’t make any blocks invalid, so it’s no soft fork either? Does it make SegWit just an additional feature which is to use out of choice?
Or did I understand completely wrong?