Repository navigation
docs(blog): builder's guide to KYC, KYB, and KYA integration - #37
Merged
Merged
Conversation
New post, author Monserrat Mendoza, EN+ES. Walks through the three attestation categories (person tiers 1-3, business tier 4, agent tier 5), how to call each from the SDK, a flow diagram, and four product shapes that gate on one category or another. Every snippet is checked against @kumply/sdk@1.3.0 as actually published on npm (downloaded the tarball, type-checked a draft against its real .d.ts files with tsc), not the repo's own packages/sdk/README.md, which already documents meetsTierRequirement (PR #26) ahead of any release. That helper doesn't exist in 1.3.0's exports, so it's not mentioned here. Everything described runs on Fuji; the post is explicit that KUMPLY's own team issues the demo attestations with no identity check behind them, and that Mainnet C-Chain stays at zero attestations until Sumsub production is active. No hackathon or track is named. Also adds minimal <pre>/<code> block styling to the post template (no earlier post used one), verified by rendering both locales with run-web. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Avoids implying other compliance checks/vendors by name, and reads more naturally: "often starts with one question" instead of "only answer one question", and "makes it easy to get the category wrong" instead of "is where most integrations get the category wrong". EN + ES, no other change. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
apps/web/src/content/blog.ts).hasTieris deprecated, a flow diagram, and four product shapes (DeFi pool, agent marketplace, B2B payments/payroll, one-person-one-vote).@kumply/sdk@1.3.0as actually published on npm, not the repo's ownpackages/sdk/README.md: downloaded the real tarball, dropped it into a scratch project withviem, and type-checked a draft of each snippet against its.d.tsfiles withtsc(clean, exit 0).meetsTierRequirement(PR feat: add pure tier requirement helper #26) is documented in the local README ahead of release but does not exist in 1.3.0's exports, so it is not mentioned.<pre>/<code>block styling to the post page template, since no earlier post needed multi-line snippets; verified both locales render correctly (code blocks, the flow diagram, the scenario list) withrun-web,pageErrorsempty throughout. The diagram went through two rendering passes: the first had a code line clipped by the container width and a branch arrow crossing visually over a box, both fixed and re-verified.Disclosure: drafted with AI assistance under the user's direction, applied per their detailed instructions (content outline, SDK-accuracy requirement, and all stated rules).
Test plan
@kumply/sdkversion is live at merge time.