Forecast records with evidence, revision windows and validator review.
Almanac keeps forecasts honest after they are published. A forecaster can open a record, attach sources, update assumptions and send the claim through GenLayer review so the final state has a readable trail instead of a bare prediction.
- Network: GenLayer Bradbury
- Chain ID: 4221
- Contract:
0xe113fF6B307F8EbB1977Ba51747CE73CD6fF9dA8 - Deploy transaction: 0xe6316779...eb6301
- Deployed:
2026-07-01T15:37:16.000Z - Source:
contracts/almanac_v2.py(37,697 bytes)
- Set the forecast standard.
- Open a dated forecast record.
- Attach source evidence and assumptions.
- Ask GenLayer validators to review the claim.
- Resolve challenge and reputation updates.
The frontend reads forecast counts, recent records, source lists, challenge state and reputation views. Contract state is public; write actions still require a connected wallet on GenLayer Bradbury.
| Action | Transaction |
|---|---|
create_forecast |
0x05b335c2...aaaf35 |
Read verification passed on Bradbury after deploy. The public app points at this contract address and reads accepted state.
python -m http.server 8080Open http://localhost:8080.
The public package is static and has no install step. Vercel receives only frontend, contract source and public deployment metadata.
Keep wallet private keys, vault exports, .env files, Vercel project state and dashboard data out of Git. This repository is for public source, UI, tests and deployment receipts only.