You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Add 'compiler' field to the blueprint.
This is a purely additive, and optional, change. So it shouldn't pose much problem to add (existing implementation that supports blueprints would keep working). Yet it documents a field that we've started using in Aiken and that has turned to be incredibly useful.
* Document few more projects in connection with blueprints.
@@ -65,13 +66,23 @@ Note that examples of specifications are given later in the document to keep the
65
66
66
67
The `preamble` fields stores meta-information about the contract such as version numbers or a short description. This field is mainly meant for humans as a mean to contextualize a specification.
67
68
68
-
| Fields | Description |
69
-
| --- | --- |
70
-
| title | A short and descriptive title of the application |
71
-
| ?description | A more elaborate description |
72
-
| ?version | A version number for the project. |
73
-
| ?plutusVersion | The Plutus version assumed for all validators |
74
-
| ?license | A license under which the specification and contract code is distributed |
69
+
| Fields | Description |
70
+
| --- | --- |
71
+
| title | A short and descriptive title of the application |
72
+
| ?description | A more elaborate description |
73
+
| ?version | A version number for the project. |
74
+
| ?compiler | Information about the compiler or framework used to produce the validator(s) |
75
+
| ?plutusVersion | The Plutus version assumed for all validators |
76
+
| ?license | A license under which the specification and contract code is distributed |
77
+
78
+
#### compiler
79
+
80
+
The `compiler` field is optional, but allows specifying metadata about the toolkit that produced the validator and blueprint.
81
+
82
+
| Fields | Description |
83
+
| --- | --- |
84
+
| name | The name of the compiler/framework/tool that generated the file. |
85
+
| ?version | An optional version number in any format. |
75
86
76
87
#### validators
77
88
@@ -405,6 +416,7 @@ Yet, whereas there's a notion of purpose on-chain that is tightly coupled to the
0 commit comments