Timeline for How does Bitcoin Cash implement replay protection?
Current License: CC BY-SA 4.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S May 9, 2021 at 23:26 | history | suggested | greatwolf | CC BY-SA 4.0 |
Content of the links got moved. Updated to new url so it doesn't 404
|
| May 9, 2021 at 22:56 | review | Suggested edits | |||
| S May 9, 2021 at 23:26 | |||||
| Aug 2, 2017 at 16:18 | comment | added | Ava Chow♦ | It is mandatory in that any transaction that does not use the redefined sighashing algorithm will be considered invalid and rejected. All transactions must use that sighashing algorithm. | |
| Aug 2, 2017 at 13:44 | comment | added | Jus12 | @AndrewChow Just confirming "Mandatory" implies that the protocol will reject those or is it just a "recommendation"? Sometimes the two terms are mixed in specs. | |
| Aug 2, 2017 at 5:32 | comment | added | Ava Chow♦ | No, it is not opt out either. The replay protection with the sighash thing is mandatory. The 530,000 block wait is unrelated to this mandatory replay protection. That only applied to the opt in one with OP_RETURN | |
| Aug 2, 2017 at 5:31 | comment | added | knocte | Ok two more questions: by this logic, it's not opt-out either, right? And last but not least: does the 530,000 magic number still hold? AFAIU the first exclusive (or divergent, let's say) block of BitCash is 478,559 so do we have to wait to use this automatic replay protection? | |
| Aug 2, 2017 at 5:15 | comment | added | Ava Chow♦ | Yes, replay protection is not opt-in. Although they have still kept the OP_RETURN thing in for some reason. | |
| Aug 2, 2017 at 5:14 | comment | added | knocte | in other words, replay protection is not opt-in anymore, right? | |
| Aug 2, 2017 at 5:07 | comment | added | Ava Chow♦ | 1. Replay protection is mandatory now and will be enforced by BCC wallets and nodes. 2. BCC wallets have probably implemented all of this now since they have forked off of the Bitcoin network. At the time this was written, many BCC wallets were not complete nor was their spec complete. | |
| Aug 2, 2017 at 5:06 | comment | added | knocte | 2 questions: does the UPDATE portion of your answer mean that replay protection is not opt-in anymore? and second: you seem to be speaking in a very theoretical way (referencing to the spec), but do the implementations, as of now, respect this spec? | |
| Jul 25, 2017 at 18:21 | vote | accept | Murch♦ | ||
| Jul 25, 2017 at 17:45 | history | edited | Ava Chow♦ | CC BY-SA 3.0 |
added 315 characters in body
|
| Jul 22, 2017 at 16:38 | vote | accept | Murch♦ | ||
| Jul 25, 2017 at 17:32 | |||||
| Jul 20, 2017 at 2:28 | history | answered | Ava Chow♦ | CC BY-SA 3.0 |