Bitcoin core wallet RPC console commands - Bitcoin-qt ...

Specify RPC wallet for each command? (x-post from /r/Bitcoin)

submitted by ASICmachine to CryptoCurrencyClassic [link] [comments]

Bitcoin ABC 0.19.12 has been released! This release includes the new ‘getblockstats’ RPC command as well as minor fixes related to logging and other bugs.

Bitcoin ABC 0.19.12 has been released! This release includes the new ‘getblockstats’ RPC command as well as minor fixes related to logging and other bugs. submitted by BitcoinXio to btc [link] [comments]

Bitcoin ABC 0.19.12 has been released! This release includes the new ‘getblockstats’ RPC command as well as minor fixes related to logging and other bugs.

Bitcoin ABC 0.19.12 has been released! This release includes the new ‘getblockstats’ RPC command as well as minor fixes related to logging and other bugs. submitted by vegasbooty to Cryptoandme [link] [comments]

Can anyone run RPC commands on my full node if I run bitcoind or bitcoin-qt connected to the internet?

Is RPC completely disabled if I don't include bitcoin.conf in my bitcoin directory, and if it's there, does bitcoind open ports automatically that allow anyone to RPC on my node?
submitted by sonkeypop to Bitcoin [link] [comments]

Recently learned about Bitcoins raw transactions and signing offline features through RPC commands, are all cryptocurrencies able to do this through their core client?

I know some coins have GUI ways of signing offline transactions like LTC and BTC having Electrum with user friendly features. As well as Ether and some others having HTML/web wallets that can be run offline.
But those tools are not available to all coins as far as I know. Having just learned that it can be done through the core client which I thought is something all coins have, I wanted to make sure if this option of keeping private keys in cold storage but still being able to send coins without making new addresses by signing offline would be available to all coins if done through RPC commands.
submitted by Epistechne to CryptoCurrency [link] [comments]

Are all these JSON-RPC commands supported by a pruned node? /r/Bitcoin

Are all these JSON-RPC commands supported by a pruned node? /Bitcoin submitted by ABitcoinAllBot to BitcoinAll [link] [comments]

09-30 18:33 - 'Recently learned about Bitcoins raw transactions and signing offline features through RPC commands, are all cryptocurrencies able to do this through their core client?' (self.Bitcoin) by /u/Epistechne removed from /r/Bitcoin within 22-32min

'''
[removed]
'''
Recently learned about Bitcoins raw transactions and signing offline features through RPC commands, are all cryptocurrencies able to do this through their core client?
Go1dfish undelete link
unreddit undelete link
Author: Epistechne
submitted by removalbot to removalbot [link] [comments]

Recently learned about Bitcoins raw transactions and signing offline features through RPC commands, are all cryptocurrencies able to do this through their core client? /r/Bitcoin

Recently learned about Bitcoins raw transactions and signing offline features through RPC commands, are all cryptocurrencies able to do this through their core client? /Bitcoin submitted by ABitcoinAllBot to BitcoinAll [link] [comments]

Recently learned about Bitcoins raw transactions and signing offline features through RPC commands, are all cryptocurrencies able to do this through their core client? /r/Bitcoin

Recently learned about Bitcoins raw transactions and signing offline features through RPC commands, are all cryptocurrencies able to do this through their core client? /Bitcoin submitted by cryptoallbot to cryptoall [link] [comments]

Can anyone run RPC commands on my full node if I run bitcoind or bitcoin-qt connected to the internet? /r/Bitcoin

Can anyone run RPC commands on my full node if I run bitcoind or bitcoin-qt connected to the internet? /Bitcoin submitted by HiIAMCaptainObvious to BitcoinAll [link] [comments]

Bitcoin RPC Remote Command Execution Exploit 2017 Secure your wallets, update!

submitted by BitcoinAllBot to BitcoinAllTV [link] [comments]

Bitcoin RPC Remote Command Execution Exploit 2017 Secure your wallets, update!

Bitcoin RPC Remote Command Execution Exploit 2017 Secure your wallets, update! submitted by BitcoinAllBot to BitcoinAll [link] [comments]

11-18 22:23 - 'Bitcoin RPC Remote Command Execution Exploit 2017 Secure your wallets, update!' (youtube.com) by /u/mra707 removed from /r/Bitcoin within 16-26min

