From ce0962eb70c7bdc03b81aaa308b9a4c7d594742c Mon Sep 17 00:00:00 2001 From: b0xxer Date: Mon, 22 Jan 2024 06:16:12 -0600 Subject: [PATCH] Update docs/liquid/liquid-part1.md --- docs/liquid/liquid-part1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/liquid/liquid-part1.md b/docs/liquid/liquid-part1.md index a99d61b..54f29d5 100644 --- a/docs/liquid/liquid-part1.md +++ b/docs/liquid/liquid-part1.md @@ -51,7 +51,7 @@ Liquid supports Asset Issuance. Any full-node can issue their own Assets (only r At its core, Liquid is basically "BTC plus special OPCODES less Mining". In order to support the Smart Contracts and Convenants seen above, Liquid reintroduces some safe but disabled opcodes, including string concatenation (CAT), substrings, integer shifts, and several bitwise operations ([see here for more](https://github.com/ElementsProject/elements/blob/master/doc/tapscript_opcodes.md?ref=blog.blockstream.com)). -Additional a new DETERMINISTICRANDOM operation which produces a random number within a range from a seed. Also included is CHECKSIGFROMSTACK (CSFS) operation which verifies a signature against a message on the stack, rather than the spending transaction itself. +Additionally a new DETERMINISTICRANDOM operation which produces a random number within a range from a seed. Also included is CHECKSIGFROMSTACK (CSFS) operation, which verifies a signature against a message on the stack, rather than the spending transaction itself. These new opcodes have several use cases, including convenant-style controls, double-spent protection bonds, lotteries, merkle tree constructions to allow 1-of-N multisig with huge N (thousands), and probabilistic payments.