i find r s z from tow transaction but the r value is not same

i need your help plase
i find r s z from tow transaction but the r value is not same

from this wallet 1XCPdWb6kk7PGfvbdRbRuNh51aPc4vqC7

this is information
tx 1 b152df9fc1087066cc12ec69c441f35559d794267209fd03f6d3f1d257b69549

raw tx : 010000000134930446c8a27fb457e65fa6f88a193843bf49a73043b997cfd005b9910173a7290000008a4730440220700d06f0d24f18e89acaf250b137b25066b4abea1f3cab58ba48b3dac7e3ede7022032236390aa15f60370236a9b88a5fbcc95aca95bbc7c32be2e781daf5ed1cd1601410433e05b29670f19cbc499f207f11abe1c69f77f00d5cbb9dbec5b5fe7527e2f41fa1e90f10a05e9c0a34d255988082e190c9ee7ea05f62297d4f76d9b61d7561bffffffff020000000000000000306a2ef24afce462d82863a3686fa4071c2d451a0e8c1056250110f8c08e8966f731b5d630d7b6a89c8ba88d3d388c3d4236150000000000001976a91405b5fca463964fc8af5ce743e1cfc1102601ecfc88ac00000000

THE R1 700d06f0d24f18e89acaf250b137b25066b4abea1f3cab58ba48b3dac7e3ede7
THE S1 32236390aa15f60370236a9b88a5fbcc95aca95bbc7c32be2e781daf5ed1cd16
THE Z1 b28f435e053ba045130a39562570bb7fcb7100d6501cb1571ee7bea979ea6377
THE PUBKEY : 0433e05b29670f19cbc499f207f11abe1c69f77f00d5cbb9dbec5b5fe7527e2f41fa1e90f10a05e9c0a34d255988082e190c9ee7ea05f62297d4f76d9b61d7561b’)

tx 2 4fa22a2149dd320655425ad7a88b6f6aad87afe10bcf7117c2499b1d5af9529c

raw tx 2 : 010000000134930446c8a27fb457e65fa6f88a193843bf49a73043b997cfd005b9910173a7280000008b483045022100e13d5d80bab1b5734684334c652cdaa53bd63003b3fb5044e7cfabb78e3e6621022007f8c435382190f1b7d3f0318924e886360ff2b4a7a565fb36d2ed6b936b3e3e01410433e05b29670f19cbc499f207f11abe1c69f77f00d5cbb9dbec5b5fe7527e2f41fa1e90f10a05e9c0a34d255988082e190c9ee7ea05f62297d4f76d9b61d7561bffffffff020000000000000000306a2ef24afce462d82863a3686fa4071c2d451a0e8c105531133861c0ed81e886d159436a4e351103320143bbdae92a2836150000000000001976a91405b5fca463964fc8af5ce743e1cfc1102601ecfc88ac00000000

(‘THE R2 e13d5d80bab1b5734684334c652cdaa53bd63003b3fb5044e7cfabb78e3e6621’)
(‘THE S2 07f8c435382190f1b7d3f0318924e886360ff2b4a7a565fb36d2ed6b936b3e3e’)
(‘THE Z2 1e8faed746b6bcfbc42d8c2c75b58e1ba2f9059089be669bbb9365b84937e89c’)
(‘THE PUBKey 0433e05b29670f19cbc499f207f11abe1c69f77f00d5cbb9dbec5b5fe7527e2f41fa1e90f10a05e9c0a34d255988082e190c9ee7ea05f62297d4f76d9b61d7561b’)

this is the wallet
https://www.blockchain.com/btc/address/1XCPdWb6kk7PGfvbdRbRuNh51aPc4vqC7

And I’m going to send some money to someone who will help me. Please, all I want is to get the private key for this wallet.
I searched again and again and did not find any solution or I did not understand the methods well Please my brothers I want help urgently
I found these variables R S Z, but the variable R is different in financial transactions. Is there a way to extract the private key via R different
I want a full explanation and if you can attach me the last result which is the private key in the messages

Help me even by a tool to find the private key via two variables of the value R

June 2020 Report & Analysis

And we’re back to you with yet another issue of our revenue report. A little siesta time for Bitcoin, June was the month when a single event affected both crypto and traditional finances communities at one stroke. Meanwhile, we were breaking our own records for the second month running, and you only need to look … Read more

Why does bitcoin uses INIT_PROTO_VERSION (209) for addrme and addryou in the Version Message

Why does Bitcoin use INIT_PROTO_VERSION (209) in the addrme and addryou message of the Version Message? Why is it not using the nodes protocolVersion which had been advertised in the same Message.

This is part why the nTime from the node in the Version Message will be ignored

