Skip to main content

[V2.1] Counterparty and Self-hosted Wallets

The wallet addresses in your transactions that your organization doesn't hold, and how your policies treat each one.

Written by Emanuel

Two screens under Network list the addresses in your transactions that your organization doesn't hold, so your policies can approve, flag or reject the transactions that use them. Your own addresses are under My Organization › My Wallets, as described in My Wallets.

Hosted and self-hosted wallets

  • Counterparty Wallets: hosted wallets, whose keys an institution or a wallet provider holds for its customer. Your policies judge them by their risk score.

  • Self-hosted Wallets: wallets whose keys a person holds themselves, with no institution behind them. Your policies judge them by the proof that the wallet belongs to its owner.

An address counts as self-hosted when a proof of ownership comes with the transaction, a proof is already stored, or it is registered as self-hosted.

Counterparty Wallets

Network › Counterparty Wallets shows each address with these columns:

  • Address: the address, with a button to copy it in full.

  • Owner: who holds the address, or Unattributed when no one is known.

  • Chain: the blockchain the address is on.

  • Risk Score: the score from your blockchain analytics provider, or Not screened until a provider has scored the address. With several providers connected, each one's result is shown.

  • Status: how your policies treat the address: Approved, Flagged, Rejected or Not Reviewed.

The Policies card above the list counts your counterparty wallet rules by verdict, and shows the verdict for addresses that no rule matches beside Not reviewed. The rules turn a provider's risk score into Approve, Flag or Reject, and a provider that can't be reached gives Flag. They appear once you connect a blockchain analytics provider, such as Chainalysis or Elliptic, under Settings › Integrations, as described in Integrations. The address is then scored at every transaction that involves it.

Self-hosted Wallets

Network › Self-hosted Wallets shows each address with its Proof Type, its Proof Status and its Status, the verdict your policies give it.

The Self-hosted Wallets screen, the Proof Type and Proof Status columns boxed

Your customer proves that a self-hosted wallet is theirs, usually in your app as they withdraw to it or deposit from it. The proof types are:

  • Digital signature: your customer signs a message with the wallet's key. The signature is checked when it arrives, so the proof is verified straight away and your team has nothing to do.

  • Self-declaration, microtransaction and screenshot: the proof reads Submitted first. It moves to Accepted after the first authorized transaction that involves the address with that proof, and your team can also accept it by hand.

A new proof for an address replaces the one before it, and the earlier proofs are kept for the audit trail. Your developers record proofs through the API or the embedded component, as described in Wallets in the developer docs.

Your self-hosted wallet rules look at whether the proof is verified. A rule for verified proofs can approve or flag the transaction, and a rule for unverified proofs can flag or reject it. A wallet with no proof counts as unverified, and self-hosted wallets have no Not reviewed verdict. Click Edit policies to change the rules under Authorization Rules › Policies, as described in Policies.

Set a status for one wallet

A status you set by hand overrides what your rules would give that address.

  1. Find the address in Network › Counterparty Wallets or Network › Self-hosted Wallets.

  2. Click the menu (⋮) at the end of its row.

  3. Choose Approve, Flag or Reject.

The status applies to every transaction that uses the address, and your other policies still apply, with the strictest verdict winning. When something changes later that makes your rules stricter, such as a higher risk score, the address moves to the stricter verdict. A lighter result never replaces the status you set.

If you have questions about wallets, write to support@notabene.id.

Did this answer your question?