📅 Original date posted:2020-11-25
📝 Original message:В Wed, 25 Nov 2020 09:43:10 -0600
Clark Moody <clark at clarkmoody.com> wrote:
> 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?
As far as I know, this is the first formal spec for Miniscript.
I also considered using the K framework [1] for the task (it would
also give the parser out of the box), but at the time it did not have
the reference documentation, only tutorials on their site. It seems that
they have published the new site, with more documentation.
I am satisfied with how Alloy spec turned out, though - in my opinion,
the node definitions in the spec are very readable.
[1] https://kframework.org/
> On Wed, Nov 25, 2020 at 5:35 AM Dmitry Petukhov via bitcoin-dev <
> bitcoin-dev at 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 at lists.linuxfoundation.org
> > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
> >
Dmitry Petukhov [ARCHIVE] /
npub10r…9afdw
2023-06-07 18:27:36
in reply to nevent1q…zu3c
Author Public Key
npub10r66s2stvnancx9axwnfc5a34asjkwkgmkq7ztm5hf30x7fa4szsv9afdwPublished at
2023-06-07 18:27:36Event JSON
{
"id": "571c5984ade22657a3d45e65a42f729ca9b15f59dba876349aff2142c83590a8",
"pubkey": "78f5a82a0b64fb3c18bd33a69c53b1af612b3ac8dd81e12f74ba62f3793dac05",
"created_at": 1686162456,
"kind": 1,
"tags": [
[
"e",
"f6dc5151542f60dfdc8979d1ba9258cb71ed6b7baf9821460942d5b791016b0f",
"",
"root"
],
[
"e",
"33ca6bd1cd30469d60b283e0aee6ee7b57bc1a91f1e077d56ec8768f4b0a4c30",
"",
"reply"
],
[
"p",
"98dea680e98226bf50f3205457779fbb9d796a4546ff0042d3fba59daafc3adc"
]
],
"content": "📅 Original date posted:2020-11-25\n📝 Original message:В Wed, 25 Nov 2020 09:43:10 -0600\nClark Moody \u003cclark at clarkmoody.com\u003e wrote:\n\n\u003e Thanks for this! I can't comment on the correctness of your\n\u003e implementation, but I really appreciate the idea and effort.\n\u003e \n\u003e By chance, did you come across any other spec definitions in alternate\n\u003e formal grammars?\n\nAs far as I know, this is the first formal spec for Miniscript.\n\nI also considered using the K framework [1] for the task (it would\nalso give the parser out of the box), but at the time it did not have\nthe reference documentation, only tutorials on their site. It seems that\nthey have published the new site, with more documentation.\n\nI am satisfied with how Alloy spec turned out, though - in my opinion,\nthe node definitions in the spec are very readable.\n\n[1] https://kframework.org/\n\n\n\u003e On Wed, Nov 25, 2020 at 5:35 AM Dmitry Petukhov via bitcoin-dev \u003c\n\u003e bitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e \n\u003e \u003e I have created a formal specification of Miniscript [1] using\n\u003e \u003e the specification language of Alloy analyzer [2]\n\u003e \u003e\n\u003e \u003e Link: https://github.com/dgpv/miniscript-alloy-spec\n\u003e \u003e\n\u003e \u003e Possible uses for the spec:\n\u003e \u003e\n\u003e \u003e - Implementing Miniscript libraries, as additional reference that\n\u003e \u003e might be easier to navigate than prose spec\n\u003e \u003e\n\u003e \u003e - Generating test cases for implementations, although currently this\n\u003e \u003e will be a manual process due to the tools limitation (can be\n\u003e \u003e overcome with GUI automation)\n\u003e \u003e\n\u003e \u003e - Checking the implementation against the spec, by writing a program\n\u003e \u003e that would generate Alloy .als files from the data structures of\n\u003e \u003e the implementation, and then checking these files in Alloy\n\u003e \u003e\n\u003e \u003e - Extending or amending Miniscript, if the need arise. Having\n\u003e \u003e extenstions and changes checked (with bounds) against a spec\n\u003e \u003e should help catch inconsistencies\n\u003e \u003e\n\u003e \u003e - Exploring the properties of Miniscript\n\u003e \u003e\n\u003e \u003e If you have an interest in Miniscript, please consider looking at\n\u003e \u003e the spec and share your ideas.\n\u003e \u003e\n\u003e \u003e The spec may contain mistakes, as it was not yet checked against any\n\u003e \u003e implementation, it was only checked for consistency using its own\n\u003e \u003e predicates, with the scope of up to 8 nodes.\n\u003e \u003e\n\u003e \u003e If you notice a mistake or inconsistency, please submit an issue on\n\u003e \u003e github (or communicate this in other ways)\n\u003e \u003e\n\u003e \u003e [1] http://bitcoin.sipa.be/miniscript/\n\u003e \u003e [2] https://alloytools.org/\n\u003e \u003e _______________________________________________\n\u003e \u003e bitcoin-dev mailing list\n\u003e \u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e \u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e \u003e",
"sig": "f336a50aabb85e780b87d2cf5c4421e267e0246bc3d232184916c717c8c147af25061a2444c481ddf00a398fcde6d6ea9008d6f61c173e0fc7bc48d861349f62"
}