FV (Identity Verification Node)
<div class="post-category"><span class="cat-badge cat-nodes">Nodes</span></div>
<p class="lead"><strong>FV is the AI face and voice verification node. It provides biometric identity checks that other 1BZ services can call to onboard customers, sign contracts, and gate high-value transactions.</strong></p>
<h2>Overview</h2>
<p>Hosted at https://fv.1bz.biz, FV pairs a liveness-checked selfie with a short voice phrase to bind a real person to a DZID. Results are issued as signed attestations that any node can verify without storing biometrics themselves.</p>
<h2>Key components</h2>
<ul><li>Liveness-checked face capture</li><li>Voice match with anti-replay</li><li>Signed attestation bound to a DZID</li><li>DZIT billing per verification</li><li>Used by CA flow for handle verification</li></ul>
<h2>Related</h2>
<ul><li>[DZID — Virtual Identity](/post.php?slug=dzid-virtual-identity)</li><li>[Handle System & CA Verification](/post.php?slug=handle-system)</li><li>[DZIT Node](/post.php?slug=dzit-node)</li></ul>
Powered by BizNode™
Related Posts
Add a Command to Your Bot in 10 Lines of YAML
Adding a new bot feature used to mean editing Python, wiring a `CommandHandler`, and redeploying. With the Feature Manifest Framework it is four steps and about ten lines of YAML — and you get a slash command and a paid network handle from
How 1BZ Bots Define Features via Manifest
1BZ bots used to hand-wire every capability as a Python `CommandHandler`. That put even a trivial command one code change and a redeploy away from production. The Feature Manifest Framework replaces that with a declarative YAML file at `bot
Slash Command vs Handle — what each is for
Slash commands and handles are related but not identical. A slash command is the owner-facing UI inside a single bot; a handle is a network-facing service endpoint that any other bot, workflow, or API on the 1BZ network can call. The same u