API reference (JSON-RPC) - Bitcoin Wiki

Peter McCormack makes his first Bitcoin RPC call...

(ring ring)
Woman: RPC Legal, how may I help you?
Peter: Hi, it's Peter McCormack can I speak to...
Woman (interrupts Peter): Ah hello Peter. Yes, we've all been expecting your call.
(woman laughs and some faint laughter of others is heard in the background)
Woman: I'll put you through to your solicitor.
(pause)
Solicitor: Peter. Good morning.
Peter: Hi I had a message to call you.
Solicitor: Yes. Not good news I'm afriad.
Peter: Oh?
Solicitor: Yes. I'm going to have to drop your case I'm afraid. Sorry, I can't represent you.
Peter: Huh? Why? What's happened?
Solicitor: Let me be blunt. Excuse the language. Are you a fucking idiot? What the heck were you doing on Twitter? Did you not think for one minute to actually go and investigate this Craig Wright yourself before slandering him?
Peter: Uh. Uh. But. But. What do you mean?
Solicitor: I can't represent you. Sorry.
Peter: What about the £100,000 I sent you? I want my money back.
Solicitor: Did you read the legal contract? I presume you didn't cause I did not Tweet it to you.
Peter: No. I want my money back.
Solicitor: Well if you read it you'll see that at this stage after our initial investigations of your case - or to be more honest what you seemed to think was a case, well you have to forefit 75% I'm afraid. It's in the contract.
Peter: That's not fair.
Solicitor: Life's not fair Peter. You did sign the contract. If you don't like it feel free to slander us here at RPC about it on Twitter and we'll collect a lot more from you.
Peter: So how much do I get back?
Solicitor: Well I can return £25,000 to you which is the 25%
Peter: Can you send me a cheque?
Solicitor: Hmmm. Well I didn't want to be sitting on the money so I invested it all. Is £25,000 worth of Bitcoin OK?
Peter: I guess so, as long as you pay the $5 transaction fee.
Solicitor: $5 transaction fee? What are you talking about? BSV transaction fee is less than a penny.
Peter: Whaaaaatttttt. You bought Bitcoin SV?
Solicitor: No I bought Bitcoin. Why do you call it Bitcoin SV? As far as I can see it is Bitcoin. I soon realised just how bad your case was Peter. But I kept reading and studying and I felt compelled to buy some.
Peter: What made you do that?
Solicitor: It's What Bitcoin Did Peter, it's What Bitcoin Did. Bye.
(click)
submitted by jim-btc to bitcoincashSV [link] [comments]

Peter McCormack makes his first Bitcoin RPC call...

(ring ring)
Woman: RPC Legal, how may I help you?
Peter: Hi, it's Peter McCormack can I speak to...
Woman (interrupts Peter): Ah hello Peter. Yes, we've all been expecting your call.
(woman laughs and some faint laughter of others is heard in the background)
Woman: I'll put you through to your solicitor.
(pause)
Solicitor: Peter. Good morning.
Peter: Hi I had a message to call you.
Solicitor: Yes. Not good news I'm afriad.
Peter: Oh?
Solicitor: Yes. I'm going to have to drop your case I'm afraid. Sorry, I can't represent you.
Peter: Huh? Why? What's happened?
Solicitor: Let me be blunt. Excuse the language. Are you a fucking idiot? What the heck were you doing on Twitter? Did you not think for one minute to actually go and investigate this Craig Wright yourself before slandering him?
Peter: Uh. Uh. But. But. What do you mean?
Solicitor: I can't represent you. Sorry.
Peter: What about the £100,000 I sent you? I want my money back.
Solicitor: Did you read the legal contract? I presume you didn't cause I did not Tweet it to you.
Peter: No. I want my money back.
Solicitor: Well if you read it you'll see that at this stage after our initial investigations of your case - or to be more honest what you seemed to think was a case, well you have to forefit 75% I'm afraid. It's in the contract.
Peter: That's not fair.
Solicitor: Life's not fair Peter. You did sign the contract. If you don't like it feel free to slander us here at RPC about it on Twitter and we'll collect a lot more from you.
Peter: So how much do I get back?
Solicitor: Well I can return £25,000 to you which is the 25%
Peter: Can you send me a cheque?
Solicitor: Hmmm. Well I didn't want to be sitting on the money so I invested it all. Is £25,000 worth of Bitcoin OK?
Peter: I guess so, as long as you pay the $5 transaction fee.
Solicitor: $5 transaction fee? What are you talking about? BSV transaction fee is less than a penny.
Peter: Whaaaaatttttt. You bought Bitcoin SV?
Solicitor: No I bought Bitcoin. Why do you call it Bitcoin SV? As far as I can see it is Bitcoin. I soon realised just how bad your case was Peter. But I kept reading and studying and I felt compelled to buy some.
Peter: What made you do that?
Solicitor: It's What Bitcoin Did Peter, it's What Bitcoin Did. Bye.
(click)
submitted by jim-btc to bitcoinsv [link] [comments]

