The specification is written. The eight-layer trust architecture, the on-chain contracts, the verification flow and the member applications are all documented in detail across the technical papers — nearly three hundred pages of it. What remains is appointing the firm that builds it.
We are in discussion with a shortlist of established software houses with blockchain delivery records. No development partner has been appointed, and no development agreement has been signed. We will publish the partner, the scope and the terms once a firm is contracted — not before.
Three things decide it, in this order:
Proven delivery. Production smart contracts, shipped. Solidity, Polygon and EVM tooling as daily work rather than a capability slide. Experience integrating KYC and AML at the protocol layer, since that is central to how Chronimy works.
An established, verifiable firm. A registered company with a checkable track record and recognised security practice — not an anonymous team. For a platform built to make trust verifiable, the people building it must themselves be verifiable.
Cost efficiency. Every franc raised is member capital. We are selecting the partner that delivers the specification properly at the best cost — not the largest name, and not the cheapest quote.
The architecture is Chronimy’s. The engineering is contracted. Whoever is appointed builds to a detailed written specification, and is paid against delivery rather than in advance.
The Independent Trust Architecture — the eight-layer trust system: identity, behavioural scoring, escrow, the PRU vault, AI trust, the Beacon audit trail, governance and development, implemented to Chronimy’s design.
Polygon smart contracts — the on-chain core: badge-tiered escrow, custody, the PRU vault and founder vesting, deployed on Polygon PoS, where CNMY is an ERC-20 token and gas is paid in POL.
Verification and member applications — the KYC and liveness flow, the Trust Check engine, and the member-facing applications that turn the architecture into something people actually use.
Milestone-gated delivery — development capital is released milestone by milestone on on-chain attestation, never as a lump sum. A lapsed milestone returns the remaining capital.
Development is funded from the raises, milestone by milestone. A partner is contracted once funding is confirmed and a scope of work is agreed — which means no engineering commitment is made against money that does not yet exist, on either side.
When a firm is appointed we will publish who they are, the agreed scope, the milestone schedule and the terms, on this page. Until then, this page says only what is true: selection is in progress.
⬡ Partner published on appointmentChronimy exists to make trust verifiable rather than assumed. It would be inconsistent to ask members to take our word for anything — including who is building it. So we will not claim a partnership before one exists, and when one does, you will be able to check it independently.