The Challenge

For our MEXC Node Giveaway campaign, we needed participants to complete KYC verification via ShareRing Me and prove on-chain staking to ShareLedger validators — all within Zealy's gamified quest platform. ShareLedger isn't a natively supported chain in Zealy, and our verification requires zero-knowledge proofs from the ShareRing Link SDK, something no existing Zealy integration supports.

We needed a solution that could bridge Zealy's API task system with ShareRing Link's browser-based QR verification and Cosmos SDK staking queries, all without requiring users to manually copy-paste wallet addresses or verification codes.

Components

The integration connects four systems through N8N middleware, with a WordPress page template serving as the bridge between Zealy's redirect flow and ShareRing Link's QR-based verification.

Quest 1: Verify with ShareRing

This is the core integration. Zealy's Zealy Connect identification method redirects users to our WordPress page, where ShareRing Link captures their KYC status and wallet address via a zero-knowledge QR scan. N8N handles HMAC signing and stores the verification server-side.

Quest 6: Verify On-Chain Staking

Once a user's wallet is stored via Zealy Connect in Quest 1, subsequent quests can automatically access it. Quest 6 uses the same Zealy Connect identifier to query ShareLedger's Cosmos LCD endpoint for delegation data.

// N8N HTTP Request node queries the Cosmos staking API
GET https://lcd.explorer.shareri.ng/cosmos/staking/v1beta1/delegations/{walletAddress}

// Headers (required to bypass Cloudflare)
User-Agent: Mozilla/5.0 (compatible; ShareRingZealy/1.0)

// Response contains delegation_responses[] with:
//   delegation.validator_address  → compare to your target validators
//   balance.amount               → in nshr (1 SHR = 10^9 nshr)

Quest Structure

Our campaign used 13 quests across four categories: onboarding, staking verification, social engagement, and referrals. Quest 1 (KYC) serves as the gateway — it blocks all other categories until completed.

Middleware Configuration

Two N8N workflows handle all automated verification. Both require HTTPS endpoints (Zealy won't call HTTP). Each webhook uses Header Auth with an API key that must match the one configured in Zealy's quest task settings.

Workflow 1: KYC Verification

Contains two webhook paths in one workflow:

// Path 1: Called by WordPress page after QR scan
POST /webhook/sharering-link-store
  ← Receives scan data + callbackUrl
  → Returns HMAC-signed redirect URL

// Path 2: Called by Zealy when user claims quest
POST /webhook/sharering-link-verify
  ← Receives { userId, accounts: { 'zealy-connect': wallet } }
  → Returns 200 (pass) or 400 (fail)

The Store & Generate Redirect URL node does the heavy lifting — it stores verification data in N8N's workflow static data (keyed by Zealy user ID), builds the callback URL with the wallet as the identifier parameter, and signs it with HMAC-SHA256 using the community secret.

const crypto = require('crypto');
const COMMUNITY_SECRET = 'YOUR_COMMUNITY_SECRET';

// Build callback URL with wallet as identifier
const separator = callbackUrl.indexOf('?') !== -1 ? '&' : '?';
const urlWithId = callbackUrl + separator +
  'identifier=' + encodeURIComponent(walletAddress);

// HMAC-SHA256 sign (before appending signature param)
const hmac = crypto.createHmac('sha256', COMMUNITY_SECRET);
hmac.update(urlWithId);
const signature = hmac.digest('hex');
const redirectUrl = urlWithId + '&signature=' + signature;

Workflow 2: Staking Verification

Single webhook: /webhook/zealy-staking-verify. Extracts the wallet from the Zealy Connect identifier, queries the ShareLedger LCD endpoint for delegations, and checks the target validator(s) and minimum stake amount.

Page Template

The verification page is a WordPress page template (page-sharering-verify.php) that loads the ShareRing Link JavaScript library and handles the Zealy Connect redirect flow. It uses wp_enqueue_script with proper dependency chains to ensure jQuery, the QR code plugin, and the ShareRing library load in the correct order.

<?php
wp_enqueue_script('jquery');
wp_enqueue_script('jquery-qrcode',
  'https://cdnjs.cloudflare.com/ajax/libs/jquery.qrcode/1.0/jquery.qrcode.min.js',
  array('jquery'), '1.0', false);
wp_enqueue_script('sharering-link-lib',
  'https://raw.githack.com/.../sharering.query.lib.prod.min.js',
  array('jquery', 'jquery-qrcode'), '1.0', false);
wp_add_inline_script('sharering-link-lib', 'var $ = jQuery;', 'before');
?>

Three values to configure in the template: the ShareRing Link Query ID (with client ID), the Query Owner address, and your N8N webhook URL. The community secret is never in this file — it stays server-side in N8N.

What We Discovered

What's Included

Everything you need to replicate this integration for your own project. Clone the repository and follow the README for step-by-step setup.