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

Transcoder Reward Call Alerting App #158

Open
ericxtang opened this Issue Jul 28, 2018 · 13 comments

Comments

Projects
None yet
6 participants
@ericxtang
Member

ericxtang commented Jul 28, 2018

What's the problem? (required)
Transcoders have to make sure they call reward for every round in the protocol. This logic is built into the go-livepeer codebase so it should be done automatically. However, a few different reasons can stop the automated calling behavior in the Livepeer node.

What's the current behavior? (required)
Nothing happens if a transcoder misses a reward call.

Describe a possible solution you've considered (optional)
There should be a monitoring tool that sends out alerts if transcoders miss reward calls. This tool can start with the following feature:

  • Allow anyone to opt into an email alert for when any transcoder has not called reward for the current round
  • This email alert can be scheduled for a specific time everyday.

Additional context (optional)
The livepeerjs sdk gives you an easy way to query the information that lives on the blockchain. There are examples in the explorer package (which uses the graphql sdk to interact with the blockchain and load data).

Note for bounty hunter
The tool can live as a stand-alone app, using APIs like Mailgun to send out emails.

@gitcoinbot

This comment has been minimized.

gitcoinbot commented Sep 3, 2018

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


Work has been started.

These users each claimed they can complete the work by 4 weeks, 1 day from now.
Please review their action plans below:

  1. bleushark1988 has been approved to start work.

    Dear.
    I am a Jin JingLong.
    I will start this task asap.
    Regards.

Learn more on the Gitcoin Issue Details page.

@gitcoinbot

This comment has been minimized.

gitcoinbot commented Sep 7, 2018

@bleushark1988 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

  • warning (3 days)
  • escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

@bleushark1988

This comment has been minimized.

bleushark1988 commented Sep 7, 2018

I am working on this issue yet. for resolve this issue, I need to review all functions. So it will take some time.

@gitcoinbot

This comment has been minimized.

gitcoinbot commented Sep 13, 2018

@bleushark1988 Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

  • warning (3 days)
  • escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

@gitcoinbot

This comment has been minimized.

gitcoinbot commented Sep 16, 2018

Issue Status: 1. Open 2. Started 3. Submitted 4. Done


@bleushark1988 due to inactivity, we have escalated this issue to Gitcoin's moderation team. Let us know if you believe this has been done in error!

  • warning (3 days)
  • escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

@iSasFTW

This comment has been minimized.

Contributor

iSasFTW commented Oct 24, 2018

Could I try to do this one, if the previous contributor isn't working on it anymore? Is this still needed?

@dob

This comment has been minimized.

Member

dob commented Oct 24, 2018

@iSasFTW I'd certainly be interested in using a productized version of this. One example that we've seen so far is this simple SMS alerting app from Bison Trails: https://gist.github.com/aaronhenshaw/d3c206a07fd86e286da3974da22979de

But there's probably a different take on the productization of this - how and when are alerts delivered, how do I opt in/out, etc. I'd rather sign up for a service that manages the reliability of this than run a script for example (and I'd be willing to pay for that!)

@ryan-shea

This comment has been minimized.

ryan-shea commented Oct 25, 2018

Hey @bleushark1988, Ryan from Gitcoin here. Are you still working on this bounty? Please let @dob know if so! 👍 🔨

@iSasFTW

This comment has been minimized.

Contributor

iSasFTW commented Oct 25, 2018

@dob That sounds good. I was mostly thinking about just adding a new package to livepeerjs, that monitors the chain and sends out emails, like the original issue described. Do you think there's still a need for something like that?

@dob

This comment has been minimized.

Member

dob commented Oct 29, 2018

@bleushark1988

This comment has been minimized.

bleushark1988 commented Oct 30, 2018

Sorry guys. I can't know issues yet.

@ryan-shea

This comment has been minimized.

ryan-shea commented Nov 8, 2018

Hey @dob, Ryan from Gitcoin here. Looks like @bleushark1988 isn't working on this one -- do you want to approve @iSasFTW to work on it?

@dob

This comment has been minimized.

Member

dob commented Nov 8, 2018

Sure, we can remove @bleushark1988, but it looks like as the funder maybe only @ericxtang can do it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment