poly-auth-wallets

Provisions per-tenant Polymarket wallets with Privy idempotent workflows and AEAD-at-rest custodial consent.

4|5|Updated Nov 5, 2025
One-click install
npx skills add https://github.com/cogni-dao/cogni --skill poly-auth-wallets
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: poly-auth-wallets
Source: https://github.com/cogni-dao/cogni/tree/main/.claude/skills/poly-auth-wallets
Command: npx skills add https://github.com/cogni-dao/cogni --skill poly-auth-wallets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the provisioning, onboarding, and secure management of per-tenant Polymarket trading wallets, including Privy-based signing, AEAD-at-rest for credentials, and phase-B workflows.

Core Features & Use Cases

  • Per-tenant provisioning: one wallet per billing account with deterministic idempotency.
  • Secure wallet signing and storage: integrated Privy HSM, AEAD-at-rest encryption, and audit-ready consent flows.
  • Onboarding and maintenance: supports onboarding new tenants, managing wallet connections, and lifecycle upgrades across generation changes.
  • Use Case: For a new tenant, run a connect flow to provision a wallet, obtain a funder address, and verify a one-row-per-wallet record in poly_wallet_connections.

Quick Start

Provision a new per-tenant wallet for a given billing_account_id with custodialConsent and return the generated connection_id and funder_address.

Frequently Asked Questions about poly-auth-wallets

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I provision per-tenant wallets for Polymarket using Privy?

Per-tenant wallet provisioning uses Privy to create a wallet for a billing account with an idempotency key, returning a connection ID and funder address. Custodial consent and RLS enforce tenant isolation.

What is AEAD-at-rest and how does it secure multi-tenant wallet onboarding?

AEAD-at-rest encrypts wallet credentials during multi-tenant onboarding, ensuring secure data handling. It protects Privy wallet signing keys and connection records stored in the database against unauthorized access.

Can I use deterministic idempotency to prevent duplicate wallet provisioning?

Yes, deterministic idempotency prevents duplicate wallet provisioning by using an idempotency key during Privy wallet creation. This ensures only one wallet is generated per billing account across retry attempts.

Does per-tenant wallet provisioning support custodial consent handling?

Per-tenant wallet provisioning supports custodial consent handling through phase-B governance workflows. It satisfies compile-time constraints for CustodialConsent, ensuring audit-ready consent flows during the wallet connection process.

What is the best way to manage wallet lifecycle upgrades across generation changes?

Managing wallet lifecycle upgrades across generation changes requires deterministic idempotent provisioning and phase-B governance workflows. This approach maintains one wallet per billing account and ensures secure data handling during transitions.

Why does tenant isolation require row-level security for wallet connections?

Tenant isolation requires row-level security (RLS) to enforce strict data boundaries for wallet connections. RLS ensures each tenant's wallet records in poly_wallet_connections remain inaccessible to other tenants, maintaining secure multi-tenancy.