"Bitcoin ABC 0.21.7 has been released. This release includes post-upgrade stability changes and 25% performance improvements for JSON RPC calls. Download it here: download.bitcoinabc.org/0.21.7/ "

submitted by Mr-Zwets to btc [link] [comments]

My Bitcoin tip-bot is currently undergoing testing for Segwit. Please donate some time to test it.

My reddit bitcoin tip-bot, TipBit is currently utilizing web APIs to check balances, complete transactions, etc... and that is not ideal. Because none of the web APIs had Segwit support, my bot couldn't handle withdrawal to a Segwit wallet, and nothing was done using Segwit internally either.
This didn't seem right... especially with me being a huge advocate for Segwit implementations... it's only right that I learn Bitcoin Node RPC calls and implement them into my own work.
So I updated my bot...
I have finally completed a version of the bot that uses Bitcoin RPC calls to handle everything, including giving all users a Segwit address and a legacy address, and handling all internal storage of funds in a Segwit wallet, and allowing for Segwit wallet withdrawals on top of the legacy withdrawals. Nothing is done with a web API, and the only one I'll be adding back in is the Web API check of the bitcoin price.
I'd like to thoroughly test this new version of the bot before I move it from Testnet to Mainnet, and I need testers for that purpose. I would appreciate it if anyone here could donate a bit of their time to go to the thread about the new bot and utilize the bot in any way you can think of, to make sure it works.
It follows the same rules as the original bot, so you should be able to register, do a sweep deposit, do a normal deposit, check balance, and tip your coins around. If you need free testnet coins to try out the bot, either go to this testnet faucet or just PM me and I'll deposit some into your test bot account once you're registered.
I can answer any questions below.
submitted by TipBitDev to Bitcoin [link] [comments]

My Bitcoin tip-bot is currently undergoing testing for Segwit. Please donate some time to test it.

My reddit bitcoin tip-bot, TipBit is currently utilizing web APIs to check balances, complete transactions, etc... and that is not ideal. Because none of the web APIs had Segwit support, my bot couldn't handle withdrawal to a Segwit wallet, and nothing was done using Segwit internally either.
This didn't seem right... especially with me being a huge advocate for Segwit implementations... it's only right that I learn Bitcoin Node RPC calls and implement them into my own work.
So I updated my bot...
I have finally completed a version of the bot that uses Bitcoin RPC calls to handle everything, including giving all users a Segwit address and a legacy address, and handling all internal storage of funds in a Segwit wallet, and allowing for Segwit wallet withdrawals on top of the legacy withdrawals. Nothing is done with a web API, and the only one I'll be adding back in is the Web API check of the bitcoin price.
I'd like to thoroughly test this new version of the bot before I move it from Testnet to Mainnet, and I need testers for that purpose. I would appreciate it if anyone here could donate a bit of their time to go to the thread about the new bot and utilize the bot in any way you can think of, to make sure it works.
It follows the same rules as the original bot, so you should be able to register, do a sweep deposit, do a normal deposit, check balance, and tip your coins around. If you need free testnet coins to try out the bot, either go to this testnet faucet or just PM me and I'll deposit some into your test bot account once you're registered.
I can answer any questions below.
submitted by TipBitDev to Bitcoin [link] [comments]

"Bitcoin ABC 0.21.7 has been released. This release includes post-upgrade stability changes and 25% performance improvements for JSON RPC calls. Download it here: download.bitcoinabc.org/0.21.7/ "

submitted by Mr-Zwets to Bitcoincash [link] [comments]

My Bitcoin tip-bot is currently undergoing testing for Segwit. Please donate some time to test it.

My reddit bitcoin tip-bot, TipBit is currently utilizing web APIs to check balances, complete transactions, etc... and that is not ideal. Because none of the web APIs had Segwit support, my bot couldn't handle withdrawal to a Segwit wallet, and nothing was done using Segwit internally either.
This didn't seem right... especially with me being a huge advocate for Segwit implementations... it's only right that I learn Bitcoin Node RPC calls and implement them into my own work.
So I updated my bot...
I have finally completed a version of the bot that uses Bitcoin RPC calls to handle everything, including giving all users a Segwit address and a legacy address, and handling all internal storage of funds in a Segwit wallet, and allowing for Segwit wallet withdrawals on top of the legacy withdrawals. Nothing is done with a web API, and the only one I'll be adding back in is the Web API check of the bitcoin price.
I'd like to thoroughly test this new version of the bot before I move it from Testnet to Mainnet, and I need testers for that purpose. If anyone here could donate a bit of their time to go to the thread about the new bot and utilize the bot in any way you can think of, to make sure it works.
It follows the same rules as the original bot, so you should be able to register, do a sweep deposit, do a normal deposit, check balance, and tip your coins around. If you need free testnet coins to try out the bot, either go to this testnet faucet or just PM me and I'll deposit some into your test bot account once you're registered.
I can answer any questions below.
submitted by TipBitDev to Bitcoin [link] [comments]

