# Audit

As part of our commitment to transparency, security, and reliability, PropiChain underwent a rigorous smart contract audit conducted by BlockAudit from September 16th to September 24th, 2024. The primary goal of this audit was to ensure that our smart contract system is resilient, secure, and adheres to industry best practices. Given the high-stakes nature of real estate transactions, it was imperative for us to ensure that our smart contracts perform flawlessly, safeguarding users' assets and data throughout the entire transaction process.

\
**Why We Conducted the Audit?**

Smart contracts are the backbone of PropiChain’s decentralized real estate platform. They govern critical aspects such as property ownership transfers, payment processing, and escrow management. Ensuring the reliability and security of these contracts is essential to build user trust and mitigate any potential vulnerabilities that could compromise the platform's functionality.<br>

**How We Conducted the Audit?**&#x20;

BlockAudit’s comprehensive approach included a combination of manual and automated reviews to scrutinize every aspect of our smart contract system. The audit focused on testing the contracts against both common and uncommon attack vectors, including reentrancy attacks, race conditions, and decentralized denial-of-service attacks. \
\
\
🔗 [PropiChain Smart Contract Audit Report ](https://github.com/Block-Audit-Report/Propichain?tab=readme-ov-file)<br>


---

# Agent Instructions: 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:

```
GET https://propichain.gitbook.io/propichain/smart-contracts/audit.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.