NID Skeleton Facets
NID (NexeraID) skeletons are similar to the basic skeletons, but differ in their user verification approach. Rather than relying solely on the eligibility interfaces, NID skeletons also integrate with ComPilot, an off-chain AML service that acts as the KYC layer. This enables more granular compliance, reinforcing the regulatory robustness of fractionalization campaigns.
Note
NID skeletons/subskeletons also delegate eligibility checks to their corresponding internal eligibility facet like their non-NID counterparts, while additionally integrating with Compilot
The basic configuration for both Campaign and Campaign with Buyback requires the following facets to be selected:
Campaign requires 3 skeleton Facets:
| Skeleton | Description |
|---|---|
CreateFractionsSkeletonNID | Provides functionality to create fractions. |
PurchaseSkeletonNID | Exposes functions that allow users to purchase fractions. There are two PurchaseSkeletonNID available that provide different functionality depending on the use case: PurchaseSkeletonGenesisIdsNID, PurchaseSkeletonNoDiscountNID. |
ReceiveSkeletonNID | Provides functionality to receive funds collected from a campaign. |
Campaign with buyback requires 5 skeleton Facets:
| Skeleton | Description |
|---|---|
CreateFractionsSkeletonNID | Provides functionality to create fractions. |
PurchaseSkeletonNID | Exposes functions that allow users to purchase fractions. There are two PurchaseSkeletonNID available that provide different functionality depending on the use case: PurchaseSkeletonGenesisIdsNID, PurchaseSkeletonNoDiscountNID. |
ReceiveSkeletonNID | Provides functionality to receive funds collected from a campaign. |
BuybackSkeletonNID | Enables the buyback functionality for users. |
ReceiveAfterBuybackSkeletonNID | Allows users to retrieve principal and interest after the buyback. |
Eligibility Verification
NID Skeletons inherit TxAuthDataVerifierFacet, developed by the ComPilot AML platform, for user verification. To interact with a platform using NID Skeletons, users must complete ComPilot’s KYC, which whitelists their address and generates call data for each interaction.
On-chain, users must include this call data - containing a ComPilot-generated signature and metadata like a block expiration number - when calling gated functions. The requireTxDataAuth modifier enforces this verification before the function logic is executed, deconstructs and validates the provided data, and only then allows execution of the core function logic (e.g., purchase()). This ensures each interaction is authorized in real time.
Note
Non-view functions in all NID skeletons have the requireTxDataAuth modifier, which acts as a gating mechanism for users interacting with any functionality of the platform.