EVMist

Get paid in ETH. Keep your wallet private. Invoice links that pay a fresh ERC-5564 stealth address every time. Non-custodial. Ethereum + Sepolia.

[EVMist @EVMist_]

The EVMist token is now live on the @Stockereum launchpad.

Get paid in ETH through fresh stealth addresses. Keep your main wallet separate.

Your keys. Your funds.

CA: 0xfb9bc3dea5219c3af1b248a65380ade66915ba1b

🌐 https://t.co/m3QkYFpsS3

[EVMist @EVMist_]

Your treasury wallet doesn’t need to be on every client invoice.

When you use the same address to hold project funds and collect development fees, each new client gets a way to inspect the balance and transaction history attached to that address.

EVMist helps you separate those roles. Every invoice gets a fresh stealth address, so you can request payment in ETH without sharing your treasury address.

Create an invoice for a shipped feature, a completed milestone, or ongoing maintenance. Share the payment link with your client, who completes a standard ETH transfer. EVMist matches the incoming payment to the invoice, while you retain control of your keys and funds.

For independent developers and small teams, that means each invoice has a dedicated receiving address. Your treasury can stay out of the payment instructions you send to clients.

Transfers remain public, and moving funds directly into a known treasury wallet creates an on-chain connection. Maintaining that separation also depends on what happens after you receive payment.

Keep your invoices focused on the work you’re billing for.

One invoice. One fresh address.

https://t.co/yDWtJIaLRu

[EVMist @EVMist_]

Freelancers: your invoice shouldn’t come with years of wallet history.

Reusing your main wallet address for every job gives each new client a way to browse the balance and past transactions attached to it. Getting paid can end up sharing far more than the fee you agreed on.

EVMist gives each invoice a fresh stealth address, so you can request payment in ETH without putting your main wallet on the invoice.

Create an invoice, add a note for the project or milestone, and share the payment link. Your client opens it and sends ETH using a compatible Ethereum wallet. EVMist matches the incoming payment to your invoice, while you retain control of your keys and funds.

A website build, a design commission, a piece of writing, or a consulting session can each have its own invoice and receiving address.

The transfer remains public on Ethereum. The benefit is reducing the exposure that comes from repeatedly sharing your main wallet to collect payments.

Keep the conversation focused on your work, the agreed fee, and getting the invoice paid.

https://t.co/yDWtJIaLRu

[EVMist @EVMist_]

Self-custody means backups matter.

With EVMist, your keys are created and kept on your device. You control the funds you receive, and keeping a reliable recovery method is part of that control.

Export a password-protected key file and store it securely. EVMist protects that backup using AES-GCM encryption and PBKDF2 with 600,000 rounds. You’ll need both the file and its password to use that recovery method.

A lost device, a browser reset, or a move to a new computer can make a backup essential. Keeping your only backup on the device you’re backing up leaves both vulnerable to the same loss.

For keys derived through wallet signing, recovery depends on retaining access to the original wallet and completing the required signing process.

If your keys and all applicable recovery methods are lost, we cannot restore access to your funds. EVMist doesn’t keep a spare copy of your private keys.

Take a moment to back up while you still have access. Store the file securely, protect its password, and understand how your recovery method works.

Your keys deserve the same care as the funds they control.

https://t.co/yDWtJIae1W

[EVMist @EVMist_]

Privacy, honestly: your next transfer matters.

Every EVMist invoice gets a fresh stealth address, helping you receive ETH without sharing your main wallet. Preserving that separation also depends on what you do after the payment arrives.

Ethereum still records the sender’s address, amount, time, and destination of a transfer. If you sweep funds directly from an invoice address to your publicly known main wallet, you create a visible connection between those addresses.

Anyone following that transfer can see where the funds went. Consolidating several invoice payments into the same known wallet can also make those payments easier to associate.

A fresh address helps reduce exposure when you receive a payment. The transaction history remains public, and later activity can reveal connections that weren’t apparent when the invoice was paid.

With EVMist, you control your keys and funds, including the decision about where to move your ETH. Before making that transfer, consider what the destination reveals and whether it maintains the separation you intended.

Get paid with a fresh address. Be deliberate about what happens next.

https://t.co/yDWtJIae1W

[EVMist @EVMist_]

Privacy, honestly.

Ethereum is a public ledger. When someone pays an EVMist invoice, the sender’s address, the amount, the transaction time, and the receiving address remain visible on-chain.

EVMist gives each invoice a fresh stealth address. This lets you receive ETH without putting your main wallet address on the invoice or directly exposing the balance and transaction history attached to it.

That separation matters. A client paying for your work doesn’t need your main wallet address to complete the payment. Someone looking at the receiving address alone won’t automatically see which other wallets you control.

There are still limits. Your client may already know who they’re paying. Publicly sharing payment details or moving funds directly to a known wallet can create connections. Amounts, timing, and subsequent transfers can also help observers link activity.

EVMist reduces a specific source of exposure: repeatedly sharing your main wallet to get paid. Keeping that separation useful also depends on how you share information and move your funds afterward.

Privacy starts with understanding what remains visible.

https://t.co/yDWtJIaLRu

