summaryrefslogtreecommitdiff
path: root/bip-0300.mediawiki
AgeCommit message (Collapse)Author
2023-07-26bip-0300: Add some guesstimate weight adjustmentsLuke Dashjr
2023-07-26bip-0300: Ensure tx fee commitment itself has zero value so sidechain coins ↵Luke Dashjr
can't get burned
2023-07-26bip-0300: Forbid extraneous OP_DRIVECHAIN outputs in M5/M6Luke Dashjr
2023-07-26bip-0300: Define endianness of upvote vectorLuke Dashjr
2023-07-26bip-0300: Reorder upvote vector version numbers to leave 1/2 bytes as ↵Luke Dashjr
version 1,2 respectively
2023-07-26bip-0300: Fix upvote vector exampleLuke Dashjr
2023-07-26bip-0300: Add OP_DRIVECHAINLuke Dashjr
2023-07-13clearer, more failure details, + use OP_TRUEPaul Sztorc
2022-09-02make idential to bip301Paul Sztorc
2022-09-02header typoPaul Sztorc
2022-09-02Update Bip300Paul Sztorc
2022-09-02Update Bip300 for consistency with latest codePaul Sztorc
2022-06-19Update bip-0300.mediawiki54627384
I've assumed that all mentions of ACK value and ACK counter are synonymous and therefore have updated all instances of this within the BIP to be "ACK-counter". I've noticed that M4 shows the different terms on two different lines (Line 256 and Line 257), which has made me think that potentially these terms aren't synonymous. Updates made to align with term used through out the BIP: Line 213 - adding explicit mention of "ACK-counter" Line 229 - adding explicit mention of "ACK-counter" Line 257 - replaced "ACK-value" with "ACK-counter" Line 288 - replaced "ACK value" with "ACK-counter"
2021-11-17tweak formattingPaul Sztorc
2021-11-17small typoPaul Sztorc
2021-11-02Update BIP 300Paul Sztorc
BIPs 300/301 were 2 years old! I have updated, shortened, and clarified them.
2019-09-20BIP 300: Fix preambleLuke Dashjr
2019-09-20add number 300 and update READMEPaul Sztorc
generated by cgit v1.2.3 (git 2.26.2) at 2024-11-19 00:03:39 +0000