> For the complete documentation index, see [llms.txt](https://dataroom.tmines.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dataroom.tmines.com/technology-and-tm-protocol.md). # Technology & TM Protocol ### TM Protocol The TM Protocol is the application and contract layer that powers the T-MINES dApp: * **ERC-3643 (T-REX)** permissioned token contracts. * **ONCHAINID** identity layer (EIP-3643 on ERC-734/735). * Shared compliance registries — **Identity Registry, Modular Compliance, Trusted Issuers Registry, Claim Topics Registry**. * A **unified on-chain settlement contract**. It is distinct from the EVM substrate (consensus, finality, ledger, gas) and is chain-agnostic within EVM — redeployable across EVM L1/L2/permissioned chains. ### Permissioned, not trustless The T-MINES dApp is a **permissioned EVM dApp**, not a DeFi protocol. Mint, burn, and forced-transfer are restricted to authorized agent roles, and **every transfer is screened** by the Identity Registry and Modular Compliance before it can settle. ### One compliance rail for all instruments A single ONCHAINID identity layer and shared registries give the whole platform one KYC/whitelist and one Transfer Agent rail across every token contract. ### Mixed-standard settlement Fungible instruments use ERC-3643 (whole-unit transfer); uniquely graded stones use **ERC-3525** (semi-fungible, value-decrement against a tokenId), wrapped with the same identity and compliance modules. The unified settlement contract reconciles both atomically and presents a single settlement primitive to the matching engine and Transfer Agent. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://dataroom.tmines.com/technology-and-tm-protocol.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.