Ethpass Crypto Gating

Wallet passes provides an easy and convenient way to issue digital passes specifically designed for use with Apple and Google Wallet. These passes can be linked to either an NFT (non-fungible token) or a wallet, allowing you to connect your digital assets to a wide range of use cases such as tickets, reservations, offers and more.

The solution is non-custodial, meaning the service will NEVER request access to your wallet or any of your assets. Full control over your digital assets remains with you.

Although the service offers the ability to send push notifications based on location or date, this feature communicates directly with Apple Wallet and Google Wallet APIs, and any user data is not available to us.

Ethpass provide a developer dashboard where you can create new projects, manage API keys, interact with passes issued in your projects.

How works NFT passes

1. To generate a pass linked to an NFT, a user validates their ownership of a token by signing a message in their wallet.
2. Ethpass uses the signed message to verify ownership by cross-referencing the smart contract on the blockchain.
3. If the user owns the NFT, the API will successfully issue the Apple or Google Wallet pass back to the calling user.
4. The service will monitor token transfer events and revoke the pass if the owner changes.
5. The pass scanner reads the barcode on the pass and calls the API to verify ownership.
6. The API confirms ownership on the chain.
7. If the token still belongs to the address bound to the pass, the API responds with a confirmation and the pass is successfully scanned.

Policies Gating

Policies allow you to customize precise control over your application's access and permissions. You can choose from different rule types such as collections, ERC20 tokens, native tokens, POAPs and permission lists, each serving different use cases in the blockchain ecosystem.

A unique feature of these rule types is the ability to customize them to be either satisfied or unsatisfied, allowing for inclusion and exclusion scenarios. This flexible approach allows for precise conditions for policy enforcement.

Policy rules can be customized according to three basic evaluation strategies:

1. In the 'All' strategy, every set of rules within a policy must be satisfied.
2.  In the 'Any' strategy, at least one rule set is required to pass the policy. 
3. The 'Some' strategy provides even more flexibility by allowing a certain number of rules to be satisfied. For example, if you have four rules and you set the policy to 'Some: 2', then at least two of the four rules must be met for the policy to pass.