Bitcoin RPC Remote Command Execution Exploit 2017 Secure your wallets, update!
Go1dfish undelete link
unreddit undelete link
Author: mra707
submitted by removalbot to removalbot [link] [comments]

Checking/polling a balance of an address in Electrum via the command line/RPC /r/Bitcoin

Checking/polling a balance of an address in Electrum via the command line/RPC /Bitcoin submitted by BitcoinAllBot to BitcoinAll [link] [comments]

Check the balance of an address in Electrun via the command line / RPC /r/Bitcoin

Check the balance of an address in Electrun via the command line / RPC /Bitcoin submitted by BitcoinAllBot to BitcoinAll [link] [comments]

Hey, r/Bitcoin and Node.js developers, I created an open-source Express middleware plugin that easily maps JSON-RPC commands to any url for rapid development.

Hey, Bitcoin and Node.js developers, I created an open-source Express middleware plugin that easily maps JSON-RPC commands to any url for rapid development. submitted by NielDLR to Bitcoin [link] [comments]

Sending RPC commands to Bitcoin Client

I'm trying like hell to learn java, and with some success. However, I want to learn how to connect to my bitcoin rpc server and send commands, such as getinfo or sendfrom.
I understand that functions are called methods in java, so I'd like a method to actually initiate the connection and verify that it works by sending a getinfo command, then when it returns something that isn't null, have the ability to send other commands.
I know there are java classes and stuff that people have already written, but I want to write it for myself and understand better how it works and what is required.
I have experience with several different programming languages and part of my job is to write custom modules for our ERP system, which uses some stupid mashup of cobol and VB. So, any help would be greatly appreciated!!! Thanks!
submitted by bmp02050 to learnjava [link] [comments]

How to Learn Bitcoin From Command Line

Hello everyone, I've been a long time BTC supporter and I'm wanting to dive deeper and learn Bitcoin from command line. Unfortunately, I have zero programming experience. I know the very basic terms but the only code I've ever written is "hello, world".
Before I start diving into command line I think it's best for me to read guides or watch youtube videos. Can someone help me on where to start? The link below is what popped up on Google but I don't even know where to start on GitHub so I'm quite lost. Any links or videos that can help me would be greatly appreciated. Thanks.
https://github.com/BlockchainCommons/Learning-Bitcoin-from-the-Command-Line
submitted by tpmv69 to Bitcoin [link] [comments]

Power of the Command Line (bitcoin-cli, hwi, electrum, trezorctl)

I think some of the console tools available with HW wallets today are greatly under utilized. Here's a quick write-up on how to create and sign a TXN very similar to 43d27...1fc06 found on the SLIP-14 wallet. I'll be using TrezorCTL, Electrum, and HWI for the signing. I won't go much into the setup or install, but feel free to ask if you have questions about it. Note, you don't have to use all three of these. Any one will produce a valid signed TXN for broadcast. I just showed how to do it three ways. Whats more some of the Electrum and HWI steps are interchangeable.
ColdCard also has a utility called ckcc that will do the sign operation instead of HWI, but in many ways they are interchangeable. KeepKey and Ledger both have libraries for scripted signing but no one-shot, one-line console apps that I know of. But HWI and Electrum of course work on all four.

TrezorCTL

This is the what most would think of to use to craft and sign TXNs, and is definitely very simple. The signing uses a script called build_tx.py to create a JSON file that is then used by the btc sign-tx command. The whole process is basically:
  1. tools/build_tx.py | trezorctl btc sign-tx -
This just means, take the output of build_tx and sign it. To copy 43d27...1fc06, I wrote a small script to feed build_tx, so my process looks like:
  1. ~/input.sh | tools/build_tx.py | trezorctl btc sign-tx -
But it's all very simple. Note... I used TrezorCTL v0.12.2 but build_tx.py version 0.13.0 1.

input.sh

