Build fails: `RuleEngineBase.sol` imports `CMTAT/library/RuleEngineInterfaceId.sol` and `CMTAT/library/ERC1404ExtendInterfaceId.sol` but those files don't exist anywhere in any tag/branch (v3.0.0 audited release)

[fernandoverboonen-eng]

Bug: CMTAT/library/RuleEngineInterfaceId and CMTAT/library/ERC1404ExtendInterfaceId import paths do not resolve

Versions

• CMTA/CMTAT tag v3.0.0 (the audited release, Wake Arena M1/M2/M3)
• CMTA/RuleEngine tag v3.0.0-rc4
• OpenZeppelin contracts v4.9.x
• OpenZeppelin contracts-upgradeable v4.9.x

Reproduction

cd /tmp && mkdir cmt-repro && cd cmt-repro
git clone --depth=1 -b v3.0.0 https://github.com/CMTA/CMTAT.git
git clone --depth=1 -b v3.0.0-rc4 https://github.com/CMTA/RuleEngine.git
cd RuleEngine && forge build

Compiler output

Error: Source "CMTAT/library/ERC1404ExtendInterfaceId.sol" not found
Error: Source "CMTAT/library/RuleEngineInterfaceId.sol" not found
   --> RuleEngineBase.sol:8:
   --> RuleEngineBase.sol:9:

Root cause

The imports in RuleEngineBase.sol reference:

• CMTAT/library/ERC1404ExtendInterfaceId.sol (singular path, "ERC1404Extend" name)
• CMTAT/library/RuleEngineInterfaceId.sol (singular path, "RuleEngine" name)

But the actual files in RuleEngine/src/modules/library/ are:

• ERC1404InterfaceId.sol (no "Extend")
• RuleInterfaceId.sol (no "Engine")

Either the Base is stale or the library library has been renamed since. I verified this consistently across all tags and branches (main and dev are at identical commits, no rebrand history).

I am using your tag pinned releases to keep the audit lineage. Without this fix, no third party can build a working integration against the audited v3.0.0 release.

I would be grateful for either:

• A patched v3.0.x point release that fixes these imports, or
• An official reply with which version pairing IS known-good

My work-in-progress: I have a working SwissDLTComplianceRule that needs to plug into RuleEngineBase. With the import bug fixed, integration tests should be straightforward.

Thanks

[rya-sge]

Hello @fernandoverboonen-eng,

Thanks a lot for your interest and issue.

The two file sets are unrelated, not a rename. RuleEngineBase.sol imports both:

// from the CMTAT submodule (CMTAT/ is a remapping → lib/CMTAT/contracts/)
import {ERC1404ExtendInterfaceId} from "CMTAT/library/ERC1404ExtendInterfaceId.sol";
import {RuleEngineInterfaceId}    from "CMTAT/library/RuleEngineInterfaceId.sol";
// RuleEngine's own local libraries
import {ERC1404InterfaceId} from "./modules/library/ERC1404InterfaceId.sol";
import {RuleInterfaceId}    from "./modules/library/RuleInterfaceId.sol";

That's why you found no rebrand history: nothing was renamed.

Root cause — three things in the repro:

1. v3.0.0-rc4 pins lib/CMTAT to 580d4776 = CMTAT v3.3.0-rc1, not v3.0.0. CMTAT v3.0.0 has no contracts/library/ directory (it uses contracts/libraries/), so the path genuinely doesn't resolve there.
2. A sibling clone at /tmp/cmt-repro/CMTAT is never on the resolution path — the remapping points inside the RuleEngine checkout. --depth=1 also drops submodule pointers.
3. OZ 4.9.x won't work: the repo pins 5.6.1, as does CMTAT v3.3.0-rc1.

Working build:

git clone -b v3.0.0-rc4 https://github.com/CMTA/RuleEngine.git
cd RuleEngine
git submodule update --init --recursive   # or: forge install
cd lib/CMTAT && npm install && cd ../..
forge build                                # Compiler run successful

On audit lineage — the part that matters for your rule. Two separate questions:

• What RuleEngine compiles against: CMTAT v3.3.0-rc1 (and soon CMTAT v3.3.0-rc3), fixed by the pin.
• What tokens it works with: includes CMTAT v3.0.0.

The second is explicitly tested. lib/CMTATv3.0.0 (remapped CMTATv3.0.0=) exists so a real v3.0.0 token can be deployed and bound: test/utils/CMTATDeploymentV3.sol plus three suites (RuleEngine/RulesManagementModuleTest/CMTATIntegrationV3.t.sol, .../RuleEngineOperationRevertV3.t.sol, RuleWhitelist/CMTATIntegrationV3.t.sol) — 15 tests, all passing.

So build SwissDLTComplianceRule against rc4 with the pins above and bind the engine to the Wake-audited CMTAT v3.0.0 token. Compiling against v3.0.0 sources was never required for that, and never a supported configuration. CMTATDeploymentV3 is the helper to copy for your own integration tests.

Let me know if you need more details

[rya-sge]

Also just this part works fine on my side

git clone --depth=1 -b v3.0.0-rc4 https://github.com/CMTA/RuleEngine.git
cd RuleEngine && forge build