Code used for Debug in protocol.h

   SERIALIZE_METHODS(CAddress, obj)
    {
        SER_READ(obj, obj.nTime = TIME_INIT);
        int nVersion = s.GetVersion();
        if (s.GetType() & SER_DISK) {
            printf("nVersion %d\n", nVersion);
            READWRITE(nVersion);
        } else {
            printf("Not evaluated nVersion %d Type %d\n", nVersion, s.GetType());
        }
        if ((s.GetType() & SER_DISK) ||
            (nVersion >= CADDR_TIME_VERSION && !(s.GetType() & SER_GETHASH))) {
            READWRITE(obj.nTime);
            printf("nTime %d\n", obj.nTime);
        } else {
            printf("Not evaluated nTime %d\n", obj.nTime);
        }
        READWRITE(Using<CustomUintFormatter<8>>(obj.nServices));
        printf("nServicesInt %d\n", obj.nServices);
        READWRITEAS(CService, obj);
    }

See below the Output

BTC’s

Receive addrMe
Not evaluated nVersion 209 Type 1
Not evaluated nTime 100000000
nServicesInt 0
Receive addrFrom
Not evaluated nVersion 209 Type 1
Not evaluated nTime 100000000
nServicesInt 1033
2020-07-07T01:35:08Z New outbound peer connected: version: 70015, blocks=638069, peer=1 (full-relay)

Is this a wanted behavior?

How to reference different wallets with curl JSONRPC requests Bitcoin core

I have a headless Bitcoin core 0.17.1 running on Debian 10, and have created a second wallet "johns-wallet".

I’d like to get the walletinfo (or any wallet request) of that specific wallet via curl, not the cli.

The Bitcoin core API reference doesn’t offer an example of how to target different wallets when not using the CLI (and neither did my Google search).

I’ve tried:

curl --user johnsmith --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getwalletinfo", "params": [] }' -H 'content-type: text/plain;' bitcoind:18332/wallets/johns-wallet/

and also

curl --user johnsmith --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "getwalletinfo", "params": ["/wallets/johns-wallet/"] }' -H 'content-type: text/plain;' bitcoind:18332

And also variations on the path itself to the wallet – none of them return a result, let alone an error.

Running without trying to specify a wallet returns:

{"result":null,"error":{"code":-19,"message":"Wallet file not specified (must request wallet RPC through /wallet/<filename> uri-path)."},"id":"curltest"}

(In case it matters, the Bitcoind is running in a docker container, with a named volume)

Why is my bitcoin core not downloading any blocks?

I am using Centos 7 and I installed the newest version of bitcoin core.
I just want to run a full node to download all the blocks.
According to their documentation, the first time we start bitcoin core, it will start automatically to download the blocks.

This is my /.bitcoin/bitcoin.conf file:

datadir=/.../blocks
server=1
txindex=1
rpcport=8332
rpcuser=<something>
rpcpassword=<something>

After I run bitcoind -daemon, bitcoin-cli getblockcount gives me 0.

Is there anything wrong with the ports?

I tried netstat -na | grep 8333, and it gives me this:

tcp        0      0 0.0.0.0:8333            0.0.0.0:*               LISTEN
tcp        0      1 <***>:40706     <***>:8333     SYN_SENT
tcp6       0      0 :::8333                 :::*                    LISTEN

And netstat -na | grep 8332 gives me:

tcp        0      0 127.0.0.1:8332          0.0.0.0:*               LISTEN
tcp6       0      0 ::1:8332                :::*                    LISTEN

Output of bitcoin-cli getblockchaininfo:

{
  "chain": "main",
  "blocks": 0,
  "headers": 0,
  "bestblockhash": "000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f",
  "difficulty": 1,
  "mediantime": 1231006505,
  "verificationprogress": 1.835803992430469e-09,
  "initialblockdownload": true,
  "chainwork": "0000000000000000000000000000000000000000000000000000000100010001",
  "size_on_disk": 293,
  "pruned": false,
  "softforks": {
    "bip34": {
      "type": "buried",
      "active": false,
      "height": 227931
    },
    "bip66": {
      "type": "buried",
      "active": false,
      "height": 363725
    },
    "bip65": {
      "type": "buried",
      "active": false,
      "height": 388381
    },
    "csv": {
      "type": "buried",
      "active": false,
      "height": 419328
    },
    "segwit": {
      "type": "buried",
      "active": false,
      "height": 481824
    }
  },
  "warnings": ""
}

Result of bitcoin-cli getnetworkinfo:

