Quoting the relevant commit message:
daemon, wallet: new pay for RPC use system
Daemons intended for public use can be set up to require payment
in the form of hashes in exchange for RPC service. This enables
public daemons to receive payment for their work over a large
number of calls. This system behaves similarly to a pool, so
payment takes the form of ...
There is no command to permanently ban, but you can set a lengthy ban time using the daemon command ban <IP> [<seconds>], or using the RPC method set_bans.
So if you set the seconds parameter to 4294967295, that will ban for just over 136 years.
As I answered to your previous question, you do not need to forward any ports for the p2p interface. This is the interface nodes use to send each other data, such as blocks. transactions and peerlists. Other nodes can sync with you fine without router port forwarding because when you initiate an outbound connection to a peer, it is kept open, thus data can ...
The p2p interface doesn't require port forwarding at the router but the RPC interface does for remote access. Therefore if you wanted to help users needing a public remote node (e.g. for using a light wallet), you'd need to port forward to whatever RPC port you decide to listen on (--rpc-bind-port, the default being 18081). If you're going to do this, I ...
The file you linked is not a Monero library. At most, all it shows is a couple of examples of calling the RPC methods, for which is an easy task in any coding language. Just run the monero-wallet-rpc application and call its HTTP methods.
If you want/need to use a library that wraps that up further, for example because you don't know how to call a HTTP ...
There are no options walletnotify or blocknotify, you probably want block-notify.
See monerod --help for all the available options and syntax.
Running the daemon with the --config flag I get...
There is no option called --config, it's --config-file.