From: Clark Moody <clark@clarkmoody•com>
To: Dmitry Petukhov <dp@simplexum•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Formal specification of Miniscript in Alloy
Date: Wed, 25 Nov 2020 09:43:10 -0600 [thread overview]
Message-ID: <CAHGSxGvqAwWQS+R5x9zMYR0VjL598g2vL+erxFeoaseJvfpBfg@mail.gmail.com> (raw)
In-Reply-To: <20201125121555.49565b3c@simplexum.com>
[-- Attachment #1: Type: text/plain, Size: 1911 bytes --]
Thanks for this! I can't comment on the correctness of your implementation,
but I really appreciate the idea and effort.
By chance, did you come across any other spec definitions in alternate
formal grammars?
-Clark
On Wed, Nov 25, 2020 at 5:35 AM Dmitry Petukhov via bitcoin-dev <
bitcoin-dev@lists•linuxfoundation.org> wrote:
> 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/
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
[-- Attachment #2: Type: text/html, Size: 3244 bytes --]
next prev parent reply other threads:[~2020-11-25 15:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 11:15 Dmitry Petukhov
2020-11-25 15:43 ` Clark Moody [this message]
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=CAHGSxGvqAwWQS+R5x9zMYR0VjL598g2vL+erxFeoaseJvfpBfg@mail.gmail.com \
--to=clark@clarkmoody$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=dp@simplexum$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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