About Unisky Pass

Membership should be a proof, not another profile.

Unisky Pass gives places a direct way to issue time-based membership and gives members a fast way to prove wallet control at the door. Connect a wallet or use passwordless Privy onboarding—without payment custody or a first-party identity database.

Why it exists

A picture can be copied. A wallet response has to be made now.

Traditional digital passes often stop at something that looks official. Unisky Pass asks a better question: can the wallet that holds this membership answer the issuer's fresh challenge while the pass is still active on Monad?

60 sec

challenge lifetime

0 tx

member check-in

Fresh

onchain read

The wallet is the membership

Passes are non-transferable records issued to a wallet. Connect an external wallet or use a Privy embedded wallet; the active address remains the onchain identity.

A check-in is a fresh proof

The member signs a new 60-second challenge. The issuer then checks the signature and current contract state before showing VALID.

Privacy is a product boundary

Privy may process optional email or available SMS login, but Unisky Pass never writes those identifiers onchain or stores them in its own database. Public wallet data stays on Monad.

Deployment truth

The same registry, rehearsed before release.

Monad network information
Monad mainnetLIVE
Chain ID
143
Registry
0x634659d15A5a98D59ff06e9Eb7deC08bD5894fF5
Public RPC
https://rpc.monad.xyz

Production registry is deployed, live, and source-code verified as an exact match (Solidity 0.8.28, optimizer 200).

View registry on Monadscan
Monad testnetREHEARSAL
Chain ID
10143
Registry
0x56e47d0233b9eAa2f6701Bb90DFD6352000D5e26
Public RPC
https://testnet-rpc.monad.xyz

Dry-run registry used for the mandatory testnet release path.

View registry on Monadscan

Built in the open

A solo six-day build by Nxrskyaa.

Unisky Pass was built as a deliberately focused hackathon MVP: one contract, one core membership loop, and clear limits instead of a fictional enterprise stack.

Honest by design

What this MVP does not promise

  • A valid proof demonstrates control of the holder wallet, not the physical identity of the person holding the phone.
  • Replay prevention is scoped to the issuer's current browser session. There is no shared backend or onchain nonce registry.
  • Deliberate wallet sharing is not prevented. Anyone with signing control of the holder wallet can create a valid response.
  • Issuer registration is permissionless. A pass in a wallet is not an endorsement, and unsolicited pass records are possible.
  • Wallet relationships, display names, and pass timing are public and permanent onchain.
  • Email or SMS login authenticates access to a wallet through Privy; it does not verify a person's legal or physical identity.

Choose your path

Carry a pass, or create one for your community.