go
go copied to clipboard
stellar
Stellar's public monorepo of go code
In https://github.com/stellar/go/issues/5059 , we discovered that the payments endpoint is performant because Stellar ledgers tend to be dense with payment operations. However, if the distribution of operations in a Stellar...
If Horizon is running captive core with BucketsDB enabled, Horizon should be able to restart quickly as long as we run captive core so that it resumes from the LCL...
Horizon currently has two modes of ingestion: 1. The deprecated [DatabaseBackend](https://github.com/stellar/go/blob/master/ingest/ledgerbackend/database_backend.go) which extracts ledgers from Stellar Core's postgres DB 2. Captive Core We need to add a third mode which...
### What problem does your feature solve? trade aggregations is implemented within horizon, it is intertwined into ingestion, db, and api. horizon ingestion must spend extra time doing trade aggregation...
### What version are you using? horizon: 2.28.1-433831fb25cce9a1a64f5125f2c132217adf4fca core: stellar-core 20.1.0 (114b833e755400178a57142f45b7fb892ddb034f) ### What did you do? Request horizon claimable balance API https://horizon.stellar.org/claimable_balances/?asset=AQUA%3AGBNZILSTVQZ4R7IKQDGHYGY2QXL5QOFJYQMXPKWRRM5PAV7Y4M67AQUA&claimant=GDNYKQZZHPDHN3WUUD5JPOK7TKUBLHUPQ3DHRI5A4ZUWYLBG22KTZYIN&cursor=38761565-00000000f52a2d584325cf460a301ec2c1a78e4ef6914a7c8189bb88190b8f2b3c1c6d92
"horizon_version": "2.28.0-24a7e9f27184ccc8b0e7a7bbf3839fcdcecc012d", "core_version": "stellar-core 20.1.0 (114b833e755400178a57142f45b7fb892ddb034f)", "ingest_latest_ledger": 0, "history_latest_ledger": 0, "history_latest_ledger_closed_at": "0001-01-01T00:00:00Z", "history_elder_ledger": 0, "core_latest_ledger": 50237470, "network_passphrase": "Public Global Stellar Network ; September 2015", "current_protocol_version": 19, "supported_protocol_version": 20, "core_supported_protocol_version": 20...
I observed a particular behavior that Horizon would constantly retry when encountering certain transient errors: 1. When investigating a crash-loop (Slack thread), Horizon would run `catchup` and `new-db` over and...
Archivist verifies the tx set hash [here](https://github.com/stellar/go/blob/77cb331d374d53f632cd1571c96d07a8ec143dda/historyarchive/verify.go#L109), but starting from v20, `txSet` in `TransactionHistoryEntry` will be [empty](https://github.com/stellar/stellar-xdr/blob/bb54e505f814386a3f45172e0b7e95b7badbe969/Stellar-ledger.x#L260). Core instead hashes `generalizedTxSet` from the `TransactionHistoryEntry` extension, which archivist needs to do...
When streaming a non-existing account the connection is currently closed immediately with a 404. It'd be nice if the endpoint could keep the connection alive and send an event when...
### What problem does your feature solve? `NETWORK=testnet|pubnet` usage will trigger default hardcoded archive url configuration on `HISTORY_ARCHIVE_URLS` to public stellar archive hosts, which doesn't promote decentralization in practice. `HISTORY_ARCHIVE_URLS`...