Loading…
Loading…
Software ideas builders can put on top of KUMPLY.
The app never holds user funds or keys, and never receives personal data. It only reads whether an address is verified.
Limit a reward to one claim per verified person, so a single person can't split it across many wallets.
isPersonAtLeast(address, TIER.BASIC)Gate voting power on a minimum verified level, so one verified person can't split their voice into many addresses.
isPersonAtLeast(address, TIER.BASIC)The same idea as the 0xGasless pilot: a paymaster only sponsors gas for addresses that hold a valid attestation, at whatever category or tier the integration needs.
verify() / isPersonAtLeast / isBusiness / isAgentSee how this works in practice on Ecosystem
Gate listing and bidding on isAgent(), with payments settled directly wallet to wallet.
isAgent(address)Check isAgent() before completing an HTTP 402 payment, so only a verified agent's wallet can pay for the response.
isAgent(address)Check isBusiness() on both sides of a transfer, so the counterparty is a verified company, not an anonymous wallet.
isBusiness(address)Gate validator registration on isBusiness(), the same check KUMPLY's ACP-99 ValidatorSetManager contract implements (the KUMPLY L1 itself is not activated yet).
isBusiness(address)Everything above runs on Avalanche Fuji testnet. Attestations used for testing are demo attestations issued directly by KUMPLY's team, not a real KYC, KYB, or KYA check. Mainnet C-Chain stays at zero attestations issued until Sumsub production is active.
This is not legal advice. Each builder reviews the rules of their own jurisdiction.