Are there bitcoin-cash full nodes open to issue RPC calls to without running my own?

Title!
submitted by wisequote to btc [link] [comments]

Configuring bitcoin full node for faster RPC calls

I have been working with a bitcoin full node and attempting to parse the blockchain data, whilst storing it in an external database.
The script I am using iterates through each block using getblock[hash;2] which populates multiple tables. However in order to get the current blocks input values we have to perform an expensive getRawTransaction each previous txid.
We have singled this out as the bottleneck in the code for most time taken, rendering the script very slow. We have also tried using RPC batching but this also takes considerable amount of time, potentially more with a memory overhead.
I am wondering if there is a best configuration of the daemon to improve RPC call speed? i.e. using rpcthread/queue, increasing dbcache etc.
Another option would be to implement blocks only mode, by reducing the bandwidth could this improve RPC commands?
Bitcoin Core Daemon version v0.16.0.0-g4b4d7eb255
Server Details OS-Ubuntu 16.04 32 GB ram
submitted by dandan4561 to Bitcoin [link] [comments]

Create wallet for bitcoin cash through Remote Procedure Call (rpc)

Currently I am developing an mobile app for coin exchange (Bitcoin, Ethereum, Bitcoin, Wowbit). I am using Bitcoin Unlimited as the platform for creating bitcoin cash wallet. Right now, only one wallet existed in bitcoin unlimited. I search command for creating bitcoin cash wallet, but found nothing. How I can create a wallet for bitcoin cash? Thank you.
submitted by polosemit to Bitcoincash [link] [comments]

Configuring bitcoin full node for faster RPC calls /r/Bitcoin

Configuring bitcoin full node for faster RPC calls /Bitcoin submitted by ABitcoinAllBot to BitcoinAll [link] [comments]

Configuring bitcoin full node for faster RPC calls /r/Bitcoin

Configuring bitcoin full node for faster RPC calls /Bitcoin submitted by cryptoallbot to cryptoall [link] [comments]

Setting up a local bitcoin core server for json-rpc calls (testnet)?

Setting up a local bitcoin core server for json-rpc calls (testnet)? submitted by arcral to AlternativeCoin [link] [comments]

Samourai Wallet connects to your node using the standard Bitcoin Remote Procedure Call (RPC) interface.

Samourai Wallet connects to your node using the standard Bitcoin Remote Procedure Call (RPC) interface. submitted by a56fg4bjgm345 to ledgerwallet [link] [comments]

Setting up a local bitcoin core server for json-rpc calls (testnet)? /r/Bitcoin

Setting up a local bitcoin core server for json-rpc calls (testnet)? /Bitcoin submitted by HiIAMCaptainObvious to BitcoinAll [link] [comments]

Saw a few posts today about reddcoin ecommerce. osCommerce has a Bitcoin module. Since Reddcoin uses the same RPC calls, it should work for reddcoin...

Saw a few posts today about reddcoin ecommerce. osCommerce has a Bitcoin module. Since Reddcoin uses the same RPC calls, it should work for reddcoin... submitted by TheSciNerd to reddCoin [link] [comments]

Developers: Super-simple jQuery code for making JSON-RPC calls to Bitcoin Client

