Listsinceblock parameter: target-confirmations

1

listsinceblock help returns:

listsinceblock ( "blockhash" target-confirmations ) Get all transactions in blocks since block [blockhash], or all transactions if omitted Arguments: 1. "blockhash" (string, optional) The block hash to list transactions since 2. target-confirmations: (numeric, optional) The confirmations required, must be 1 or more

I sent a coin to my wallet and a few seconds later I executed listsinceblock 1. My transaction was just broadcasted so it had 0 confirmations, as expected. Note the target-confirmations parameter above which must be greater than 0 no matter what.

So for my test I executed bitcoin-cli listsinceblock 0000000008eb5d53efbb39d2cb9f595e5bd567c295936de5c2282bbb8ef46cf0 1 which returned:

{ "transactions" : [ { "account" : "", "address" : "mzE6DJMHPghYpVg4GCurMbxSSXBfW1KCFH", "category" : "receive", "amount" : 1.00000000, "confirmations" : 0, "txid" :...
0 0
2

Hi, I'm trying to track incomming transactions using bitcoind RPC API, --blocknotify and listsinceblock:

0. wait for --blocknotify hint
1. execute listsinceblock blockhash, 6 (target-confirmations), where blockhash is empty if running for the first time or lastblock returned by listsinceblock last time (step 3)
2. save to database transactions with confirmations >= 6 and with txid not already in database
3. remember lastblock returned by listsinceblock
4. goto 0

It is working fine and thanks to listsinceblock target-confirmation parameter lastblock is correctly shifted by 6 so I don't ommit any transactions.

If I understand correctly during chain fork blocks are lost and listsinceblock will return all transactions again because lastblock won't exist in new blockchain.

Questions:

A. Is it safe to rely on txid while ignoring already imported transactions in such situation?

B. I should also delete already imported...

0 0
3

The second param of listsinceblock

From issue 8752

The second parameter (target confirmation) is quite strange and should probably be better > documented in the RPC help of listsinceblock (check original comment: #199 (comment))

From the actual docs here is it is:

target-confirmations: (numeric, optional) The confirmations required, must be 1 or more

However, that's misleading at best. I've seen at least one project thinking that target-confirmations means "filter to only show transactions of n target-confirmations". It's a weird param but I'd document it as

target-confirmations: (numeric, optional) Return the hash of the block that has target-confirmations of confirmations, for use in a further call to listsinceblock

Transactions confirmations

Says:

"confirmations": n, (numeric) The number of confirmations for the transaction. Available for 'send' and 'receive' category of transactions.

It should...

0 0
4


Colossuscoin2.0 has been launched successful on February 08, 2015! Fair Launch, no ICO/IPO!
Colossuscoin announced the planned release of ColossusCoin2.0 9 days before the release on January 30, 2015.
https://www.altcoinc.../coins/1288-CV2

October 14, 2015 Feature update for CV2
New Update:
Please update your Colossuscoin2.0 wallets
ColossusCoin2.0 Version 1.2.0 has been released

ColossusCoin2 Version 1.2.0 comes with a the change of Multisend GUI which replaces the CV2 for Charity function. Multisend allows you to send up to 100% of your Stake to multiple addresses of your choosing. A small fix to the Hashsettings has been added.

MultiSend RPC calls
multisend
What is MultiSend?
MultiSend is a rebuild of what used to be called Stake For Charity (s4c)
MultiSend allows a user to automatically send a percent of their stake reward to as many addresses as you would like
The...

0 0
5

Novacoind & GUI console commands

In command line:

novacoind help

or

help

in console.

For get help for command

novacoind help

or

help

in console

Commands

addmultisigaddress [account] Add a nrequired-to-sign multisignature address to the wallet" each key is a NovaCoin address or hex-encoded public key If [account] is specified, assign address to [account]. addnode Attempts add or remove from the addnode list or try a connection to once. addredeemscript [account] Add a P2SH address with a specified redeemScript to the wallet. If [account] is specified, assign address to [account]. backupwallet Safely copies wallet.dat to destination, which can be a directory or a path with filename. checkwallet Check wallet for integrity. ...
0 0
6

Command: help

listsinceblock ( "blockhash" target_confirmations include_watchonly) Get all transactions in blocks since block [blockhash], or all transactions if omitted Arguments: 1. "blockhash" (string, optional) The block hash to list transactions since 2. target_confirmations: (numeric, optional) The confirmations required, must be 1 or more 3. include_watchonly: (bool, optional, default=false) Include transactions to watch-only addresses (see 'importaddress') Result: { "transactions": [ "account":"accountname", (string) DEPRECATED. The account name associated with the transaction. Will be "" for the default account. "address":"address", (string) The bitcoin address of the transaction. Not present for move transactions (category = move). "category":"send|receive", (string) The transaction category. 'send' has negative amounts, 'receive' has positive amounts. "amount": x.xxx, (numeric) The amount in BTC. This is negative for...
0 0
7
Command Parameters Description Requires unlocked wallet addmultisigaddress [account] Add a nrequired-to-sign multisignature address to the wallet. Each key is a Litecoin address or hex-encoded public key. If [account] is specified, assign address to [account]. N addnode version 0.8 Attempts add or remove from the addnode list or try a connection to once. N backupwallet Safely copies wallet.dat to destination, which can be a directory or a path with filename. N bannode OMG2 only Bans until unix timestamp . Set to -1 to unban a node. N createmultisig Creates a multi-signature address and returns a json object createrawtransaction [{"txid":txid,"vout":n},...] {address:amount,...} Creates a raw transaction spending given inputs. N decoderawtransaction Produces a human-readable JSON object for a raw transaction. N dumpprivkey Reveals the private key corresponding to Y encryptwallet Encrypts the wallet with . N getaccount Returns the account associated...
0 0
8

Many commands can be used for multiple units (Such as NuBits or NuShares). Some commands will force you to specify the unit code (B or S), but others will not. In the cases where you aren’t required to provide the code, commands will default to NuShares. If you would like to use other units it can be done a couple different ways.

Pointing to the units network port Preceeding commands with the --unit= parameter

Network ports should always be used in cases of connecting your application with Nu (such as an exchange).

Command line

The --unit= flag is provied as a command line convenience. For example to get a new NuBits address from the daemon you would run ./nud --unit=B getnewaddress as ./nud getnewaddress would return a NuShares address by default.

Nu Network Ports

Example of pointing Peatio exchange to use NuBits from the daemon:

rpc: http://nuEx:123exch@127.0.0.1:14002

protocol ports

RPC Ports

Other...

0 0
9

Listing the bitcoin addresses in your wallet is easily done via listreceivedbyaddress. It normally lists only addresses which already have received transactions, however you can list all the addresses by setting the first argument to 0, and the second one to true.

Required arguments are denoted inside < and > Optional arguments are inside [ and ].

Command Parameters Description Requires unlocked wallet? (v0.4.0+) addmultisigaddress [account] Add a nrequired-to-sign multisignature address to the wallet. Each key is a bitcoin address or hex-encoded public key. If [account] is specified, assign address to [account]. Returns a string containing the address. N addnode version 0.8 Attempts add or remove from the addnode list or try a connection to once. N backupwallet Safely copies wallet.dat to destination, which can be a directory or a path with filename. N createmultisig Creates a multi-signature address and returns a json object createrawtransaction ...
0 0
10

Open up the debug window, simply type the RPC command.

Navigate to the proper directory and type "./hobonickelsd" followed by the command.

Required arguments are denoted inside < and >. Optional arguments are inside [ and ].

Usage is Command Parameters.

Command Parameters Description Example

[account] Add a nrequired-to-sign multisignature address to the wallet. Each key is a HoboNickels address or hex-encoded public key. If [account] is specified, assign address to [account].

remove|onetry> Attempts add or remove from the addnode list or try a connection to once.

backupwallet

Safely copies wallet.dat to destination, which can be a directory or a path with filename.

checkwallet

Check wallet for integrity.

createmultisig

Creates a multi-signature address and returns a json object with keys:

address : hobonickels address redeemScript : hex-encoded redemption script

...
0 0
11

listsinceblock

Lists all transactions since the block with the hash.

Example

listsinceblock 0000000000009fe250400eed6cb80ecf09cd90642b0a12019d097c60ac462dcb [ { "account": , "address": VJtg5gwsYWNkuFpk7KQm3xSTjv79KJxfYW, "category": immature, "amount": 44.083437, "confirmations": -1, "generated": true, "txid": e3d4926ca5096d718a0df41068e26e00f928e77ca7de7abfba2c5e44cdc11bdd, "time": 1440620800, "timereceived": 1440620808, "fromaccount": }, { "account": , "address": VJtg5gwsYWNkuFpk7KQm3xSTjv79KJxfYW, "category": immature, "amount": 44.066961, "confirmations": -1, "generated": true, "txid": f2c3ac0a792a75f2086c42d6a0c5bef00850f5f0342d657cd009cc9af84e94ff, "time": 1440813453, "timereceived": 1440813508, "fromaccount": }, { "account": , "address": VJtg5gwsYWNkuFpk7KQm3xSTjv79KJxfYW, "category": immature, ...
0 0
12

Enter RPC commands in the console visible at menu help - debug window - console. In windows debug console you can type commands from below to get textual answers. Assuming you are running the daemon, typing gridcoinresearchd COMMAND may do the trick.

Command Parameters Description Requires unlocked wallet? addmultisigaddress [account] Add a nrequired-to-sign multisignature address to the wallet. Each key is a Gridcoin address or hex-encoded public key. If [account] is specified, assign address to [account]. Returns a string containing the address. N addnode Attempts add or remove from the addnode list or try a connection to once. N backupwallet Safely copies wallet.dat to destination, which can be a directory or a path with filename. N createmultisig Creates a multi-signature address and returns a json object createrawtransaction [{"txid":txid,"vout":n},...] {address:amount,...} Creates a raw transaction spending given inputs. N decoderawtransaction ...
0 0
13

The following commands are to be typed in the Help -> debug -> console in anoncoin-qtc or else at the command line to anoncoin-cli, after having started anoncoind

./anoncoind Anoncoin server starting ./anoncoin-cli help

This is the list of all commands:

== Blockchain == getbestblockhash getblock [verbose] getblockchaininfo getblockcount getblockhash getchaintips getdifficulty getmempoolinfo getrawmempool [verbose] gettxout [includemempool] gettxoutproof [blockhash] gettxoutsetinfo verifychain [checklevel] [numblocks] verifytxoutproof == Control == getinfo help ["command"] stop == Mining == getblocktemplate ["jsonrequestobject"] getgenerate gethashmeter [clear] getmininginfo getnetworkhashps [blocks] [height] getretargetpid [height] [verbose] getwork ["data"] prioritisetransaction setgenerate [genproclimit] submitblock ["jsonparametersobject"] == Network == addnode destination ["match|good|attempt|connect"] ["b32.i2p|base64|ip:port"] getaddednodeinfo ["node"]...
0 0
14

API Methods

addmultisigaddress

$ ./$COINNAMEd addmultisigaddress [account]

Add a nrequired-to-sign multisignature address to the wallet. Each key is a $COINNAME address or hex-encoded public key. If [account] is specified, assign address to [account].

addnode

$ ./$COINNAMEd addnode [account]

The addnode RPC attempts to add or remove a node from the addnode list, or to try a connection to a node once. The node to add as a string in the form of :. The IP address may be a hostname resolvable through DNS, an IPv4 address, an IPv4-as-IPv6 address, or an IPv6 address

addwitnessaddress (Added in Bitcoin Core 0.13.0)

$ ./$COINNAMEd addwitnessaddress 1BRo7qrYHMPrzdBDzfjmzteBdYAyTMXW75

A witness address that gets added to a script. Needs to be in the wallet and uncompressed.

backupwallet

$ ./$COINNAMEd backupwallet

Copies wallet.dat to destination, which can be a directory or a path with filename.

bumpfee (Added...

0 0
15

ZMQ:

When a “Transaction Lock” occurs the hash of the related transaction is broadcast through ZMQ using both the “zmqpubrawtxlock” and “zmqpubhashtxlock” channels.

zmqpubrawtxlock: publishes the raw transaction when locked via InstantSendzmqpubhashtxlock: publishes the transaction hash when locked via InstantSend

Note that Insight API has been customized to support the detection InstantSend transactions, this information is provided to clients through API and WebSocket.

RPC:

Prior to using RPC it’s important however to understand the underlying mechanisms behind how InstantSend works.

By default, the Dash Core daemon will launch using the following constant:

static const int DEFAULT_INSTANTSEND_DEPTH = 5;

This value can be overridden by passing the following argument to the Dash Core daemon:

-instantsenddepth=

This value indicates the number of “confirmations” a successful Transaction Lock represents. These parameters...

0 0
16

The Blockchain Receive Payments API V2 is the quickest and easiest way to begin accepting automated bitcoin payments. Consisting of just a simple HTTP GET request, you can be up and running in minutes.

One of the difficulties involved with receiving bitcoin payments is the need to generate a unique address for each new user or invoice. These addresses need to monitored and stored securely. The blockchain receive payments API takes care of the generation and monitoring of addresses. We will notify your server using a simple callback whenever a payment is received.

In order to use the Receive Payments API V2, please apply for an API key at https://api.blockchain.info/v2/apikey/request/. This API key is only for our Receive Payments API. You cannot use the standard blockchain wallet API key for Receive Payments V2, and vice versa.

This API requires you to have a BIP 32 account xPub in order to receive payments. The easiest way to start receiving...

0 0
17

Code:

$ dash-cli help == Blockchain == getbestblockhash getblock "hash" ( verbose ) getblockchaininfo getblockcount getblockhash index getblockheader "hash" ( verbose ) getchaintips getdifficulty getmempoolinfo getrawmempool ( verbose ) gettxout "txid" n ( includemempool ) gettxoutsetinfo verifychain ( checklevel numblocks ) == Control == getinfo help ( "command" ) stop == Dash == darksend masternode "command"... ( "passphrase" ) masternodelist ( "mode" "filter" ) mnbudget "command"... ( "passphrase" ) mnbudgetvoteraw mnfinalbudget "command"... ( "passphrase" ) mnsync [status|reset] spork [] == Generating == getgenerate gethashespersec setgenerate generate ( genproclimit ) == Mining == getblocktemplate ( "jsonrequestobject" ) getmininginfo getnetworkhashps ( blocks height ) prioritisetransaction submitblock "hexdata" ( "jsonparametersobject" ) == Network == addnode "node" "add|remove|onetry" getaddednodeinfo dns ( "node" ) getconnectioncount getnettotals getnetworkinfo...
0 0
18

bitcoin-python is a set of Python libraries that allows easy access to the bitcoin peer-to-peer cryptocurrency client API.

bitcoin-python is not actively maintained. I don't have the mental bandwidth to maintain it and good alternatives have sprung up over time.

I'd suggest python-bitcoinlib (https://github.com/petertodd/python-bitcoinlib ) as is the ultimate python bitcoin library. It offers not only RPC access but also a Python version of almost every bitcoin data structure.

The RPC is can be used through bitcoin.rpc.Proxy, see for example https://github.com/petertodd/python-bitcoinlib/blob/master/examples/make-bootstrap-rpc.py.

If anyone wants to take up the maintainer role for bitcoin-python, let me know.

Documentation can be found here, or in the source archive. It is built using Sphinx:

http://laanwj.github.com/bitcoin-python/doc/

bitcoin-python uses setuptools for the install script. There are no dependencies apart from Python...

0 0