vPawHookSame paws.
New possibilities.
vPawHook is a persistent clan-pet world built around an upgradeable Uniswap v4 hook. The game can change. Your pet keeps its story.
Explore the formatsOne pool. Room to evolve.
The pool points to one hook proxy. Governance can replace its implementation while keeping the same hook address and liquidity pool.
- PET / ETH poolShared liquidity
- Hook proxySame address
- ImplementationUpgradeable logic
- Event rulesVersion fixed at entry
New event rules use the same shared liquidity pool. The hook handles pool behaviour; pet progression, event scoring and custody live in separate contracts.
A different way to win.
The same pet can play very differently under a new set of rules.
Daily climb
Grow your clan’s combined power across a 24-hour round.
- Your choice
- Burn for permanent commitment, or lock PET until the round ends. Every pet starts the next round at zero power.
- Under the hood
- The shared pool funds the prize pot. Committed PET earns power; ordinary trading volume does not.
Event lengths, entry windows and boost limits are published before each event opens.
A pet with a past.
And a next chapter.
Pets keep their identity, completed-event history, podiums and unlocked forms. Each new event resets its competitive score, not your pet’s history.
Specialise as a sprinter, an endurance runner or a support pet. Each playstyle changes how actions score. Forms require qualified event participation as well as burns, and the signature form also requires a podium.
Meet your petBase → grown → signature. Forms change your look; your event rules set your power.
What could the next hook do?
Today’s building blocks leave room for new games, community ideas and future implementations.
- Tactical boosts
- Burn for a tactical boost during the event. Limited charges, cooldowns and a total boost cap create choices beyond spending more.
- Clan pit crews
- Deposit an eligible pool position for your clan and build recognition over time. ETH rewards come only from a separate funded budget. Explore the pit crews.
- The Workshop
- Describe a skin, track or rule idea. AI helps preview it; the community proposes future seasons. Template proposals and community feedback start in the Workshop. New rules still require testing and review.
- Every result, replayable
- Follow starting stats, confirmed actions, rule versions and scoring steps through to the prize funding and claims. Inspect an event in the race explorer.
AI assists proposals and cosmetics. It does not control funds, pick winners or deploy contracts.
The next season starts after this one ends.
One active event at a time is vPawHook’s protocol policy. A proxy could support multiple modules; the event schedule deliberately keeps one competition in focus.
- Propose & testPublish the implementation, event rules, simulations and storage compatibility checks.
- Queue the changeMultisig governance schedules the upgrade with a public 48-hour delay.
- Finish the eventClose and finalise the current competition under its existing rules.
- Open the nextActivate the new version between events. Publish its rules before entry opens.
What an upgrade can—and cannot—change
Pool behaviour can change. This is a full proxy architecture. The 2% fee and its allocation are the current governed policy, not an immutable guarantee against future governance changes.
The address sets the callback limits. Uniswap v4 encodes callback permissions in the hook address. Replacing the implementation cannot add permissions absent from that address. Uniswap hook documentation
An event keeps its rules. Rules and scoring parameters are pinned when entry opens. A new season must not rewrite an event already entered or its earned claims. Pet custody and claim contracts remain separate from the hook proxy.
Liquidity remains exposed to hook changes. You can withdraw your position NFT from the pit crew vault. Redeeming its underlying liquidity still goes through the pool hook, whose future implementation can change that behaviour.
Upgrade compatibility matters. Implementations need safe initialisation and compatible storage layouts. A delay gives people time to inspect a change; it does not make arbitrary new code safe. OpenZeppelin upgrade guidance
Onchain actions have timing constraints. Ethereum confirms discrete inputs. Boosts use explicit block windows and cannot promise instant input or immunity to transaction ordering. Any random outcome must publish how its randomness is verified.