rarible / ethereum-indexer-public Goto Github PK

View Code? Open in Web Editor NEW

158.0 158.0 40.0 17.87 MB

Ethereum indexer and APIs

Home Page: https://rarible.org

License: GNU General Public License v3.0

Kotlin 100.00% Dockerfile 0.01%

ethereum-indexer-public's People

Contributors

Stargazers

Watchers

Forkers

polychainlink atapin cristian-delosrios azimanuar5874 metalink-app alphaquark collector-x stears88 nftdroppr griffin-finance zena-park estk avishka-rathnavibhushana pcmode kevkoch goodvibesohmly mengwp2004 tat2bu toledoroy linthertoss justinjiach 0xnivek mehranhydary issypro101 yulmaxi karthickselvan2 samspzn obilo509 lidong1211 jugernautus alexdevapi aranoverse shubham-0536 realoff deqodelabs sanjayarun07 luishsr alexandruverbitsky harrybite chainargos

ethereum-indexer-public's Issues

cancel_list duplicate bug when fetching order activities

Hi, I found an interesting bug that duplicates a cancel_list order when fetching order activities.

I have not explored if this bug persists outside of this query; I've only tested on this specific query with the only change being on the size and types parameter. I noticed that there was a persistent duplication of objects that have the cancel_list type when there are multiple types set.

Here's a curl example of this bug which shows this duplication;

Bugged request:
curl -XPOST -H "Content-type: application/json" -d '{ "@type": "by_collection", "contract": "0xed5af388653567af2f388e6224dc7c4b3241c544", "types": [ "CANCEL_LIST", "LIST", "MATCH" ] }' 'https://ethereum-api.rarible.org/v0.1/order/activities/search?continuation=1642781293000_61eada83fa963d40822ff05f&sort=EARLIEST_FIRST&size=2'

The two objects returned are identical. This bug does not persist when the types parameter only has "CANCEL_LIST" set. I have not explored further possible combinations.

Working request:
curl -XPOST -H "Content-type: application/json" -d '{ "@type": "by_collection", "contract": "0xed5af388653567af2f388e6224dc7c4b3241c544", "types": [ "CANCEL_LIST" ] }' 'https://ethereum-api.rarible.org/v0.1/order/activities/search?continuation=1642781293000_61eada83fa963d40822ff05f&sort=EARLIEST_FIRST&size=2'

P.S: Appreciate the work on the Rarible API, it's a strong powerhouse tool that I hope will continually be maintained in the distant future. All the best to the team, great work!

The "Get Started" guide does not work.

I saw Get Started and followed it, but it doesn't work.
docker/.env, docker/docker-compose.yaml file update is required.

please update or guide to build in local environment

TokenUpdateServiceTest.should send msg to external topic with meta

mvn package in nft (after allowing for illegal java.desktop/com.sun.imageio.plugins imports which also errors). This is on latest master. release/1.19 and release/1.20 not affected

[INFO] 
[INFO] Results:
[INFO] 
[ERROR] Failures: 
[ERROR]   TokenUpdateServiceTest.should send msg to external topic with meta 
Expecting any elements of:
  []
