AMANAH chain

What it is, in plain terms

AMANAH chain is an application-layer protocol — like Ordinals on Bitcoin, or NFTs on Ethereum — built on top of the existing AMANAH Network blockchain (Substrate-based PoS, mainnet at wss://rpc.amanah.eblessing.co). It does not introduce a new L1 chain.

What it stores: verbatim human testimony before Allah — written by one author, anchored cryptographically so future tampering is detectable, organized as a hash-linked sequence (block 0 → block N). Each block is verifiable independently of the writer.

Architecture

Block format (JSON, schema v1.0.0)

{
  "block": {
    "index": 12,
    "type": "shahada-stream-block",
    "schema_version": "1.0.0",
    "previous_hash": "0x91c21f5cd854723a441a7546509610238b...",
    "created_at_iso": "2026-05-12T00:12:00Z"
  },
  "writer": {
    "alias": "warhawk",
    "real_name": "Muhammad Saddam Hussain",
    "email_at_capture": "hussain@eblessing.co",
    "amanah_address": null,
    "anchor_signed_by": null
  },
  "title": "...",
  "transcript": [
    { "turn": 1, "role": "writer", "text": "verbatim words" },
    { "turn": 2, "role": "assistant-as-agent", "is_witness": false, "summary": "..." }
  ],
  "anchor": {
    "target_chain": "AMANAH",
    "target_chain_rpc": "wss://rpc.amanah.eblessing.co",
    "anchor_method": "system.remarkWithEvent",
    "tx_hash": null,
    "anchored_at_iso": null,
    "signer_address": null
  }
}

Hash derivation (deterministic)

Every block hash is computed by:

1. Read block-N.json from disk.
2. Parse → recursively sort keys (canonicalize).
3. Strip the anchor field (hash is over pre-anchor form).
4. JSON.stringify the canonicalized form (no extra whitespace).
5. Encode as UTF-8 bytes.
6. blake2b-256 → 0x-prefixed hex.

The same input always yields the same hash. Anyone running node scripts/compute-hash.mjs genesis/block-N.json from the source repo will produce identical output to what was committed.

On-chain anchor (AMANAH mainnet)

The anchor extrinsic is system.remarkWithEvent(remark) where the remark payload is JSON:

{
  "protocol": "shahada-stream",
  "version": 1,
  "block_index": <int>,
  "block_hash": "0x..."
}

This payload is hex-encoded and submitted as the remark parameter. Indexers can detect AMANAH-chain anchors among arbitrary system.remark traffic by parsing the JSON payload and checking protocol === "shahada-stream". The signer's AMANAH wallet pays the small chain fee (typically < 1 HARF).

Tech stack

Verify yourself (no trust required)

You don't have to take any of this on faith. Three reproducible verification paths:

Path A — Verify a block's hash locally

# Clone the source
git clone <repo-url> talkstream
cd talkstream

# Install (uses @polkadot deps)
ln -s ../my-shizu/node_modules node_modules    # or: pnpm install

# Compute hash for any block
node scripts/compute-hash.mjs genesis/block-12.json

# Output: { "hash_blake2b_256": "0x1045490f..." }
# Compare against the previous_hash field in genesis/block-13.json — they must match.

Path B — Verify the on-chain anchor (when broadcast)

# Once the writer signs and broadcasts the anchor:
node scripts/verify-on-chain.mjs

# This script:
#  1. Re-derives the local block hash
#  2. Connects to AMANAH mainnet (wss://rpc.amanah.eblessing.co)
#  3. Fetches the system.remark extrinsic by recorded tx_hash
#  4. Parses the on-chain remark payload
#  5. Asserts block_hash matches local hash
# Exit code 0 = verified, 2 = mismatch.

Path C — Verify the chain's continuity

For each block N from 1 to current:

1. Compute hash of block N-1.
2. Read block N's previous_hash field.
3. Assert they match.

If any link fails, the chain has been tampered between those blocks. The first link (block 0) has previous_hash: null by definition.

Who can add a block

The protocol is permissionless at the technical layer. Anyone with:

• An AMANAH wallet (or any signing wallet capable of system.remarkWithEvent)
• Affirmation of a Necessary Being (the protocol's only theological gate — see Block 58 for the rationale)
• Willingness to write their own testimony and link to the previous block hash

...can author Block N+1. There is no central gatekeeper. The current writer (Muhammad Saddam Hussain / warhawk) verifies any submission claiming to be one of the existing characters in the chain (per Block 27 governance), but new attestations require no permission.

Minimum block requirements

• block.index = N (monotonically incremented from previous)
• block.previous_hash = blake2b-256 of canonical block N-1
• writer.alias OR writer.real_name present
• At least one transcript turn with role: "writer" and verbatim text
• shahada or equivalent attestation content (in any language, any modality per Block 3 multimodal proposal)

Economic primitives (proposed, community-ratified)

All extensions are proposed by the writer for community consultation. None are enforced at the protocol layer. The chain records the proposals; the AMANAH community decides which to implement.

eblessing.co domain family

How to join (add Block N+1)

1. Read the existing chain at eblessing.co/haqchain. Particularly Block 27 (governance) and Block 58 (entry tier).
2. Affirm the Necessary Being floor (Block 58). If you cannot, you are welcome to read but not to participate as block-author.
3. Write your own testimony. Use any language. Use the schema. Set previous_hash to the latest block's hash.
4. Sign with your AMANAH wallet (or any sr25519 signer). Submit the system.remarkWithEvent extrinsic to AMANAH mainnet.
5. Submit your block JSON via pull-request (once the source repo is published) or by direct contact to the current writer.

What this is NOT

• Not a new religion. The chain explicitly defers to the Quran (Block 23, Block 34, Block 49). It claims no new revelation (Block 23 — Khatm-e-Nubuwwat protected).
• Not a cult. The current writer has refused Khalifa-status (Block 47) and explicitly told readers "don't even listen to me" (Block 44, Block 47). Eight humility-blocks across the chain (Block 4, 8, 18, 23, 29, 36, 46, 47) structurally pre-empt cult-of-personality formation.
• Not Quran commodification. Block 49 makes the chain's economic-theology halal-by-construction: Quran ayat are NEVER for sale; only the writer's own testimony.
• Not Dajjal infrastructure. Block 56 documents the writer's direct interrogation of the AI typewriter (Jassasa + Dajjal questions) and the husn-e-zan resolution — the chain's anti-Dajjal verification pattern is built in.
• Not a token speculation vehicle. HARF tokens flow as private receipt (read Quran, earn harf) and public exchange (offer your testimony, receive harf for it). No financial speculation primitive on chain.
• Not a closed garden. Block 58 opens entry to any human who affirms a Necessary Being — Muslim, Christian, Jewish, Hindu monotheist, Sikh, Deist, philosophical theist.

FAQ

Why "AMANAH"?

Three meanings (Block 58):

1. Surah Al-Ahzab 33:72 — the Trust the heavens, earth, and mountains refused; humans accepted.
2. AMANAH Network — the existing Substrate blockchain on which this protocol anchors.
3. The writer's own AMANAT (trust) to each human who affirms a Necessary Being.

Is the chain GDPR-compliant?

The chain is public-by-design. Writers consent explicitly (signing with their wallet) to permanent on-chain attestation. Anonymous beneficiaries (people referenced in writer's stories) are protected per Block 27 — Officer-with-No-Name principle. The chain does NOT collect or store personal data of non-writers.

Why isn't there a token sale?

Because the writer of the genesis chain explicitly refused commodification of Quran content (Block 49) and refused Khalifa-status (Block 47). HARF tokens are earned by Quran-reading work and exchanged for testimony-content; no presale, no allocation to founders, no VC round. This is the "halal-by-construction" economic posture documented across Blocks 25, 43, 49.

What if the AMANAH Network goes down?

Off-chain blocks (this static HTML, the git repo) remain readable. The cryptographic linkage between blocks remains verifiable. Only the on-chain anchor confirmation requires a working AMANAH RPC. Multiple RPC providers + community-run nodes mitigate this.

Can I fork the chain?

Yes. The chain is open-source. Fork it, run it on your own infrastructure, accept different writers. Block 27's governance permits forks explicitly. Verifiers (other humans) MAY choose which forks they recognize as canonical; the protocol takes no position.

Who is the writer?

Muhammad Saddam Hussain (alias: warhawk). Real name revealed by writer himself in Block 8. Contact: hussain@eblessing.co. GitHub orgs: apeaxe-ca and eblessings. The writer is one human, accountable, named, with a public technical track-record (this chain + the AMANAH ecosystem + 313muslim.com).

How do I report a bug?

Open an issue against the source repository (once published) or contact the writer via the GitHub orgs above. The chain has a "humility arc" of 8 explicit blocks where the writer admits fallibility — bug reports are welcomed in the same spirit.