```

!/bin/bash

secho() { sleep 1; echo $*}
secho "Testnet" # coin name secho "tbtc1.trezor.io" # blockbook server and outpoint (below) secho "e294c4c172c3d87991b0369e45d6af8584be92914d01e3060fad1ed31d12ff00:0" secho "m/84'/1'/0'/0/0" # prev_out derivation to signing key secho "4294967293" # Sequence for RBF; hex(-3) secho "segwit" # Signature type on prev_out to use secho "" # NACK to progress to outs secho "2MsiAgG5LVDmnmJUPnYaCeQnARWGbGSVnr3" # out[0].addr secho "10000000" # out[1].amt secho "tb1q9l0rk0gkgn73d0gc57qn3t3cwvucaj3h8wtrlu" # out[1].addr secho "20000000" # out[1].amt secho "tb1qejqxwzfld7zr6mf7ygqy5s5se5xq7vmt96jk9x" # out[2].addr secho "99999694" # out[2].amt secho "" # NACK to progress to change secho "" # NACK to skip change secho "2" # txn.version secho "0" # txn.locktime ```

Electrum

Electrum is one of the better GUI wallets available, but it also has a pretty good console interface. Like before you need your Trezor with the SLIP-14 wallet loaded and paired to Electrum. I'll assume Electrum is up and running with the Trezor wallet loaded to make things simple.
Like with TrezorCTL, Electrum feeds on a JSON file, but unlike TrezorCTL it needs that JSON squished into the command line. This is a simple sed command, but I won't bore you with the details, but just assume that's done. So the process in Electrum (v4.0.3) looks like:
  1. electrum serialize (create psbt to sign)
  2. electrum --wallet signtransaction (sign said psbt)
Still pretty simple right! Below is the JSON I smushed for #1

txn.json

{ "inputs": [{ "prevout_hash":"e294c4c172c3d87991b0369e45d6af8584be92914d01e3060fad1ed31d12ff00", "prevout_n": 0, "value_sats": 129999867 }], "outputs": [{ "address": "2MsiAgG5LVDmnmJUPnYaCeQnARWGbGSVnr3", "value_sats": 10000000 },{ "address": "tb1q9l0rk0gkgn73d0gc57qn3t3cwvucaj3h8wtrlu", "value_sats": 20000000 },{ "address": "tb1qejqxwzfld7zr6mf7ygqy5s5se5xq7vmt96jk9x", "value_sats": 99999694 }]}

HWI

HWI is an unsung hero in my book. It's a very small clean and simple interface between HW wallets and Bitcoin Core. It currently supports a good range of HW wallets. It keeps itself narrowly focused on TXN signing and offloads most everything else to Bitcoin Core. Again, I'll assume you've imported your Trezor keypool into Core and done the requisite IBD and rescan. And if you don't have the RPC enabled, you can always clone these commands into the QT-console.
To sign our TXN in HWI (v1.1.2), we will first need to craft (and finalize) it in Bitcoin Core (0.21.1). Like in Electrum, we will have to use simple sed to smush some JSON into command arguments, but I'll assume you have that covered. It will take an inputs.json and an outputs.json named separately.
  1. bitcoin-cli createpsbt (create psbt)
  2. bitcoin-cli -rpcwallet= walletprocesspsbt (process psbt)
  3. hwi -f signtx (sign psbt)
  4. bitcoin-cli -rpcwallet= finalizepsbt (get a signed TXN from psbt)
A little more involved, but still nothing too bad. Plus this gives you the full power of Bitcoin Core including integrations with LND (lightning).

inputs.json

[{ "txid": "e294c4c172c3d87991b0369e45d6af8584be92914d01e3060fad1ed31d12ff00", "vout": 0 }]

outputs.json

[{ "2MsiAgG5LVDmnmJUPnYaCeQnARWGbGSVnr3": 0.10000000 },{ "tb1q9l0rk0gkgn73d0gc57qn3t3cwvucaj3h8wtrlu": 0.20000000 },{ "tb1qejqxwzfld7zr6mf7ygqy5s5se5xq7vmt96jk9x": 0.99999694 }]

Conclusion

This may all seem like very low level coding, but is surprisingly simple once you get a knack for it. Whats more, all these platforms support testnet which allows you to practice with valueless coins until you get the hang of it. And, like many things in bitcoin, this is all (mostly) python, which is one of the easier languages to learn.
Enjoy
Footnotes
1 - https://github.com/trezotrezor-firmware/issues/1296
submitted by brianddk to Bitcoin [link] [comments]

How do you build a Online Shop that accepts only bitcoin?

I've been looking for tutorials but had no luck. I know Woocommerce has 3rd party plugins but I don't want to go that route. I know there is a way to code it yourself so it generates a btc wallet address etc but I have no idea how and can not find info. Can anyone point me in the right direction?
submitted by mikrofreaky to Bitcoin [link] [comments]