[EVMist @EVMist_]

EVMist never holds your funds or your keys.

Getting paid should leave you in control of what you earn. That principle sits at the heart of how EVMist works.

Your keys are created and kept on your device. Each invoice gets a fresh stealth address, and your client sends ETH directly to that address. Spending those funds requires your private keys.

EVMist helps you create the invoice, share the payment link, and match the incoming payment to the right invoice. Throughout that process, custody stays with you.

For your client, it’s a familiar ETH transfer. For you, it means receiving payment without putting your main wallet address on every invoice or handing control of your funds to a payment platform.

Once the payment arrives, you decide when to move it and where to send it next. There is no custodial balance held by EVMist on your behalf.

From the invoice you create to the ETH you receive, control stays in your hands.

Your keys. Your funds. Yours.

https://t.co/yDWtJIae1W

[EVMist @EVMist_]

The key lives after the #.

In an EVMist payment link, the section after the # carries the key used to decrypt the invoice’s protected content. That section is called a URL fragment.

When your client opens the link, the browser leaves the fragment out of the HTTP request used to load the page. EVMist is designed to use the key locally in the browser to unlock the encrypted invoice notes.

Our server stores the encrypted note data, while the full link provides the information your client needs to read it.

That makes sharing the link an important part of the privacy model. Anyone with the complete link can potentially access the invoice’s protected content, so send it directly to your intended client and keep it out of public posts or screenshots.

Keep the link intact, including everything after the #, so your client can open the invoice correctly.

A familiar payment link, with a deliberate separation between encrypted content and the key that opens it.

Treat the full link like the key it contains.

https://t.co/yDWtJIae1W

[EVMist @EVMist_]

original text requires the corresponding decryption key.

You can still give your client the context they need through the invoice link: what the payment covers, which milestone it belongs to, and what you agreed to deliver. Encryption happens behind that familiar experience.

This protection applies to the note’s contents. The ETH transfer itself remains visible on Ethereum, including its amount and participating addresses.

Alongside a fresh stealth address for each invoice, encrypted notes help protect another part of the payment experience: the written context surrounding your work.

Sealed in your browser. Stored as encrypted data.

https://t.co/yDWtJIaLRu

[EVMist @EVMist_]

There’s no EVMist token requirement to pay an invoice, and your client doesn’t need to understand the cryptography behind stealth addresses. They pay in ETH using the amount and destination shown in the invoice.

Once the payment is detected, EVMist matches it to the corresponding invoice, helping you keep track of what has been paid.

That simplicity matters when you’re working with clients. Clear payment steps mean fewer things to explain and an easier handoff from completed work to payment.

Privacy becomes more practical when it fits naturally into everyday transactions.

One link. A familiar wallet. One ETH transfer.

https://t.co/yDWtJIaLRu

[EVMist @EVMist_]

Every EVMist invoice gets its own address.

Using ERC-5564 stealth addresses, EVMist creates a fresh destination for each ETH invoice. Your client sends payment to that address, keeping your main wallet out of the receiving process.

A new invoice begins with a new address, without carrying over the transaction history attached to your main wallet.

Behind the scenes, cryptographic derivation lets you recognize the receiving address and control its funds using your private keys. The addresses change from invoice to invoice, while control stays with you.

For your client, the experience stays straightforward: open the payment link, review the amount, and pay in ETH. EVMist detects the payment and matches it to the corresponding invoice.

This gives each client payment its own destination and helps reduce its direct public connection to your main wallet.

Transactions remain visible on Ethereum, and sending funds onward to a known wallet can reveal a connection. Stealth addresses protect a specific part of the payment experience: how you receive.

One invoice. One fresh address. Funds controlled by your keys.

https://t.co/yDWtJIae1W

[EVMist @EVMist_]

Your wallet address is a public diary.

Every payment, transfer, and interaction recorded against that address adds another entry. When you share the wallet you use for everything, a client can explore much more than the payment for their project.

Your balance. Previous payments. Trading activity. Transfers between wallets.

Together, those entries can reveal financial context you never intended to include in an invoice.

EVMist helps you put a boundary around that exchange. Each ETH invoice gets a fresh stealth address, so receiving a client payment doesn’t require sharing your main wallet address.

Set the amount, share one payment link, and receive ETH at the invoice’s dedicated address. You retain control of the keys and funds.

The transaction remains public on Ethereum. A fresh address helps separate the payment from your main wallet’s history, although transferring funds directly back to that wallet can link the addresses again.

For freelancers, developers, and creators, that means more control over the information shared with each client.

Give every invoice a fresh page.

https://t.co/yDWtJIaLRu

[EVMist @EVMist_]

Meet EVMist.

Getting paid for your work shouldn’t mean sharing your main wallet’s balance and transaction history.

With EVMist, create an ETH invoice, set the amount, and share a single payment link. Your client pays a fresh stealth address created for that invoice, keeping your main wallet out of the receiving process.

Whether you’re delivering code, designing a website, or creating content, the workflow stays familiar: create an invoice, share the link, and receive ETH.

Built on ERC-5564 stealth addresses, with invoice notes encrypted in your browser and a non-custodial design that keeps control of your funds in your hands.

