Just skimmed through the readme and it is really cluttered with a lot of information. The TOC helps but I think a lot of the stuff can be moved over to the wiki. We should keep just the important part inside the readme (like getting started and contributions etc.)

I will probably create empty wiki pages the coming days to showcase the idea that I have. Any help is appreciated in this department

[11:15:38 AM] <bogdomania> for /ns saset [redacted-other-account-name] always-on true
[11:15:54 AM] <bogdomania> [Notice] -NickServ- Successfully changed your account settings
[11:15:56 AM] <bogdomania> [16.07.2020 18:15] [Notice] -NickServ- Your stored always-on setting is: mandatory

The replies here should be changed to reflect that these are not the operator's own settings.

Not sure if this is the correct way to do it, but I wanted to save a cache script I could easily run.

"cache": {
      "desc": "Cache versions and update lock file",
      "cmd": "deno cache server.ts --lock-write",
      "lock": "./lock.json"
}

The result however when running denon cache is an endless loop instead of just executing it once, looks like this:

![Skärmavbild

We avoid using cgo anywhere in the codebase since it causes problems with cross compilation. However, cgo would be advantageous in some cases (e.g. can use certain optimized libraries, can use libsecp256k1 bindings)

Investigate the viability of using xgo to do this. Test it on linux/osx/windows.

• https://github.com/karalabe/xgo
• https://github.com/ethereum/go-ethereum/wiki/Cross-compili