Caddy version: v2.2.0 h1:sMUFqTbVIRlmA8NkFnNt9l7s0e+0gw+7GPIrhty905A=

I am trying to pass pem-encoded client certificate to proxied service via a X-SSL-Cert header, like so:

sub.example.com {
    reverse_proxy 127.0.0.1:8000 {
        header_up X-SSL-Cert {http.request.tls.client.certificate_pem}
    }

    tls {
        client_auth {
            mode require
        }
    }
}

OS/Environment

None yet, but I'm working on OS X v10.11.6 'El Capitan' client-side. (See 'The way of deployment (cloud or local)' below for details on considered server infrastructure.)

Ansible version

None yet, as I haven't yet gotten that far into setting up Algo.

Version of components from requirements.txt

Not applicable (see above.)

Summary of the pro

On my rpi4 (Linux liumeo-rpi4 5.4.72-v7l+ #1356 SMP Thu Oct 22 13:57:51 BST 2020 armv7l GNU/Linux), there are 107XXs. And it seems there's an endless loop in the last 2 cases (don't know which case yet).

pi@liumeo-rpi4:~/github/radare2/test $ r2r
Skipping db/archos/linux-x64 because it does not match the current platform.
Skipping db/archos/darwin-x64 because it does not match the current 

The upstream issues got closed. It is referenced in:

• .goreleaser.yml#L66

This issue was created by the ORY Closed Reference Notifier GitHub action.

🧐 Motivation
Create simple ERC20 and ERC777 presets with fixed supply.
The benefits are:

• Easy to deploy (including from Remix).
• No access control (for minting/pausing), and hence no governance required.
• Can be verified easily on public networks and then are verified for all.

📝 Details

Community members are creating their own simple ERC20 tokens, so it would be good if they