go
go copied to clipboard
stellar
Stellar's public monorepo of go code
Hi team, I recently experienced the same issue as https://github.com/stellar/go/issues/2714 except my setup is a bit different. Horizon version 2.8.1 Kubernete 1.21 **Steps to repro:** Launch remote-captive-core instance (e.g localhost:8001)...
### What version are you using? Horizon 2.14 Go 1.17 ### What did you do? Follow the documentation steps to setup Remote Captive Core: https://developers.stellar.org/docs/run-api-server/remote-core/ ### What did you expect...
### What problem does your feature solve? Performance degradations caused by code changes can be subtle in their cause and go unnoticed. For instance, in https://github.com/stellar/go/pull/4178 @paulbellamy and I had...
### What problem does your feature solve? How should filters handle rule config changes over time, i.e. lifecycle. Should filter rule changes retro-actively backfill history per changes, etc. ### What...
### What problem does your feature solve? Capturing sponsored account related tx/ops data during filtering which is normally one-hop away and not dynamically captured during normal account whitelist rule processing....
### What problem does your feature solve? Capturing asset related tx/ops data during filtering which is normally one-hop away and not dynamically captured during normal account whitelist rule processing. ###...
### What problem does your feature solve? Capturing account oriented tx/ops data during filtering which is normally one-hop away and not dynamically captured during normal asset whitelist rule processing. ###...
Horizon should check on init stage if the connected stellar-core version is compatible. Otherwise it should print error and exit. See: https://github.com/stellar/go/issues/371 #455. To discuss: do we need Horizon-Core protocol...
the trade streaming feature in ticker exits when it receives a 429 (too many requests) error from horizon. ticker should retry the connection with an exponential backoff.
### What problem does your feature solve? Right now there's not an endpoint that gives an aggregate amount of lumens held by accounts. An example of when this is needed...
