pinpox
March 26, 2024, 12:47pm
1
Hello,
I’m eligible for a reward of 5000 FLT for my open source contributions, but am not able to claim them.
I’m following the inctructions at:
# Manual instructions for the paranoid
The following can be done in a Docker container for additional isolation, including disconnecting its network once required components are installed, but is not necessary.
1. Setup and run in Docker (optional)
- `docker run -ti --rm ubuntu:22.04 bash` to start a very basic docker container
- `apt-get update && apt-get dist-upgrade -y`
- `apt-get install -y age curl xxd gcc` to install age, curl, xxd and gcc compiler (for `sha3sum` compilation below)
- `curl https://sh.rustup.rs -sSf | sh` to install rust
2. `~/.cargo/bin/cargo install sha3sum` to install the sha3sum tool with keccak256
3. `curl -LO https://fluence-dao.s3.eu-west-1.amazonaws.com/metadata.bin` to download the metadata file to your current directory
4. Optional: if running in Docker, disconnect it from the network, on the host: `docker network disconnect bridge <container id>` (use `docker ps` to find the container id)
5. `grep '^githubusername,' metadata.bin` (if no output, you are not eligible)
6. Take one of the output lines, minus 'githubusername,' at the beginning, this is your encrypted blob in hex
7. `echo <encrypted blob in hex> | xxd -r -p -c 1000 > enc.bin` to convert the hex to binary
8. If running in Docker, copy your private ssh key inside the docker (e.g. `docker cp path/to/local/private/key/file <container id>:/path/to/private/key/file`, or just use copy/paste in your terminal to a file)
9. `age --decrypt --identity <path to private key file> --output dec.bin enc.bin` to decrypt the binary file
10. The file `dec.bin` has one line with 4 comma-separated entries, extract each of them to a variable:
- `USER_ID=$(cat dec.bin | cut -d, -f1)`
- `ETH_ADDR=$(cat dec.bin | cut -d, -f2)`
This file has been truncated. show original
But I use GPG for my SSH keys and have no way of deriving my age secret key from it. I found Accept GPG-based ssh keys · Issue #48 · fluencelabs/dev-rewards · GitHub where you recommend the openpgp2ssh but that tool only works for RSA and I (and others) use the newer ed25519 algorithm
Could you provide an alternative way of verification or instructions on how to proceed?
I have not found a way of claiming the reward yet, even though I have the secret key (but in the wrong fromat)
4 Likes
pinpox
March 27, 2024, 11:47pm
3
I am the author of the tool
My problem is solved