{
  "version": 200000,
  "subversion": "/Satoshi:0.20.0/",
  "protocolversion": 70015,
  "localservices": "0000000000000409",
  "localservicesnames": [
    "NETWORK",
    "WITNESS",
    "NETWORK_LIMITED"
  ],
  "localrelay": true,
  "timeoffset": 0,
  "networkactive": true,
  "connections": 0,
  "networks": [
    {
      "name": "ipv4",
      "limited": false,
      "reachable": true,
      "proxy": "",
      "proxy_randomize_credentials": false
    },
    {
      "name": "ipv6",
      "limited": false,
      "reachable": true,
      "proxy": "",
      "proxy_randomize_credentials": false
    },
    {
      "name": "onion",
      "limited": true,
      "reachable": false,
      "proxy": "",
      "proxy_randomize_credentials": false
    }
  ],
  "relayfee": 0.00001000,
  "incrementalfee": 0.00001000,
  "localaddresses": [
    {
      "address": "<***>",
      "port": 8333,
      "score": 1
    }
  ],
  "warnings": ""
}

I know the question is kind of dumb but please help me figure out what’s wrong.

Edit:

bitcoind always freezes at this:

Loading addresses from DNS seed seed.bitcoin.sipa.be
2020-07-07T04:16:00Z Loading addresses from DNS seed seed.btc.petertodd.org
2020-07-07T04:16:00Z Loading addresses from DNS seed seed.bitcoin.sprovoost.nl
2020-07-07T04:16:11Z Loading addresses from DNS seed dnsseed.bluematt.me
2020-07-07T04:16:12Z Loading addresses from DNS seed dnsseed.emzy.de
2020-07-07T04:16:12Z Loading addresses from DNS seed dnsseed.bitcoin.dashjr.org
2020-07-07T04:16:23Z Loading addresses from DNS seed seed.bitcoinstats.com
2020-07-07T04:16:23Z Loading addresses from DNS seed seed.bitcoin.jonasschnelli.ch
2020-07-07T04:16:23Z 202 addresses found from DNS seeds
2020-07-07T04:16:23Z dnsseed thread exit

Is there anything wrong?

How to use Multisig feature on Bitcoin Core RPC in an online exchange?

I’ve craeted a small online exchange based on Bitcoin Core. The features in this application are:

  1. User send request to get a new address, and the Bitcoin Core generate a new one with defined passphrase.
  2. User can receive BTC on his own address.
  3. User can send BTC from his own address, and for this purpose, I’ve used sendtoaddress after unlocking account with walletPassphrase.

In this scenario, there is one complicated passphrase which is able to unlock all accounts. But after reading about multisig feature, I thought about implementing a scenario in this regard on my application. But there are some questions in my mind:

  1. I have used a fixed passphrase in my codes while sending transactions. Regarding to multisig concepts, I need to use different private keys to sign data instead of using a passphrase to unlock that account. Am I right?
  2. As the operation in an online exchange should be do automatically, I think I have to use all required private keys in the final step of my codes. In this case, I think I did not add any new security mechanism to my application as everything is located beside each other. Can I cound on security impact of multisig accounts in my application at all?

I hope you can help me so solve these issues in my mind.

Unknown Address Format Parsing Bitcoin Addresses from Blockchair Data

I’ve obtained a list of all current Bitcoin addresses with balances from Blockchair, which is downloadable from their data repository located here. I have downloaded the Bitcoin / Addresses TSV database dump.

The list consists of:

  • ~23m P2PKH (1xxx) addresses
  • ~5.8m P2SH (3xxx) addresses
  • ~1.3m Bech32 (bc1xxx) addresses

However, there are also ~400k addresses that have prefixes that I don’t recognise, including:

  • d-xxx (example: d-b697921d996831d1a26ca8d8e92571c1)
  • m-xxx (example: m-942943e227462513f33c4f32ec6f1e56)
  • s-xxx (example: s-2ad548f2459c0ed6123400e5d61a479e)

Are these valid Bitcoin addresses?

If they are, how do I view information about them?

If they are not, any idea why they appear in the dump of current Bitcoin addresses from Blockchair?

Blockchain Services Provider OKGroup Leads $2 Million Pre-IPO Investment Round in Banxa

Banxa, a full-service, internationally compliant digital banking infrastructure provider, announced it has completed its USD$2 million Pre-IPO investment round. The round was led by OK Group, a world-leading blockchain technology and service provider focused on the research and development of the technology and its all-scenario applications.. The funding round will be used to support Banxa’s … Continue reading Blockchain Services Provider OKGroup Leads $2 Million Pre-IPO Investment Round in Banxa

The post Blockchain Services Provider OKGroup Leads $2 Million Pre-IPO Investment Round in Banxa appeared first on CoinSpectator Blog.