Anchoring
Every night the day’s ledger events are combined into one fingerprint and written to Polygon, which the plan calls . Only that fingerprint and the date go on chain.
18 Aug 2027, so far
Nights of 4 Aug to 17 Aug 2027
Read back at 01:15 today
Writes today's 21 events so far to Polygon
Ledger events per night
4 Aug 2027 to 18 Aug 2027. Weekdays are busier than weekends; 10 Aug, when Gulmohar’s bids were opened, was the busiest night. Every past night is anchored on Polygon; today’s batch stays open until it posts tonight at 01:00 IST.
Daily re-check
At 01:15 IST the batch for 17 Aug 2027 was read back from the chain and compared with our records. The root matches.
- Root
- 137d4845127d46…0c7d3d40
- Block
- 115,634,750
- Chain
- Polygon PoS
- Today's batch
- 21 events so far
- Posts at
- 01:00 IST tonight
Batches
| Date | Events | Merkle root | Transaction | Block | Posted | Status |
|---|---|---|---|---|---|---|
| 18 Aug 2027 | 21 | 5fe345ec60…e34459 | Not yet | Pending | Tonight, 01:00 | Open |
| 17 Aug 2027 | 42 | 137d484512…7d3d40 | 0x3cec0f11…ec10a4 | 115,634,750 | 18 Aug, 01:01 | Anchored on time |
| 16 Aug 2027 | 47 | 2cefcbbe2d…efd077 | 0x55215e0a…21562b | 115,591,600 | 17 Aug, 01:02 | Anchored on time |
| 15 Aug 2027 | 14 | 69cbbe8f68…cbb9d6 | 0x91fd50db…fd58ba | 115,548,450 | 16 Aug, 01:03 | Anchored on time |
| 14 Aug 2027 | 11 | 732aa12074…2aac25 | 0x1b840c5c…840ac9 | 115,505,300 | 15 Aug, 01:00 | Anchored on time |
| 13 Aug 2027 | 38 | d80ab8c9d7…0aba5c | 0xf85f680d…5f5d08 | 115,462,150 | 14 Aug, 01:01 | Anchored on time |
| 12 Aug 2027 | 44 | f17d3c42f2…7d3463 | 0xf09484a6…94895f | 115,419,000 | 13 Aug, 01:02 | Anchored on time |
| 11 Aug 2027 | 51 | ae586593ad…586d72 | 0x4d70a9d7…70a51e | 115,375,850 | 12 Aug, 01:03 | Anchored on time |
| 10 Aug 2027 | 63 | 56a21ef457…a21d61 | 0x56cf8c68…cf976d | 115,332,700 | 11 Aug, 01:00 | Anchored on time |
| 9 Aug 2027 | 40 | ffdd9e0600…dda2bf | 0xacb1985a…b1907b | 115,289,550 | 10 Aug, 01:01 | Anchored on time |
| 8 Aug 2027 | 9 | 066b4ced05…6b41e8 | 0x933f14e1…3f1674 | 115,246,400 | 9 Aug, 01:02 | Anchored on time |
| 7 Aug 2027 | 16 | a18b3544a2…8b33b1 | 0x051da3e0…1daee5 | 115,203,250 | 8 Aug, 01:03 | Anchored on time |
| 6 Aug 2027 | 35 | 780510e377…0518c2 | 0xfbbec14f…bebc96 | 115,160,100 | 7 Aug, 01:00 | Anchored on time |
| 5 Aug 2027 | 41 | 3b291e123c…291633 | 0xbee2ce7e…e2d337 | 115,116,950 | 6 Aug, 01:01 | Anchored on time |
| 4 Aug 2027 | 33 | 21b69a9920…b69c2c | 0xa5704b05…704000 | 115,073,800 | 5 Aug, 01:02 | Anchored on time |
How a certificate is verified
1. Hash every event
Every ledger event is hashed together with a random salt, so no hash can be traced back to a person.
2. Combine each night
Each night the day’s hashes are combined into a Merkle tree, and only its root and the date are written to Polygon.
3. Carry the proof
Each certificate carries its event hash, the proof that links it to that root, and the transaction id.
4. Check against the chain
The public verify page recomputes the root from the proof and checks it against the chain. If anything in the entry changed, the roots do not match.