GNORIXBIOMETRIC AUTHORIZATION NEAR / LOCAL SANDBOX
Connecting to local node

FROM FINGERPRINT TO APPROVAL

How it works

  1. Find the useful details

    Gnorix finds distinctive points in a fingerprint, such as where a line ends or splits, and rates how clearly each one appears.

  2. Prepare many ways to sign

    It combines these points in different groups, giving clearer details more weight. Each chosen combination produces a signing key. One public ID represents this set of prepared keys.

  3. Use a smaller sample

    A fresh scan can contain just part of the fingerprint. Gnorix tries combinations from that sample, allowing for small shifts, until it recovers a registered key. If it cannot find one, the attempt does not produce a signature.

  4. Approve the exact transfer

    The recovered key signs the chosen recipient and amount. NEAR checks the signature and verifies that the key belongs to the registered set before moving the test tokens.

Your demo session has its own wallets and test balances for one hour. All sessions use one private local NEAR chain and synthetic test fingerprints.

Transaction lab

Real NEAR transactions Test tokens

Transfer

02 / BIOMETRIC INPUT

Your fingerprint

Awaiting wallet

The wallet’s test fingerprint will appear here.

Signing points appear after reconstruction

Each approval analyzes a new random circular sample. The surroundings fade into blur. Minimum feature priority: 0.1.

03 / AUTHORIZE

Send test tokens

GXT
Transfer recipient and amount
Other demo wallet
Available —
GXT

No GXT transfer fee. Up to 24 decimal places.

TRANSFER SUMMARY

Enter an amount

Choose the recipient before signing.

Fresh capture per approval. Signs this exact transfer.

Ready when you are
No transfer submitted.

Execution

  1. 01
    Reconstruct & signFingerprint key
  2. 02
    Submit to NEAROn-chain verification
  3. 03
    Confirm transferReceipt & balances
GAS LIMIT—

Signature & Merkle proof

Sign a transfer to reveal its membership path

Public signature

Hex strings you can inspect and copy. The private key never appears here.

Registered root
—
Public key
Available after signing
Signature
Available after signing
Nonce
—
Leaves
—
Path levels
—

Merkle membership path

Awaiting signature

Selected leaf → sibling hashes → registered root. Each sibling represents the other subtree.

An enrolled key will connect to this root through a Merkle path. Approve a transfer to see the exact nodes.