-
Notifications
You must be signed in to change notification settings - Fork 129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integration/Stellar #949
base: master
Are you sure you want to change the base?
Integration/Stellar #949
Conversation
…a into intergation/stellar-dia
…nge StellarScraper adopted.
…d of go version binding
…lar-dia # Conflicts: # cmd/assetCollectionService/go.mod # cmd/assetCollectionService/go.sum # cmd/assetCollectionService/main.go
f789546
to
d0582ed
Compare
d0582ed
to
1b9c8e2
Compare
log = log.WithField("tomlURL", tomlURL) | ||
|
||
tr := &http.Transport{ | ||
TLSClientConfig: &tls.Config{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is necessary to take into account that some TOML files for Stellar assets are uploaded by their issuers onto servers without a certificate, or with an invalid certificate. Such assets will be skipped and not stored in the DIA database.
It is possible to accept these TOML files; to do this, you need to specify a parameter InsecureSkipVerify: true
in the TLS client. However, this parameter will not be accepted by your pull request validator DeepSource.
…ed from env - with horizon url
Integration with the Stellar protocol has been added.
The following services have been updated to support Stellar:
Exchange scraper - streams all trades from Stellar
Liquidity scraper - reads and stores Stellar LPs’ data
Asset collector - reads and stores Stellar assets’ data
Work with the horizon client (Stellar Go SDK) was implemented.
Adapters have been added to convert Stellar data objects to those of DIA.
Additionally, building scripts has been added.