getstandardfee is being adopted, and we have been actively and directly reaching out to wallet developers over the last few weeks/months to keep them up to date and advocate for its use.
- Use getstandardfee for transaction fees, supporting Zebra’s 1,000-zat logical-action rate · Issue #357 · zcashme/zns-mint · GitHub
- Zcash: get the fee from getstandardfee and add a 'pay more for inclusion' option · Issue #7310 · horizontalsystems/unstoppable-wallet-ios · GitHub
- Zcash: get the fee from getstandardfee and add a 'pay more for inclusion' option · Issue #9806 · horizontalsystems/unstoppable-wallet-android · GitHub
Yes, getstandardfee is the indirection for the dynamic fee market Shielded Labs is building. It allows wallets to follow fee changes automatically, which is how we avoid threads exactly like this one :). A world where every node and wallet has their own constant(s) that they need to keep track of and update is, IMO, haphazard.
Wallets only reading from indexers is exactly the intended path. lightwalletd v0.6.1 already serves GetStandardFee over gRPC, relaying the node’s value. The interface is on the full node because the node already holds all the data the estimator will need. It’s a matter of convenience and availability.
Updating it to 1000 and separating it from mempool admission policy is not what I would have recommended. I think the nodes should have the same marginal fee value and that’s what should be communicated, and I’m agnostic as to whether that value is 400 or 1000. It’s just important to me that wallets don’t have to pay attention to what the node devs are doing like they currently do.