Skip to main content

On chain, not on trust

Proof

Every claim Ovryth makes about custody resolves to a transaction on Base. Each row reads its hash from the database and links to BaseScan.

Permission approval
0x9d44d136f7ab6e6988c8f5e17a2d2c5a0b2a744f7d96b12267fb082239392270 ↗

The project's Base Account signed a weekly spend permission naming the payer as the only spender. Registration happens inside the first payout transaction, not as a separate step.

Capped payout
0x70e20c42cdef263888e1d40105a972b83556a327fdd586c42c16eaee1360637b ↗

A real payout executed by the payer contract: spend within the cap, then transfer to the member wallet in one transaction.

Over-cap revert
0x2a0e8147e07e9685d8a03443e86a7f605074d889a9d58361e7cb293d2429436b ↗

A payout past the weekly allowance. It reverts on chain and is recorded, so the cap cannot be crossed.

Revoke
0x139943041ac91448f6de842ec9151af6e71fa577a564fc82b202bd81ac6d2c96 ↗

The project's account revoked the spend permission in one transaction. Ovryth stopped immediately and can no longer move funds.

Payer contract (verified)
0x485457f86fbf5e2385ae183bd5518c7d965e3999 ↗

The OvrythPayer contract with verified source. No general withdrawal, arbitrary-call, ETH receive, or token rescue path; normal payouts pull and forward the exact token amount in one transaction.

Last sweeper tick
2026-09-28T06:36:20.901Z

The minute sweeper polls permission status, releases expired holds, and retries payouts. Shows the last run time once live.