You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Start Orchestrator with high ticket EV (e.g. -ticketEV 10000000000000000)
Register Orchestrator
Start Broadcaster with high max ticket EV (e.g. -maxTicketEV 30000000000000000)
Deposit ETH funds to Broadcaster
Start streaming video
Check that the video is transcoded in the Orchestrator
Check that the winning ticket was received by the Orchestrator
Check that the ticket was redeemed by the Orchestrator
The text was updated successfully, but these errors were encountered:
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:
-ticketEV 10000000000000000
)-maxTicketEV 30000000000000000
)The text was updated successfully, but these errors were encountered: