[yebyen]

The configuration is the same as Bitcoin.

Basically, the Dogecoin wallet is going to attempt to punch a hole in your firewall with UPnP and any other NAT-busting techniques the author (of Bitcoin) has contrived to enable you to help new nodes to come to sync by sending them blocks from the winning blockchain.

The daemon mode (which listens on an RPC/HTTP port for commands like "send money here") is not going to attempt to run unless you enable a password in your .doge/config (just like bitcoind). RPC clients will need this password to be able to issue commands. If you have one node, then both the client and server will have the same .doge/config and it's secure, assuming they don't guess your password. If you have multiple nodes, this is the way to have a lightweight client that sends commands to your "heavyweight" wallet. If the client doesn't have your RPC password, the client can't do anything that any 'nobody' new node on the network should be able to do.

You can run Dogecoin on public networks, or the Dogecoin wallet has a bug that you should report. Whether it's wise to be in a position to be the first to discover such a bug (by losing all the coins in your wallet), that's another matter, but if there are such bugs in the wallet then it's really not viable, and you should therefore probably sell all your doges immediately.

[yebyen]

(If you haven't ever looked at your .doge/config or attempted to run in daemon mode, you won't have an RPC password and your client is also secure, since it won't accept commands that are not authenticated.)

[mkeung]

Thanks, i'll update the content today