ChainSafe / ChainSafe/canton-extending-mainnet

[P2-E4.3] Single rate-computation function (Phase-3 socket)

Open
#93 0 comments 0 reactions 0 assignees View on GitHub
phase-2
Dominant language
Shell
Stars
0
Forks
0
Avg merge
22h 58m
Merged PRs (30d)
1

Description

**Context.** Phase 3 multiplies tiers and three discount curves into pricing. Phase 2
concentrates all rate math in one pure Daml function (base rate → factors → effective
rate) so Phase 3 changes one function and its inputs, not N call sites.

**Deliverable.** `computeTrafficRate` (or equivalent) as the only place effective rate is
derived; buy path and any UI/Scan estimation call it; documented as the Phase-3 extension
point.

**Acceptance.** Grep-level: exactly one rate derivation; unit tests over factor
composition; property: factor 1.0 reproduces current gsync pricing bit-for-bit.

**Depends on.** P2-E4.2.

**Phase-3 foundation.** Tier and curve factors compose here (FR-11, FR-14..FR-22).


Epic: #67 · Plan: [P2-E4-governance-discount.md](https://github.com/ChainSafe/canton-extending-mainnet/blob/main/docs/planning/phase-2-epics/P2-E4-governance-discount.md)

Contributor guide

No contributing guide indexed for this repository

Research direction

Read docs/planning/phase-2-epics/P2-E4-governance-discount.md and resolve the P2-E4.2 dependency first. Trace rate derivation in the buy path and UI/Scan estimation, then use grep to verify one computation entry point. Done means factor-composition unit tests pass and factor 1.0 matches current gsync pricing bit-for-bit.

Written by the indexing model from the issue text.

Assessment

Domain
backend-api-design
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.