zeekayandHanzo Dev a14d237d16 State a version once
A version written into a manifest is written into every manifest that wants it,
which is how eslint came to exist in a hundred and four forms across this estate
and how a package came to resolve twice at run time. The catalog moves the number
out of the manifest: a manifest names the package, the workspace names the
version.

Four are held below their latest because the newer release cannot be used, and
the reason is recorded rather than the version alone: @noble/hashes 2 renamed
every subpath the web3 stack imports, @splinetool/runtime 2 depends on a package
that was never published, @dynamic-labs 5.4.1 the same, and react-resizable-panels
3 points its types condition at the bundle.

Co-authored-by: Hanzo Dev <[email protected]>
2026-09-08 02:40:27 -07:00
2023-04-27 17:27:41 +02:00
2023-04-27 17:27:41 +02:00
2023-04-27 17:27:41 +02:00
2024-02-22 09:57:39 +01:00
2019-07-09 09:41:17 +02:00
2023-04-27 17:27:41 +02:00
πŸŽ‰ Initial commit
2019-07-08 16:27:15 +02:00
2023-04-27 17:27:41 +02:00
2026-09-08 02:40:27 -07:00
2023-06-29 10:32:47 +02:00
🚨(verifier) Lint
2023-07-04 11:28:12 +02:00
2024-02-22 09:57:39 +01:00
2023-04-27 17:27:41 +02:00
2023-07-04 17:27:29 +02:00
2023-07-04 17:27:29 +02:00
2020-03-02 22:42:09 +01:00
2023-04-27 17:27:41 +02:00
2026-09-08 02:40:27 -07:00
2023-04-27 17:27:41 +02:00

OnchainID Smart Contracts

Lux Fork

This is a Lux Industries fork of the canonical upstream:

  • Upstream: https://github.com/onchain-id/solidity
  • Pinned commit: 0e681fbf
  • Pinned tag: 2.2.2-beta3
  • License: GPL-3.0 (preserved from upstream β€” see LICENSE.md, provenance in SOURCE.md)
  • Lux extensions: NONE (verbatim parity with upstream).
  • Tag policy: track upstream semver verbatim. Divergence (if ever required) signaled by next-minor bump, NOT prerelease suffixes.

GitHub GitHub release (latest by date) GitHub Workflow Status (branch) GitHub repo size GitHub Release Date


OnchainID Smart Contracts

Smart Contracts for secure Blockchain Identities, implementation of the ERC734 and ERC735 proposal standards.

Learn more about OnchainID and Blockchain Identities on the official OnchainID website: https://onchainid.com.

Usage

  • Install contracts package to use in your repository yarn add @onchain-id/solidity
  • Require desired contracts in-code (should you need to deploy them):
    const { contracts: { ERC734, Identity } } = require('@onchain-id/solidity');
    
  • Require desired interfaces in-code (should you need to interact with deployed contracts):
    const { interfaces: { IERC734, IERC735 } } = require('@onchain-id/solidity');
    
  • Access contract ABI ERC734.abi and ByteCode ERC734.bytecode.

Development

  • Install dev dependencies npm ci
  • Update interfaces and contracts code.
  • Run lint npm run lint
  • Compile code npm run compile

Testing

  • Run npm ci
  • Run npm test
    • Test will be executed against a local Hardhat network.

S
Description
Smart Contracts for secure Blockchain Identities, implementation of the ERC734 and ERC735 proposal standards.
Readme
2.6 MiB
Languages
TypeScript 63.4%
Solidity 35.9%
JavaScript 0.7%