stronk-dev / livepeerevents Goto Github PK

Just match any field with the orch address

https://nframe.nl/livepeer?orchAddr=0x08f10D03A0CF7a9eADdc7EacD4cf135a07A0feff

has a 10K unstake from https://explorer.livepeer.org/accounts/0x5ec2be1adc70bc338471277c2dcc183b0b2c91be/delegating

{
"address":"0x35Bcf3c30594191d53231E4FF333E8A770453e40",
"transactionHash":"0x8bec6edb47f5085c61abf28e0ff9a70280929fc7d9cc95b615df485881361d8d",
"transactionUrl":"https://arbiscan.io/tx/0x8bec6edb47f5085c61abf28e0ff9a70280929fc7d9cc95b615df485881361d8d",
"name":"Unbond",
"data":{
"0":"0x08f10D03A0CF7a9eADdc7EacD4cf135a07A0feff",
"1":"0x5Ec2be1aDC70Bc338471277c2dCc183b0b2C91be",
"2":"1",
"3":"10000000000000000000000",
"4":"2491",
"delegate":"0x08f10D03A0CF7a9eADdc7EacD4cf135a07A0feff",
"delegator":"0x5Ec2be1aDC70Bc338471277c2dCc183b0b2C91be",
"unbondingLockId":"1",
"amount":"10000000000000000000000",
"withdrawRound":"2491"
}
},
{
"address":"0x35Bcf3c30594191d53231E4FF333E8A770453e40",
"transactionHash":"0x8bec6edb47f5085c61abf28e0ff9a70280929fc7d9cc95b615df485881361d8d",
"transactionUrl":"https://arbiscan.io/tx/0x8bec6edb47f5085c61abf28e0ff9a70280929fc7d9cc95b615df485881361d8d",
"name":"EarningsClaimed",
"data":{
"0":"0x08f10D03A0CF7a9eADdc7EacD4cf135a07A0feff",
"1":"0x5Ec2be1aDC70Bc338471277c2dCc183b0b2C91be",
"2":"118964187072793932562",
"3":"0",
"4":"2481",
"5":"2484",
"delegate":"0x08f10D03A0CF7a9eADdc7EacD4cf135a07A0feff",
"delegator":"0x5Ec2be1aDC70Bc338471277c2dCc183b0b2C91be",
"rewards":"118964187072793932562",
"fees":"0",
"startRound":"2481",
"endRound":"2484"
}
},

livepeer.js header, as well as the event viewer and buttons do not scale for mobile devices yet

Right now if you click on a delegator in the eventViewer, it clears your current selected orchestrator info

On clicking an address in the event viewer, set a loading screen in the orchestrator viewer, if getOrchestrator returns an empty list, getOrchestratorByDelegator (separate issue) and remove the loading screen once we have an orchestrator. If we do not have an O at this point, show an error

In src/livepeer.js render the OrchestratorViewer if we have a loaded Orchestrator object, else the text

Make it a suburl or query param:
https://www.nframe.nl/livepeer/0x847791cbf03be716a7fe9dc8c9affe17bd49ae5e
https://www.nframe.nl/livepeer?add=0x847791cbf03be716a7fe9dc8c9affe17bd49ae5e
If present, init the filter and get their data for the OrchestratorViewer

Leave out all of the event stuff, only use the backend as a caching mechanism for the CMC, L1, L2 and thegraph stuff. Only stuff we want to leave in are the JSON outputs and the prometheus integration

There's a lot of CSS hardcoded overrides in the frontend. We should create new CSS classes as needed and try to reuse existing ones

Query thegraph for winning tickets: WinningTicketRedeemedEvent

Doesn't display the right information right now. Should parse nested obj.subEvents in order to display better info

Manier om de Event DB helemaal opnieuw te syncen, alle events uitlezen

Bij booten doen we fullsync totdat alle blokken behandeld zijn
Dus een teller voor block verwerkt, een lege collectie, en dan alle events niet cachen, alleen aanmaken in de DB
Tijdens de fullsync, geen contract listener aanhebben
Als afgerond, gehele lijst ophalen en in de cache stoppen. De timeout op 1x per uur zetten ofzo
Contract listener vervangen door een timed event die blocks in de gaten houdt

TBD
Going to be similar to https://hubble.figment.io/livepeer/chains/mainnet

Currrent scroller is very simple.
Try something which handles large list sizes better, since dragging when there are many elements becomes very slow
Would be nice if you can scroll like on mobile, where it slowy comes to a stop when releasing the drag button

Just like getOrchestrator, by doing a search for the delegator at the thegraph API en then doing a getOrchestrator call on the address where they are delegating

We will be increasing the amount of processing done in the loading screen

Also show a progress indicator or an error thingy if there is no backend connection

Right now in a transaction events like moving stake take priority over claiming eanings. During some rebond events claiming and moving stake happens in 1 transaction. We should split a transaction into possible subtransactions, or just leave out earnings all together

