Skip to content

Commit e5546b8

Browse files
Address latest harding feedback
1 parent 193ec1a commit e5546b8

File tree

1 file changed

+24
-30
lines changed

1 file changed

+24
-30
lines changed

_topics/en/simplicity.md

Lines changed: 24 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -9,32 +9,30 @@ categories:
99

1010
## Required. Use Markdown formatting. Only one paragraph. No links allowed.
1111
excerpt: >
12-
**Simplicity** is a work in progress low level programming language designed
13-
to offer greater flexibility and expressiveness than Bitcoin Script whilst
14-
allowing you to verify the safety, security and costs of your program. It
15-
offers native Merklized scripting, formal semantics and type checking.
16-
It is not Turing complete but it can verify the execution of Turing complete
17-
programs. Although Simplicity provides certain proofs of correctness,
18-
sufficient care will need to be applied in the writing of Simplicity programs
19-
to ensure they perform as intended. To use Simplicity directly on the
20-
Bitcoin blockchain requires a soft fork and any such proposal is unlikely to
21-
be formalized until at least 2022-23. Currently there is Simplicity support
22-
for test branches of Bitcoin and Elements and a collection of jets are in
23-
development.
12+
**Simplicity** is a work in progress low level programming language with
13+
greater flexibility and expressiveness than Bitcoin Script. It allows
14+
you to verify the safety, security and costs of a program. It also offers
15+
native merklized scripting, formal semantics and type checking. To use
16+
Simplicity on Bitcoin requires a soft fork and a proposal is unlikely to be
17+
formalized until at least 2022. Currently there is Simplicity support for
18+
test branches of Bitcoin and Elements.
2419
2520
## Optional. Use Markdown formatting. Multiple paragraphs. Links allowed.
2621
extended_summary: |
27-
Jets are pre-made building blocks that can be combined to construct
28-
Simplicity programs. They have efficient machine-code implementations for raw
29-
performance. At its core Simplicity consists of nine primitive operators
30-
called combinators where semantics are formally specified. However,
31-
implementing Bitcoin functionality at such a low level typically results in
32-
large, slow and expensive programs. So instead functionality like hash
33-
functions and signature verification are implemented in higher level languages
34-
like C which are then proved to be equivalent to the pure Simplicity programs.
35-
Assuming Simplicity is soft forked into Bitcoin with sufficient jets at some
36-
stage, proposed soft forks like [SIGHASH_ANYPREVOUT][topic SIGHASH_ANYPREVOUT]
37-
could be utilized on Bitcoin without needing a separate soft fork.
22+
Simplicity includes supports for Jets, pre-made building blocks that can be
23+
combined to construct Simplicity programs. They have efficient machine-code
24+
implementations for raw performance. At its core Simplicity consists of
25+
nine primitive operators called combinators where semantics are formally
26+
specified. However, implementing Bitcoin functionality at such a low level
27+
typically results in large, slow and expensive programs. So instead
28+
functionality like hash functions and signature verification are implemented
29+
in higher level languages like C which are then proved to be equivalent to
30+
the pure Simplicity programs. Assuming Simplicity is soft forked into Bitcoin
31+
with sufficient jets at some stage, proposed soft forks like
32+
[SIGHASH_ANYPREVOUT][topic sighash_noinput] could be utilized on Bitcoin
33+
without needing a separate soft fork. Although Simplicity provides certain
34+
proofs of correctness, care still needs to be applied in the design of any
35+
contract protocol.
3836
3937
## Optional. Produces a Markdown link with either "[title][]" or
4038
## "[title](link)"
@@ -45,23 +43,19 @@ primary_sources:
4543
## Optional. Each entry requires "title", "url", and "date". May also use "feature:
4644
## true" to bold entry
4745
optech_mentions:
48-
- title: OP_CHECKTEMPLATEVERIFY
49-
url: /en/newsletters/2019/12/04/#op-checktemplateverify-ctv
50-
date: 2019-12-04
51-
5246
- title: Question about Simplicity and static analysis
5347
url: /en/newsletters/2020/04/29/#how-is-simplicity-better-suited-for-static-analysis-compared-to-script
5448
date: 2020-04-29
5549

56-
- title: Simplicity - Next Generation Smart Contracting
50+
- title: Transcript on next generation smart contracting with Simplicity
5751
url: /en/newsletters/2020/05/06/#simplicity-next-generation-smart-contracting
5852
date: 2020-05-06
5953

60-
- title: Question about implementing Taproot with Simplicity
54+
- title: Question about implementing taproot with Simplicity
6155
url: /en/newsletters/2020/07/29/#could-we-skip-the-taproot-soft-fork-and-instead-use-simplicity-to-write-the-equivalent-of-taproot-scripts
6256
date: 2020-07-29
6357

64-
- title: BIP-Taproot
58+
- title: Transcript on implementing Simplicity as a taproot leaf version
6559
url: /en/newsletters/2020/08/05/#bip-taproot
6660
date: 2020-08-05
6761

0 commit comments

Comments
 (0)