Search content
Sort by
Showing 20 of 91 results by jacky19790729
About
RadiumX is a blockchain protection project with the ability to send signed transactions. The project hasfast transactions, low commission for transfers.
In addition, the distinctive features are:
Without premine
Not ico
No bounty programs
Quick access to stock exchanges
Without masternode
As well as many other features, which we describe in the future.
There will be no coin sale. The coins will be mined and available
soon after on several exchanges to be named.
We believe this to be a much fairer way of launching our project.
There will be a maximum of 255 Million coins ever created.
This is Pre launch RadiumX blockchain.
Specification
Coin Name: RadiumX
Symbol: RDX
Coin Type: PoW
Algorithm: X16S
Block Time: 1 Minute
Block Reward: 5000 RDX
Halving Schedule: Every 2.1M Blocks (Approximately every 4 years)
Max Supply: 255 Million
Block Size: 1MB (scalable)
GPU Minable: Yes
ASIC Resistant: Yes
ICO: No
Pre-mine: No
Founders Reward: No
Wallet Address Prefix: P
Wallets
https://github.com/RadiumXMain/RadiumX/releases/download/v2.0.3/RadiumX_win64_v2.0.3.zip
Site
radiumxcoin.info (in maintenance)
Explorer & Miner
Integrated in wallet
Mining pools
launch today
Check this topic !
RadiumX is a blockchain protection project with the ability to send signed transactions. The project hasfast transactions, low commission for transfers.
In addition, the distinctive features are:
Without premine
Not ico
No bounty programs
Quick access to stock exchanges
Without masternode
As well as many other features, which we describe in the future.
There will be no coin sale. The coins will be mined and available
soon after on several exchanges to be named.
We believe this to be a much fairer way of launching our project.
There will be a maximum of 255 Million coins ever created.
This is Pre launch RadiumX blockchain.
Specification
Coin Name: RadiumX
Symbol: RDX
Coin Type: PoW
Algorithm: X16S
Block Time: 1 Minute
Block Reward: 5000 RDX
Halving Schedule: Every 2.1M Blocks (Approximately every 4 years)
Max Supply: 255 Million
Block Size: 1MB (scalable)
GPU Minable: Yes
ASIC Resistant: Yes
ICO: No
Pre-mine: No
Founders Reward: No
Wallet Address Prefix: P
Wallets
https://github.com/RadiumXMain/RadiumX/releases/download/v2.0.3/RadiumX_win64_v2.0.3.zip
Site
radiumxcoin.info (in maintenance)
Explorer & Miner
Integrated in wallet
Mining pools
launch today
Check this topic !
Public Key 0x40f08294791bb07e908196847f79ad162ba0dff28eb312b1669ee2c8a72f7bfb, 0x28c29cc6ec6f2ddf9f54f32da1ea727de71c2ef168528475f5233ba28c06c4a8
Interesting, right?
Code:
r1 = 0x7029db68c1420fe2d41c1fd7b86ea0739bc8e6d0a7c58f754b93e5ff6c8040
s1 = 0xdbe4b484c838fce2aa65d85901f94f6fad6ad5f604d805c30ce05c58371c6991
z1 = SHA256('This is test 4.')
r2 = 0xdfb77cd83e2251dc96caad4c45cf98fcf76b8c24aa349c2dbba548029571331f
s2 = 0x352b52b52b52b52b52b52b52b52b52b4e7c1db2bf914fdd54560dc7fb517156e
z2 = Private key for Puzzle #130
s1 = 0xdbe4b484c838fce2aa65d85901f94f6fad6ad5f604d805c30ce05c58371c6991
z1 = SHA256('This is test 4.')
r2 = 0xdfb77cd83e2251dc96caad4c45cf98fcf76b8c24aa349c2dbba548029571331f
s2 = 0x352b52b52b52b52b52b52b52b52b52b4e7c1db2bf914fdd54560dc7fb517156e
z2 = Private key for Puzzle #130
Interesting, right?
Recovered Bitcoin public key: 0240f08294791bb07e908196847f79ad162ba0dff28eb312b1669ee2c8a72f7bfb
Bitcoin Address： 1AaEnbgVCKmG7RM8KYxjiQ2xaqn4NmyA7a
r1 = 0x7029db68c1420fe2d41c1fd7b86ea0739bc8e6d0a7c58f754b93e5ff6c8040
s1 = 0xdbe4b484c838fce2aa65d85901f94f6fad6ad5f604d805c30ce05c58371c6991
z1 = 0x9cabe7317b243f04a211a282035b96caa14d646dc32ba0e326f52d43cef07d8c
why z2 will be Private key for Puzzle #130 ??
Hi there!
It looks like you all are crazy for nonces and signatures, so I have some special values for you
It looks like you all are crazy for nonces and signatures, so I have some special values for you
Code:
r=0x678afdb0fe5548271967f1a67130b7105cd6a828e03909a67962e0ea1f61deb6
s=0x24c8a42e8fe11d670633fa66ebedb1672c71a517a30cbbaa9e14f2d5a15a3783
z=SHA256('This is test 1.')
PubKey=0x3e42b3151f310f5f417f11b4c32d8360b22109dcc6432339243332b56cd596de, 0x7903116327cab6891b810588e4c909273c7eb013aea2162fa63afa1f11562b3a
r=0x678afdb0fe5548271967f1a67130b7105cd6a828e03909a67962e0ea1f61deb6
s=0x768a0e3b0cfb3c8d9b7899f59f480555176ef25eefa1e96d3ac575ba4ffe85fd
z=SHA256('This is test 2.')
PubKey=0xc79fa242694e3148c8d50e667010e0c221f6004d108692c5040ff139595ed081, 0x525bd76c21c8e2d45725a378c973a646d5971acd8f240322e5f1fdf0ed4f8589
r=0x678afdb0fe5548271967f1a67130b7105cd6a828e03909a67962e0ea1f61deb6
s=0xd17c5ed9fb37692cd152f381c4a3f16a896f96d26100310fe818d6963c402b25
z=SHA256('This is test 3.')
PubKey=0xc03657988e2baf31a1a1061a87fa3da20f166dc8a22c02658f6d325dec722d84, 0x97ffbac6bec2de2b8d9f9bcaeced8e56abdd0b3996b48153cf0a1a92dc2d5529
Btw. I think that those who do serious research of this topic do not need your script, but all contributions are welcome, of course.s=0x24c8a42e8fe11d670633fa66ebedb1672c71a517a30cbbaa9e14f2d5a15a3783
z=SHA256('This is test 1.')
PubKey=0x3e42b3151f310f5f417f11b4c32d8360b22109dcc6432339243332b56cd596de, 0x7903116327cab6891b810588e4c909273c7eb013aea2162fa63afa1f11562b3a
r=0x678afdb0fe5548271967f1a67130b7105cd6a828e03909a67962e0ea1f61deb6
s=0x768a0e3b0cfb3c8d9b7899f59f480555176ef25eefa1e96d3ac575ba4ffe85fd
z=SHA256('This is test 2.')
PubKey=0xc79fa242694e3148c8d50e667010e0c221f6004d108692c5040ff139595ed081, 0x525bd76c21c8e2d45725a378c973a646d5971acd8f240322e5f1fdf0ed4f8589
r=0x678afdb0fe5548271967f1a67130b7105cd6a828e03909a67962e0ea1f61deb6
s=0xd17c5ed9fb37692cd152f381c4a3f16a896f96d26100310fe818d6963c402b25
z=SHA256('This is test 3.')
PubKey=0xc03657988e2baf31a1a1061a87fa3da20f166dc8a22c02658f6d325dec722d84, 0x97ffbac6bec2de2b8d9f9bcaeced8e56abdd0b3996b48153cf0a1a92dc2d5529
Recovered Bitcoin public key: 023e42b3151f310f5f417f11b4c32d8360b22109dcc6432339243332b56cd596de
Bitcoin Address： 1ak61eAXk4bxNbovZuqh4f1PxBaf1VUBV
r=0x678afdb0fe5548271967f1a67130b7105cd6a828e03909a67962e0ea1f61deb6
s=0x24c8a42e8fe11d670633fa66ebedb1672c71a517a30cbbaa9e14f2d5a15a3783
z=0xe0f6c07e19eb2dfa2e0c3586a2a9f4b225dba10c353fc354baa2dabcc9d42051
Recovered Bitcoin public key: 03c79fa242694e3148c8d50e667010e0c221f6004d108692c5040ff139595ed081
Bitcoin Address： 1GLKrFmj8eUsHS7s91PTMh2L6rPtF1RzNj
r=0x678afdb0fe5548271967f1a67130b7105cd6a828e03909a67962e0ea1f61deb6
s=0x768a0e3b0cfb3c8d9b7899f59f480555176ef25eefa1e96d3ac575ba4ffe85fd
z=0x48ef5d298a862b6f74338ebb5281f5212d8221a2fd8cce827be72779bffd25dd
Recovered Bitcoin public key: 03c03657988e2baf31a1a1061a87fa3da20f166dc8a22c02658f6d325dec722d84
Bitcoin Address： 17aj9BWZyDTqr6UnK7LScoCHdsbFRT6LZG
r=0x678afdb0fe5548271967f1a67130b7105cd6a828e03909a67962e0ea1f61deb6
s=0xd17c5ed9fb37692cd152f381c4a3f16a896f96d26100310fe818d6963c402b25
z=0x1e6a32d38fb096d19ad46186c6299f82b7bfd5a92d0d3b17142e8ff18b75e358
I can't understand special values
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
I think that you are being limited somehow by that electrum API, it only let you 6 tries?
I think that it should give you a more detailed error of why it fail.
I think that it should give you a more detailed error of why it fail.
I don't use electrum at this time ~~
my BOT is writed by python and bitcoinlib
about 6~7 second POST RatTX to https://mempool.space/api/tx
I think I gave away too often and didn’t calculate BTC/kvB properly.
Code:
====== w.utxos_update()
Found 2 unspent transaction outputs.
Filtered unspent UTXOs: 2
UTXO 7855cf143b41f86b04f385423a000f7cd6456f0d1ad4a76a8d3bd4850f8c8c9e:1 - Address: 166Bitrbfa16oR7DKKSzgdhU4MpVKE4cKb, Amount: 429618 satoshis, Spent: False
UTXO ca4aa3bd9e38eba447bff85a000e74fc27ca3ca78f1295a8481e50af65fcd511:3 - Address: 166Bitrbfa16oR7DKKSzgdhU4MpVKE4cKb, Amount: 90000 satoshis, Spent: False
2024-07-28 09:42:08 (UTC+8)
Send_BTC : 502098
Send_BTC_Fee: 17520
unspent_total_value = 519618
●Response from mempool.space : sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement c938ceda6608cf912dba5dda7b2979ed11fa287c67670b359d365b436445116a; new feerate 0.00051681 BTC/kvB <= old feerate 0.00307514 BTC/kvB"}
2024-07-28 09:42:15 (UTC+8)
Send_BTC : 484778
Send_BTC_Fee: 34840
unspent_total_value = 519618
●Response from mempool.space : sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement 8bd50cf10b880973a65a37b78e10f7c64413a6b995f1b639d184a2518449fbf2; new feerate 0.00103076 BTC/kvB <= old feerate 0.00307514 BTC/kvB"}
2024-07-28 09:42:18 (UTC+8)
Send_BTC : 467458
Send_BTC_Fee: 52160
unspent_total_value = 519618
●Response from mempool.space : sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement 8adcb6a53e6524ca8c5c6b819e14d17ed7842a5a10ff597d763ff8c964039695; new feerate 0.00154319 BTC/kvB <= old feerate 0.00307514 BTC/kvB"}
2024-07-28 09:42:24 (UTC+8)
Send_BTC : 450138
Send_BTC_Fee: 69480
unspent_total_value = 519618
●Response from mempool.space : sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement cc0d34c088e6e62a077ccd154db7cc0d4b0789d4a3a649c4907193d4d48412f3; new feerate 0.00205562 BTC/kvB <= old feerate 0.00669492 BTC/kvB"}
Send_BTC : 432818
Send_BTC_Fee: 86800
unspent_total_value = 519618
2024-07-28 09:42:31 (UTC+8)
●Response from mempool.space : sendrawtransaction RPC error: {"code":-25,"message":"bad-txns-inputs-missingorspent"}
2024-07-28 09:42:33 (UTC+8)
Error: Unable to send transaction (status code: 429)
●Response from mempool.space : <html>
<head><title>429 Too Many Requests</title></head>
<body>
<center><h1>429 Too Many Requests</h1></center>
<center><h2>Sign Up for <a href="https://mempool.space/enterprise">Mempool Enterprise</a> to get increased API limits</h2></center>
</body>
</html>
....
....
....
Found 2 unspent transaction outputs.
Filtered unspent UTXOs: 2
UTXO 7855cf143b41f86b04f385423a000f7cd6456f0d1ad4a76a8d3bd4850f8c8c9e:1 - Address: 166Bitrbfa16oR7DKKSzgdhU4MpVKE4cKb, Amount: 429618 satoshis, Spent: False
UTXO ca4aa3bd9e38eba447bff85a000e74fc27ca3ca78f1295a8481e50af65fcd511:3 - Address: 166Bitrbfa16oR7DKKSzgdhU4MpVKE4cKb, Amount: 90000 satoshis, Spent: False
2024-07-28 09:42:08 (UTC+8)
Send_BTC : 502098
Send_BTC_Fee: 17520
unspent_total_value = 519618
●Response from mempool.space : sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement c938ceda6608cf912dba5dda7b2979ed11fa287c67670b359d365b436445116a; new feerate 0.00051681 BTC/kvB <= old feerate 0.00307514 BTC/kvB"}
2024-07-28 09:42:15 (UTC+8)
Send_BTC : 484778
Send_BTC_Fee: 34840
unspent_total_value = 519618
●Response from mempool.space : sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement 8bd50cf10b880973a65a37b78e10f7c64413a6b995f1b639d184a2518449fbf2; new feerate 0.00103076 BTC/kvB <= old feerate 0.00307514 BTC/kvB"}
2024-07-28 09:42:18 (UTC+8)
Send_BTC : 467458
Send_BTC_Fee: 52160
unspent_total_value = 519618
●Response from mempool.space : sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement 8adcb6a53e6524ca8c5c6b819e14d17ed7842a5a10ff597d763ff8c964039695; new feerate 0.00154319 BTC/kvB <= old feerate 0.00307514 BTC/kvB"}
2024-07-28 09:42:24 (UTC+8)
Send_BTC : 450138
Send_BTC_Fee: 69480
unspent_total_value = 519618
●Response from mempool.space : sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement cc0d34c088e6e62a077ccd154db7cc0d4b0789d4a3a649c4907193d4d48412f3; new feerate 0.00205562 BTC/kvB <= old feerate 0.00669492 BTC/kvB"}
Send_BTC : 432818
Send_BTC_Fee: 86800
unspent_total_value = 519618
2024-07-28 09:42:31 (UTC+8)
●Response from mempool.space : sendrawtransaction RPC error: {"code":-25,"message":"bad-txns-inputs-missingorspent"}
2024-07-28 09:42:33 (UTC+8)
Error: Unable to send transaction (status code: 429)
●Response from mempool.space : <html>
<head><title>429 Too Many Requests</title></head>
<body>
<center><h1>429 Too Many Requests</h1></center>
<center><h2>Sign Up for <a href="https://mempool.space/enterprise">Mempool Enterprise</a> to get increased API limits</h2></center>
</body>
</html>
....
....
....
then~~~All response is "429 Too Many Requests"
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Also albert0, why was your trans fee still lower than my original. You said it was increased 3 times but still was lower than my one and only fee, correct?
My log
Code:
●Response from mempool.space : sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement c938ceda6608cf912dba5dda7b2979ed11fa287c67670b359d365b436445116a; new feerate 0.00051681 BTC/kvB <= old feerate 0.00307514 BTC/kvB"}
●Response from mempool.space : sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement 8bd50cf10b880973a65a37b78e10f7c64413a6b995f1b639d184a2518449fbf2; new feerate 0.00103076 BTC/kvB <= old feerate 0.00307514 BTC/kvB"}
●Response from mempool.space : sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement 8adcb6a53e6524ca8c5c6b819e14d17ed7842a5a10ff597d763ff8c964039695; new feerate 0.00154319 BTC/kvB <= old feerate 0.00307514 BTC/kvB"}
●Response from mempool.space : sendrawtransaction RPC error: {"code":-26,"message":"insufficient fee, rejecting replacement cc0d34c088e6e62a077ccd154db7cc0d4b0789d4a3a649c4907193d4d48412f3; new feerate 0.00205562 BTC/kvB <= old feerate 0.00669492 BTC/kvB"}
●Response from mempool.space : <html>
<head><title>429 Too Many Requests</title></head>
<body>
<center><h1>429 Too Many Requests</h1></center>
<center><h2>Sign Up for <a href="https://mempool.space/enterprise">Mempool Enterprise</a> to get increased API limits</h2></center>
</body>
</html>
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
I don't know, maybe I'm wrong, but what I noticed is that your transaction was not broadcast from the Mempool route. I think you know a way.
The history here has two networks, one is the main one and the other is the main Mempool route, the transaction was not confirmed on the Mempool route, although it was sent earlier, but it was not approved, and maybe the Mempool policy behaved like this. but your transaction did not pass through the Mempol route, am I wrong? ?
https://blockchair.com/bitcoin/address/197kFKvMHoRJPXktc8xJwMjeTuE9xijBQ
The history here has two networks, one is the main one and the other is the main Mempool route, the transaction was not confirmed on the Mempool route, although it was sent earlier, but it was not approved, and maybe the Mempool policy behaved like this. but your transaction did not pass through the Mempol route, am I wrong? ?
https://blockchair.com/bitcoin/address/197kFKvMHoRJPXktc8xJwMjeTuE9xijBQ
After this experiment, I realized that the wallet software "Electrum" cannot grab the BTC of #66
we must create own RawTX (raw_hex)
use API broadcasts to blockchain
response = requests.post(
'https://blockchain.info/pushtx',
data={'tx': raw_tx}
)
print(response.text)
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Yeah, Bud, I know the concept of this whole test. I wanted to know if anyone took snapshots or notes, of how many different people / competing transactions were happening, before whichever one, finally got through. The play by play, wilspen.
https://www.youtube.com/watch?v=CjxjkDEE43s
18UGZENCDBHF8ciPUuHFDMDNy1vm8aUmYt 0 BTC
Creator’s BTC snatched away within 5 minutes
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Can anyone give a rundown on what happened?
Like the original broadcasted transaction, the competing transactions, and which one won?
Like the original broadcasted transaction, the competing transactions, and which one won?
197kFKvMHoRJPXktc8xJwMjeTuE9xijBQ ==> 18UGZENCDBHF8ciPUuHFDMDNy1vm8aUmYt
someone use high Fee to replace orig Txid and got 0.00467224 BTC ( bc1qcrej0q6xqfyr9ecayk3y6khykuugt7za6umuk4 )
https://explorer.btc.com/btc/transaction/354dbcb6fd3532a051e1e363c9122d862949c3d075280d4144f719d6ba99e14a
puzzle 66 is unsafe
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
I have a theory, when making a transfer using the electrum wallet and sending the total, the value in the wallet is reset to zero, how would your program do to cancel the transaction if there are no more funds? and to do the RBF you would need funds to increase rates, and without funds it would only be possible to make the first transaction. Do you have any theories if it would still be possible?
Your theory is wrong. It doesn't matter what amount you will transfer or how high the fee is or the software you will use.
The transaction can be replaced at any time by anyone from any location. Only a higher fee is required to make this fully effective.
yesterday , I am online and use Kangaroo.exe crack private key about 2 minutes
then I import private key to Electrum ( Win10 )
I got 2 transaction notifications immediately, one was +0.00495561 BTC , the other was -0.00495561 BTC , while the balance was 0 BTC
At the time , Transaction is 0 confirmations , but I can't do anything ....
Electrum show the balance 0 BTC
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
Pub: 0x02DC28EF701BB67EB35C759CCA511CD522A598EDAC322FD073A2C0A0BD4CC8C910
Priv: 0x3CB359F64B27EF00
But why you are giving wrong range its not 66 bit its 62 bit.. lets try another
Orig TX https://www.blockchain.com/explorer/transactions/btc/2ee4f5155390a888a22b1417d35bd9023a1005b171b97615f4532d207e581c24
New TX https://www.blockchain.com/explorer/transactions/btc/098fec25954faad5571bb81234658228c888cd428a2531538ed1d40e278af9e3
ADDRESS: 1DWQHdi1mh27vcUyrN5NYB1kWrs3BBKUXA
No one seems to have taken his BTC
Re: Bitcoin puzzle transaction ~32 BTC prize to who solves it
I finally got back around to try to come up with a python solution, I think I got it.
Code:
Bitcoin Address: 13zb1hQbWVuYdZoAkztVrNrm65aReL2pYD
Message : I finally got this to work with python
Signature : H6DZ+QYaSIb+EafHdwIC9uJrM3B6ZovzsvkpIIkNIij8QdORG03/ccbyodreXNp5YlyclvkiSA8lu9XThd8ZauU=
Message : I finally got this to work with python
Signature : H6DZ+QYaSIb+EafHdwIC9uJrM3B6ZovzsvkpIIkNIij8QdORG03/ccbyodreXNp5YlyclvkiSA8lu9XThd8ZauU=
I get r s z from this Message and Signature
r = 0xa0d9f9061a4886fe11a7c7770202f6e26b33707a668bf3b2f92920890d2228fc
s = 0x41d3911b4dff71c6f2a1dade5cda79625c9c96f922480f25bbd5d385df196ae5
z = 0xac6ff2c56216ace1660a6c04052774769ed7bc40542e1bc3408253eadb7223b8
Recovered Bitcoin public key: 03f3fb41f466d9893e5af7dfd788211b0503eb38d49615a19aa22b419ed4ff308d
Bitcoin Address： 13zb1hQbWVuYdZoAkztVrNrm65aReL2pYD
then use Kangaroo find private key
python3 gen_data.py -f data.json -c SECP256K1 -b 1 -t LSB -n 360
Private Key: 0xa0a9e351153934a4d5e86c4c53f21bef542e676e2639235596c5d3b81f57
Preparing Data
Generating 360 signatures with curve SECP256K1
leaking 1 bits for k (LSB) ...
File data.json written with all data.
Private Key: 0xa0a9e351153934a4d5e86c4c53f21bef542e676e2639235596c5d3b81f57
Preparing Data
Generating 360 signatures with curve SECP256K1
leaking 1 bits for k (LSB) ...
File data.json written with all data.
=== my test results ===
252 ( leak 4 bit ) ===> 70 rsz Success ( Time: 8 seconds )
253 ( leak 3 bit ) ===> 155 rsz Success (Time: 661 seconds )
254 ( leak 2 bit ) ===> 200~1500+ rsz Never Recovery my Private Key
255 ( leak 1 bit ) ===> 1500+ rsz Never Recovery my Private Key
256 ( leak 0 bit ) ===> 1500+ rsz Never Recovery my Private Key
Code:
# rsz 1
r=0xd7232c0eed9a80a6e53d74b57d80cd892816b46c69157f8e543ee76dc21f8410
s=0xe6665792427b98ebd93cd43f694e03383c84af34b00e5f471c5cec5a24541808
z=0xc3479c8d5591597a4b12018ccacd0215528e584aa18125d63fac5c0c0c92588b
# rsz 2
r=0xafc4670c63a5677641ba51b0eb413f7d8be3cfeb100f2c2097eb57dd673d58c2
s=0xe14e5906641085412561a083c002b76d6ac5a54372a9c811edc9e3b86b2dde11
z=0x1b636df9eef267995d6918047ba3bafca25f693a47ff73c7c0d500cd4aa9783a
r=0xd7232c0eed9a80a6e53d74b57d80cd892816b46c69157f8e543ee76dc21f8410
s=0xe6665792427b98ebd93cd43f694e03383c84af34b00e5f471c5cec5a24541808
z=0xc3479c8d5591597a4b12018ccacd0215528e584aa18125d63fac5c0c0c92588b
# rsz 2
r=0xafc4670c63a5677641ba51b0eb413f7d8be3cfeb100f2c2097eb57dd673d58c2
s=0xe14e5906641085412561a083c002b76d6ac5a54372a9c811edc9e3b86b2dde11
z=0x1b636df9eef267995d6918047ba3bafca25f693a47ff73c7c0d500cd4aa9783a
Code:
N = 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364141
def inv(a):
return pow(a, N - 2, N)
r1 = 0xd7232c0eed9a80a6e53d74b57d80cd892816b46c69157f8e543ee76dc21f8410
s1 = 0xe6665792427b98ebd93cd43f694e03383c84af34b00e5f471c5cec5a24541808
z1 = 0xc3479c8d5591597a4b12018ccacd0215528e584aa18125d63fac5c0c0c92588b
HA = 0xd7232c0eed9a80a6e53d74b57d80cd892816b46c69157f8e543ee76dc21f8410 * inv(0xafc4670c63a5677641ba51b0eb413f7d8be3cfeb100f2c2097eb57dd673d58c2)
HA = HA % N
print("HA: %064x" % HA )
r2 = 0xafc4670c63a5677641ba51b0eb413f7d8be3cfeb100f2c2097eb57dd673d58c2 * HA
s2 = 0xe14e5906641085412561a083c002b76d6ac5a54372a9c811edc9e3b86b2dde11 * HA
z2 = 0x1b636df9eef267995d6918047ba3bafca25f693a47ff73c7c0d500cd4aa9783a * HA
z2 = z2 - s2
r2 = r2 % N
s2 = s2 % N
z2 = z2 % N
print("r1= 0x%064x " % r1 )
print("s1= 0x%064x " % s1 )
print("z1= 0x%064x " % z1 )
print("r2= 0x%064x " % r2 )
print("s2= 0x%064x " % s2 )
print("z2= 0x%064x " % z2 )
def inv(a):
return pow(a, N - 2, N)
r1 = 0xd7232c0eed9a80a6e53d74b57d80cd892816b46c69157f8e543ee76dc21f8410
s1 = 0xe6665792427b98ebd93cd43f694e03383c84af34b00e5f471c5cec5a24541808
z1 = 0xc3479c8d5591597a4b12018ccacd0215528e584aa18125d63fac5c0c0c92588b
HA = 0xd7232c0eed9a80a6e53d74b57d80cd892816b46c69157f8e543ee76dc21f8410 * inv(0xafc4670c63a5677641ba51b0eb413f7d8be3cfeb100f2c2097eb57dd673d58c2)
HA = HA % N
print("HA: %064x" % HA )
r2 = 0xafc4670c63a5677641ba51b0eb413f7d8be3cfeb100f2c2097eb57dd673d58c2 * HA
s2 = 0xe14e5906641085412561a083c002b76d6ac5a54372a9c811edc9e3b86b2dde11 * HA
z2 = 0x1b636df9eef267995d6918047ba3bafca25f693a47ff73c7c0d500cd4aa9783a * HA
z2 = z2 - s2
r2 = r2 % N
s2 = s2 % N
z2 = z2 % N
print("r1= 0x%064x " % r1 )
print("s1= 0x%064x " % s1 )
print("z1= 0x%064x " % z1 )
print("r2= 0x%064x " % r2 )
print("s2= 0x%064x " % s2 )
print("z2= 0x%064x " % z2 )
output:
r1 = 0xd7232c0eed9a80a6e53d74b57d80cd892816b46c69157f8e543ee76dc21f8410
s1 = 0xe6665792427b98ebd93cd43f694e03383c84af34b00e5f471c5cec5a24541808
z1 = 0xc3479c8d5591597a4b12018ccacd0215528e584aa18125d63fac5c0c0c92588b
r2= 0xd7232c0eed9a80a6e53d74b57d80cd892816b46c69157f8e543ee76dc21f8410
s2= 0xe6665792427b98ebd93cd43f694e03383c84af34b00e5f471c5cec5a24541808
z2= 0xc3479c8d5591597a4b12018ccacd0215528e584aa18125d63fac5c0c0c92588b
r1 = r2 , s1 = s2 , z1 = z2 .......Your 2 rsz are from the same rsz
Code:
# rsz 1
r=0xd7232c0eed9a80a6e53d74b57d80cd892816b46c69157f8e543ee76dc21f8410
s=0xe6665792427b98ebd93cd43f694e03383c84af34b00e5f471c5cec5a24541808
z=0xc3479c8d5591597a4b12018ccacd0215528e584aa18125d63fac5c0c0c92588b
# rsz 2
r=0xafc4670c63a5677641ba51b0eb413f7d8be3cfeb100f2c2097eb57dd673d58c2
s=0xe14e5906641085412561a083c002b76d6ac5a54372a9c811edc9e3b86b2dde11
z=0x1b636df9eef267995d6918047ba3bafca25f693a47ff73c7c0d500cd4aa9783a
You try bruteforce 02d7232c0eed9a80a6e53d74b57d80cd892816b46c69157f8e543ee76dc21f8410 ? r=0xd7232c0eed9a80a6e53d74b57d80cd892816b46c69157f8e543ee76dc21f8410
s=0xe6665792427b98ebd93cd43f694e03383c84af34b00e5f471c5cec5a24541808
z=0xc3479c8d5591597a4b12018ccacd0215528e584aa18125d63fac5c0c0c92588b
# rsz 2
r=0xafc4670c63a5677641ba51b0eb413f7d8be3cfeb100f2c2097eb57dd673d58c2
s=0xe14e5906641085412561a083c002b76d6ac5a54372a9c811edc9e3b86b2dde11
z=0x1b636df9eef267995d6918047ba3bafca25f693a47ff73c7c0d500cd4aa9783a
no....bruteforce nonce k , that is impossible
It's seem use 1 rsz convert to 2 rsz
even know that
k2 = k1 + 1
I still can't recovery private key
Code:
# rsz 1
r=0xd7232c0eed9a80a6e53d74b57d80cd892816b46c69157f8e543ee76dc21f8410
s=0xe6665792427b98ebd93cd43f694e03383c84af34b00e5f471c5cec5a24541808
z=0xc3479c8d5591597a4b12018ccacd0215528e584aa18125d63fac5c0c0c92588b
# rsz 2
r=0xafc4670c63a5677641ba51b0eb413f7d8be3cfeb100f2c2097eb57dd673d58c2
s=0xe14e5906641085412561a083c002b76d6ac5a54372a9c811edc9e3b86b2dde11
z=0x1b636df9eef267995d6918047ba3bafca25f693a47ff73c7c0d500cd4aa9783a
With k2 = k1 + 1.r=0xd7232c0eed9a80a6e53d74b57d80cd892816b46c69157f8e543ee76dc21f8410
s=0xe6665792427b98ebd93cd43f694e03383c84af34b00e5f471c5cec5a24541808
z=0xc3479c8d5591597a4b12018ccacd0215528e584aa18125d63fac5c0c0c92588b
# rsz 2
r=0xafc4670c63a5677641ba51b0eb413f7d8be3cfeb100f2c2097eb57dd673d58c2
s=0xe14e5906641085412561a083c002b76d6ac5a54372a9c811edc9e3b86b2dde11
z=0x1b636df9eef267995d6918047ba3bafca25f693a47ff73c7c0d500cd4aa9783a
sorry......I can't recovery private key for this 2 rsz
my result:
k1 = 0
k2 = 1
Recovered Bitcoin public key: 028629507d9eef1748ec67ca2c4ab641fa0951d7f0bb0cf226f1c0f465a4e29404
Bitcoin Address： 1Ln1NYjtCamBG2UZDTKcHqcaNLP8TUrKFe
Recovered Bitcoin public key: 0395c632a7af384a67104afd5b6a4a5d882e782d232519c59084f0744d08093876
Bitcoin Address： 1P5TaCC8ZQohntb3NwRXQE5zFzB2De2Dvz
show your private key .. ??
Well, then I have two more for you, but this public key doesn't point to the puzzle #130 it seems...
# Public Key
0x8629507d9eef1748ec67ca2c4ab641fa0951d7f0bb0cf226f1c0f465a4e29404, 0x2237204a53021490adfec9f0b3f0732f5024181d50fde2dcfc7a428c992b8d70
# Public Key
0x8629507d9eef1748ec67ca2c4ab641fa0951d7f0bb0cf226f1c0f465a4e29404, 0x2237204a53021490adfec9f0b3f0732f5024181d50fde2dcfc7a428c992b8d70
I had edit my post ~~ fix it #130
public key 0x633cbe3ec02b9401c5effa144c5b4d22f87940259634858fc7e59b1c09937852, 0xb078a17cc1558a9a4fa0b406f194c9a2b71d9a61424b533ceefe27408b3191e3
and Provide 5 sets of my own generated rsz for #130
# 130 rsz 1
r=0x56a37728d3036203ba57a2399ba282351b55e7b7a2660080a510732f373f18f8
s=0x6bf0c1501792f3184866f56a82b69ad17cb169105ed85350ca30f3e2070e032e
z=0x0042fe8868fbfa3d16b603af849bb81a35d6292651ab36a23af4c427d4265bf9
# 130 rsz 2
r=0x84812aade108ee63f12098f31e0819b36fcd4a4433fdbd29dbc8d94082e1a822
s=0xa7da5a2552d02a4551a23381fe4bcca9f1108d66cb0137712d9325d2a1fe4b4a
z=0x50825e90bcae246a62602d3719d895da1108545b3c09527ed1dbf599034cf0a2
# 130 rsz 3
r=0x1567a88d2dc54158afc135433f5bd7cb673a73ecd978626504fa7a972fc88eb0
s=0x0340b27310b89895c166c839b5a27fd6de1a271a8765de608c07e96539827850
z=0x503f919c88920407436211529abf8f8d2459d8aec963181dbaf822e20f162d0e
# 130 rsz 4
r=0x3facca914bf602c454b2e1332e4bd9db3482cdc648bc9f79328fed36de7babca
s=0xfe9797f9323c74e8b5d91937c4ea704f0a73e3aae536d8f051e7c77214a4a5a9
z=0xdde32a1d171f66168bc88211c5bbd1f0de2bc8aa504b70af8591f7619b6a3632
# 130 rsz 5
r=0x63444d8aa42965428ea68fa74976fe38772ba59e6e1b4f8682e6f6178ee4c1e9
s=0x33f53e75c58b289d094932407c4f1eac3156a0029c9a33f257485a0c3b5b497d
z=0xfe4573a2009e9f7985f8f366949757f001aaccc81da635ea3868c1d70b9a2e04
1Fo65aKq8s8iquMt6weF1rku1moWVEd5Ua
Hi there!
It looks like you all are crazy for nonces and signatures, so I have some special values for you
Btw. I think that those who do serious research of this topic do not need your script, but all contributions are welcome, of course.
It looks like you all are crazy for nonces and signatures, so I have some special values for you
Btw. I think that those who do serious research of this topic do not need your script, but all contributions are welcome, of course.
the same r value , we can recovery private key ........
but we are interested in recovering the private key of #puzzle 130 from a large set of r s z and public key ...
But we need to know the bits of k ， from every set of r s z .........
if anyone can know the bits of k from every r s z and public key , all bitcoin address that leaks the public key can recovery private key
Of course, currently only 252 bit k can be recovery by the lattice attack.
would you mind sharing your code on how you leak the RSZ and how you create more sample for the given public key. thank you
https://bitcointalk.org/index.php?topic=5394249.100
read it ....... garlonicon share his source code
Even if I have 100000 puzzle #130 r , s, z
I still can't use lattice-attack crack ....Because the generated rsz and k values are unknown....
I used my private key and public key to see nonce K value ...
From the probability, more than 50% is a 256-bit nonce K value ~~ It must be 252 bit or less bit ......
N = 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEBAAEDCE6AF48A03BBFD25E8CD0364141
if N <= 252 bit , we can use #130 public key to produce 70 ~ 100 fake rsz , and ECDSA will broken ~~~ Now, ECDSA is still safe
I have been learning about ECDSA ( r s z, public key ,private key ) for about 2 months
# 130 Although only one rsz is know , but 1000 rsz can be produced using the public key, the nonce K value will be 240~256 bits
50% - nonce is 256 bit
25% - nonce is 254 bit
25% - nonce is 253~240 bit
However, more than 64 rsz must be leaked at the same time to leak more than 12 bits to use lattice-attack
# 130 Public Key
0x8629507d9eef1748ec67ca2c4ab641fa0951d7f0bb0cf226f1c0f465a4e29404, 0x2237204a53021490adfec9f0b3f0732f5024181d50fde2dcfc7a428c992b8d70
create #130 rsz
# 130 Although only one rsz is know , but 1000 rsz can be produced using the public key, the nonce K value will be 240~256 bits
50% - nonce is 256 bit
25% - nonce is 254 bit
25% - nonce is 253~240 bit
However, more than 64 rsz must be leaked at the same time to leak more than 12 bits to use lattice-attack
# 130 Public Key
0x8629507d9eef1748ec67ca2c4ab641fa0951d7f0bb0cf226f1c0f465a4e29404, 0x2237204a53021490adfec9f0b3f0732f5024181d50fde2dcfc7a428c992b8d70
create #130 rsz
Code:
# 130 rsz 1
r=0x56a37728d3036203ba57a2399ba282351b55e7b7a2660080a510732f373f18f8
s=0x6bf0c1501792f3184866f56a82b69ad17cb169105ed85350ca30f3e2070e032e
z=0x0042fe8868fbfa3d16b603af849bb81a35d6292651ab36a23af4c427d4265bf9
# 130 rsz 2
r=0x84812aade108ee63f12098f31e0819b36fcd4a4433fdbd29dbc8d94082e1a822
s=0xa7da5a2552d02a4551a23381fe4bcca9f1108d66cb0137712d9325d2a1fe4b4a
z=0x50825e90bcae246a62602d3719d895da1108545b3c09527ed1dbf599034cf0a2
# 130 rsz 3
r=0x1567a88d2dc54158afc135433f5bd7cb673a73ecd978626504fa7a972fc88eb0
s=0x0340b27310b89895c166c839b5a27fd6de1a271a8765de608c07e96539827850
z=0x503f919c88920407436211529abf8f8d2459d8aec963181dbaf822e20f162d0e
# 130 rsz 4
r=0x3facca914bf602c454b2e1332e4bd9db3482cdc648bc9f79328fed36de7babca
s=0xfe9797f9323c74e8b5d91937c4ea704f0a73e3aae536d8f051e7c77214a4a5a9
z=0xdde32a1d171f66168bc88211c5bbd1f0de2bc8aa504b70af8591f7619b6a3632
# 130 rsz 5
r=0x63444d8aa42965428ea68fa74976fe38772ba59e6e1b4f8682e6f6178ee4c1e9
s=0x33f53e75c58b289d094932407c4f1eac3156a0029c9a33f257485a0c3b5b497d
z=0xfe4573a2009e9f7985f8f366949757f001aaccc81da635ea3868c1d70b9a2e04
....
....
....
r=0x56a37728d3036203ba57a2399ba282351b55e7b7a2660080a510732f373f18f8
s=0x6bf0c1501792f3184866f56a82b69ad17cb169105ed85350ca30f3e2070e032e
z=0x0042fe8868fbfa3d16b603af849bb81a35d6292651ab36a23af4c427d4265bf9
# 130 rsz 2
r=0x84812aade108ee63f12098f31e0819b36fcd4a4433fdbd29dbc8d94082e1a822
s=0xa7da5a2552d02a4551a23381fe4bcca9f1108d66cb0137712d9325d2a1fe4b4a
z=0x50825e90bcae246a62602d3719d895da1108545b3c09527ed1dbf599034cf0a2
# 130 rsz 3
r=0x1567a88d2dc54158afc135433f5bd7cb673a73ecd978626504fa7a972fc88eb0
s=0x0340b27310b89895c166c839b5a27fd6de1a271a8765de608c07e96539827850
z=0x503f919c88920407436211529abf8f8d2459d8aec963181dbaf822e20f162d0e
# 130 rsz 4
r=0x3facca914bf602c454b2e1332e4bd9db3482cdc648bc9f79328fed36de7babca
s=0xfe9797f9323c74e8b5d91937c4ea704f0a73e3aae536d8f051e7c77214a4a5a9
z=0xdde32a1d171f66168bc88211c5bbd1f0de2bc8aa504b70af8591f7619b6a3632
# 130 rsz 5
r=0x63444d8aa42965428ea68fa74976fe38772ba59e6e1b4f8682e6f6178ee4c1e9
s=0x33f53e75c58b289d094932407c4f1eac3156a0029c9a33f257485a0c3b5b497d
z=0xfe4573a2009e9f7985f8f366949757f001aaccc81da635ea3868c1d70b9a2e04
....
....
....
Hello friends. I've been trying to learn for a while. Where and how do you find the known bit value and Lbs/mbs? No matter what I did, I could not perform a successful lattice attack. I'm sorry for my English and my inexperience. I'm trying to learn.
https://github.com/bitlogik/lattice-attack lattice-attacklattice-attack only can recovery 252 bit nonce , from 88 rsz
Code:
# python3 gen_data.py -f data252_88.json -m "HelloYou" -c SECP256K1 -b 4 -t MSB -n 88
# python3 lattice_attack.py -f data252_88.json
......
BKZ reduction : block size = 25
...
...
\o/ 000000000000000000000000F320D5823C07E40B8EA073FF9AF7017C2A9294EB
time: 4.3 second
# python3 lattice_attack.py -f data252_88.json
......
BKZ reduction : block size = 25
...
...
\o/ 000000000000000000000000F320D5823C07E40B8EA073FF9AF7017C2A9294EB
time: 4.3 second
only 4.3 seconds , I can recovery my private key
when I test 254, 255,256 bit , even use 2000 rsz , lattice-attack unable to recover private key