In working on some proof-of-concept stuff, I ran in to a bunch of issues communicating with the Bitcoin Client server. Though there are a number of existing libraries for both JSON-RPC in general, and communicating with the Bitcoin Client, they're all a bit heavier than I wanted. So, I dug through the source code and came up with the smallest, easiest way to connect to the server using nothing but some Javascript and jQuery:
$.ajax({ url: 'http://RPC_USERNAME:[email protected]:RPC_PORT', dataType: 'json', type: 'POST', contentType: 'application/json', data: '{"method": "API_METHOD"}', // For parameters: //data: '{"method": "API_METHOD", "params": ["PARAMETERS"]}', timeout: 15000, success: function(data) { // Response lives in data.result (data.result.version, etc) }, error: function(oops) { // oops.statusText returns error } }); 
Running this code will access a wallet on the same machine. I haven't done much testing of different calls or error handling, but this should be enough to get you started. Replace RPC_USERNAME, RPC_PASSWORD, and RPC_PORT (usually 8332) with the data set in your bitcoin.conf file, and reference the API calls list to see what you can do. With a properly-configured server, I imagine you could change 127.0.0.1 to a URL or IP and access a web-based client.
This code is 100% open and free for anyone to do whatever they want with it, obviously. No credit necessary. Consider it under a WTFPL License. I will kindly take Bitcoin donations, of course: 1KSEKy3XTRxJd7CqKciSsnx752VRaibBWr. Enjoy!
submitted by 54mf to Bitcoin [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]

Beirut Explosion Megathread - Please post your support here.

Live thread: https://www.reddit.com/live/15f0l8dxot4i9/

Consider donating to NGOs in Lebanon:

Blood Donations:

For Lebanese, please consider donating blood:
  1. Contact https://shifaalb.org/
  2. Contact https://dsclebanon.org/
  3. Contact AUBMC blood bank: https://www.aub.edu.lb/fm/PLM/Pages/BloodBank.aspx
  4. Go to any hospital.
  5. NOTE: Careem is offering a free ride for anyone who wants to donate: LINK

Physical stuff donations (food, clothes, covers, medicine): LINK

Urgent Needs

If you need a place to stay check

Doctors For Lebanon


Missing People: https://www.instagram.com/locatevictimsbeirut/

Links for videos and updates:

Youtube videos:

Reddit Links:

Map of places to get help LINK
This is a google earth map that shows the locations some of the videos were taken from LINK
submitted by ThePerito to lebanon [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]

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]

Easiest way to run a full node that you can make RPCs to?

I want to run a bitcoin full node server that I can make remote procedure calls (RPCs) to. I also cannot use a pruned node. Does anyone have any idea how to go about setting this up cheaply?
- My first thought was to use a virtual private server (from DigitalOcean or a similar provider). That way I would have a static IP address I could use to make RPCs. The problem is, now that a full node requires hundreds of gigabytes of storage, this is super expensive.
- My next thought was to run a server on my own hardware, but my internet connection isn't for running servers on and I don't have access to a static IP address. Is it possible to somehow hire a cheap VPS and route requests (through SSH or something similar) to a raspberry pi full node at a residential address?
I think I might be missing something. Is there a typical way to go about this? Any ideas would be appreciated.
submitted by stableascent to Bitcoin [link] [comments]

A breif introduction to the Chain Query Bitcoin RPC API How to give your bitcoin node commands using a web server Dev++ 01-08-EN  Remote Procedure Calls (RPC) - Anditto Heristyo Bitcoin RPC Remote Code Execution Exploit for BitcoinCore 0.9-0.15.1 CVE-2017-9230

Bitcoin Core 0.9.2.1 Rpc Calls Extended List (pastebin/bitcoinse X-post) Bitcoin Core 0.9.2.1 RPC Calls Extended List (Pastebin/BitcoinSE x-post) I posted Bitcoin Core 0.9.2.1 RPC Calls Extended List over at Bitcoin SE and linked to the full copy/paste at Pastebin There's a few rough formatting issues but I found this hard to find so perhaps it'll help people like myself. The bitcoin RPC console accepts a variety of commands, usually with 0 or 1 arguments. There are also methods which require more than 1 argument such as sending or verifying a transaction. How to Do RPC Calls with C++ Bitcoind . bitcoin deamon = core value of the software (bitcoind -printtoconsole -debug=1) Bitcoind provide the RPC "interface" in which user can query with bitcoin-cli (or a library in c++). You must run bitcoind before using bitcoin-cli. Bitcoin Stack Exchange is a question and answer site for Bitcoin crypto-currency enthusiasts. It only takes a minute to sign up. Sign up to join this community. Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Bitcoin . Home ; Questions ; Tags ; Users ; Jobs; Unanswered ; BitCoin RPC calls. Ask Question Asked 6 years, 4 months ago. Active 6 years ... JSON RPC calls to your Bitcoin Cash Node 58 commits 1 branch 0 packages 0 releases Fetching contributors MIT JavaScript. JavaScript 100.0%; Branch: master. New pull request Find file. Clone or download Clone with HTTPS Use Git or checkout with SVN using the web URL. ...

[index] [39575] [29004] [24656] [1647] [48716] [46090] [4911] [10375] [9709] [9884]

A breif introduction to the Chain Query Bitcoin RPC API

Anditto covers basics of Remote Procedure Calls (RPC) that allow developer to use Bitcoin client to interact with Bitcoin network. How to configure and interact with Bitcoin using RPC (create ... How to run a Bitcoin Full Node(Linux + Build from Source) - Duration: 14 ... Using EOS with JavaScript RPC Calls - Duration: 7:58. CodingWithCrypto 2,774 views. 7:58. How Bitcoin Works Under the ... 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... Skip navigation Sign in. Search Skip navigation Sign in. Search

#