zeekayandHanzo Dev
dd70418407
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]>
T-REX : Token for Regulated EXchanges
Lux Fork
This is a Lux Industries fork of the canonical upstream:
- Upstream: https://github.com/ERC-3643/ERC-3643
- Pinned commit:
b6c5fabf - Pinned tag:
4.1.3 - License: GPL-3.0 (preserved from upstream β see
LICENSE.md, provenance inSOURCE.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.
Overview
The T-REX (Token for Regulated EXchanges) protocol is a comprehensive suite of Solidity smart contracts, implementing the ERC-3643 standard and designed to enable the issuance, management, and transfer of security tokens in compliance with regulations. It ensures secure and compliant transactions for all parties involved in the token exchange.
Key Components
The T-REX protocol consists of several key components:
-
ONCHAINID: A smart contract deployed by a user to interact with the security token or any other application where an on-chain identity may be relevant. It stores keys and claims related to a specific identity.
-
Trusted Issuers Registry: This contract houses the addresses of all trusted claim issuers associated with a specific token.
-
Claim Topics Registry: This contract maintains a list of all trusted claim topics related to the security token.
-
Identity Registry: This contract holds the identity contract addresses of all eligible users authorized to hold the token. It is responsible for claim verification.
-
Compliance Smart Contract: This contract independently operates to check whether a transfer is in compliance with the established rules for the token.
-
Security Token Contract: This contract interacts with the Identity Registry to check the eligibility status of investors, enabling token holding and transactions.
Getting Started
- Clone the repository:
git clone https://github.com/ERC-3643/ERC-3643.git - Install dependencies:
npm ci - Compile the contracts:
hardhat compile - Run tests:
hardhat test
Documentation
For a detailed understanding of the T-REX protocol, please refer to the whitepaper. All functions of T-REX smart contracts are described in the T-REX documentation
Contributing
We welcome contributions from the community. Please refer to the CONTRIBUTING guide for more details.
License
This project is licensed under the GNU General Public License v3.0.
