live — chrome 154 emulation
discord headers,
zero guesswork
drop-in chrome154 header and gateway emulation. payloads served from an encrypted api — no hardcoded values, nothing to reverse out of your code.
$ curl -fsSL modifyself.com/modifyself | shchrome 154
emulated build
x25519
key exchange
msgpack
binary wire
< 50ms
payload fetch
token encryption
tokens travel end-to-end encrypted via x25519 + xsalsa20-poly1305. even cloudflare never sees them in plaintext.
always current
build numbers, capabilities, and identify structure auto-sync server-side. your code never breaks on a discord deploy.
opaque payloads
header logic stays on our servers. clients receive binary blobs — nothing extractable in your distributable.
jerk cli
one-command updates. jerk pull modifyself.com/modifyself and you are on the latest.
drop in, ship out
two lines for headers. three to connect the gateway.
example.py
from modifyselfclient import Spoofer sp = Spoofer('your.discord.token') # rest headers — fully spoofed chrome154 headers = sp.get_headers() # gateway identify payload identify = sp.get_gateway_identify(status='online') # websocket connection headers ws_headers = sp.get_websocket_headers()
ship it in under a minute
one curl, one import. the hard part lives on our servers so your code stays clean.
$ curl -fsSL modifyself.com/modifyself | sh