Topic: Getting current block reward from *coind (Read 716 times)

I've set up an instance of mmcfe-ng with moopless' stratum-mining-litecoin to get a Bitgem pool running.  One snag I've run into is with mining-income estimates.  The Bitgem block subsidy appears to have a bit more variability than some other coins (lately, it's actually crept up a little bit).  I know that the coinbasevalue entry in the output of the getblocktemplate RPC call is supposed to have the value I want (though it appears off in bitgemd by a factor of 100, but that's another matter), but calling getblocktemplate with no parameters can also return a bunch of transactions (especially with bitcoind) that generates lots of activity.  (For example, while the JSON-formatted output of bitgemd getblocktemplate currently returns only 603 bytes, comparable output from bitcoind getblocktemplate returns nearly 2 MB!)

This makes it look like getblocktemplate can take some options, but I'm having a bit of difficulty puzzling them out to see if I can get it to do what I want it to do.  If I could get it to just return a coinbase transaction without gathering up a bunch of transactions from the memory pool, that should run much faster and would be more feasible to call as needed to get the included coinbasevalue.  Is there some invocation of getblocktemplate that will do this, short of tweaking the *coind config file's block-generation parameters (which would most likely be a Bad Idea on a mining-pool rig)? It looks like sigoplimit and sizelimit might be able to control this, but whenever I try something like this:


the result is no different than without the parameters.  Is there something I'm doing wrong here?