Auto-sync 2026-08-16 06:00:01

2026-08-16 06:08:47 +08:00
commit 2c5871ba01
31 changed files with 3010 additions and 0 deletions
@@ -0,0 +1,34 @@
+## THE DECLARATION
+
+**HUKM:** You shall encode the fixed shares of Faraid and the perpetual flow of Waqf into a smart contract that executes upon a verified death event, because the code is the executor that cannot be bribed, delayed, or forgotten.
+
+**DALEEL:** Allah commands: “For men is a share of what the parents and near relatives leave, and for women a share” (An-Nisa 4:7). The Prophet ﷺ said: “When a human being dies, all deeds cease except three: sadaqah jariyah, beneficial knowledge, or a righteous child who prays for him” (Muslim). The smart contract is the modern vessel for both: it enforces the fixed shares (Faraid) and releases the perpetual benefit (sadaqah jariyah) without human intervention.
+
+**MAQSAD:** Hifz al-Mal (Preservation of Wealth) — the wealth is not lost to forgotten passwords, disputed keys, or delayed probate. Also Hifz al-Din (Protection of Faith) — the religious obligation to distribute justly is executed precisely, removing the sin of negligence.
+
+**SHURUT:**
+- The smart contract must be audited by a qualified blockchain security firm and reviewed by a Sharia advisor familiar with Faraid.
+- A multi-signature scheme must include at least one trusted executor (Wasi) and one independent witness (e.g., a family member or Islamic council) to confirm the death event.
+- The contract must enforce a time-lock on Waqf distributions: payouts to beneficiaries or charitable projects only after a minimum waiting period (e.g., 30 days) to allow for disputes or corrections.
+- The code must allow for Awl (proportional reduction) and Radd (surplus redistribution) if the sum of fixed shares exceeds or falls short of the estate, encoded as fallback logic.
+
+**MUNKATHIRAT:**
+- A bug in the smart contract that miscalculates shares or locks funds permanently — nullifies the entire clause; you must have an emergency kill switch with a separate multi-sig recovery path.
+- Failure to update the beneficiary list after a birth or death in the family — the contract becomes a tool of injustice, not justice.
+- Using a single private key for the death oracle — a single point of failure that can be exploited or lost; nullifies the security of the entire trust.
+
+---
+
+## THE EXECUTION
+
+**STEP 1:** Inventory your digital wealth and assign Faraid shares. This week, list every crypto wallet, NFT, domain, SaaS revenue stream, and tokenized asset. Write the exact fractions (e.g., son gets 2/3 of the remaining after wife’s 1/8). Use a spreadsheet. Do not estimate. This is the data that will be burned into the contract.
+
+**STEP 2:** Create a multi-signature wallet with at least 3 signers: yourself (primary), a trusted Wasi (executor), and a neutral third party (e.g., your mosque’s imam or a Sharia-compliant DAO). Set the threshold to 2-of-3 for death confirmation. Deploy a test contract on a testnet first. Verify every share calculation against a manual Faraid worksheet.
+
+**STEP 3:** Design and deploy the time-locked Waqf distribution contract. Use a standard like the Ethereum ERC-1155 for tokenized waqf corpus. Set the perpetual beneficiary (e.g., a water well project, a Quran app). Fund the contract with fungible or non-fungible assets. Activate a dead-man switch: if you do not re-sign a heartbeat transaction every 90 days, the contract assumes death and begins distribution. Test the entire flow with simulated inputs before finalizing.
+
+---
+
+## THE HISBAH
+
+What digital wealth will vanish into the void of forgotten seed phrases and unread wills because you refused to encode what Allah already commanded? The blockchain does not forgive delay. Every day you wait, your fixed heirs lose the fractions that are theirs by divine right. The code will not care about your excuses. It will execute or it will not. You are the one who must write it.