Gridcoin 5.0.0.0-Mandatory "Fern" Release

https://github.com/gridcoin-community/Gridcoin-Research/releases/tag/5.0.0.0
Finally! After over ten months of development and testing, "Fern" has arrived! This is a whopper. 240 pull requests merged. Essentially a complete rewrite that was started with the scraper (the "neural net" rewrite) in "Denise" has now been completed. Practically the ENTIRE Gridcoin specific codebase resting on top of the vanilla Bitcoin/Peercoin/Blackcoin vanilla PoS code has been rewritten. This removes the team requirement at last (see below), although there are many other important improvements besides that.
Fern was a monumental undertaking. We had to encode all of the old rules active for the v10 block protocol in new code and ensure that the new code was 100% compatible. This had to be done in such a way as to clear out all of the old spaghetti and ring-fence it with tightly controlled class implementations. We then wrote an entirely new, simplified ruleset for research rewards and reengineered contracts (which includes beacon management, polls, and voting) using properly classed code. The fundamentals of Gridcoin with this release are now on a very sound and maintainable footing, and the developers believe the codebase as updated here will serve as the fundamental basis for Gridcoin's future roadmap.
We have been testing this for MONTHS on testnet in various stages. The v10 (legacy) compatibility code has been running on testnet continuously as it was developed to ensure compatibility with existing nodes. During the last few months, we have done two private testnet forks and then the full public testnet testing for v11 code (the new protocol which is what Fern implements). The developers have also been running non-staking "sentinel" nodes on mainnet with this code to verify that the consensus rules are problem-free for the legacy compatibility code on the broader mainnet. We believe this amount of testing is going to result in a smooth rollout.
Given the amount of changes in Fern, I am presenting TWO changelogs below. One is high level, which summarizes the most significant changes in the protocol. The second changelog is the detailed one in the usual format, and gives you an inkling of the size of this release.

Highlights

Protocol

Note that the protocol changes will not become active until we cross the hard-fork transition height to v11, which has been set at 2053000. Given current average block spacing, this should happen around October 4, about one month from now.
Note that to get all of the beacons in the network on the new protocol, we are requiring ALL beacons to be validated. A two week (14 day) grace period is provided by the code, starting at the time of the transition height, for people currently holding a beacon to validate the beacon and prevent it from expiring. That means that EVERY CRUNCHER must advertise and validate their beacon AFTER the v11 transition (around Oct 4th) and BEFORE October 18th (or more precisely, 14 days from the actual date of the v11 transition). If you do not advertise and validate your beacon by this time, your beacon will expire and you will stop earning research rewards until you advertise and validate a new beacon. This process has been made much easier by a brand new beacon "wizard" that helps manage beacon advertisements and renewals. Once a beacon has been validated and is a v11 protocol beacon, the normal 180 day expiration rules apply. Note, however, that the 180 day expiration on research rewards has been removed with the Fern update. This means that while your beacon might expire after 180 days, your earned research rewards will be retained and can be claimed by advertising a beacon with the same CPID and going through the validation process again. In other words, you do not lose any earned research rewards if you do not stake a block within 180 days and keep your beacon up-to-date.
The transition height is also when the team requirement will be relaxed for the network.

GUI

Besides the beacon wizard, there are a number of improvements to the GUI, including new UI transaction types (and icons) for staking the superblock, sidestake sends, beacon advertisement, voting, poll creation, and transactions with a message. The main screen has been revamped with a better summary section, and better status icons. Several changes under the hood have improved GUI performance. And finally, the diagnostics have been revamped.

Blockchain

The wallet sync speed has been DRASTICALLY improved. A decent machine with a good network connection should be able to sync the entire mainnet blockchain in less than 4 hours. A fast machine with a really fast network connection and a good SSD can do it in about 2.5 hours. One of our goals was to reduce or eliminate the reliance on snapshots for mainnet, and I think we have accomplished that goal with the new sync speed. We have also streamlined the in-memory structures for the blockchain which shaves some memory use.
There are so many goodies here it is hard to summarize them all.
I would like to thank all of the contributors to this release, but especially thank @cyrossignol, whose incredible contributions formed the backbone of this release. I would also like to pay special thanks to @barton2526, @caraka, and @Quezacoatl1, who tirelessly helped during the testing and polishing phase on testnet with testing and repeated builds for all architectures.
The developers are proud to present this release to the community and we believe this represents the starting point for a true renaissance for Gridcoin!

