New Events Handled DelegatorUnstakeWithId and ShareBurnedWithId

The events are not emitted from the StakingInfo Contract but from the EventsHub Contract.

made the changes accordingly.

v0.1.11: Merge pull request #29 from maticnetwork/new-delegator-unbond-events

With the new contracts being released. We need to handle two new events for a delegator.

1. ShareBurnedWithId
2. DelegateUnstakeWithId

This is due to the partial unbonding that the delegator can do. With the addition of nonce to the function, the event will also have a nonce to identify how much amount the delegator has unstaked and what is the withdraw epoch for a particular unbond.

Releasing v0.1.10

What's new ?

• Easier iteration through large number of entries present in Delegators entity
• Keeping global counter for uniquely assigning each new delegator identifier, from monotonically increasing ( by 1 ) state variable

Releasing v0.1.7

Changes

Plasma & POS both token mappings tracking supported 🚀

v0.1.5: Merge pull request #19 from maticnetwork/array-initialisation-issue-f…

…ixed

Initialisation Issue of Array fixed

v0.1.4: Merge pull request #18 from maticnetwork/jdkanani/fix-abi

add StakingNft abi for staking subgraph

v0.1.3

fix: release ci

v0.1.2: Merge pull request #16 from maticnetwork/jdkanani/ci

fix: ci for build

v0.1.1: Merge pull request #14 from maticnetwork/fix-for-staking-api

Adds new subgraph for Staking NFT

v0.1.0: new: add json linter (#11)

Basic subgraphs for plasma/pos withdraws and staking