[
{
"address": "0x35Bcf3c30594191d53231E4FF333E8A770453e40",
"transactionHash": "0x23b41d7f7fd388766484d7288ec164171a185e15d09a694270c091164ecdbafe",
"transactionUrl": "https://arbiscan.io/tx/0x23b41d7f7fd388766484d7288ec164171a185e15d09a694270c091164ecdbafe",
"name": "WithdrawFees",
"data": {
"0": "0xDFc452Da1fA53f5DCD1EBc63A3E5f6C5F9139F76",
"1": "0x2cC53Ae643038a51C0F10964efEdb04285607771",
"2": "6915574260931571",
"delegator": "0xDFc452Da1fA53f5DCD1EBc63A3E5f6C5F9139F76",
"recipient": "0x2cC53Ae643038a51C0F10964efEdb04285607771",
"amount": "6915574260931571"
}
},
{
"address": "0x35Bcf3c30594191d53231E4FF333E8A770453e40",
"transactionHash": "0x23b41d7f7fd388766484d7288ec164171a185e15d09a694270c091164ecdbafe",
"transactionUrl": "https://arbiscan.io/tx/0x23b41d7f7fd388766484d7288ec164171a185e15d09a694270c091164ecdbafe",
"name": "Rebond",
"data": {
"0": "0x525419FF5707190389bfb5C87c375D710F5fCb0E",
"1": "0x2cC53Ae643038a51C0F10964efEdb04285607771",
"2": "0",
"3": "13175701400114191076727",
"delegate": "0x525419FF5707190389bfb5C87c375D710F5fCb0E",
"delegator": "0x2cC53Ae643038a51C0F10964efEdb04285607771",
"unbondingLockId": "0",
"amount": "13175701400114191076727"
}
},
{
"address": "0x35Bcf3c30594191d53231E4FF333E8A770453e40",
"transactionHash": "0x23b41d7f7fd388766484d7288ec164171a185e15d09a694270c091164ecdbafe",
"transactionUrl": "https://arbiscan.io/tx/0x23b41d7f7fd388766484d7288ec164171a185e15d09a694270c091164ecdbafe",
"name": "EarningsClaimed",
"data": {
"0": "0x0000000000000000000000000000000000000000",
"1": "0x2cC53Ae643038a51C0F10964efEdb04285607771",
"2": "0",
"3": "0",
"4": "1",
"5": "2483",
"delegate": "0x0000000000000000000000000000000000000000",
"delegator": "0x2cC53Ae643038a51C0F10964efEdb04285607771",
"rewards": "0",
"fees": "0",
"startRound": "1",
"endRound": "2483"
}
},
{
"address": "0x35Bcf3c30594191d53231E4FF333E8A770453e40",
"transactionHash": "0x23b41d7f7fd388766484d7288ec164171a185e15d09a694270c091164ecdbafe",
"transactionUrl": "https://arbiscan.io/tx/0x23b41d7f7fd388766484d7288ec164171a185e15d09a694270c091164ecdbafe",
"name": "TransferBond",
"data": {
"0": "0xDFc452Da1fA53f5DCD1EBc63A3E5f6C5F9139F76",
"1": "0x2cC53Ae643038a51C0F10964efEdb04285607771",
"2": "161",
"3": "0",
"4": "13175701400114191076727",
"oldDelegator": "0xDFc452Da1fA53f5DCD1EBc63A3E5f6C5F9139F76",
"newDelegator": "0x2cC53Ae643038a51C0F10964efEdb04285607771",
"oldUnbondingLockId": "161",
"newUnbondingLockId": "0",
"amount": "13175701400114191076727"
}
},
{
"address": "0x35Bcf3c30594191d53231E4FF333E8A770453e40",
"transactionHash": "0x23b41d7f7fd388766484d7288ec164171a185e15d09a694270c091164ecdbafe",
"transactionUrl": "https://arbiscan.io/tx/0x23b41d7f7fd388766484d7288ec164171a185e15d09a694270c091164ecdbafe",
"name": "Unbond",
"data": {
"0": "0x525419FF5707190389bfb5C87c375D710F5fCb0E",
"1": "0xDFc452Da1fA53f5DCD1EBc63A3E5f6C5F9139F76",
"2": "161",
"3": "13175701400114191076727",
"4": "2490",
"delegate": "0x525419FF5707190389bfb5C87c375D710F5fCb0E",
"delegator": "0xDFc452Da1fA53f5DCD1EBc63A3E5f6C5F9139F76",
"unbondingLockId": "161",
"amount": "13175701400114191076727",
"withdrawRound": "2490"
}
}
]

Display datetime in locale format

Would require some major modifications, since the backend does not even attach a date. Maybe just add the time an event was inserted into the database?

Normal: inset effect
When active: hide that type of event and grey out the color

