@Zhivko is exactly right, @dmydlarz. It’s hard to believe, but the fee really is that low.
Bear in mind that BTG supports SegWit, so with our 1 MB base block size, we can support weights close to 4 MB between the base block and the SegWIt block space. We very rarely see block size go anywhere near those limits (except for periods where a large organization is programmatically cleaning up old dust.)
The only thing I’ll add - the
estimatefee call is for Core Wallet v0.15. The new core wallet, v0.17.1 (coming out as Release Candidate) deprecated that command, and you’ll need to use
estimatesmartfee. But it gives the same result you’re getting from the API. Here they are, right now:
However, as @h4x3rotab noted, you can usually set the minimum 1 sat per Byte, 0.00000001 BTG (or 1000 sat per Kbyte- 0.00001 BTG) and the transaction will nearly always go through in the very next block.