NanoRPCProxy VS nano-dpow

https://github.com/Joohansson/NanoRPCProxy https://github.com/dev-ptera/nano-rpc-proxy

Waiting for boomPoW v2 support on the NanoRPCProxy: https://github.com/Joohansson/NanoRPCProxy/pull/131

the PR adding support for BPoW v2 to NanoRPCProxy (that's used by 2 or 3 nault community nodes) can be tracked here: https://github.com/Joohansson/NanoRPCProxy/pull/131

Or if you need to watch a particular address you can bookmark the link. For example, to watch the saviour binance refund bot using api.nanos.cs:

https://powernode.cc/api or https://api.nanos.cc/ , also MyNanoNinja has one I believe

You can send RPC request to one of the public Nano nodes. This is pretty simple with this website: https://api.nanos.cc/

Public APIs - Anyone who uses my nanoissuperior or nanoarcade public API please change this to another such as https://api.nanos.cc/

NanoRPCProxy sits between the node and the open internet and allows configuring which aspects of the node can be controlled remotely and by who.

It uses nanos.cc as default RPC and bitrequest.app/rpc/ (my node) as a secondary, because mine is really slow somehow. Haven't figured out why yet. nanos.cc is really fast!

Anyone can do that via: https://github.com/guilhermelawless/nano-dpow/tree/master/client

boomPoW is a fork of dPoW, but dPoW is kind of dead now

It has 2 instances: - https://dpow.nanocenter.org/ (seems link redirects to nanolooker now) - https://bpow.banano.cc (dPoW for both Nano and Banano, you can also earn some Bananos)

"BoomPoW (bPow) is a peel of the Distributed Proof of Work System (DPoW). The aim is to provide reliable, fast proof of work to not only BANANO apps and services, but also to NANO apps and services.

No? And how would we do that in a decentralized way? Services, that do a lot of transactions and are considered useful to NANO have access to a system called Distributed PoW. By registering for DPOW they get verified. You can't have that kind of gate keeping for a whole network. It wouldn't be open anymore.

It depends on how you setup your node and service. If your node is generating work, then process will by default watch_work and generate PoW at a higher difficulty. If your node is not generating PoW, which is the most common setup, then it's up to services how to approach and implement it. Many services will also precompute work, which is entirely dependent on the services implementation. Some services use dPoW for generation, which is only generating work at base difficulty at the moment.

Natrium already uses distributed PoW and doesn't generate the work on its own: https://github.com/guilhermelawless/nano-dpow#projects-using-dpow

DPow: https://dpow.nanocenter.org