We can do this separately in each src/OrchAddressViewer.js
Wait for ENS and/or Ceramic support to be implemented first, since 3box is deprecated

Right now it only displays the latest event in a transaciton
We should look at all events and fill in some kind of metadata on the entire transaction, like type, from, to, amount, caller, etc

Should contain more info on what the program does, requirements, how to install, how to update, other useful commands

https://thegraph.com/hosted-service/subgraph/livepeer/livepeer

We can then create an endpoint in the API to get all details on a given Orchestrator:
{
transcoders(where: {id: "0x847791cbf03be716a7fe9dc8c9affe17bd49ae5e"}) {
activationRound
deactivationRound
active
lastRewardRound {
id
length
startBlock
endBlock
mintableTokens
volumeETH
volumeUSD
totalActiveStake
totalSupply
participationRate
movedStake
newStake
}
rewardCut
feeShare
pricePerSegment
pendingPricePerSegment
pendingFeeShare
pendingRewardCut
totalStake
totalVolumeETH
totalVolumeUSD
serviceURI
delegators {
id
bondedAmount
startRound
}
delegator {
id
bondedAmount
startRound
}
}
}

Pass a name to the eventViewer in order to filter out specific transactions

Add buttons to livepeer.js in order to set this to ALL, TranscoderActivated, TranscoderUpdate, Reward, WithdrawStake

TBD event types, which we might throw away or not:
EarningsClaimed
Unbond
TransferBond
Bond
Rebond

At least check if we are not missing any events like stake moving around

Events we are skipping:
// Filter
if (eventObj.name === "WithdrawFees" || eventObj.name === "TransferBond"
|| eventObj.name === "Rebond" || eventObj.name === "Unbond" || eventObj.name === "EarningsClaimed") {
return;
}

Would be nice if all of our cached data is also available to Prometheus, enabling for better integration with Grafana

Maybe make the topbar a side bar? find a way to make the feed taller at least
Would also make scaling for mobile easier if all components are less wide

Think making events 3 lines tall and very narrow?

Free tier mongodb cloud or self-hosted tips

Bij het filteren wordt er altijd naar addrFrom en addrTo gekeken
Dit is niet altijd handig bv, bij een stake inital stake waarbij het from addr 0x00000000000000000000000000000000000000 is ofzo

Any way to quickly remove any unused CSS?

Add configs for:

Adding block times (or not)
Timeouts for each API endpoint

Right now Events get bundled during render
We should bundle them into a list of transactions before render

All components are currently just in the root directory
A lot of components also have conditional subcomponents which should be split off into separate components
Todo: organize the components and split off large components into multiple subcomponents

Should be more clear whether they are pressed or not

Current Batching does not work as expected and causes the eventviewer to rerender for each individual dispatch

Since we remove it once we load the livepeer component anywat, better keep it a local scope so that it gets destructed automatically once the component unrenders itself

Does not show who they are taking it from. This is contained in one of the nested obj.subEvents

Still a relic from my old website. Counter itself can stay but at least remove the text of who interacted, since we are not tracking this at this moment

https://api.thegraph.com/subgraphs/name/livepeer/arbitrum-one/graphql
Due to a limitation in gql queries, it is only getting max 100 delegators. Something like this does not work:
{
transcoders(limit: 2,
where: {id: "0x525419ff5707190389bfb5c87c375d710f5fcb0e"}) {
activationRound
deactivationRound
active
lastRewardRound {
id
length
startBlock
endBlock
mintableTokens
volumeETH
volumeUSD
totalActiveStake
totalSupply
participationRate
movedStake
newStake
}
rewardCut
feeShare
pendingFeeShare
pendingRewardCut
totalStake
totalVolumeETH
totalVolumeUSD
serviceURI
delegators {
id
bondedAmount
startRound
}
delegator {
id
bondedAmount
startRound
}
}
}

Maybe we have to try a different query, or see if this is a limitation in the api itself:
https://github.com/livepeer/livepeerjs/tree/master/packages/subgraph
Maybe we need to create a PR there to get more than 100 results, which seems to be the default limit

When fully synced, we have thousands of events

Loads in a few seconds, but can be quicker if we simply don't render any event which is too old

Biggest problem being the filters and search function, which should function on the entire set of events

This is a problem since right now the render functions determines the type of the event bundle

Also add instruction for hosting your own backend in simple mode

Since watching for events can cause you to miss one or two

Rather than start from scratch, keep track of what range of blocks have been added live and what range of blocks have been synced by getting all events

Then on boot continueSync all blocks which were added live

Any events which come in live do not get added to the database, but only cached serverside

Make a separate guide on how to use just the frontend and my API in order to easily host a website for your own orchestrator

steps:
installing dependencies
cloning repo
modifying my orch address to theirs
modifying grafana panel links
build the website
explanation on updating and and resetting branch to master
modifying nginx config
certbot