{"id":1429,"date":"2020-01-20T00:00:00","date_gmt":"2020-01-20T08:00:00","guid":{"rendered":"https:\/\/www.opennode.com\/blog\/?page_id=1429"},"modified":"2020-01-17T11:25:39","modified_gmt":"2020-01-17T19:25:39","slug":"segwit","status":"publish","type":"page","link":"https:\/\/blog.opennode.com\/blog\/glossary\/segwit\/","title":{"rendered":"Segregated Witness (SegWit)"},"content":{"rendered":"Reading Time: <\/span> < 1<\/span> minute<\/span><\/span>\n

Segregated Witness (SegWit): <\/h1>\n\n\n\n

SegWit is a soft fork<\/a> blockchain improvement protocol update that increased the amount of transactions that can fit into a block<\/a> by as much as 300%. This is possible by \u201csegregating\u201d the witness signatures on each transaction from the rest of the transaction data within the block, and placing it outside the block. Witness signature data is required to validate the data, but not it is not integral to the transaction effects. <\/p>\n\n\n\n

Before SegWit, on-chain Bitcoin transaction speeds were limited to 4 transactions per second. After SegWit, on-chain transaction speeds increased to 7 – 11 transactions per second.SegWit also enables second-layer smart contract solutions like Lightning Network to exist, enabling transaction speeds which exceed 100,000+ transactions per second. <\/p>\n\n\n\n

Blocks have a finite data limit of 1MB. SegWit is a clever way of putting more transactions into that 1MB without raising the block limit, which would have resulted in a hard fork<\/a>.\u00a0<\/p>\n\n\n\n

Links<\/h2>\n\n\n\n