> For the complete documentation index, see [llms.txt](https://triple-plus-global.gitbook.io/tpt-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://triple-plus-global.gitbook.io/tpt-whitepaper/risk-framework/fraud-resistance.md).

# Fraud Resistance

The protocol guards against several fraud vectors, following patterns established by protocols like Goldfinch.

***

## Fraudulent Seller, Honest Investors

**Scenario:** A seller submits fake invoices for non-existent goods.

{% @mermaid/diagram content="flowchart LR
S\["Fraudulent<br/>Seller"] -->|"Fake invoice"| P\["Platform"]
P -->|"Funds"| S
I\["Honest<br/>Investors"] -->|"Capital"| P
P -->|"Nothing"| I" %}

### Guards

| Guard                    | Description                             |
| ------------------------ | --------------------------------------- |
| **Verification Process** | Documents cross-referenced with debtors |
| **Debtor Confirmation**  | Direct outreach to confirm obligation   |
| **Seller Staking**       | Sellers stake collateral against fraud  |
| **Legal Recourse**       | Off-chain agreements enable prosecution |
| **Reputation System**    | New sellers face stricter scrutiny      |

### Why It's Hard to Pull Off

{% stepper %}
{% step %}
Verifiers contact debtors directly.
{% endstep %}

{% step %}
Fake debtors are detectable.
{% endstep %}

{% step %}
Seller stake provides immediate loss.
{% endstep %}

{% step %}
Legal consequences for fraud.
{% endstep %}

{% step %}
Platform ban prevents repeat attempts.
{% endstep %}
{% endstepper %}

***

## Seller-Investor Collusion

**Scenario:** A seller colludes with investors to extract capital.

{% @mermaid/diagram content="flowchart LR
S\["Seller"] <-->|"Collusion"| I\["Fake<br/>Investors"]
S -->|"Fake invoice"| P\["Platform"]
I -->|"'Invest' "| P
P -->|"Funds"| S
S -->|"Split proceeds"| I" %}

### Guards

| Guard                   | Description                             |
| ----------------------- | --------------------------------------- |
| **KYC/KYB Separation**  | Verification that parties are unrelated |
| **Debtor Independence** | Debtors must be third parties           |
| **Pattern Detection**   | Monitoring for suspicious relationships |
| **Multiple Investors**  | Large assets require multiple funders   |

### Why It's Hard to Pull Off

{% stepper %}
{% step %}
KYC shows if parties are related.
{% endstep %}

{% step %}
Debtor must be real, independent company.
{% endstep %}

{% step %}
Unusual patterns trigger review.
{% endstep %}

{% step %}
Requires fooling multiple parties.
{% endstep %}
{% endstepper %}

***

## Verification Manipulation

**Scenario:** Verifiers approve invalid assets for bribes.

{% @mermaid/diagram content="flowchart LR
S\["Fraudulent<br/>Seller"] -->|"Bribe"| V\["Corrupt<br/>Verifier"]
V -->|"Approve"| P\["Platform"]
S -->|"Fake asset"| P
P -->|"Funds"| S" %}

### Guards

| Guard                  | Description                                    |
| ---------------------- | ---------------------------------------------- |
| **Verifier Staking**   | Stake slashed if approved assets default       |
| **Random Assignment**  | Verifiers randomly selected, hard to predict   |
| **Multiple Verifiers** | High-value assets require multiple approvals   |
| **Reputation System**  | Long-term reputation more valuable than bribes |

### Why It's Hard to Pull Off

{% stepper %}
{% step %}
Can't predict which verifier assigned.
{% endstep %}

{% step %}
Bribing multiple verifiers expensive.
{% endstep %}

{% step %}
Stake loss exceeds potential bribe.
{% endstep %}

{% step %}
Reputation damage ends career.
{% endstep %}
{% endstepper %}

***

## Fraudulent Investors, Honest Seller

**Scenario:** Investors manipulate a legitimate seller's asset.

{% @mermaid/diagram content="flowchart LR
S\["Honest<br/>Seller"] -->|"Real invoice"| P\["Platform"]
I\["Fraudulent<br/>Investors"] -->|"Manipulate"| P
P -->|"Funds"| S
D\["Debtor"] -->|"Pays"| I" %}

### Guards

| Guard                         | Description                          |
| ----------------------------- | ------------------------------------ |
| **Smart Contract Settlement** | Payments go to escrow, not investors |
| **Transparent Flow**          | All distributions on-chain           |
| **No Early Withdrawal**       | Funds locked until maturity          |

### Why It's Hard to Pull Off

{% stepper %}
{% step %}
Investors can't redirect debtor payments.
{% endstep %}

{% step %}
Settlement is automatic via smart contract.
{% endstep %}

{% step %}
No way to extract more than entitled.
{% endstep %}
{% endstepper %}

***

## Platform Insider Threat

**Scenario:** Platform team member exploits access.

### Guards

| Guard                     | Description                          |
| ------------------------- | ------------------------------------ |
| **Multi-sig Controls**    | No single person controls funds      |
| **Time-locks**            | Delays on sensitive operations       |
| **On-chain Transparency** | All actions visible                  |
| **Limited Access**        | Smart contracts hold funds, not team |

### Why It's Hard to Pull Off

{% stepper %}
{% step %}
Funds in smart contracts, not team wallets.
{% endstep %}

{% step %}
Multi-sig requires multiple conspirators.
{% endstep %}

{% step %}
Time-lock allows detection before execution.
{% endstep %}

{% step %}
On-chain actions are auditable.
{% endstep %}
{% endstepper %}

***

## Summary

| Fraud Vector              | Primary Defense       | Secondary Defense   |
| ------------------------- | --------------------- | ------------------- |
| Fake invoices             | Debtor verification   | Seller staking      |
| Seller-investor collusion | KYC separation        | Pattern detection   |
| Verifier corruption       | Random assignment     | Multiple verifiers  |
| Payment diversion         | Smart contract escrow | On-chain settlement |
| Insider abuse             | Multi-sig + time-lock | Transparency        |

{% hint style="info" %}
No system is 100% fraud-proof. These guards make fraud difficult and expensive, but some risk remains. Diversify investments accordingly.
{% endhint %}


---

# 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://triple-plus-global.gitbook.io/tpt-whitepaper/risk-framework/fraud-resistance.md?ask=<question>&goal=<endgoal>
```

`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.