Topic: Bitcoin Core 22.0 Released (Read 2551 times)
Bitcoin Core 23.0 has been released: https://bitcointalksearch.org/topic/bitcoin-core-230-released-5396054
anyone know who is the creator of this website and how to take funds out of this? any help would be appreciated
https://blockchaincore.net/
https://blockchaincore.net/
Yeah, pay close attention to any site that is not the official site. And when downloading from official sites, always spend a few more minutes checking signatures of the files you download. It's not that hard and it always pay off, as you will always know you're downloading the real stuff!
Never take down your guard!
~
Where do you found that site and how did you manage to have funds within the site?The site is shady and most likely it is a scam. If you take a look at the testimonial section, all the reviewed photos are using publicly available photos.
And best if you have trouble and feel scammed, you post some thread with clarification on Scam accusations board: https://bitcointalk.org/index.php?board=83.0
anyone know who is the creator of this website and how to take funds out of this? any help would be appreciated
https://blockchaincore.net/
https://blockchaincore.net/
And another question I have is if this new address also helps in any way reducing the space taken for transactions??
If I understand Taproot correctly, the least I know is that Taproot does make multisig transactions smaller but besides that, there isn't much improvement.Take it with a grain of salt since I didn't comprehend Taproot fully. I remember some users have made a thread comparing bitcoin transaction size with P2TR tx, but I can't remember which one and where, surely it's on the technical board.
Yeah, that part I know. I think maybe my question might even be confusing and maybe even non-sensical. I mean, I'm not sure if the fact that the Taproot makes it as a whole or the Taproot implementation can be separated from the P2TR addresses, because I think Taproot is used weather you use P2TR addresses or not. So, my question was like if Taproot + P2TR saves more space and brings more privacy than only Taproot itself (not using P2TR).
And another question I have is if this new address also helps in any way reducing the space taken for transactions??
If I understand Taproot correctly, the least I know is that Taproot does make multisig transactions smaller but besides that, there isn't much improvement.Take it with a grain of salt since I didn't comprehend Taproot fully. I remember some users have made a thread comparing bitcoin transaction size with P2TR tx, but I can't remember which one and where, surely it's on the technical board.
Hello. Is it already possible, with this latest release, to generate the P2TR addresses or the PR is not yet merged into the release? I can see from some stackexchange posts that by the time those posts were made, a Taproot descriptor needed to be created and then imported into the wallet, and only in signet, to prevent loss of funds.
How is this right now?
There was this description on how to do it, though:
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-October/019543.html
Bitcoin Core 22.0 doesn't include the Taproot descriptor yet and the PR21500 that is required by the tutorial hasn't been merged at the 22.0 release.How is this right now?
There was this description on how to do it, though:
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-October/019543.html
I believe if you running the latest master branch, you should be able to generate the address. The last time I tried to play around with Taproot is when I'm using the #22364 @Achow101 branch and could successfully make a transaction on testnet.
Oh, ok. I really appreciate your feedback. I'll take a look to that PR of @Achow101 branch and maybe I'll give it a try myself also on the testnet just to have the feeling of how it works. And another question I have is if this new address also helps in any way reducing the space taken for transactions??
Hello. Is it already possible, with this latest release, to generate the P2TR addresses or the PR is not yet merged into the release? I can see from some stackexchange posts that by the time those posts were made, a Taproot descriptor needed to be created and then imported into the wallet, and only in signet, to prevent loss of funds.
How is this right now?
There was this description on how to do it, though:
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-October/019543.html
Bitcoin Core 22.0 doesn't include the Taproot descriptor yet and the PR21500 that is required by the tutorial hasn't been merged at the 22.0 release.How is this right now?
There was this description on how to do it, though:
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-October/019543.html
I believe if you running the latest master branch, you should be able to generate the address. The last time I tried to play around with Taproot is when I'm using the #22364 @Achow101 branch and could successfully make a transaction on testnet.
Hello. Is it already possible, with this latest release, to generate the P2TR addresses or the PR is not yet merged into the release? I can see from some stackexchange posts that by the time those posts were made, a Taproot descriptor needed to be created and then imported into the wallet, and only in signet, to prevent loss of funds.
How is this right now?
There was this description on how to do it, though:
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-October/019543.html
How is this right now?
There was this description on how to do it, though:
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-October/019543.html
fine, how i can view wallet address?
You are typing an incorrect option/parameter. Actually, you can see the reference by running ./bitcoin-cli --help
Or depending on what you need/want you can just see the below reference:
RPC API Reference
Bitcoin CLI JSON RPC
Or depending on what you need/want you can just see the below reference:
RPC API Reference
Bitcoin CLI JSON RPC
Unlikely, if his system ran out of memory he should see message such as "Killed" or "kernel: Out of memory: Kill process XXXXX".
You mean the "oom_kill_process" and "out_of_memory" lines aren't good enough for you?The message you mentioned is part of call/stack trace, so i'm not sure whether "OOM killer" crashed when system out of memory or hardware error (e.g. faulty RAM).
why?
Unlikely, if his system ran out of memory he should see message such as "Killed" or "kernel: Out of memory: Kill process XXXXX".
You mean the "oom_kill_process" and "out_of_memory" lines aren't good enough for you? Hi, run
, why error?
Code:
./bitcoind -server -daemon=1 -prune=2024
, why error?
Looks like hardware error to me, but i can't be sure without additional log.
~
Unlikely, if his system ran out of memory he should see message such as "Killed" or "kernel: Out of memory: Kill process XXXXX".
Anyway, you better post a thread on Bitcoin Technical Support board and make sure you read [READ BEFORE POSTING] Tech Support Help Request Format post.
I agree, but i also recommend to include relevant line of your system log.
~
Anyway, you better post a thread on Bitcoin Technical Support board and make sure you read [READ BEFORE POSTING] Tech Support Help Request Format post.
Hi, run
, why error?
Code:
./bitcoind -server -daemon=1 -prune=2024
, why error?
Excited to update my node to this.
It's odd but it's probably not because of the name change because it appears that the posts are ordered by date but for some reason, the 0.21.2 version was posted on the 26th of October while the newest versions were posted prior to that date.
Because of version number change, bitcoin.org website orders releases odd way.
https://bitcoincore.org
https://bitcoincore.org
It's odd but it's probably not because of the name change because it appears that the posts are ordered by date but for some reason, the 0.21.2 version was posted on the 26th of October while the newest versions were posted prior to that date.
Jump to: