LogoLogo
PAO DocsInfrastructure DocsDeveloper DocsPeerplays.com
  • Introduction to Peerplays
  • Concepts
    • Decentralization
    • Consensus Mechanisms Compared
  • Technology
    • Peerplays Technical Summary
    • Intro to Peerplays Tokens
    • Intro to Peerplays Liquidity Pools
      • Service Infrastructure Pools
    • Staking (PowerUp) in Peerplays
    • Gamified User Namespaces and Subject Matter Expert Committees
    • Peer-to-Peer Autonomous Organizations: Flow Diagram
    • Gamified Proof of Stake (GPOS)
      • Wallet User Guide
        • GPOS Panel
        • GPOS Landing Page
        • Power Up
        • Power Down
        • Vote
        • Thank you for voting!
      • FAQ
        • General
        • GPOS Panel
        • Power Up & Power Down
        • Voting
        • Participation Rewards
    • Sidechain Operator Nodes (SONs)
      • New to SONs?
        • What are Sidechain Operating Nodes?
        • How do SONs Work?
        • Why are SONs important?
        • How do SONs impact me?
        • SON Fees & Performance Requirements
        • Peerplays SONs
      • FAQ
      • Running a SON Node
    • NFTs and Marketplace
      • NFT marketplace in Python
      • NFT Operations in Python
      • NFT, Marketplace, HRP, and RBAC related Commands/Use Cases
      • NFT command reference
    • Peerplays DEX
      • User Guide
        • Account Creation
        • Dashboard
          • Bitcoin Transaction
        • Market Activity
        • Peerplays Blocks
        • Settings
        • Wallet
        • Profile
        • GPOS - Voting
        • Logout
  • Witnesses
    • What is a Peerplays Witness?
    • Becoming a Peerplays Witness
    • Hardware Requirements
    • Installation Guides
  • Bookie Oracle Suite (BOS)
    • Introduction to BOS
    • BOS Installation
    • BookieSports
    • Manual Intervention Tool (MINT)
  • Data Proxies
    • Introduction to Data Proxies
    • How Data Proxies Work
    • Data Proxy Set Up
  • Couch Potato
    • Introduction
    • Installation
    • User Guide
  • Random Number Generator (RNG)
    • RNG Technical Summary
    • RNG API
  • API
    • Peerplays Core API
      • Popular API Calls
      • Account History API
      • Asset API
      • Block API
      • Crypto API
      • Database API
      • Network Broadcast API
      • Network Nodes API
      • Orders API
    • Wallet API
      • Account Calls
      • Asset Calls
      • Blockchain Inspection
      • General Calls
      • Governance
      • Privacy Mode
      • Trading Calls
      • Transaction Builder
      • Wallet Calls
    • Bookie API
      • General
      • Tournaments
      • Listeners
    • Python Peerplays
      • Installation
      • Creating the wallet
      • Creating an Account
      • NFT
      • Market Place
      • HRP / RBAC
  • Connecting Elasticsearch to a blockchain node
  • GitLab
    • GitLab Ticket Templates
    • Labels
    • Time Tracking
  • Other Documentation
    • Peerplays Home
    • Infrastructure Docs
    • Developer Docs
    • Site Reliability Engineering
  • Known Issues
    • Peerplays Disaster Recovery Plan
    • Sept 2021 Mainnet Outage - Postmortem Report
  • Kickstart Guide
    • Peerplays Developer
  • Risk Register
    • Introduction
      • Bunker Issue
        • DDOS Attack
        • Hypervisor Compromised
        • Power and Backup Failure
        • Crypto Restriction
      • Core-Block Issue
        • Expensive Servers
        • Witness node - Not reachable
        • Witnesses get DDOS'd
        • Bad Actor infiltrate witness/SONs
      • Credential Security
        • NEX Open Source Vulnerabilities
        • Keyloggers, access to NEX deployment
        • Password manager hacked
        • SONs active keys exposed in configuration
    • Glossary
  • Operation Cost Estimation
    • Project Operations
    • Cost Estimation
Powered by GitBook
On this page
  • Privacy Mode
  • set_key_label
  • get_key_label
  • get_public_key
  • get_blind_accounts
  • get_my_blind_accounts
  • get_blind_balances
  • create_blind_account
  • transfer_to_blind
  • transfer_from_blind
  • blind_transfer
  • blind_history
  • receive_blind_transfer
Export as PDF
  1. API
  2. Wallet API

Privacy Mode

PreviousGovernanceNextTrading Calls

Last updated 1 year ago

Privacy Mode

set_key_label

These methods are used for stealth transfers This method can be used to set a label for a public key

Note: No two keys can have the same label.

bool graphene::wallet::wallet_api::set_key_label(
    public_key_type key, 
    string label)
  • key: a public key

  • label: a user-defined string as label

True if the label was set, otherwise false

get_key_label

Get label of a public key.

string graphene::wallet::wallet_api::get_key_label(
    public_key_type key)const
  • key: a public key

The label if already set by , or an empty string if not set

get_public_key

Get the public key associated with a given label

public_key_type graphene::wallet::wallet_api::get_public_key(
    string label)const
  • label: a label

The public key associated with the given label.

get_blind_accounts

Get all blind accounts.

map<string, public_key_type> graphene::
wallet
::
wallet_api
::get_blind_accounts()const

All blind accounts

get_my_blind_accounts

Get all blind accounts for which this wallet has the private key.

map<string, public_key_type> graphene::wallet::wallet_api::get_my_blind_accounts()const

All blind accounts for which this wallet has the private key.

get_blind_balances

Return the total balances of all blinded commitments that can be claimed by the given account key or label.

vector<asset> graphene::wallet::wallet_api::get_blind_balances(
    string key_or_label)
  • key_or_label: a public key in Base58 format or a label

The total balances of all blinded commitments that can be claimed by the given account key or label

create_blind_account

Generates a new blind account for the given brain key and assigns it the given label

public_key_type graphene::
wallet
::
wallet_api
::create_blind_account(string label, string brain_key)
  • label: a label

  • brain_key: the brain key to be used to generate a new blind account

The public key of the new account

transfer_to_blind

Transfers a public balance from from_account_id_or_name to one or more blinded balances using a stealth transfer.

blind_confirmationgraphene::wallet::wallet_api::transfer_to_blind(
    string from_account_id_or_name, 
    string asset_symbol, 
    vector<pair<string, string>> to_amounts, 
    bool broadcast = false)
  • from_account_id_or_name: ID or name of an account to transfer from

  • asset_symbol: symbol or ID of the asset to be transferred

  • to_amounts: map from key or label to amount

  • broadcast: true to broadcast the transaction on the network

A blind confirmation

transfer_from_blind

Transfers funds from a set of blinded balances to a public account balance.

blind_confirmationgraphene::wallet::wallet_api::transfer_from_blind(
    string from_blind_account_key_or_label, 
    string to_account_id_or_name, 
    string amount, 
    string asset_symbol, 
    bool broadcast = false)
  • from_blind_account_key_or_label: a public key in Base58 format or a label to transfer from

  • to_account_id_or_name: ID or name of an account to transfer to

  • amount: the amount to be transferred

  • asset_symbol: symbol or ID of the asset to be transferred

  • broadcast: true to broadcast the transaction on the network

A blind confirmation.

blind_transfer

Transfer from one set of blinded balances to another.

blind_confirmationgraphene::wallet::wallet_api::blind_transfer(
    string from_key_or_label, 
    string to_key_or_label, 
    string amount, 
    string symbol, 
    bool broadcast = false)
  • from_key_or_label: a public key in Base58 format or a label to transfer from

  • to_key_or_label: a public key in Base58 format or a label to transfer to

  • amount: the amount to be transferred

  • symbol: symbol or ID of the asset to be transferred

  • broadcast: true to broadcast the transaction on the network

A blind confirmation

blind_history

Get all blind receipts to/form a particular account.

vector<blind_receipt> graphene::wallet::wallet_api::blind_history(
    string key_or_account)
  • key_or_account: a public key in Base58 format or an account

All blind receipts to/form the account.

receive_blind_transfer

Given a confirmation receipt, this method will parse it for a blinded balance and confirm that it exists in the blockchain. If it exists then it will report the amount received and who sent it.

blind_receipt graphene::
wallet
::
wallet_api
::receive_blind_transfer(string confirmation_receipt, string opt_from, string opt_memo)
  • confirmation_receipt: a base58 encoded stealth confirmation

  • opt_from: if not empty and the sender is a unknown public key, then the unknown public key will be given the label opt_from

  • opt_memo: a self-defined label for this transfer to be saved in local wallet file

A blind receipt.

set_key_label()