Josh Rickmar
Josh Rickmar
I'm unsure how it would work logistically (and may depend on how frequently you wish to make changes), but even without direct write access, I would gladly pull any changes...
If you are going to use wsrpc as an example for ping-pong, see https://github.com/jrick/wsrpc/compare/v2.0.0...v2.1.1 which is most of that diff but also fixes a couple oversights.
This all assumes that the miner or pool wishes to be identified. They could not provide any identification at all and mine using a unique address and you wouldn't know...
No, and `vgo` will actually prefer to fetch a module bundle (zip file) instead of using `git` directly (this was the original `vgo` default but was disabled for github.com recently...
If the security of multiple servers, and especially servers we don't control, is a concern, I believe we should go entirely self hosted. This would be the first step towards...
See decred/dcrwallet#1538 which performs this conversion for the dcrwallet main module.
Are you by chance running a very large --gaplimit option in dcrwallet? and if so, why?
OK.. well just so are aware, even with a large gap limit, there is still the possibility that none of the addresses will be used and eventually wraparround will occur...
Sorry but that API is borderline unusable if that is how it is intended to work. We need to inspect the k/v to determine whether to delete it before moving...
@chuckg the bug isn't in my iterator wrapper apis but in bolt itself. The linked test is testing the bolt apis without using any of our projects db wrappers over...