herald.go
herald.go copied to clipboard
lbryio
The initial batch of blockchain.address.{get_balance,get_history,...} RPCs are lacking the ability to report things happening in unconfirmed TXs. Need to monitor the mempool tables written by scribe? Or contact lbcd?
I don't see lbry-sdk calling these. So lower priority.
This data was gathered with some local changes plus my published branch herald.go/blockchain_tx_rpc1: [failure.txt](https://github.com/lbryio/herald.go/files/10045483/failure.txt) It's not completing, even though some messages are emitted like these: ``` 2022-11-18 17:12:30,189 - lbry.wallet.ledger...
Old: ```the transaction was rejected by network rules.\n\nMissing inputs\n...``` New: ```ejected: orphan transaction 7e27725626174a5e19ebab2dd3fcafce1ca68971bd5710d0a0112f46bee90246 references outputs of unknown or fully-spent transaction fbdb1ce2c895c4bd82fef905b35a10a7bcef68972f260c7be1dbab02f239000d\n[0``` Old: ```'the transaction was rejected by network rules.\n\ntxn-mempool-conflict...
blockchain.claimtrie.resolve is the only one registered for JSON service. Need to register the others.
Some of these are in progress under: https://github.com/lbryio/herald.go/pull/69 Remaining ones: server.ping server.payment_address server.donation_address server.peers.subscribe
Right now, a `--debug` option is supported. But we need to have more options to control the logging. Some logging sites are `Warn()` or higher just to ensure messages show...
If you immediately start and then CRTL+C herald it (I suspect) continues to load the rocksdb database before it initiates shutdown. Ideally this behavior should be avoided. However it does...
herald.go can be run and connected to by a desktop client that can sync its wallet and otherwise do everything that can be done on desktop
