@inco/lightning 0.1.20

package/CHANGELOG.md

@@ -0,0 +1,39 @@
+# Changelog
+
+## 0.1.20
+
+- Bug fix in EIP712 signature verification in Advanced ACL. [#485](https://github.com/Inco-fhevm/inco-monorepo/pull/485)
+
+Note: version 0.1.18 and 0.1.19 are unused, and were part of testing purposes only.
+
+## 0.1.17
+
+- Add deployment of `SessionVerifier` as part of the IncoLite deployment.
+
+## 0.1.16
+
+- Added missing arithemetic, bitwise, and random operations to IncoLib
+
+## 0.1.15
+
+- Same deployment as 0.1.13, but deployed across both Base Sepolia and Monad Testnet.
+
+## 0.1.14
+
+- **This deployment is a test deployment, and should not be used.** [#378](https://github.com/Inco-fhevm/inco-monorepo/pull/378) Test the new multi-chain deployments. No changes over 0.1.13.
+
+## 0.1.13
+
+"Advanced" access control first iteration, provides a way for accounts (EOAs / Smart Wallets / Contracts) to share their read access to handles with arbitrary logic using onchain or offchain signatures
+
+## 0.1.10
+
+- Update contract deployment logic to include ECIES public key and also to set the callback signer address on deployed contracts
+
+## 0.1.2
+
+Type embedding in handle after trivial encrypts and operations is consistent with zama
+
+## 0.1.1
+
+Embed type into every handle. Check handle type on every op.

package/README.md

@@ -0,0 +1,69 @@
+# Inco lite
+
+## Install dependencies
+
+`bun install`
+
+## Build
+
+Use [forge](https://book.getfoundry.sh/getting-started/installation) version 1.0 or higher
+
+`forge build`
+
+## Deploy
+
+### One-time key import
+
+1. Import key into Foundry cast wallet using [`make import_sepolia_deployer`](./Makefile)
+
+### Deploy new IncoLite contracts
+
+Targest for deploying the contracts are in the [Makefile](./Makefile). There are separate targtes for each chain and a target that deploys to all of them.
+
+The version of the contracts that will be deployed is defined by the current working directory and it will be deployed to an address that is deterministically calculated based on:
+
+- The contract name
+- The contract version
+- The deployer address
+- An optional deploy-time 'pepper'
+
+The contract name and version are constants in [IncoLightningConfig.sol](./src/version/IncoLightningConfig.sol) and the deployer address is the address of the wallet that is used to deploy the contracts. The optional deploy-time 'pepper' is a deployment-time string that can be chosen to alter the contract address for each deployment in the case where you what to differentiate a deployment from others.
+
+The point of the deterministic address is that holding the values above constant we can obtain a consistent canonical deployment address across all chains.
+
+#### Deployment process
+
+1. Bump IncoLite version in [IncoLightningConfig.sol](./src/version/IncoLightningConfig.sol)
+2. Run [`make deploy_multichain`](./Makefile) - this will update the manifest with the new release
+3. Run [`make deploy_test_contracts_multichain`](./Makefile)
+
+##### Providing a pepper
+
+If you want to provide a pepper then use `make deploy_multichain INCO_LITE_PEPPER=<pepper>` where `pepper` is the string you want to use. This will be used to calculate the contract address and will be included in the manifest.
+
+## Defining a release without explicit deployment
+
+The deployment machinery is currently in a halfway house whereby we capture releases at the same time as performing smart contract deployments locally. In the future we expect the contract deployment (and later upgrade) processes to be run by CI or a by a covalidator initialisation container. At that point rather than the manifest being an artefact of record it will be a declaration of intent. At the moment it serves both purposes, but will be refactored to remove the deployment log capture element.
+
+With a nod to the future we provide the `make release` target which performs a simulated deploy, updates the manifest with a dummy deployment, and declares a release.
+
+## Deploy NPM modules
+
+1. Bump contracts NPM version in [package.json](./package.json)
+2. Bump JS NPM version in [package.json](../js/package.json)
+3. Publish contracts `npm publish:github`
+4. Build JS [`make build`](../js/Makefile) (depends on contract deployment being done first)
+5. Publish js `npm publish:github`
+
+## Build covalidator docker images
+
+1. PR to main
+2. Manually grab hash from dockerhub which is also `git describe --tags --always --dirty`
+
+## Update denver multi-chain testnet
+
+1. Copy docker tag into [Pulumi.multichain.yaml](../../infraco/pkg/denver/Pulumi.multichain.yaml)
+2. Consider whether to cobber `requestConter.txt` and `lastBlock.txt` depending on the type of update:
+   - If updating a covalidator to an existing contract use `--no-clobber`
+   - If updating a covalidator to a new contract omit `--no-clobber`
+3. Run `pulumi up`