Improve README and Makefile

Makefile

@@ -74,21 +74,6 @@ build-release-tarballs:
 	$(MAKE) build-aarch64-portable
 	$(call tarball_release_binary,$(BUILD_PATH_AARCH64),$(AARCH64_TAG),"-portable")
 
-# Builds the Remote Signer binary in release (optimized).
-#
-# Binaries will most likely be found in `./target/release`
-build-remote-signer:
-ifeq ($(PORTABLE), true)
-	cargo build --release --manifest-path remote_signer/Cargo.toml --features "portable"
-else
-	cargo build --release --manifest-path remote_signer/Cargo.toml
-endif
-
-# Builds the Remote Signer binary in release (optimized),
-# using the slower Milagro BLS library, which is written in native Rust.
-build-remote-signer-milagro:
-	cargo build --release --manifest-path remote_signer/Cargo.toml --features "milagro"
-
 # Runs the full workspace tests in **release**, without downloading any additional
 # test vectors.
 test-release:

remote_signer/README.md

@@ -77,12 +77,7 @@ Content | `{"error": "Key not found: <identifier>"}`
 
 1. [Get Rust](https://www.rust-lang.org/learn/get-started).
 2. Go to the root directory of this repository.
-3. Execute `make build-remote-signer`.
-4. The binary `remote-signer` will most likely be found in `./target/release`.
-
-Or,
-
-3. You can just execute `make`
+3. Execute `make`
 4. The binary `lighthouse` will most likely be found in `./target/release`.
 5. Run it as `lighthouse remote_signer` or `lighthouse rs`.
 
@@ -119,10 +114,6 @@ OPTIONS:
         --storage-raw-dir <DIR>       Data directory for secret keys in raw files.
 ```
 
-## Implementation Tracking
-
-Please, check this repository's issue for the [Implementation Tracking](https://github.com/sigp/rust-bls-remote-signer/issues/1)
-
 ## Roadmap
 
 - [X] EIP standard compliant