On-chain Proof Guide
KCWorld never asks you to “just trust us.” We record the digital fingerprint (hash) of the calculation behind every distribution on the blockchain, so anyone can verify the data hasn't been altered — without going through the company.
Fingerprinted on confirmation
The moment a monthly distribution is confirmed, the SHA-256 hash of its summary — revenue, costs, reserve and per-investor amounts — is automatically recorded on the disclosure-anchor contract.
Nobody can change it
Once on the blockchain, the record cannot be modified or deleted by anyone, including KCWorld itself. The blockchain even proves when it was recorded.
Verify it yourself
Recompute the hash from the published statement in the same way and compare it with the on-chain value — a match proves not a single character has changed since confirmation.
How to read the event log
In a project's distribution history, click “View anchor ↗” to open the Tronscan event-log page. Each field means the following. (Example anchor transaction ↗)
| Field | Example | Meaning |
|---|---|---|
| Event Name | Anchored | The disclosure-anchor contract's “record complete” declaration |
| category | 6522b1ac… | Record type. The original value is distribution — shown as a keccak256 hash because it is an indexed field |
| refId | KCW-2026-K:2026-07 | Human-readable reference — project code : distribution month |
| dataHash | 77031ee5… | SHA-256 fingerprint of the distribution summary (revenue, costs, reserve, per-investor amounts) |
| timestamp | 1786859343 | Time stamped by the blockchain (Unix time) — proof of when the data existed |
Verification in 4 steps
Check the statement
In the project's distribution history, check the month's revenue, costs and distributable amount.
Open the anchor
Use “View anchor ↗” to check refId and dataHash in the Tronscan event log.
Recompute the hash
Serialize the published distribution summary into the canonical JSON format and compute its SHA-256.
Compare
If your value equals dataHash, integrity is proven. If not, the data was changed after confirmation.
Project RWA tokens work the same way
Each project's RWA token is never pre-minted — it is minted only for confirmed allotments (1 Unit = 1 USDT subscribed, plus Investment Bonus). Total supply therefore always equals total allotted Units, verifiable directly on-chain.
Minting: operator only, and only up to confirmed allotments (max supply pre-disclosed incl. Bonus)
Holding: KYC-verified custodial wallets only
Transfers: fully locked in MVP (mint / burn / recovery only) — secondary transfers open after regulatory approval
RWA token (pilot): TFGgZCLn88L9zo4nwdNLtv4C3rP7BZYpwu ↗Disclosure anchor: TQ37p7isr5QRxXbRCYrcUx5DrbieohUp93 ↗Privacy: only hashes (fingerprints) are recorded on the blockchain — never raw data such as amounts or names. On-chain records currently run on the TRON Nile testnet as a pilot; the setup may change under applicable laws and regulatory approval at full launch.