-
Notifications
You must be signed in to change notification settings - Fork 14
Open
Milestone
Description
Tracking issue for the changes regarding AIP#61: AdEx v5: significantly cheaper channels (full details here)
- Adapter
- Calculate total spendable amount AIP #61 AdEx v5: Adapter - total spendable amount #339 (PR: V5 adapter #353)
-
Channel&CampaignAIP #61 v5: Channel and Campaign #341 -
NewState&Accounting - Sentry
- Accounting & spenders
- GET /channel/:id/spender/:addr
- GET /channel/:id/spender/all
- POST /channel/:id/spender/:addr
- POST /channel/:id/pay (Channel Payout with authentication of the spender)
Withdrawals of advertiser funds - re-introduces thePAYevent with a separate route - GET /channel/:id/get-leaf
from AIP#61:add another helper route /get-leaf that is called like this: /get-leaf?spender=... or /get-leaf?earner=...; this will get the latest approved state (NewState/ApproveState pair), will find the given spender/earner in the balances tree, and produce a merkle proof for it; this is useful for the Platform to verify if a spender leaf really exists
- POST /campaign/:id/close (
newBudget = totalSpent, i.e.newBudget=oldBudget - remaining) - POST / PUT /campaign (create / modify)
-
also update spender available funds when they try to mutate campaigns
-
- Enforce limits
- Events
- enforce per-campaign spending limits atomically
-
update the spenderLeaf directly in the DB when we receive an authenticated ApproveState/NewState
- Distribute fees
- Analytics breakdowns by 1hr
- Validator
- worker will group the ticks (i.e. Accounting, NewState/ApproveState) per channel
- Unified precision AIP #61 AdEx v5: Unified precision (8) #342
- Targeting rules DSL - use UnifiedNum instead of BigNum (part of AIP #61 AdEx v5: Unified precision (8) #342)
- Double-check per-spender limits
- Remove Fees (and move to Sentry)
- Worker flow AIP #61 v5: Validator Worker workflow #360
- Outpace - spender & earner limits
- remove old routes and remove V5 suffixes from var names (eg
analyticsRouterV5->analyticsRouter); do not remove the/v5prefix from the routes themselves
Reactions are currently unavailable