Skip to content
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

docs: explain relayer and sweeping #50

Open
Ivshti opened this issue Dec 7, 2019 · 0 comments
Open

docs: explain relayer and sweeping #50

Ivshti opened this issue Dec 7, 2019 · 0 comments

Comments

@Ivshti
Copy link
Member

Ivshti commented Dec 7, 2019

  • the adex-relayer is currently a proprietary component
  • it's not a custodian, and you can interact with the entire AdEx ecosystem without it
    • this can be practically done through MyCrypto/MEW or through a (wip) AdEx CLI
  • it's job is to relay signed messages from the user so that we can have gasless transactions or in other words, to allow the user to only care about one token (currently DAI)
  • a more subtle job of the relayer is to "sweep" channels: which means it will take your earnings from the channels to the Identity contract itself through calling channelWithdraw/channelWithdrawExpired
  • another job of the relayer is to manage Identity accounts for the Platform by recording which wallets control which Identities and recognizing you when you enter the Platform (e.g. you login on the Platform with your Trezor, and it will recognize which Identity is yours)
  • channels: the time period between spec.withdrawPeriodStart and validUntil must be at least a week + a few days, e.g. 10 days; the reason is that automatic relayer sweeping will be done weekly (currently it's daily), but we also need a few days to be extra safe in case of ETH network disruptions/delays or relayer failures; so basically we need the time to ensure the sweeping is done and everyone gets their earnings
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants