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

Test manually E2E workflow on Goerli #2665

Open
leszko opened this issue Nov 23, 2022 · 0 comments
Open

Test manually E2E workflow on Goerli #2665

leszko opened this issue Nov 23, 2022 · 0 comments

Comments

@leszko
Copy link
Contributor

leszko commented Nov 23, 2022

After the Livepeer contracts are deployed into Arbitrum Goerli we should perform the whole E2E workflow to see if Livepeer transcoding and payments work correctly.

I remember that when we tested it at some point in Arbitrum Devnet (after the Arbitrum Nitro migration), it didn't work correctly, because Arbitrum created blocks only when there were some transactions. So, in the case when non transactions were sent for a while, the L1 blocks were created faster then L2 blocks, which in result caused issues with the ticket validity.

To confirm there is no problem in Arbitrum Goerli, we should perform the following steps:

  1. Start Orchestrator with high ticket EV (e.g. -ticketEV 10000000000000000)
  2. Register Orchestrator
  3. Start Broadcaster with high max ticket EV (e.g. -maxTicketEV 30000000000000000)
  4. Deposit ETH funds to Broadcaster
  5. Start streaming video
  6. Check that the video is transcoded in the Orchestrator
  7. Check that the winning ticket was received by the Orchestrator
  8. Check that the ticket was redeemed by the Orchestrator
@github-actions github-actions bot added the status: triage this issue has not been evaluated yet label Nov 23, 2022
@leszko leszko removed the status: triage this issue has not been evaluated yet label Nov 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants