SkyeGate - Token and NFT Gating
| 开发者 | skyemeta |
|---|---|
| 更新时间 | 2026年11月13日 23:13 |
| PHP版本: | 8.2 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
详情介绍:
SkyeGate puts any part of a post or page behind a wallet check. Wrap the content in a shortcode, name the token or NFT collection a visitor must hold, and holders see it. Everyone else sees a "Connect Crypto Wallet" button. It is web3 token gating without the setup: no API key, no account.
Free and fully functional. One condition per gate, as many gates as you like, on 32 blockchains. Nothing to sign up for.
Private by design. Your site never sees balances or holdings, just a signed yes or no. Gated content stays on your server until a check passes, so it is never in the page source. No personal data is collected.
Much more than token gating. Tokens and NFTs are where most sites start, but SkyeGate is condition-based access for WordPress: recognition, not passwords. The same gate can recognize an on-chain attestation (EAS), a chain's own coin, or a community membership pass that a member opens with an email code and no wallet app. One pass can be recognized on every site and store that welcomes it, and SkyeGate Pro stacks up to 10 conditions on a single gate and adds Farcaster conditions.
Checks run through InsumerAPI (the condition-based access API). After connecting, Ethereum-style wallets approve a quick, free ownership signature (passkey wallets confirm with Face ID).
Your first gate in two minutes
The quickest way: after activating, open Settings > SkyeGate and use Create a gate. Choose a token, an NFT collection or a chain's own coin, paste the address, and copy the finished shortcode into any post or page (a Shortcode block works well).
Prefer to write it by hand? Paste one of these and change the address to your own token or collection.
Token holders. This one works exactly as written: it asks for at least 100 USDC on Ethereum.
[skyegate chain="ethereum" contract="0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48" threshold="100"]Only holders see this.[/skyegate]
NFT holders. Replace the address with your collection's contract address.
[skyegate chain="ethereum" type="nft_ownership" contract="0xYourCollectionAddress"]Only holders see this.[/skyegate]
Everything between the opening tag and the closing [/skyegate] is the gated content. Change chain to where your token lives, for example base, polygon, arbitrum, solana or xrpl.
Want to see a gate before installing? Try the live demo, or watch the short video:
https://www.youtube.com/watch?v=P-0z7WwXYwY
What you can gate by
- Token balance: require visitors to hold a minimum amount of any ERC-20 or SPL token
- NFT ownership: require visitors to own an NFT from a specific collection
- Native tokens: gate by ETH, SOL, POL, and other native chain tokens
- EAS attestations: require on-chain attestations via Ethereum Attestation Service
- Membership passes: optional. Recognize community membership passes created with SkyeMeta's Bothy. Members prove it's them with a one-time code sent to their email, no wallet app needed. You do not need a pass to use token or NFT gates
- Wrap any content in the shortcode:
[skyegate chain="..." contract="..."]your content[/skyegate] - Visitors see a "Connect Crypto Wallet" button
- After connecting, an Ethereum-style wallet approves a quick, free signature proving it's really theirs (on Lite, Solana and XRP Ledger wallets are checked without one), and SkyeGate verifies the holdings via InsumerAPI
- If they qualify, the gated content is revealed (loaded server-side, not in page source)
安装:
- Upload the
skyegatefolder to/wp-content/plugins/or install via the WordPress plugin directory - Activate the plugin through the Plugins menu
- Open Settings > SkyeGate and use Create a gate: choose what a visitor must hold, pick the chain, paste the token's or collection's address, and copy the shortcode it writes
- Paste the shortcode into any post or page and put your content between the two tags. Open the page: you should see the gate with a "Connect Crypto Wallet" button where your content was
- Optionally configure default chain, button text, and gate style under Settings > SkyeGate
屏幕截图:
常见问题:
How do I set up my first gate?
The quickest way is Create a gate under Settings > SkyeGate: answer its questions and it writes the shortcode for you to copy. To write one by hand, wrap the content you want to protect in the shortcode and say what a visitor must hold. Four attributes do most of the work:
chain: where the token or collection lives, for exampleethereum,base,polygon,solanaorxrplcontract: the token's or collection's address. To gate on a chain's own coin, usecontract="native"(on Solana and the XRP Ledger you can simply leave it out)threshold: how much of a token a visitor must hold. The default is 1type: leave it out for a token, or settype="nft_ownership"for an NFT collection
[skyegate chain="ethereum" contract="0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48" threshold="100"]Only holders see this.[/skyegate] (at least 100 USDC on Ethereum).
An NFT gate: [skyegate chain="ethereum" type="nft_ownership" contract="0xYourCollectionAddress"]Only holders see this.[/skyegate]
Always close the gate with [/skyegate], and always say what must be held. A [skyegate] with no contract on an Ethereum-style chain is not a working gate: administrators see a message saying what to correct, and visitors see nothing in its place.
Do I need an API key to get started?
No. SkyeGate includes InsumerAPI verification out of the box. No API key or account required.
What wallets are supported?
MetaMask, Phantom (EVM + Solana), Coinbase Wallet, and any wallet that supports EIP-6963. Visitors without a wallet extension can use a Coinbase Smart Wallet: a passkey wallet that opens in a popup, no install required.
Can I gate by Solana tokens?
Yes. Put the token's mint address in contract, for example [skyegate chain="solana" contract="<mint address>" threshold="1000"]. Classic Solana tokens and Token-2022 tokens both work. Leave contract out to gate on SOL itself. Phantom connects automatically for Solana verification.
Can I gate by a Solana NFT collection?
Yes. Use type="nft_ownership" and put the collection's verified address in contract, for example [skyegate chain="solana" type="nft_ownership" contract="<collection address>"]. Anyone holding an NFT from that collection gets in. Put one NFT's own address in contract instead to recognize that one NFT only. An NFT counts only when the collection's creator has verified it as part of the collection, so an NFT that merely claims to belong is not recognized.
Can the gate tell visitors what it recognizes?
Yes, by default. The gate shows a "Recognized here:" line with the chain name, so visitors know which wallet to bring. Add recognized to choose the words, or recognized="none" to hide it.
- Your own words:
[skyegate contract="0xA0b8..." chain="ethereum" threshold="100" recognized="Hold 100 USDC"] - A description built from the condition:
[skyegate chain="solana" threshold="1" recognized="auto"]shows "At least 1 of the native coin" and "Solana".
fail_message, and offers "Try another wallet".
Can the gate show the collection's picture, or where to get it?
Yes. image puts a picture at the top of the gate (a link to the collection's image or your logo). get_url adds a button for visitors whose wallet does not qualify yet ("Get one" on an NFT gate, "How to qualify" on others), and get_label changes its words.
Will the gate match my site?
Yes. Under Settings, Appearance, "Match my site" (the default) draws the gate from the colours around it, so it suits light and dark pages alike. Light and Dark fix the colours instead. Accent Colour sets the button and highlights.
Can I gate by XRP Ledger tokens and NFTs?
Yes. Use chain="xrpl".
- XRP itself:
[skyegate chain="xrpl" threshold="10"] - A token (trust line): put the issuer's address in
contractand the token's currency code incurrency, for example[skyegate chain="xrpl" contract="rIssuerAddress..." currency="USD" threshold="100"]. A code is 1 to 40 characters with no spaces, and is sent exactly as you write it. Currency codes on the XRP Ledger are case-sensitive (USDandusdare different tokens), so copy it exactly as the issuer created it. If a code contains symbols a shortcode cannot carry, such as<,>,&,[or], enter its 40-character hex form instead. - An NFT:
[skyegate chain="xrpl" type="nft_ownership" contract="rIssuerAddress..."]accepts any NFT from that issuer. Addtaxon="123"(a whole number from 0 to 4294967295) to accept only one collection under the issuer.
What does a visitor see if a check cannot be completed?
The gate stays closed. A visitor is told their wallet does not meet the requirements only when a signed check says so. If the check could not be completed, they are told it could not be checked right now and offered a Try again button. If the gate's own setup was declined, they are asked to contact the site owner, and administrators see the reason on the gate.
Is the gated content truly hidden?
Yes. Gated content is stored server-side and only delivered via AJAX after wallet verification passes. It is not present in the page source.
Is user data collected?
No. SkyeGate uses InsumerAPI to check on-chain data (token balances, NFT ownership). Verification results are cryptographically signed (ECDSA + JWKS). No personal information, email addresses, or wallet contents are stored.
更新日志:
1.5.1 - 2026-11-13
- Blast is retired: the network has shut down, so nothing on it can be checked. A gate that names Blast stays closed and tells the site administrator why.
- Adds Tempo (
chain="tempo"). Tempo has no coin of its own, so a gate there always names a token, and Create a gate does not offer the coin choice on Tempo. - Visitors holding tokens on Tempo connect with a standard wallet such as MetaMask or Rabby.
- The chain count is unchanged at 32. No change to how a gate on any other chain is checked.
- New: Create a gate. Settings > SkyeGate now opens with a short form. Choose what a visitor must hold (a token, an NFT from a collection, or a chain's own coin), pick the chain, paste the address, and copy a finished shortcode. Nothing to write by hand.
- New: a "Create a gate" link beside the plugin on the Plugins screen, and a short welcome after activation that points to it.
- A gate placed outside a post's own text, such as in a widget, a page builder or a theme template, now loads what it needs to work.
- The examples on the Settings screen are brought up to date, and the post-quantum status lines there are worded more plainly.
- The default connect button now reads "Connect Crypto Wallet" everywhere. Button text you set yourself is unchanged.
- Removed a setting left over from an early version that no longer did anything.
- The plugin's name and description now say what it does, and its details link to the plugin's home page.
- The readme opens with a first gate you can copy, and answers "How do I set up my first gate?" first.
- No change to how a gate is checked or to any gate you have already made.
- Hardened: each gate's access is now tied to that exact gate, meaning its conditions and the content it protects. A wallet that qualifies for one gate on a page can only ever open that gate, however the page is shown (feeds, archives, paginated posts).
- Hardened: the gated part of a draft, scheduled, private or password-protected post is only given to visitors who may read that post.
- Hardened: the browser session that holds a visitor's access is now made from the system's secure random source.
- After updating, visitors who unlocked a gate in the last day are asked to check their wallet once more.
- Requires PHP 8.2 or newer. PHP 7.4, 8.0 and 8.1 no longer receive security fixes.
- A new look for the gate. It takes on the colours around it, so it sits naturally on light and dark sites instead of showing as a white box. Settings has Appearance (Match my site, Light or Dark) and Accent Colour; button text turns dark or light to stay readable on any accent.
- The gate can show a picture of what unlocks it: add
imagewith a link to the collection's image or a logo. Without one it shows a lock. - What the gate asks for is now shown by default, under "Recognized here:". Add
recognized="none"to hide it. - While a wallet is checked the gate shows its steps: Connect, Sign, Check.
- A wallet that does not qualify gets a clear answer: "This wallet doesn't qualify yet.", each requirement ticked or crossed, and a "Try another wallet" button that brings the gate back as it started. Add
get_urlto offer visitors a link: "Get one" on an NFT gate, "How to qualify" on others, or your own words withget_label. - After unlocking, a small "Unlocked" note above the content names what unlocked it. It can be turned off under Settings, After Unlocking.
- Icons are drawn, not emoji. A wallet button that fails to connect keeps the text you set for it.
- A Solana token can now be named by its mint address in either
contractortoken. Before, a mint address intokenwas not used and the gate checked SOL instead. On other chains an address intokennow shows the site owner a message pointing tocontract, and the gate stays closed until it is moved. Token symbols intokenwork as before. - Settings and readme show a Solana token example.
- The membership pass window now opens on skyemeta.com as the Bothy Pass. A member already signed in to their Bothy Pass approves in one tap. Gates, conditions and checks are unchanged.
- Adds "Recognized here": a gate can now tell visitors what it recognizes, so they know which wallet to bring. Add the new
recognizedattribute with your own words (for examplerecognized="Hold 100 USDC") orrecognized="auto"for a description built from the condition. The chain name is shown beside it. Gates without the attribute look exactly as before. - A gate that shows what it recognizes keeps that line on screen after a signed no, and says the wallet does not hold what the gate recognizes. Your own
messageandfail_messageare left as written. - The attribute only changes what is displayed. The check, and anything already remembered for a visitor, is the same with or without it.
- Updates: the default gate message now says "This content is for holders" where it said "members". A
messageyou wrote yourself is unchanged.
- Clearer messages at the gate. A visitor is told their wallet does not meet the requirements only when a signed check says so. If a check could not be completed, the gate stays closed, says the wallet could not be checked right now, and offers a Try again button. If the gate's own setup was declined, the visitor is asked to contact the site owner.
- For administrators: when the verification service declines a gate's setup, its explanation appears on the gate, visible to administrators only, so a shortcode that needs correcting says what to correct.
- A missing or lapsed ownership signature now says so and lets the visitor sign again.
- Adds XRP Ledger token gates: the new
currencyattribute names a trust line token's currency code and is checked and then sent exactly as written (codes are case-sensitive). An XRP Ledger token gate that leaves it out, or carries a code that is not well formed, says so on the page for administrators. - Adds the optional
taxonattribute, a whole number from 0 to 4294967295, which limits an XRP Ledger NFT gate to one collection under an issuer. - Updates: the readme states SkyeGate Pro's chain count as 34.
- Post-quantum signature checking strengthened: the post-quantum signature now has to vouch for every claim in the verification it accompanies, where before it was matched on a few. On hosts that can check it (PHP 8.4+ with OpenSSL 3.5+), a post-quantum signature that differs from the signed verification in any claim is refused. Nothing changes on other hosts, and there is nothing to configure.
- Updates: token gates no longer send a decimals value. The token's own decimals are read from the chain, so the
decimalsattribute is no longer needed. Shortcodes that still carry it keep working. - Adds Robinhood Chain and Arc.
- Updates: Moonbeam and Moonriver are retired. A gate that names either one stays closed and tells the site administrator why.
- Clarifies: an NFT gate with no collection address now says so on the page for administrators.
- A remembered verification now belongs to the visitor who earned it. A verdict was remembered against the wallet address alone, and an address is public, so someone who knew a member's address could pick up that member's access during the cache window without proving the wallet was theirs. The ownership signature is now part of what identifies a remembered verdict, and a check on an EVM wallet that carries no signature is declined by the plugin itself.
- The cache duration setting now explains what it does and what to set it to.
- Access now expires exactly when the check behind it does. A returning visitor refreshed their own access without a new check being made, so access could outlast the check that granted it by up to the cache window. It is now capped by the remaining life of that check.
- EAS attestation gates now work from the shortcode. The
templateattribute is read as documented. - Token thresholds are sent as exact decimal strings, matching the current verification contract. Very small and very large thresholds are no longer reshaped in transit.
- Post-quantum signature checking strengthened: a post-quantum signature is now accepted only from the attestation signing key, and the key named in the response must be the key that actually signed.
- The settings screen reports the outcome of the most recent verification, not just whether this host can check post-quantum signatures.
- Housekeeping: the package no longer includes the build tooling's dependency lockfile, which WordPress never used. No functional changes.
- Post-quantum signatures: InsumerAPI now signs each result twice, with ES256 and a post-quantum ML-DSA-65 signature. On hosts that can verify the second one (PHP 8.4+ with OpenSSL 3.5+) the plugin checks it and refuses one that fails; on other hosts the ES256 verification stands alone and the settings screen says so. Nothing existing changes.
- Verification now accepts attestations from InsumerAPI's newer signing keys (key identifier insumer-attest-v2) alongside the original insumer-attest-v1 - required as verification accounts move to the newer keys
- Strengthened wallet verification with an ownership signature: after connecting, the visitor's wallet approves a quick, free signature (no transaction, nothing to type) proving they control the address - passkey wallets confirm with Face ID or fingerprint
- One signature covers the whole visit - every gate on the page then verifies as usual
- The signature goes straight from the visitor's browser to the verification service; your site never handles it, and still only ever sees the signed yes-or-no
- Membership pass (email) connections carry the same ownership proof automatically - the pass signs during Approve, nothing extra for the member to do
- New: "Membership pass (email)" on every gate. Visitors whose community pass lives in an email wallet (a SkyeMeta Bothy pass) connect through a secure window on the pass's own site: they approve once and the gate verifies as usual. No app, no extension, nothing installed
- Clearer gate: "Connect Crypto Wallets" says what it does, the passkey option carries its current Base account name, and each alternative explains who it's for
- Works alongside every existing wallet connection, nothing changes for MetaMask, Phantom, Coinbase, GemWallet, or Crossmark
- New: Coinbase Smart Wallet (passkey) support. Visitors without a wallet extension can connect with a passkey popup; the Coinbase Wallet SDK ships inside the plugin and loads only when chosen (no CDN)
- Clearer guidance when no browser wallet is detected
- Single-condition gates on 31 blockchains (token balance, NFT ownership, EAS attestation)
- Multi-wallet: MetaMask, Phantom, Coinbase Wallet, and any wallet supporting EIP-6963
- Cryptographically signed verification results (ECDSA + JWKS), verified on the server before content release
- Server-side content delivery: gated HTML is never present in the page source
- Per-visitor session binding so a verification in one browser does not unlock gated content in another
- Built-in caching to minimize verification calls