Milestone 1: Architecture & Daml / Bridge Contracts
Combines the system design and the on-ledger Daml packages that the middleware, indexer, and bridge all build on.
-
Architecture & Design document
- System architecture diagram describing interactions between Daml contracts, middleware, and indexer.
- Data flow specifications outlining how token state changes propagate across layers (ledger → indexer → API).
- Interface definitions and API schemas (OpenAPI spec or gRPC IDL) for ERC-20 middleware endpoints.
- Security and privacy model detailing identity mapping, authorization flow, and data access restrictions.
-
Daml CIP-56 Token + Bridge Contracts
- CIP-56 / Splice Token Standard compliant Daml packages:
cip56-token(Token, TransferFactory, Events, Config, Compliance) reference token implementation. - Bridge Daml packages:
bridge-core(lock/unlock/mint/burn state machine). - Shared modules:
common/FingerprintAuth.damland supporting types/utilities for external-party authorization. - ERC-20 semantics (transfer, approve, transferFrom, balanceOf, allowance, totalSupply, mint, burn) exposed through the JSON-RPC layer and mapped to TransferFactory / signed-instruction flows rather than via a standalone allowance template.
- Unit and integration test suites against Canton mainnet.
- CIP-56 / Splice Token Standard compliant Daml packages:
| Field | Details |
|---|---|
| Estimated Resources | Engineering: 8 weeks; Project Management: 2 weeks |
| Estimated Duration | 4 weeks |
| Amount | 1,500,000 CC |
| Acceptance Criteria 1 | Architecture and design documents (deployment topology, data-flow, API schemas, security/privacy model) published to the public repository and available for committee review. |
| Acceptance Criteria 2 | cip56-token and bridge-core packages build and pass their unit + integration test suites against Canton mainnet, reproducibly from the repo. |