starknet-id / indexer Goto Github PK

Will fix: starknet-id/api.starknet.id#62

Auto renewal would start renewing domains too quickly and transactions would fail because allowance is not yet accepted.

Description

We have trouble managing data for referrals, Ideally, we would have something where we can have:

• Check the revenue generated by a particular address on direct referrals for Starknet ID (so the 75%)
• Check the revenue generated by a particular address on direct referrals for the affiliate (so the 25%)
• Check the revenue generated by a particular address on indirect referrals for the Starknet ID
• Check the revenue generated by a particular address on indirect referrals for the affiliate
• Check the total revenue generated by Starknet ID on direct/indirect affiliates
• Check the total revenue generated by Affiliates
• Check the top affiliates

Maybe we can use the the current stats dashboard made in python but Idk

Develop an indexer to manage the 'nfts_images' collection by indexing 'EquipmentUpdated' events.

{ token_id, image_id }

Brief: https://app.skiff.com/file/47a912b4-2f07-48d6-b6eb-4e799a20c240

Add new indexers to support new naming events and disable the old indexers at a specified block.

starknet_id_update -> DomainRenewal and DomainMint
domain_to_resolver_update -> DomainResolverUpdate
domain_transfer -> DomainTransfer
domain_to_addr_update -> removed, check starknetid
addr_to_domain_update -> AddressToDomainUpdate
reset_subdomains_update -> SubdomainsReset

We meed a database to keep updated the balances of assets owned by a user off chain.

These balances can be updated by our server:

• increased when the user completes an achievement for example
• decreased when a signature for updating the image_id is generated

But also by our indexer:

• decreased when someone claims an asset on chain in AssetsContract (via mint_assets, see https://github.com/starknet-id/starkurabu_asset_contract/issues/1 )
• increased when someone burns an asset on chain (also in AssetsContract)
• updated (with + and -) when someone changes the equipment (via EquipmentUpdated in Starkurabu NFT Contract)

Collections:
on_chain_credits:

{ asset_id, variant_id, owner, amount }

off_chain_credits:
{ asset_id, variant_id, owner, amount, cursor }

To get the balance of user, find his credits on_chain and off_chain and do the sum.

If a chain reorganization happens, it's possible that a user could end up double spending:
He burns an asset on chain and receives it off chain, and then generate the signature to mint it back on chain. If a reorg cancels the burn, he can still mint it even though he didn't burn the first one. I think it's not a too big issue but we need to know what would happen in that case (would the balance be -1, 0, ...).

Add support to custom resolving to indexer

• creation_date is missing
• rev_addr not removed