The trust layer
for Web3
Pavoriz puts what is known about a dApp, an address or a project in front of somebody at the moment they sign, and gives them a way to take permissions back.
Use the arrow keys to step through the slides.
Problem
People do not lose funds to bad decisions. They lose them to missing information.
Permissions never expire
Every dApp asks for a standing approval. They pile up across every chain a person has used, to contracts they cannot name.
The warning signs are scattered
Block explorers, security feeds, incident databases and calldata nobody can read. Four places, none of them the wallet.
Nothing is there at Confirm
The one moment a good decision is possible is the moment none of that information is on screen.
Product
One layer. Four questions that today take four products.
Revoke console
What has this wallet already given away?
65 chains, value at risk priced
Pavoriz Shield
Is this dApp safe right now, while I am on it?
Browser extension, always on
Threat intelligence
Is this address or site known to be dangerous?
438,200 entries, four feeds
Project Trust Check
Is this project what it claims to be?
Fifteen sources, four groups
How it works
Protection that sits in the session, not in a tab somebody forgets to open.
- 1
Launch
Open a dApp through Pavoriz once. Its host is enrolled for always on protection.
- 2
Grade
Every wallet request is scored before the wallet sees it, against the live threat list.
- 3
Decide
A risky call is stopped with a clear Allow or Block card carrying the Pavoriz mark.
- 4
Undo
An approval that goes through is met with the offer to revoke it, right then.
Only the host leaves the browser, never the path or the query, and only for hosts already under the Shield.
What is built
Not a prototype. A working platform, measured end to end.
70
chains across nine ecosystems
65
chains the approval scanner reads
438,200
threat feed entries held
2,530
drainer addresses walked
82,698
lines across 413 source files
2,137
test assertions, plus 35 Foundry tests
Web app, Manifest V3 extension, 59 API routes, an operator console, and an escrow contract live on BNB Chain.
Why it compounds
The screens can be copied. The dataset cannot.
- A drainer victim graph read off chain logs, published by nobody else
- 1,250 incidents priced and dated
- Phishing hosts deduplicated across four publishers into one key
- Live approval state on 65 chains
- An identity corpus that grows with every trust check
Business model
Free core tools. Revenue where the value is.
Spotlight placements
Projects buy home page placements by the term, paid into an on chain escrow. Settled on approval, refunded on rejection.
Auto revoke fees
A dollar priced fee on each automatic revoke, collected within limits the user granted on chain. Switches on after the contract audit.
Public data API
Keyed access to address reputation, threat, exploit and approval data for wallets and dApps that build the answer themselves today.
Revoking, scanning, the Shield and the trust check stay free. They are what builds the dataset.
Security by design
Break the auto revoke keys completely and the attacker can cancel approvals. Nothing else.
PavorizRevoker
2,736 bytesThe EIP-7702 delegate for auto revoke. One canonical address on every chain.
Checked against the compiled bytecode, not the source.
SpotlightEscrow
Live on BNBThe server key can settle or refund. It cannot name a destination, withdraw, or re-decide a payment.
0xd8349cf26ddbe37350cf75bd5d8c14a64b42815d
Roadmap
Ordered by what unblocks what.
- 1
Q4 2026
Launch
- Public launch
- Shield on the Chrome and Firefox stores
- Off chain signature coverage
- 2
Next
Data as a product
- Address reputation
- Keyed public API
- New approval alerts
- 3
Then
Reach
- WalletConnect
- Pavoriz mobile browser
- Shield on Solana
- 4
After
Depth
- Audit of both contracts
- Auto revoke in production
- $PAVO and governance
Make every signature an informed one.
For investors, partners and incubators. The white paper has the detail; the team is a message away.
pavoriz.com