-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
payment spec: change price per impression (or any other event) dynamically (AIP#6) #16
Comments
Ivshti
changed the title
payment spec: change price per impression dynamically
payment spec: change price per impression (or any type of event) dynamically
Mar 19, 2019
closing cause it's a dupe of #157 ; actually this one was obviously the older one, but the newer one is better described |
Re-opened cause we need a new spec for this (AIP6) |
Ivshti
changed the title
payment spec: change price per impression (or any type of event) dynamically
payment spec: change price per impression (or any type of event) dynamically: AIP#6
Mar 16, 2020
Ivshti
changed the title
payment spec: change price per impression (or any type of event) dynamically: AIP#6
payment spec: change price per impression (or any type of event) dynamically (AIP#6)
Mar 16, 2020
Ivshti
changed the title
payment spec: change price per impression (or any type of event) dynamically (AIP#6)
payment spec: change price per impression (or any other event) dynamically (AIP#6)
Mar 16, 2020
closing, it was done by #272 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
advertisers should be able to dynamically change the price per impression; this could be done by having them submit a validator message to both validators, which will update their
eventRecorder
s to address the changethe original payment spec should contain a thresholds: see
pricingBounds
herethis would require changing
eventAggregator
,eventReducer
and the channel routes so that existing recorders can be updated dynamicallyfor details on the schema, see AIP#6
@samparsky start by going off the comment in the AIP that outlines the spec and PR-ing it to
campaignSpec.md
in adex-protocolthen, implement the date structures in Rust
primitives
and open a PR so we can reviewThen proceed to implementing in the JS and Rust implementations, with comprehensive tests - unit tests for rule matching and integration test with a few compound rules matched together
The text was updated successfully, but these errors were encountered: