From: Dmitry Petukhov <dp@simplexum.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] Formal specification of Miniscript in Alloy
Date: Wed, 25 Nov 2020 12:15:55 +0100 [thread overview]
Message-ID: <20201125121555.49565b3c@simplexum.com> (raw)
I have created a formal specification of Miniscript [1] using
the specification language of Alloy analyzer [2]
Link: https://github.com/dgpv/miniscript-alloy-spec
Possible uses for the spec:
- Implementing Miniscript libraries, as additional reference that might
be easier to navigate than prose spec
- Generating test cases for implementations, although currently this
will be a manual process due to the tools limitation (can be overcome
with GUI automation)
- Checking the implementation against the spec, by writing a program
that would generate Alloy .als files from the data structures of the
implementation, and then checking these files in Alloy
- Extending or amending Miniscript, if the need arise. Having
extenstions and changes checked (with bounds) against a spec should
help catch inconsistencies
- Exploring the properties of Miniscript
If you have an interest in Miniscript, please consider looking at the
spec and share your ideas.
The spec may contain mistakes, as it was not yet checked against any
implementation, it was only checked for consistency using its own
predicates, with the scope of up to 8 nodes.
If you notice a mistake or inconsistency, please submit an issue on
github (or communicate this in other ways)
[1] http://bitcoin.sipa.be/miniscript/
[2] https://alloytools.org/
next reply other threads:[~2020-11-25 11:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 11:15 Dmitry Petukhov [this message]
2020-11-25 15:43 ` [bitcoin-dev] Formal specification of Miniscript in Alloy Clark Moody
2020-11-25 16:09 ` Dmitry Petukhov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201125121555.49565b3c@simplexum.com \
--to=dp@simplexum.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox