is this really me?

people copy accounts. each account below links to the others, so you can check that you are talking to me; an account with my name that is missing here belongs to somebody else.

where i am

where i am not

the list above is complete: i have no telegram, no discord, no instagram, no tiktok, no linkedin, no youtube, no farcaster and no second x account. i sell no signals, run no group, and never write first about a trade, a listing, a "collab" or a wallet. an account with my name or my bull that does any of that belongs to somebody else; tell me at the address above and i will list it here.

the key

one openpgp key, ed25519, made 8 september 2026, valid until 7 september 2028. it signs my git commits and it can encrypt mail to me.

get it from /pgp.txt, or let gpg find it through this domain (web key directory):

gpg --locate-keys hello@alinaschanz.life
gpg --fingerprint hello@alinaschanz.life

the fingerprint gpg prints has to match the one above. if it does not, stop.

check a commit

git clone https://github.com/alinaschanz/gasweek
cd gasweek
gpg --import <(curl -s https://alinaschanz.life/pgp.txt)
git log --show-signature -1

"good signature from alina schanz" with the fingerprint above means the code is what i pushed. github shows the same check as a "verified" badge on each commit.

check a number

every number in a note or a post comes from a script in one of the repositories. the methods page says which endpoint and which formula. if a rerun gives you something else, the note is wrong and i want to know.

check a note

every note on this site has an opentimestamps proof next to it: the same file name with .ots at the end. it proves the note existed, byte for byte, before a certain bitcoin block, without anybody having to trust me or this server. a note that changes gets a new proof, and the change goes in the changelog.

curl -sLO https://alinaschanz.life/notes/2026-09-08-week-37-in-numbers.html
curl -sLO https://alinaschanz.life/notes/2026-09-08-week-37-in-numbers.html.ots
ots verify 2026-09-08-week-37-in-numbers.html.ots

ots is pip install opentimestamps-client; checking the block needs a bitcoin node, or drop both files on opentimestamps.org and let the page do it. a fresh proof reads "pending" for a few hours until a block covers it; after that it is final.

let somebody else check

the key above carries two machine-readable proofs in the ariadne format: a gist on my github account and a txt record on this domain, each naming the key's fingerprint. keyoxide fetches the key through this domain and checks both in your browser, with nothing of mine in the loop. you will find the key on keys.openpgp.org as well.

what this page cannot prove

the accounts above point at each other, i sign the commits and i timestamp the notes. that proves three things: what lands on github comes from whoever holds the key, a note existed byte for byte before a certain bitcoin block, and a number in a note comes out of a script you can rerun. who holds the key stays unproven. i made the key in september 2026, and the rest of this page is about as old; the x account is older, and its age tells you when somebody registered it and no more. check the numbers, the scripts and the signatures, and give the rest the trust that a few weeks of public work has earned.

found a problem?

this site has a security.txt, signed with the same key. it says the same thing as this page: write to hello@alinaschanz.life, encrypted if you like.