Crates.io | soltrack |
lib.rs | soltrack |
version | 1.0.0 |
source | src |
created_at | 2021-12-02 10:40:02.864836 |
updated_at | 2021-12-02 10:40:02.864836 |
description | A tool to find the developer of a Solana program |
homepage | |
repository | |
max_upload_size | |
id | 491137 |
size | 98,459 |
A tool to find the developer of a Solana program.
At the fundamental level, Solana programs are just variantion of eEBPF programs which are compiled from the Rust compiler. By default, the programs contain paths which also contains username of the machine you used to compile it. There were efforts like this pre-RFC to remove the username by default, but it is not implemented at the moment. The following is an example that the home directory and username are leaked in a compiled program.
$ strings your-compiled-program.so
# ...
# /<your-home-directory>/<your-username>/.cargo/registry/src/github.com-1ecc6299db9ec823/solana-program-1.7.11/src/account_info.rs
# ...
If you follow official documentations on Solana or a framework like Anchor for building programs, chances are your identity is leaked in the programs.
This is a well known issue for several years and it is actually fine as long as you have no reason to hide your identity. However, in case you want to stay anonymous, with the fact that your programs contain your username and Solana programs are publicly accessible by anyone on the internet, your programs might leak your identity if your username can be used to identify you (which in most cases it could).
In the meantime, to strip a username in programs, we can use --remap-path-prefix
flag to map the default path prefix to something else.
For example, we can add the flag like the following.
RUSTFLAGS=--remap-path-prefix=/<your-home-directory>/<my-username>=src cargo build-bpf
Or if you use Anchor framework.
RUSTFLAGS=--remap-path-prefix=/<your-home-directory>/<my-username>=src anchor build
Alternatively, you can consider to build your program with a separated CI/CD machine (i.e., Github Actions which also supports private repo, etc.).
cargo install soltrack
cargo build
The compiled binary will be at ./target/debug/soltrack
.
$ ./target/debug/soltrack -h
# SolTrack 1.0
# Wasin Sae-ngow <https://github.com/chrsow>
# Track potential developer of a Solana program
# USAGE:
# soltrack [OPTIONS] <PROGRAM_ID>
# ...
soltrack <PROGRAM_ID> --network <NETWORK>
For example, if you want to find who is the developer of the native Memo program in the Solana devnet. You can run the following command.
$ soltrack MemoSq4gqABAXKb96qnH8TysNcWxMyWCqXgDLGmfcHr --network devnet
# [+] The program MemoSq4gqABAXKb96qnH8TysNcWxMyWCqXgDLGmfcHr on mainnet is deployed by: tyeraeulberg
As you can see, we have obtained the developer of the Memo program is "tyeraeulberg" who is one of the engineers of Solana.