@overcast-xyz/evm-contracts 0.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +201 -0
- package/README.md +162 -0
- package/dist/cjs/generated/abis.d.ts +8064 -0
- package/dist/cjs/generated/abis.d.ts.map +1 -0
- package/dist/cjs/generated/abis.js +4108 -0
- package/dist/cjs/generated/abis.js.map +1 -0
- package/dist/cjs/generated/enums.d.ts +42 -0
- package/dist/cjs/generated/enums.d.ts.map +1 -0
- package/dist/cjs/generated/enums.js +44 -0
- package/dist/cjs/generated/enums.js.map +1 -0
- package/dist/cjs/generated/structs.d.ts +392 -0
- package/dist/cjs/generated/structs.d.ts.map +1 -0
- package/dist/cjs/generated/structs.js +419 -0
- package/dist/cjs/generated/structs.js.map +1 -0
- package/dist/cjs/index.d.ts +4 -0
- package/dist/cjs/index.d.ts.map +1 -0
- package/dist/cjs/index.js +26 -0
- package/dist/cjs/index.js.map +1 -0
- package/dist/cjs/package.json +3 -0
- package/dist/esm/generated/abis.d.ts +8064 -0
- package/dist/esm/generated/abis.d.ts.map +1 -0
- package/dist/esm/generated/abis.js +4105 -0
- package/dist/esm/generated/abis.js.map +1 -0
- package/dist/esm/generated/enums.d.ts +42 -0
- package/dist/esm/generated/enums.d.ts.map +1 -0
- package/dist/esm/generated/enums.js +41 -0
- package/dist/esm/generated/enums.js.map +1 -0
- package/dist/esm/generated/structs.d.ts +392 -0
- package/dist/esm/generated/structs.d.ts.map +1 -0
- package/dist/esm/generated/structs.js +416 -0
- package/dist/esm/generated/structs.js.map +1 -0
- package/dist/esm/index.d.ts +4 -0
- package/dist/esm/index.d.ts.map +1 -0
- package/dist/esm/index.js +10 -0
- package/dist/esm/index.js.map +1 -0
- package/package.json +52 -0
package/LICENSE
ADDED
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright [yyyy] [name of copyright owner]
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
package/README.md
ADDED
|
@@ -0,0 +1,162 @@
|
|
|
1
|
+
# @overcast-xyz/evm-contracts
|
|
2
|
+
|
|
3
|
+
TypeScript ABIs and types for the Overcast protocol contracts.
|
|
4
|
+
|
|
5
|
+
The package has **no runtime dependencies**. The ABIs are `as const` arrays that
|
|
6
|
+
viem and abitype infer from directly, and the struct types are fully expanded, so
|
|
7
|
+
nothing is imported into a consumer's dependency tree.
|
|
8
|
+
|
|
9
|
+
## Usage
|
|
10
|
+
|
|
11
|
+
```ts
|
|
12
|
+
import { createPublicClient, http } from "viem";
|
|
13
|
+
import { coreAbi, OptionSide, type Offer } from "@overcast-xyz/evm-contracts";
|
|
14
|
+
|
|
15
|
+
const client = createPublicClient({ transport: http() });
|
|
16
|
+
|
|
17
|
+
// Return type is inferred from the ABI — no generics, no casts.
|
|
18
|
+
const option = await client.readContract({
|
|
19
|
+
address: "0x…",
|
|
20
|
+
abi: coreAbi,
|
|
21
|
+
functionName: "getOption",
|
|
22
|
+
args: ["0x…"],
|
|
23
|
+
});
|
|
24
|
+
|
|
25
|
+
const offer: Offer = {
|
|
26
|
+
salt: "0x…",
|
|
27
|
+
creator: "0x…",
|
|
28
|
+
optionDetails: { /* … */ },
|
|
29
|
+
expiry: 0n,
|
|
30
|
+
side: OptionSide.Maker,
|
|
31
|
+
counterparty: "0x…",
|
|
32
|
+
};
|
|
33
|
+
```
|
|
34
|
+
|
|
35
|
+
`coreAbi` is the composed `Core` contract, so it carries the full surface of
|
|
36
|
+
every module under `src/core/` — functions, events, and all protocol errors, which
|
|
37
|
+
means `decodeErrorResult` against it resolves any revert the protocol can produce.
|
|
38
|
+
The extension points are exported too: `iSettlementLayerAbi`,
|
|
39
|
+
`iOptionCreationHookAbi`, `physicalSettlementAbi`,
|
|
40
|
+
`physicalSettlementFactoryAbi`, `chainlinkSettlementAbi`.
|
|
41
|
+
|
|
42
|
+
Each struct also ships its ABI fragment — `offerParameter`,
|
|
43
|
+
`optionDetailsParameter`, … — for use with `encodeAbiParameters`, which is handy
|
|
44
|
+
when reproducing the content-addressed offer and option ids that
|
|
45
|
+
`libraries/Serialization.sol` computes on-chain.
|
|
46
|
+
|
|
47
|
+
## Addresses
|
|
48
|
+
|
|
49
|
+
Deployed addresses come from the `deployments.toml` that `script/Deploy.s.sol`
|
|
50
|
+
writes, fed to the wagmi foundry plugin's `deployments` option. Each chain with a
|
|
51
|
+
committed table contributes an entry:
|
|
52
|
+
|
|
53
|
+
```ts
|
|
54
|
+
import { coreConfig, physicalSettlementFactoryAddress } from "@overcast-xyz/evm-contracts";
|
|
55
|
+
|
|
56
|
+
// coreConfig = { address: { 11155111: "0x…" }, abi: coreAbi }
|
|
57
|
+
const domain = await client.readContract({ ...coreConfig, functionName: "domain" });
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
`coreAddress` is the **proxy** — the address to call the protocol at. The
|
|
61
|
+
implementation behind it is not exported, because calling it directly does
|
|
62
|
+
nothing useful.
|
|
63
|
+
|
|
64
|
+
Chains appear as they are deployed and their table is committed, so on a
|
|
65
|
+
checkout with no deployments these exports simply do not exist yet.
|
|
66
|
+
|
|
67
|
+
`ChainlinkSettlementFactory` is exported the same way, for the chains whose
|
|
68
|
+
deployment table names one — a chain that has not been redeployed since it was
|
|
69
|
+
added simply does not appear.
|
|
70
|
+
|
|
71
|
+
Two things are deliberately not here:
|
|
72
|
+
|
|
73
|
+
- **Settlement layers themselves.** A chain holds one `PhysicalSettlement` per
|
|
74
|
+
`ExerciseMode` and one `ChainlinkSettlement` per configuration, while the
|
|
75
|
+
plugin's model is a single address per contract. Derive them from their
|
|
76
|
+
factory's `predictAddress(...)` — the factories exist to be that source of
|
|
77
|
+
truth.
|
|
78
|
+
|
|
79
|
+
Note that this is a call rather than a local derivation, and deliberately so:
|
|
80
|
+
the `CREATE2` salt is pure ABI encoding and can be computed off-chain, but the
|
|
81
|
+
init-code hash covers the layer's creation code, which this package does not
|
|
82
|
+
export. Doing so would only look cheaper — a copy compiled from a different
|
|
83
|
+
commit than the deployed factory derives a confidently wrong address, so the
|
|
84
|
+
only bytes that answer the question correctly are the ones the deployed
|
|
85
|
+
factory holds.
|
|
86
|
+
- **Local development.** An `anvil` deployment's addresses belong to a chain that
|
|
87
|
+
gets recreated on demand, so they cannot be published. Read the `[31337]` table
|
|
88
|
+
of `deployments.toml` directly, or pass the address in from config.
|
|
89
|
+
|
|
90
|
+
## Regenerating
|
|
91
|
+
|
|
92
|
+
Everything under `src/generated/` is derived from the Foundry artifacts and is
|
|
93
|
+
committed, so consumers and downstream CI never need Foundry installed.
|
|
94
|
+
|
|
95
|
+
```sh
|
|
96
|
+
pnpm generate # forge build → wagmi generate (ABIs) → generate-types.ts (structs, enums)
|
|
97
|
+
pnpm typecheck
|
|
98
|
+
pnpm build
|
|
99
|
+
```
|
|
100
|
+
|
|
101
|
+
`pnpm generate` must be re-run and its output committed whenever a change to the
|
|
102
|
+
Solidity alters an external signature, struct, or enum. CI regenerates and fails
|
|
103
|
+
on any difference, so a stale commit does not get far.
|
|
104
|
+
|
|
105
|
+
## Building
|
|
106
|
+
|
|
107
|
+
`pnpm build` emits the package twice — ESM to `dist/esm`, CommonJS to
|
|
108
|
+
`dist/cjs` — and the `exports` map routes `import` and `require` to the matching
|
|
109
|
+
half. Dual-publishing costs nothing here (the package is `as const` data and
|
|
110
|
+
types, with no runtime imports) and it is what lets the two kinds of consumer
|
|
111
|
+
coexist:
|
|
112
|
+
|
|
113
|
+
- **ESM / bundlers** take `dist/esm`, so `sideEffects: false` can drop the ABI
|
|
114
|
+
arrays a build never references. These are large, so that matters.
|
|
115
|
+
- **CommonJS** — every `@overcast-xyz/*` SDK package is `module: commonjs` —
|
|
116
|
+
takes `dist/cjs` through the `require` condition, and through the top-level
|
|
117
|
+
`main` / `types` for the older `node10` resolution those packages still use.
|
|
118
|
+
Without that half they cannot see this package at all.
|
|
119
|
+
|
|
120
|
+
Two details are load-bearing. `scripts/emit-cjs-marker.mjs` writes a nested
|
|
121
|
+
`dist/cjs/package.json` marking that directory `"type": "commonjs"`, since the
|
|
122
|
+
root manifest is `"type": "module"` and would otherwise have Node read the
|
|
123
|
+
CommonJS emit as ESM; tsc only picks the `.cjs` extension for `.cts` inputs, so
|
|
124
|
+
the marker is the way to say it. And `tsconfig.build.cjs.json` pairs `module:
|
|
125
|
+
CommonJS` with `moduleResolution: bundler` — TypeScript 7 removed `node10`, and
|
|
126
|
+
`bundler` is the only mode left that pairs with a CommonJS emit. Nothing under
|
|
127
|
+
`src/` imports a package, only its own `./generated/*.js` siblings, so the
|
|
128
|
+
resolution mode has nothing to decide.
|
|
129
|
+
|
|
130
|
+
## Layout
|
|
131
|
+
|
|
132
|
+
| Path | Generated by | Contents |
|
|
133
|
+
| ------------------------- | --------------------------- | ----------------------------------------------- |
|
|
134
|
+
| `src/generated/abis.ts` | `@wagmi/cli` foundry plugin | one `as const` ABI per exported contract, plus `*Address` / `*Config` for deployed chains |
|
|
135
|
+
| `src/generated/structs.ts`| `scripts/generate-types.ts` | ABI tuple parameters + expanded struct types |
|
|
136
|
+
| `src/generated/enums.ts` | `scripts/generate-types.ts` | const objects for each file-level Solidity enum |
|
|
137
|
+
| `test/generated.assert.ts`| `scripts/generate-types.ts` | compile-time check of the struct types |
|
|
138
|
+
|
|
139
|
+
`scripts/contracts.ts` is the single list of exported contracts, read by both
|
|
140
|
+
generators. `scripts/deployments.ts` is the single reader of `deployments.toml`,
|
|
141
|
+
used by `wagmi.config.ts` to supply addresses.
|
|
142
|
+
|
|
143
|
+
The wagmi CLI is used for ABIs only — the `react` and `actions` plugins are
|
|
144
|
+
deliberately not enabled, since the hooks they emit import from `wagmi/codegen`
|
|
145
|
+
and would make wagmi a runtime dependency of this package.
|
|
146
|
+
|
|
147
|
+
The plugin's `includeBroadcasts` option, which would lift addresses out of
|
|
148
|
+
`broadcast/` and remove `scripts/deployments.ts`, is off for two reasons that were
|
|
149
|
+
checked against this project's own broadcast logs. It attributes the *implementation*
|
|
150
|
+
to `Core`, since `Core` reaches the chain twice and the address consumers need
|
|
151
|
+
belongs to a transaction named `ERC1967Proxy`; and `run-latest.json` holds the
|
|
152
|
+
latest run rather than accumulated state, so a re-run that only reconciles
|
|
153
|
+
configuration overwrites it and every address disappears. A deployment record has
|
|
154
|
+
neither problem — it names the proxy, and it describes a chain's current state
|
|
155
|
+
rather than the last thing that happened to it.
|
|
156
|
+
|
|
157
|
+
The struct types are expanded rather than derived from abitype so that the
|
|
158
|
+
published `.d.ts` has no imports. That puts the Solidity-to-TypeScript width
|
|
159
|
+
mapping (`uint48` and below are `number`, wider is `bigint`) in
|
|
160
|
+
`scripts/generate-types.ts`, so `test/generated.assert.ts` checks it against what
|
|
161
|
+
abitype — and therefore viem — infers from the same ABI fragment. abitype is a
|
|
162
|
+
devDependency used only by that check.
|