-
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
AIP #61 v5: Channel and Campaign #341
Milestone
Comments
26 tasks
The update way of use for channels does not need campaigns in the validators. Each channel will be used as ledgere between all participants. For the analytics we can use the campaignID (exteranl id generated on the backend) in tha path of the event record. |
|
Open
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://github.com/AdExNetwork/aips/issues/61
Rust reference:
Issue: AmbireTech/adex-validator-stack-rust#382
PRs: AmbireTech/adex-validator-stack-rust#383
Channel
As AIP#61 states the Channel is defined by
(leader, follower, guardian, tokenAddr, nonce)
Campaign
Campaign { id: CampaignId, channel: Channel, creator, validators, title.... rest of the ChannelSpec fields }
Note: The fields were aligned with Ivo before making the changes for the Campaign.
CampaignId
should be a randomly assigned value bySentry
, we've chose theUuid
as a random generator in Rust and using a representation of the 16 bytes as0x
prefixed hex stringNo migration
Apart from that we can remove obsolete fields in the
ChannelSpec
as the v5 will not have migration from v4 as it will work in a different way that v4.The text was updated successfully, but these errors were encountered: