Published here are the complete source texts of the Nexelorant Account contracts and CPP deals in Affaire, along with their related factories, messages, and constants. Every file is available to read in full.
Each file lists the SHA-256 of the published bytes, so you can check your own copy against the file on this page. The checksum alone does not confirm that the source matches the deployed contract. In case of discrepancy, what governs is the code and state of the specific contract on-chain; matching the source is verified separately.
Foundation
Nexelorant Account
Nexelorant Account is a programmable account with an owner address and its public key. The contract verifies the authorization it's built to require and sends commands to the linked jetton wallet. Its role is distinct from the CPP deal contract, which holds a specific deal's state and manages its settlement.
The group includes the account contract and its deployment factory, plus four files of messages and constants. These describe the messages it accepts, its authorization parameters, and its limits. A good place to start reading is the account implementation.
account.messages.tact
account.constants.tact
NexelorantAccountFactoryV1.tact
factory.messages.tact
factory.constants.tact
Affaire
CPP — the deal layer
Affaire is the martech execution layer in the Nexelorant ecosystem. The published set shows the current implementation of a CPP deal between an advertiser and a performer: a separate smart contract is deployed for it, with parameters set at creation. distributorAddress is Nexelorant's technical financial address for the fee portion the contract provides for, and not a third business party to the deal.
Deal parameters are set at deployment, and the permitted state transitions and settlements are defined by the contract's code. The published source lets you check that logic and the limits of every handler.
CPPDealV1.tact
cppdeal.messages.tact
cppdeal.constants.tact
CPPDealFactoryV1.tact
factory.messages.tact
factory.constants.tact
Checking this against your own copy?
If you find a discrepancy, tell us the file, the line, and the behavior you expected. If you're checking a deployed instance, add the contract address; if you're comparing files, add the checksums you got.