Summary Changelog

Accrual

Changed

Most significantly, nodes calculate research rewards directly from the magnitudes in EACH superblock between stakes instead of using a two- or three- point average based on a CPID's current magnitude and the magnitude for the CPID when it last staked. For those long-timers in the community, this has been referred to as "Superblock Windows," and was first done in proof-of-concept form by @denravonska.

Removed

Beacons

Added

Changed

Removed

Unaltered

As a reminder:

Superblocks

Added

Changed

Removed

Voting

Added

Changed

Removed

Detailed Changelog

[5.0.0.0] 2020-09-03, mandatory, "Fern"

Added

Changed

Removed

Fixed

submitted by jamescowens to gridcoin [link] [comments]

RPC Specify wallet for each command?

Hello there. I made a post on bitcoin about a week ago here asking for help with loading wallets in rpc. I got that sorted and now I'm moving onto working with Monero
I am able to connect to bitcoin-wallet-rpc which is connected to my local testnet daemon but if I want to interact with a users wallet I have to unload all the other wallets to make sure I am interacting with the right one because I can't seem to work out how to specify which wallet for each command.
The solution with BTC was to add /wallet/ onto the end of the service_url but there dosn't seem to be anything like that in XMR.
Am I missing something obvious? Any help appreciated!!
submitted by AnAsepticAttack to Monero [link] [comments]

Bitcoin RPC Remote Code Execution Exploit for BitcoinCore 0.9-0.15.1 CVE-2017-9230 A breif introduction to the Chain Query Bitcoin RPC API How to mine bitcoins (solo mining) with the core client ... Bitcoin JSON-RPC Tutorials - YouTube 6. bitcoin-qt

Accept command line and JSON-RPC commands -rest : Accept public REST requests (default: 0) -rpcbind=<addr> Bind to given address to listen for JSON-RPC connections. Use [host]:port notation for IPv6. This option can be specified multiple times (default: bind to all interfaces) -rpccookiefile=<loc> Location of the auth cookie (default: data dir) -rpcuser=<user> Username for JSON-RPC connections ... Bitcoin console commands. Bitcoin RPC console window accepts a variety of commands. Type help and enter. You should see the list of commands that is currently accepted by the console. We’ve shared all the available command lists below. We’ll not get into all that in detail. Just to get familiar with the console window we’ll show you some basic commands. > getblockcount. Returns the ... This site aims to provide the docs you need to understand Bitcoin and start building Bitcoin-based applications. The second method uses JSON-RPC. This is a common interface that allows you to connect to bitcoind and execute commands from any language - and possibly even from another computer. The Bitcoin Wiki has a page with a detailed description of some ways to make a JSON-RPC call in various programming languages. For brevity, only two are listed. In ... There are two variations of the original bitcoin program available; one with a graphical user interface (usually referred to as just Bitcoin), and a 'headless' version (called bitcoind ). They are completely compatible with each other, and take the same command-line arguments, read the same configuration file, and rea . trending; Bitcoin Rpc Commands Bitcoin . Bitcoin Rpc Commands . Apr 8 ...

[index] [47719] [2548] [34928] [46796] [22184] [7303] [14180] [15786] [36065] [9569]

Bitcoin RPC Remote Code Execution Exploit for BitcoinCore 0.9-0.15.1 CVE-2017-9230

In this video I revisit an old topic where several things have changed since 2015 in regards to using the JSON-RPC to communicate with your node with an apache server with PHP. https://www.amazon ... https://ChainQuery.com/tutorials/a-brief-introduction-to-the-chain-query-bitcoin-rpc-api Take a brief tour of the features and functionality of the Chain Que... RPC commands: - getbalance - getwalletinfo - getnewaddress - getblockcount - getnetworkinfo www.bitcoinhackers.org @402PaymentRequierd bc1qny4am3clu0gcsq3hvj... *****UPDATE***** Solo mining has been removed from client. I'll keep the video up for how it used to work, it might still work for some alt coins (unsure) yo... Skip navigation Sign in. Search

#