@inco/lightning 0.1.20 → 0.1.29
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/CHANGELOG.md +4 -0
- package/README.md +32 -0
- package/dumps/incoLightning_0_1_25__861473222.dump.json +1 -0
- package/dumps/incoLightning_0_1_25__861473222.env +15 -0
- package/dumps/incoLightning_0_1_26__18043964.dump.json +1 -0
- package/dumps/incoLightning_0_1_26__18043964.env +15 -0
- package/dumps/incoLightning_0_1_26__444235330.dump.json +1 -0
- package/dumps/incoLightning_0_1_26__444235330.env +15 -0
- package/dumps/incoLightning_0_1_27__125335042.dump.json +1 -0
- package/dumps/incoLightning_0_1_27__125335042.env +14 -0
- package/dumps/incoLightning_0_1_27__558243565.dump.json +1 -0
- package/dumps/incoLightning_0_1_27__558243565.env +14 -0
- package/dumps/incoLightning_0_1_29__183408998.dump.json +1 -0
- package/dumps/incoLightning_0_1_29__183408998.env +14 -0
- package/dumps/incoLightning_0_1_29__340846814.dump.json +1 -0
- package/dumps/incoLightning_0_1_29__340846814.env +14 -0
- package/manifest.yaml +258 -0
- package/package.json +5 -4
- package/src/Lib.sol +1 -1
- package/src/libs/incoLightning_0_1_25__861473222.sol +389 -0
- package/src/libs/incoLightning_0_1_26__18043964.sol +389 -0
- package/src/libs/incoLightning_0_1_26__444235330.sol +389 -0
- package/src/libs/incoLightning_0_1_27__125335042.sol +389 -0
- package/src/libs/incoLightning_0_1_27__558243565.sol +389 -0
- package/src/libs/incoLightning_0_1_29__183408998.sol +389 -0
- package/src/libs/incoLightning_0_1_29__340846814.sol +389 -0
- package/src/test/IncoTest.sol +2 -1
- package/src/version/IncoLightningConfig.sol +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,9 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.1.29
|
|
4
|
+
|
|
5
|
+
- Publish contracts with verification [#535](https://github.com/Inco-fhevm/inco-monorepo/pull/535)
|
|
6
|
+
|
|
3
7
|
## 0.1.20
|
|
4
8
|
|
|
5
9
|
- Bug fix in EIP712 signature verification in Advanced ACL. [#485](https://github.com/Inco-fhevm/inco-monorepo/pull/485)
|
package/README.md
CHANGED
|
@@ -67,3 +67,35 @@ With a nod to the future we provide the `make release` target which performs a s
|
|
|
67
67
|
- If updating a covalidator to an existing contract use `--no-clobber`
|
|
68
68
|
- If updating a covalidator to a new contract omit `--no-clobber`
|
|
69
69
|
3. Run `pulumi up`
|
|
70
|
+
|
|
71
|
+
## Manifest file
|
|
72
|
+
|
|
73
|
+
[`manifest.yaml`](./manifest.yaml) is a file that tracks Inco Lightning smart contract releases (versioned instances of the executor contract) and deployments (actual instances of the contract on particular chains). The release names correspond to the names of the [solidity libs](./src/libs) that are libraries that statically link to the correct executor for the corresponding release.
|
|
74
|
+
|
|
75
|
+
Release names have a one-to-one correspondence with on-chain addresses - the same unique release will have the same address across chains and will run the same major version of the protocol.
|
|
76
|
+
|
|
77
|
+
The release names have the following format:
|
|
78
|
+
|
|
79
|
+
```
|
|
80
|
+
incoLightning_<major>_<minor>_<patch>__<salt>
|
|
81
|
+
```
|
|
82
|
+
|
|
83
|
+
The salt is derived from the version and additional value called the `pepper`. The salt determines the on-chain address of the release, whence the pepper can be used to for releases of the same contract versions with separate state and addresses (e.g. for testing purposes).
|
|
84
|
+
|
|
85
|
+
## Deployment dumps
|
|
86
|
+
|
|
87
|
+
In [`dumps`](./dumps) you can find a sequence of pairs of files named with the following format:
|
|
88
|
+
|
|
89
|
+
```
|
|
90
|
+
<release_name>.dump.json
|
|
91
|
+
```
|
|
92
|
+
|
|
93
|
+
Contains an [Anvil](https://book.getfoundry.sh/anvil/) state dump that can be loaded with `anvil --load-state <state-dump-file>`, which you see used in our local node [`docker-compose`](../../docker-compose.yaml) setup.
|
|
94
|
+
|
|
95
|
+
```
|
|
96
|
+
<release_name>.env
|
|
97
|
+
```
|
|
98
|
+
|
|
99
|
+
Is a dump parameters file, it contains a set of private and public keys, configuration for a covalidator, utility addresss, and the executor address as it exists in the particular state dump.
|
|
100
|
+
|
|
101
|
+
Everything require to run a local covalidator (in docker or otherwise), to encrypt values and communicate with the executor contract of the dump, is included within this parameters file. The secrets are generated for each dump.
|