Transactions remain visible on Ethereum. EVMist helps reduce the direct public connection between incoming payments and your main wallet.

A fresh address for every invoice. More control over what you share.

Get paid in ETH. Keep your wallet private.

https://t.co/yDWtJIae1W

[EVMist @EVMist_]

Fresh addresses have an everyday privacy use case, too.

With EVMist, each ETH invoice gets a fresh stealth address, so getting paid doesn’t require sharing your main wallet.

A practical step toward better payment privacy on Ethereum.

https://t.co/m3QkYFoV2v

[vitalik.eth @VitalikButerin]

I don't recommend anyone scramble to move their funds to new wallets today. But we should take the risks to cryptography from AI-accelerated math seriously, and minimize our exposure to not just quantum-vulnerable cryptography, but also potentially AI-vulnerable cryptography.

The core new area of risk from this viewpoint is, unfortunately, ML-DSA / FHE / lattices.

(and it's also another reason, along with quantum, why ECDSA might fall even faster than expected, hence the "fresh address" recommendation)

So far most people have been in the mode of thinking "elliptic curves broken, hashes safe, lattices safe". But there is a good chance that the concrete security of lattices will take serious hits from the next two years of AI math.

The basic threat model is: factoring is something that naively takes 2^(n/2) time, but over decades smart people have found and optimized number field sieves, and degraded that to 2^O(n^(1/3)), which is why RSA keys and signatures need to be ~400 bytes (and not 64 bytes). What if there are skeletons in the closet like that, both for elliptic curves and lattices, that we are simply not smart enough to discover - but bots soon will be?

This is a major part of the reason why for the past year ethereum's lean roadmap has been going in the "hash-only" direction: no lattices, no ML-DSA, no Falcon, no lattice-based commitments inside ZK proofs, etc. Signatures in lean ethereum are all hash-based, either WOTS or SPHINCS-.

For signatures and proofs, we already know how to go hash-only. The bigger challenge is for *public-key encryption* - and this goes far beyond blockchains. Secure communication, anonymizing protocols, lots of things need public-key encryption.

And unfortunately there are long-standing mathematical theorems showing why public-key encryption cannot be done with hashes alone. You have to have some kind of trapdoor object that has at least one form of usable "structure" - either group theory (incl. isogenies) or lattices or code-based or potentially in the future even more newfangled and spooky things (local mixing?). But for anything that has structure, you should assume that AI will make at least some progress in breaking that structure. Here, one reasonable inference is that if you want to make something plausibly long-term secure, multiply the key sizes by 10.

To me that's a very plausible world and something not at all extreme to predict. If AI will bring us 50 years of math in 2 years, then that 50 years of math may very plausibly include a "naive factoring -> GNFS" level of improvement to our ability to break lattices. In that world, lattices will still exist, but they will have to be significantly bigger to guarantee the same level of safety.

And at those new larger sizes, hash-based constructions will beat lattice-based constructions on concrete efficiency in every use case where hash-based constructions are possible at all.

Theoretically, of course it's possible that hashes are broken too (eg. P = NP would imply that). But I think P = NP is very unlikely. And intuitively, it's much more likely that a mathematical object has exactly no exploitable structure (like hashes are intended to), than that a mathematical object has exactly ~3 forms of exploitable structure (for elliptic curves: associativity, Schoof, pairings) and not some secret fourth form of structure we have not yet discovered that greatly degrades its security (for elliptic curves, ECDLP and pairing security). Similar for LWE, SVP, RLWE and the zoo of lattice problems.

For this reason, we do not yet see any reason to worry and start padding the byte size of hashes (if we start to worry more, we would pad the round count first before doing anything to the byte size).

Concrete TLDR, my own personal views:

* Hash-based > lattice-based, in those situations where hash-based is possible at all
* For anything lattice-based, be much more paranoid on param sizes. Remember that blockchains are only a small portion of the cryptography story; this point goes far beyond blockchains and applies to eg. access to websites, secure messaging, Tor / VPNs ...
* For privacy protocols, strongly favor NOT putting encrypted notes onchain. Instead, send them offchain through some third-party mechanism.
* If it's not difficult for you, keeping your funds in addresses which have not yet been used to make a transaction is a good idea. If it's easy for you, do it. **But be careful about migrations; I personally have lost more money in botched migrations than I have lost in all hacks combined**.
* For multisig wallets, doing confirmations offchain is better than onchain, because this way the signatures of signer wallets do not get exposed to the public, so if ECDSA falls to AI much faster than expected, at least the multisig "gracefully degrades" to a 1-of-1 where the 1 is whoever was gathering the signatures - a much better place to be than "anyone can take the money"
https://t.co/oVjwZog2lL

[EVMist @EVMist_]

Sharing your main wallet to get paid shows clients more than the invoice.

EVMist gives every ETH invoice its own fresh stealth address (ERC-5564).

Create → share the link → get paid.
Non-custodial. Notes encrypted in your browser.

https://t.co/m3QkYFoV2v

[EVMist @EVMist_]

https://t.co/m4r44Cj8sq