MIME-Version: 1.0
References: <20201125121555.49565b3c@simplexum.com>
In-Reply-To: <20201125121555.49565b3c@simplexum.com>
From: Clark Moody <clark@clarkmoody.com>
Date: Wed, 25 Nov 2020 09:43:10 -0600
Message-ID: <CAHGSxGvqAwWQS+R5x9zMYR0VjL598g2vL+erxFeoaseJvfpBfg@mail.gmail.com>
To: Dmitry Petukhov <dp@simplexum.com>, 
 Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Content-Type: multipart/alternative; boundary="0000000000005e337e05b4f04a56"
Subject: Re: [bitcoin-dev] Formal specification of Miniscript in Alloy
Precedence: list

--0000000000005e337e05b4f04a56
Content-Type: text/plain; charset="UTF-8"

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
>

--0000000000005e337e05b4f04a56
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:tahoma,s=
ans-serif;font-size:small;color:#000000">Thanks for this! I can&#39;t comme=
nt on the correctness of your implementation, but I really appreciate the i=
dea and effort.<br></div><div class=3D"gmail_default" style=3D"font-family:=
tahoma,sans-serif;font-size:small;color:#000000"><br></div><div class=3D"gm=
ail_default" style=3D"font-family:tahoma,sans-serif;font-size:small;color:#=
000000">By chance, did you come across any other spec definitions in altern=
ate formal grammars?<br clear=3D"all"></div><div><div dir=3D"ltr" class=3D"=
gmail_signature" data-smartmail=3D"gmail_signature"><div><br></div><div><br=
></div><div>-Clark</div><div></div></div></div><br></div><br><div class=3D"=
gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Nov 25, 2020 at =
5:35 AM Dmitry Petukhov via bitcoin-dev &lt;<a href=3D"mailto:bitcoin-dev@l=
ists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>&gt; wro=
te:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I have creat=
ed a formal specification of Miniscript [1] using<br>
the specification language of Alloy analyzer [2]<br>
<br>
Link: <a href=3D"https://github.com/dgpv/miniscript-alloy-spec" rel=3D"nore=
ferrer" target=3D"_blank">https://github.com/dgpv/miniscript-alloy-spec</a>=
<br>
<br>
Possible uses for the spec:<br>
<br>
- Implementing Miniscript libraries, as additional reference that might<br>
=C2=A0 be easier to navigate than prose spec<br>
<br>
- Generating test cases for implementations, although currently this<br>
=C2=A0 will be a manual process due to the tools limitation (can be overcom=
e<br>
=C2=A0 with GUI automation)<br>
<br>
- Checking the implementation against the spec, by writing a program<br>
=C2=A0 that would generate Alloy .als files from the data structures of the=
<br>
=C2=A0 implementation, and then checking these files in Alloy<br>
<br>
- Extending or amending Miniscript, if the need arise. Having<br>
=C2=A0 extenstions and changes checked (with bounds) against a spec should<=
br>
=C2=A0 help catch inconsistencies<br>
<br>
- Exploring the properties of Miniscript<br>
<br>
If you have an interest in Miniscript, please consider looking at the<br>
spec and share your ideas.<br>
<br>
The spec may contain mistakes, as it was not yet checked against any<br>
implementation, it was only checked for consistency using its own<br>
predicates, with the scope of up to 8 nodes.<br>
<br>
If you notice a mistake or inconsistency, please submit an issue on<br>
github (or communicate this in other ways)<br>
<br>
[1] <a href=3D"http://bitcoin.sipa.be/miniscript/" rel=3D"noreferrer" targe=
t=3D"_blank">http://bitcoin.sipa.be/miniscript/</a><br>
[2] <a href=3D"https://alloytools.org/" rel=3D"noreferrer" target=3D"_blank=
">https://alloytools.org/</a><br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">=
bitcoin-dev@lists.linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</blockquote></div>

--0000000000005e337e05b4f04a56--