to match given predicate but none did.
[ERROR]   OpenseaTokenPropertiesResolverTest.should parse from json:44 
expected: TokenProperties(name=Feudalz, description=Feudalz emerged to protect their Peasants. When the system run smoothly, it lead to peace and prosperity for everyone., image=https://lh3.googleusercontent.com/wveucmeXBJfqyGiPZDhC1jVaJcx9SH0l2fiLmp2OdLD0KYpFzUIQD_9tTOV57cCDjJ4EjZT6X-Zoyym9eXXHTDxmVfCYzhC_RgkAU0A=s120, externalLink=https://feudalz.io, feeRecipient=0xc00f4b8022e4dc7f086d703328247cb6adf26858, sellerFeeBasisPoints=250)
but was : null
[ERROR]   StandardTokenPropertiesResolverTest.should parse from ipfs:63 
expected: TokenProperties(name=Feudalz, description=Feudalz emerged to protect their Peasants. When the system run smoothly, it lead to peace and prosperity for everyone., image=https://ipfs.io/ipfs/QmTGtDqnPi8TiQrSHqg44Lm7DNvvye6Tw4Z6eMMuMqkS6d, externalLink=https://feudalz.io, feeRecipient=0x6ef5129faca91e410fa27188495753a33c36e305, sellerFeeBasisPoints=250)
but was : null
[INFO] 
[ERROR] Tests run: 106, Failures: 3, Errors: 0, Skipped: 20
[INFO] 
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for protocol-nft-indexer 1.21:
[INFO] 
[INFO] protocol-nft-indexer ............................... SUCCESS [  1.386 s]
[INFO] protocol-nft-indexer-core .......................... FAILURE [01:17 min]
[INFO] protocol-nft-indexer-listener ...................... SKIPPED
[INFO] protocol-nft-indexer-api ........................... SKIPPED
[INFO] protocol-nft-indexer-migration ..................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  01:19 min
[INFO] Finished at: 2021-12-15T09:20:01-06:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.22.2:test (default-test) on project protocol-nft-indexer-core: There are test failures.
[ERROR] 
[ERROR] Please refer to /Users/primary/repos/whiskey-sierra/ethereum-indexer/nft/core/target/surefire-reports for the individual test results.
[ERROR] Please refer to dump files (if any exist) [date].dump, [date]-jvmRun[N].dump and [date].dumpstream.
[ERROR] -> [Help 1]

protocol-ethereum-contracts-nft not found

Parameter 0 of method sender in com.rarible.protocol.erc20.api.configuration.Erc20IndexerApiConfiguration required a bean of type 'scalether.core.MonoEthereum' that could not be found.

Build and run protocol-erc20-indexer-api on openjdk version "1.8.0_312"

Just trying to run locally without services (mongo, kafka, logging, parity, etc). Is this expected given these conditions? I would think Spring should be finding all the beans regardless.

***************************
APPLICATION FAILED TO START
***************************

Description:

Parameter 0 of method sender in com.rarible.protocol.erc20.api.configuration.Erc20IndexerApiConfiguration required a bean of type 'scalether.core.MonoEthereum' that could not be found.


Action:

Consider defining a bean of type 'scalether.core.MonoEthereum' in your configuration.

2021-12-10 18:17:19.804 WARN 69582 --- [ main] onfigReactiveWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'erc20TokenController' defined in URL [jar:file:/Users/primary/Desktop/ethereum-indexer/erc20/api/target/boot/protocol-erc20-indexer-api-boot.jar!/BOOT-INF/classes!/com/rarible/protocol/erc20/api/controller/Erc20TokenController.class]: Unsatisfied dependency expressed through constructor parameter 0; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'erc20Service' defined in URL [jar:file:/Users/primary/Desktop/ethereum-indexer/erc20/api/target/boot/protocol-erc20-indexer-api-boot.jar!/BOOT-INF/classes!/com/rarible/protocol/erc20/api/service/token/Erc20Service.class]: Unsatisfied dependency expressed through constructor parameter 1; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'contractService' defined in URL [jar:file:/Users/primary/Desktop/ethereum-indexer/erc20/api/target/boot/protocol-erc20-indexer-api-boot.jar!/BOOT-INF/lib/rarible-ethereum-contract-1.4.0.jar!/com/rarible/ethereum/contract/service/ContractService.class]: Unsatisfied dependency expressed through constructor parameter 1; nested exception is org.springframework.beans.factory.UnsatisfiedDependencyException: Error creating bean with name 'sender' defined in class path resource [com/rarible/protocol/erc20/api/configuration/Erc20IndexerApiConfiguration.class]: Unsatisfied dependency expressed through method 'sender' parameter 0; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No qualifying bean of type 'scalether.core.MonoEthereum' available: expected at least 1 bean which qualifies as autowire candidate. Dependency annotations: {}

NullPointerException "Parameter specified as non-null is null: method com.rarible.protocol.nft.api.configuration.NftIndexerApiProperties.<init>, parameter operator"

When I run the Nft Indexer Api Application on my local machine, it gives me the NullPointerException like this

"java.lang.NullPointerException: Parameter specified as non-null is null: method com.rarible.protocol.nft.api.configuration.NftIndexerApiProperties., parameter operator"

Please anyone can explain the cause of this issue and what I miss?

bootstrap.yml
spring:
application:
name: foo
cloud:
consul:
host: localhost
port: 8500

logging:
logstash:
tcp-socket:
enabled: true
destinations: localhost:4560

logback-spring.xml

<include resource="org/springframework/boot/logging/logback/defaults.xml" />
<include resource="org/springframework/boot/logging/logback/console-appender.xml" />

<springProperty name="APPLICATION_SERVICE_NAME" source="spring.application.name" defaultValue="unknown"/>
<springProperty name="APPLICATION_ENVIRONMENT" source="application.environment" defaultValue="dev"/>

<appender name="STASH" class="net.logstash.logback.appender.LogstashTcpSocketAppender">
    <destination>localhost:4560</destination>
    <encoder class="net.logstash.logback.encoder.LogstashEncoder">
        <customFields>{"service":"${APPLICATION_SERVICE_NAME}","environment":"${APPLICATION_ENVIRONMENT}"}</customFields>
    </encoder>
</appender>

<root level="DEBUG">
    <if condition='property("LOGSTASH_TCP_SOCKET_ENABLED").contains("true")'>
        <then>
            <appender-ref ref="STASH" />
        </then>
    </if>
    <appender-ref ref="CONSOLE" />
</root>

application-consul.yml

spring:
data:
mongodb:
uri: mongodb://${localhost:27017}
database: ${test}

redisUri: ${redis://localhost:6379}

parityUrls: ${https://speedy-nodes-nyc.moralis.io/xxxxxxxx/eth/mainnet}
parityWebSocketUrls: ${wss://speedy-nodes-nyc.moralis.io/xxxxxxxxx/eth/mainnet/ws}

rarible:
ethereum:
httpUrl: ${https://speedy-nodes-nyc.moralis.io/xxxxxxxxxx/eth/mainnet}
websocketUrl: ${wss://speedy-nodes-nyc.moralis.io/xxxxxxxxxx/eth/mainnet/ws}

common:
kafka-replica-set: ${localhost:9092}

blockchain:
scanner:
kafka:
broker-replica-set: ${localhost:9092}

ERROR [local-ethereum-order-listener 5/5] COPY ./target/boot/*.jar application.jar

Hey,

While trying to build the docker container on WSL, I'm getting this error.

failed to solve: lstat /var/lib/docker/tmp/buildkit-mount3224062329/target/boot: no such file or directory

Issues while trying to encode Buy/Sell orders

I'm having issues while trying to use the indexer API to encode the following sell order:

{
    "type": "RARIBLE_V2",
    "maker": "0x40fad45a745b8026c7a7dc8ae3e4d3e0022f0a14",
    "make": {
        "assetType": {
            "assetClass": "ERC1155",
            "contract": "0x88b48f654c30e99bc2e4a1559b4dcf1ad93fa656",
            "tokenId": "104973005838411526967788951744070314427519032974523733371440111381847342055524"
        },
        "value": "1"
    },
    "take": {
        "assetType": {
            "assetClass": "ERC20",
            "contract": "0xc778417e063141139fce010982780140aa0cd5ab"
        },
        "value": "1000000000000000"
    },
    "data": {
        "dataType": "RARIBLE_V2_DATA_V1",
        "payouts": [],
        "originFees": []
    },
    "salt": 721,
    "start": "1634706000",
    "end": "1634965200"
}

The error I'm getting is the following:

An error occurred while trying to encode Rarible order: (BAD_REQUEST): Instantiation of [simple type, class com.rarible.protocol.dto.RaribleV2OrderFormDto] value failed for JSON property signature due to missing (therefore NULL) value for creator parameter signature which is a non-nullable type

I'm running some tests on Rinkeby (https://api-staging.rarible.com/protocol/v0.1/ethereum/order/encoder/order) Did something change in the JSON schema for buy/sell orders?

Why doesn't my Ethereum node have any peers ?

Hi, I'm working on Ethereum indexer, try to connect mainnet using openethereum by rarible. it's connected to mainnet, listening command also returns true but it can't find any peers. I've already tried the syncing command that also return false.but My bandwidth is good

.

How do I configure the indexer to listen to LooksRare order events?

What configurations do I need to add so that the indexer is able to listen to order events from LooksRare? Running the indexer with default settings from the Getting Started section doesn't listen to LooksRare order events.

Thanks in advance.

Could you please let me know the uses of Kafka in the Ethereum indexer?

In the SDK, it says Kafka is used to handling events. But who consumes those events and why do we need to consume them. Due to the fact that all the data is stored in Mongo DB, I'm confused about the use of Kafka. Could someone please explain this to me? Thank you in advance.

Bean of type 'com.rarible.protocol.order.core.repository.order.OpenSeaOrderRepository' could not be found

***************************
APPLICATION FAILED TO START
***************************

Description:

Parameter 0 of constructor in com.rarible.protocol.order.listener.service.order.LoadOpenSeaOrdersTaskHandler required a bean of type 'com.rarible.protocol.order.core.repository.order.OpenSeaOrderRepository' that could not be found.


Action:

Consider defining a bean of type 'com.rarible.protocol.order.core.repository.order.OpenSeaOrderRepository' in your configuration.

Pool#acquire(Duration) has been pending for more than the configured timeout of 45000ms

Getting this problem on the https://api.rarible.org/v0.1/items/byOwner endpoint on around 2/3 requests, not sure if it is due to load on that server or what. Might take a stab at running my own instance of this API. Full error below:

Pool#acquire(Duration) has been pending for more than the configured timeout of 45000ms; nested exception is reactor.netty.internal.shaded.reactor.pool.PoolAcquireTimeoutException: Pool#acquire(Duration) has been pending for more than the configured timeout of 45000ms

Additionally, I've noticed that there's some huge inconsistencies in the results between the API used on the Rarible website, the /v0.1/items/byOwner endpoint with the V1 search engine and the LEGACY search engine. I've seen assets that were transferred away from someone over a year ago still listed as being under their ownership (on rarible.org), so I'm not quite sure what that's all about. I'll see if I can get you guys some examples.

I have noticed that /v0.1/items/byOwner with the V1 search engine returns the best results by far.

The indexer crashes after 20 mins.

Hi,
I got the a small part of the indexer to work, but after 20mins-1hr running, it crashes.

Connections to Mongo gets a Timeout and the NFT Listener stops working.

What is the recommended setup for the mongo instance and the application?

Also, how long does it take to index the NFT data?

Maven project depends on private repositories

I have configured my maven ~/.m2/settings.xml thusly (see https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-apache-maven-registry):

<settings xmlns="http://maven.apache.org/SETTINGS/1.0.0"
          xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://maven.apache.org/SETTINGS/1.0.0
                      http://maven.apache.org/xsd/settings-1.0.0.xsd">

    <activeProfiles>
        <activeProfile>rarible</activeProfile>
    </activeProfiles>

    <profiles>
        <profile>
            <id>rarible</id>
            <repositories>
                <repository>
                    <id>central</id>
                    <url>https://repo1.maven.org/maven2</url>
                </repository>
                <repository>
                    <id>rarible</id>
                    <url>https://maven.pkg.github.com/rarible/*</url>
                    <snapshots>
                        <enabled>true</enabled>
                    </snapshots>
                </repository>
            </repositories>
        </profile>
    </profiles>

    <servers>
        <server>
            <id>rarible</id>
            <username>silasdavis</username>
            <password>REDACTED</password>
        </server>
    </servers>
</settings>

However I get various errors (maven complaining about/blocking non http in favour of https) but the the real issue is your parent POM depends on private Nexus repositories: https://github.com/rarible/parent-pom/blob/master/pom.xml#L19-L39

I note that this project was open sourced less than a month ago so its still early days. Is there any chance we could get a build that will work without access to private repos?

Add docker compose configuration

I am interested in taking this project for a spin, I understand it depends on Kafka and MonogDB and looks like it itself has a number of separate services. A convenient way to understand a distributed system is to have a working executable runtime via docker compose. It makes it clear how each service boots and the docker compose file serves as a wiring diagram.

I'd be willing to work on this you are interested and can give some pointers. It would consist in:

Dockerfiles for each separate services hosted in this repo
Top-level docker-compose.yml configuring databases and services

blocked for me on #30

Open source helm templates?

Any chance the helm templates will be open sourced? There is quite a bit of run time context missing in this project.

Also, it's unclear whether the values.yaml in this repo is maintained and up to date, as it had a typo up until this https://github.com/rarible/ethereum-indexer/commit/47e451fd5c1fe1030792a41fb3960115e918a599. I suspect it isn't used for actual deploys?

Maven repos are not found when building latest indexer

When building, looks like the maven repos for older versions are not found on rarible's or central's maven repo urls

Downloading from nexus-ext-maven-public: https://repo.rarible.org/repository/maven-public/com/rarible/core/rarible-core-parent/2.4.9/rarible-core-parent-2.4.9.pom
Downloading from central: https://repo.maven.apache.org/maven2/com/rarible/core/rarible-core-parent/2.4.9/rarible-core-parent-2.4.9.pom
Downloading from nexus-ext-maven-public: https://repo.rarible.org/repository/maven-public/com/rarible/core/rarible-core-parent/2.3.8/rarible-core-parent-2.3.8.pom
Downloading from central: https://repo.maven.apache.org/maven2/com/rarible/core/rarible-core-parent/2.3.8/rarible-core-parent-2.3.8.pom
Downloading from nexus-ext-maven-public: https://repo.rarible.org/repository/maven-public/com/rarible/ethereum/rarible-ethereum-parent/1.5.7/rarible-ethereum-parent-1.5.7.pom
Downloading from central: https://repo.maven.apache.org/maven2/com/rarible/ethereum/rarible-ethereum-parent/1.5.7/rarible-ethereum-parent-1.5.7.pom
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[ERROR] Non-resolvable import POM: Could not find artifact com.rarible.core:rarible-core-parent:pom:2.4.9 in nexus-ext-maven-public (https://repo.rarible.org/repository/maven-public/) @ com.rarible.ethereum:rarible-ethereum-parent:1.6.0, /home/hemant/.m2/repository/com/rarible/ethereum/rarible-ethereum-parent/1.6.0/rarible-ethereum-parent-1.6.0.pom, line 53, column 19
[ERROR] Non-resolvable import POM: Could not find artifact com.rarible.core:rarible-core-parent:pom:2.3.8 in nexus-ext-maven-public (https://repo.rarible.org/repository/maven-public/) @ com.rarible.protocol.ethereum:rarible-ethereum-openapi:1.33.0, /home/hemant/.m2/repository/com/rarible/protocol/ethereum/rarible-ethereum-openapi/1.33.0/rarible-ethereum-openapi-1.33.0.pom, line 81, column 19
[ERROR] Non-resolvable import POM: Could not find artifact com.rarible.ethereum:rarible-ethereum-parent:pom:1.5.7 in nexus-ext-maven-public (https://repo.rarible.org/repository/maven-public/) @ com.rarible.protocol.ethereum:rarible-ethereum-openapi:1.33.0, /home/hemant/.m2/repository/com/rarible/protocol/ethereum/rarible-ethereum-openapi/1.33.0/rarible-ethereum-openapi-1.33.0.pom, line 88, column 19
[ERROR] Non-resolvable import POM: com.rarible.core:rarible-core-parent:pom:2.4.9 was not found in https://repo.rarible.org/repository/maven-public/ during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of nexus-ext-maven-public has elapsed or updates are forced @ com.rarible.ethereum:rarible-ethereum-parent:1.6.0, /home/hemant/.m2/repository/com/rarible/ethereum/rarible-ethereum-parent/1.6.0/rarible-ethereum-parent-1.6.0.pom, line 53, column 19
 @ 
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]   
[ERROR]   The project com.rarible.protocol:rarible-protocol-ethereum-indexer:1.32 (/home/hemant/work/indexer/rarible/ethereum-indexer-temp/pom.xml) has 4 errors
[ERROR]     Non-resolvable import POM: Could not find artifact com.rarible.core:rarible-core-parent:pom:2.4.9 in nexus-ext-maven-public (https://repo.rarible.org/repository/maven-public/) @ com.rarible.ethereum:rarible-ethereum-parent:1.6.0, /home/hemant/.m2/repository/com/rarible/ethereum/rarible-ethereum-parent/1.6.0/rarible-ethereum-parent-1.6.0.pom, line 53, column 19 -> [Help 2]
[ERROR]     Non-resolvable import POM: Could not find artifact com.rarible.core:rarible-core-parent:pom:2.3.8 in nexus-ext-maven-public (https://repo.rarible.org/repository/maven-public/) @ com.rarible.protocol.ethereum:rarible-ethereum-openapi:1.33.0, /home/hemant/.m2/repository/com/rarible/protocol/ethereum/rarible-ethereum-openapi/1.33.0/rarible-ethereum-openapi-1.33.0.pom, line 81, column 19 -> [Help 2]
[ERROR]     Non-resolvable import POM: Could not find artifact com.rarible.ethereum:rarible-ethereum-parent:pom:1.5.7 in nexus-ext-maven-public (https://repo.rarible.org/repository/maven-public/) @ com.rarible.protocol.ethereum:rarible-ethereum-openapi:1.33.0, /home/hemant/.m2/repository/com/rarible/protocol/ethereum/rarible-ethereum-openapi/1.33.0/rarible-ethereum-openapi-1.33.0.pom, line 88, column 19 -> [Help 2]
[ERROR]     Non-resolvable import POM: com.rarible.core:rarible-core-parent:pom:2.4.9 was not found in https://repo.rarible.org/repository/maven-public/ during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of nexus-ext-maven-public has elapsed or updates are forced @ com.rarible.ethereum:rarible-ethereum-parent:1.6.0, /home/hemant/.m2/repository/com/rarible/ethereum/rarible-ethereum-parent/1.6.0/rarible-ethereum-parent-1.6.0.pom, line 53, column 19 -> [Help 2]
[ERROR]

Production values for erc721Rarible, erc721RaribleUser, erc1155Rarible, erc1155RaribleUser

dev/staging application YAML have values for erc721Rarible, erc721RaribleUser, erc1155Rarible, erc1155RaribleUser, but not prod/mainnet. They aren't secrets, so can they be shared? I assume a two of them from https://etherscan.io/accounts/label/rarible but unsure about the User addresses.

nft/listener/src/main/resources/config/application-dev.yml:

common:
  royaltyRegistryAddress: "0x1747757768Ff4AA61390B1ed3AA019141605717B"
  factory:
    erc721Rarible: "0x2e6fAFAD2Af251Add7400cBD98C4620772692c49"
    erc721RaribleUser: "0xCc228ecb71B3456AeCb35D2dE66E228DAFd7Ae2d"
    erc1155Rarible: "0xbF90b7F8d59BE6D08dBd47fF984a22877996E91F"
    erc1155RaribleUser: "0x71Cf04F4f75eEb3262B1AB7D8438432EC4a30ee4"

How to run this indexer?

How to run this indexer?
Can we run this indexer in a market place which is built without using rarible protocol?
If it is possible, are there any configurations to be done and what are they?

Support OpenSea's SeaPort orders

When querying order data from the API, I only see Wyvern listings, that are currently being deprecated. I do not believe SeaPort orders are yet supported.

Example query;

https://ethereum-api.rarible.org/v0.1/order/orders/sell/byItemAndByStatus?contract=0xbce3781ae7ca1a5e050bd9c4c77369867ebc307e&tokenId=4619

for https://opensea.io/assets/ethereum/0xbce3781ae7ca1a5e050bd9c4c77369867ebc307e/4619

How to run this indexer, I didn't find where to configure mongodb

Return API String or Object

Hey!

Some API responses that return the ID have changed but the SDK still expecting the old ones.

From: id: "BLOCKCHAIN:CONTRACT"
To: id: { type: "BLOCKCHAIN", value: "CONTRACT"}

It's not clear if the error is in the indexer or the SDK

ref: rarible/protocol#262

protocol-nft-indexer-api: PendingTransactionService.kt: Unresolved reference: factory

openjdk version "1.8.0_312"

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for protocol-nft-indexer 1.21:
[INFO] 
[INFO] protocol-nft-indexer ............................... SUCCESS [  1.938 s]
[INFO] protocol-nft-indexer-contract ...................... SUCCESS [ 15.024 s]
[INFO] protocol-nft-indexer-core .......................... SUCCESS [01:31 min]
[INFO] protocol-nft-indexer-listener ...................... SUCCESS [01:11 min]
[INFO] protocol-nft-indexer-api ........................... FAILURE [  2.666 s]
[INFO] protocol-nft-indexer-migration ..................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  03:02 min
[INFO] Finished at: 2021-12-10T09:36:59-06:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.jetbrains.kotlin:kotlin-maven-plugin:1.5.31:compile (compile) on project protocol-nft-indexer-api: Compilation failure: Compilation failure: 
[ERROR] /Users/primary/Desktop/ethereum-indexer/nft/api/src/main/kotlin/com/rarible/protocol/nft/api/service/pending/PendingTransactionService.kt:[62,34] Unresolved reference: factory
[ERROR] /Users/primary/Desktop/ethereum-indexer/nft/api/src/main/kotlin/com/rarible/protocol/nft/api/service/pending/PendingTransactionService.kt:[63,34] Unresolved reference: factory
[ERROR] /Users/primary/Desktop/ethereum-indexer/nft/api/src/main/kotlin/com/rarible/protocol/nft/api/service/pending/PendingTransactionService.kt:[67,34] Unresolved reference: factory
[ERROR] /Users/primary/Desktop/ethereum-indexer/nft/api/src/main/kotlin/com/rarible/protocol/nft/api/service/pending/PendingTransactionService.kt:[68,34] Unresolved reference: factory
[ERROR] /Users/primary/Desktop/ethereum-indexer/nft/api/src/main/kotlin/com/rarible/protocol/nft/api/service/pending/PendingTransactionService.kt:[124,76] Unresolved reference: factory
[ERROR] /Users/primary/Desktop/ethereum-indexer/nft/api/src/main/kotlin/com/rarible/protocol/nft/api/service/pending/PendingTransactionService.kt:[138,80] Unresolved reference: factory
[ERROR] /Users/primary/Desktop/ethereum-indexer/nft/api/src/main/kotlin/com/rarible/protocol/nft/api/service/pending/PendingTransactionService.kt:[158,77] Unresolved reference: factory
[ERROR] /Users/primary/Desktop/ethereum-indexer/nft/api/src/main/kotlin/com/rarible/protocol/nft/api/service/pending/PendingTransactionService.kt:[172,81] Unresolved reference: factory
[ERROR] -> [Help 1]

Symbol is declared in module 'java.desktop' which does not export package 'com.sun.imageio.plugins...

[INFO] Reactor Summary for protocol-nft-indexer 1.21:
[INFO] 
[INFO] protocol-nft-indexer ............................... SUCCESS [  1.655 s]
[INFO] protocol-nft-indexer-contract ...................... SUCCESS [ 14.623 s]
[INFO] protocol-nft-indexer-core .......................... FAILURE [ 13.260 s]
[INFO] protocol-nft-indexer-listener ...................... SKIPPED
[INFO] protocol-nft-indexer-api ........................... SKIPPED
[INFO] protocol-nft-indexer-migration ..................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  29.814 s
[INFO] Finished at: 2021-12-09T18:21:05-06:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.jetbrains.kotlin:kotlin-maven-plugin:1.5.31:compile (compile) on project protocol-nft-indexer-core: Compilation failure: Compilation failure: 
[ERROR] /Users/primary/Desktop/ethereum-indexer/nft/core/src/main/kotlin/com/rarible/protocol/nft/core/service/item/meta/MediaMetaService.kt:[15,36] Symbol is declared in module 'java.desktop' which does not export package 'com.sun.imageio.plugins.bmp'
[ERROR] /Users/primary/Desktop/ethereum-indexer/nft/core/src/main/kotlin/com/rarible/protocol/nft/core/service/item/meta/MediaMetaService.kt:[16,36] Symbol is declared in module 'java.desktop' which does not export package 'com.sun.imageio.plugins.gif'
[ERROR] /Users/primary/Desktop/ethereum-indexer/nft/core/src/main/kotlin/com/rarible/protocol/nft/core/service/item/meta/MediaMetaService.kt:[17,37] Symbol is declared in module 'java.desktop' which does not export package 'com.sun.imageio.plugins.jpeg'
[ERROR] /Users/primary/Desktop/ethereum-indexer/nft/core/src/main/kotlin/com/rarible/protocol/nft/core/service/item/meta/MediaMetaService.kt:[18,36] Symbol is declared in module 'java.desktop' which does not export package 'com.sun.imageio.plugins.png'
[ERROR] /Users/primary/Desktop/ethereum-indexer/nft/core/src/main/kotlin/com/rarible/protocol/nft/core/service/item/meta/MediaMetaService.kt:[99,36] Symbol is declared in module 'java.desktop' which does not export package 'com.sun.imageio.plugins.gif'
[ERROR] /Users/primary/Desktop/ethereum-indexer/nft/core/src/main/kotlin/com/rarible/protocol/nft/core/service/item/meta/MediaMetaService.kt:[99,88] Symbol is declared in module 'java.desktop' which does not export package 'com.sun.imageio.plugins.gif'
[ERROR] /Users/primary/Desktop/ethereum-indexer/nft/core/src/main/kotlin/com/rarible/protocol/nft/core/service/item/meta/MediaMetaService.kt:[99,109] Symbol is declared in module 'java.desktop' which does not export package 'com.sun.imageio.plugins.gif'
[ERROR] /Users/primary/Desktop/ethereum-indexer/nft/core/src/main/kotlin/com/rarible/protocol/nft/core/service/item/meta/MediaMetaService.kt:[100,36] Symbol is declared in module 'java.desktop' which does not export package 'com.sun.imageio.plugins.jpeg'
[ERROR] /Users/primary/Desktop/ethereum-indexer/nft/core/src/main/kotlin/com/rarible/protocol/nft/core/service/item/meta/MediaMetaService.kt:[101,36] Symbol is declared in module 'java.desktop' which does not export package 'com.sun.imageio.plugins.bmp'
[ERROR] /Users/primary/Desktop/ethereum-indexer/nft/core/src/main/kotlin/com/rarible/protocol/nft/core/service/item/meta/MediaMetaService.kt:[102,36] Symbol is declared in module 'java.desktop' which does not export package 'com.sun.imageio.plugins.png'
[ERROR] /Users/primary/Desktop/ethereum-indexer/nft/core/src/main/kotlin/com/rarible/protocol/nft/core/service/item/meta/MediaMetaService.kt:[103,36] Symbol is declared in module 'java.desktop' which does not export package 'com.sun.imageio.plugins.png'
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <args> -rf :protocol-nft-indexer-core

retrying connection to the node - java.net.UnknownHostException

Hi all, I am trying to indexing rarible mainnet logs, While deploy listeners, unknown host exception error occurs, retrying connection to the node and log also not reflect in db. i attach screenshot below, kindly help me. thanks in advance.

RARIBLE_ETHEREUM_HTTP-URL AND RARIBLE_ETHEREUM_WEBSOCKET-URL

https://github.com/rarible/ethereum-indexer/blob/master/docker/docker-compose.yaml#L21
https://github.com/rarible/ethereum-indexer/blob/master/docker/docker-compose.yaml#L22

should be RARIBLE_ETHEREUM_HTTP_URL and RARIBLE_ETHEREUM_WEBSOCKET_URL

[Compile Problem] Could not find artifact com.rarible.core:rarible-core-parent:pom:2.4.9 in nexus-ext-maven-public

Describe what happened (or what feature you want)

Using itelliJ IDE
Executing the mvn clean package -DskipTests command returns an error as follows:

Could not find artifact com.rarible.core:rarible-core-parent:pom:2.4.9 in nexus-ext-maven-public (https://repo.rarible.org/repository/maven-public/)

Using cli the error as follows:

[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[ERROR] Non-resolvable import POM: Failure to find com.rarible.core:rarible-core-parent:pom:2.4.9 in https://repo.rarible.org/repository/maven-public/ was cached in the local repository, resolution will not be reattempted until the update interval of nexus-ext-maven-public has elapsed or updates are forced @ com.rarible.ethereum:rarible-ethereum-parent:1.6.0, /root/.m2/repository/com/rarible/ethereum/rarible-ethereum-parent/1.6.0/rarible-ethereum-parent-1.6.0.pom, line 53, column 19
[ERROR] Non-resolvable import POM: Failure to find com.rarible.protocol.ethereum:rarible-ethereum-openapi:pom:1.30.1 in https://repo.rarible.org/repository/maven-public/ was cached in the local repository, resolution will not be reattempted until the update interval of nexus-ext-maven-public has elapsed or updates are forced @ com.rarible.protocol:rarible-protocol-ethereum-indexer:${revision}, /home/deq/Desktop/Projects/ethereum-indexer/pom.xml, line 70, column 25
[ERROR] Non-resolvable import POM: Failure to find com.rarible.blockchain.scanner:rarible-blockchain-scanner:pom:2.2.26 in https://repo.rarible.org/repository/maven-public/ was cached in the local repository, resolution will not be reattempted until the update interval of nexus-ext-maven-public has elapsed or updates are forced @ com.rarible.protocol:rarible-protocol-ethereum-indexer:${revision}, /home/deq/Desktop/Projects/ethereum-indexer/pom.xml, line 77, column 25

Tell us your environment

ubuntu 64-bit

Is it possible to run particular indexer listener test case ?

Hi all, i am setup ethereum indexer and try to unit test particular indexer like erc20-listener-test, i got error like below attached screenshot. if any solution to fix that error please mention. thanks in advance !