Pages:
Author

Topic: Bitcoin puzzle transaction ~32 BTC prize to who solves it - page 61. (Read 230409 times)

newbie
Activity: 10
Merit: 3

I decide in my code 250~500 transactions with better fees and  ~2500 with small fees and get ~4000transactions and try mine block. I think lucky your transaction faill

Nice to know, What you mean with " I think lucky your transaction faill" ? BTW edit your post and quote it correctly.

I’ll try to explain better.
In my btc_miner, using Bitcoin Core and an RPC connection, I have access to all unverified transactions.
In this mempool, for example, I have 15,000 transactions. It’s impossible to include all of them in the block for mining.
I have limited space, so I typically choose between 3,000 to 5,000 transactions to be included in the block.
To make it profitable, I select transactions with higher fees first and then add those with lower fees to the block.
Once the transactions are defined, along with the Merkle tree and the previous block hash, I attempt to find the nonce.
The goal is to find a SHA-256 double hash with 19 leading zeros within the 2^32 possible nonce values.
If a valid nonce isn’t found, the process restarts. The miner who discovers the nonce and submits it first wins.
Unfortunately, after 5 months, I haven’t been able to mine any block. I only have 3 RTX 3080 GPUs; I don’t have an ASIC machine.
Therefore, Alberto, it’s possible that the miner didn’t choose your transaction, even if it had a higher fee.
newbie
Activity: 29
Merit: 0
My bot found the key and I send 3 Transactions all accepted by mempool, but they weren't mined.

Hello everybody. In 2019, I create my firt btc_miner, in python and C and bitcoincore (personal project).
With my RTX-3080 i got 1.3 GHhash/s not bad
some code to select transactions in pool.
Code:
try:
      pc_connection = AuthServiceProxy(serverURL)
      mempool = rpc_connection.getrawmempool(True)
      alltxs = [(txid, tx['fees'], tx['unbroadcast'],tx['bip125-replaceable']) for txid, tx in mempool.items()]
      alltxs_sorted = sorted(alltxs, key=lambda x: x[1]['modified'], reverse=False)

except Exception as e:
time.sleep(10)
continue

# how many transactions i want (random)
nx = random.randint(3000, 5000)
tokens = alltxs_sorted[:nx]



txhashes = []
txs_hex  = []

# fees
fees = 0
ntx1  = 0
pos_tx  = 0

for txs in tokens:
pos_tx += 1
tx_hash = txs[0]
brod = txs[2]
taxa = txs[1]['modified']
repl = txs[3]
if brod == False:
try:
raw_tx = rpc_connection.getrawtransaction(tx_hash)
if repl == False and ntx1 < 4500:
   ....

I decide in my code 250~500 transactions with better fees and  ~2500 with small fees and get ~4000transactions and try mine block. I think lucky your transaction faill


Did you or did Alberto make the btc_miner?
hero member
Activity: 862
Merit: 662
Is anyone else concerned about digaran?

TBH no, I think he is using another account, what you can expected from a troll.

I decide in my code 250~500 transactions with better fees and  ~2500 with small fees and get ~4000transactions and try mine block. I think lucky your transaction faill

Nice to know, What you mean with " I think lucky your transaction faill" ? BTW edit your post and quote it correctly.
newbie
Activity: 10
Merit: 3
My bot found the key and I send 3 Transactions all accepted by mempool, but they weren't mined.

Hello everybody. In 2019, I create my firt btc_miner, in python and C and bitcoincore (personal project).
With my RTX-3080 i got 1.3 GHhash/s not bad
some code to select transactions in pool.
Code:
try:
      pc_connection = AuthServiceProxy(serverURL)
      mempool = rpc_connection.getrawmempool(True)
      alltxs = [(txid, tx['fees'], tx['unbroadcast'],tx['bip125-replaceable']) for txid, tx in mempool.items()]
      alltxs_sorted = sorted(alltxs, key=lambda x: x[1]['modified'], reverse=False)

except Exception as e:
time.sleep(10)
continue

# how many transactions i want (random)
nx = random.randint(3000, 5000)
tokens = alltxs_sorted[:nx]

txhashes = []
txs_hex  = []

# fees
fees = 0
ntx1  = 0
pos_tx  = 0

for txs in tokens:
pos_tx += 1
tx_hash = txs[0]
brod = txs[2]
taxa = txs[1]['modified']
repl = txs[3]
if brod == False:
try:
raw_tx = rpc_connection.getrawtransaction(tx_hash)
if repl == False and ntx1 < 4500:
   ....

I decide in my code 250~500 transactions with better fees and  ~2500 with small fees and get ~4000transactions and try mine block. I think lucky your transaction faill
newbie
Activity: 29
Merit: 0
You can have your own mempool on your home machine. No one can block you in localhost. You can only DDoS ​​Clearnet and Tor network.

I've already tweaked the number of connections a node can make.  Grin

So you've setup your own Bitcoin node, have 5 computers, are worried about how many seconds of advantage you have and how many IPs to use to not get blocked, use your own mempool, and after all of this struggle you still invoke some 3rd party process to create and send your faith-based bumped-up TX consisting of a few hundred bytes? Jesus.

At least my excuse was that I was out of electricity last night. Bot was running for days. Bad luck.

No one needs some gigantic setup to run a bot. 400 lines of Python and a working kangaroo binary is enough.

Good.
My script is wrong, it's returning "balance error".

My setup it's just my keyhunt on WSL, and my python loopping.. I'll fix that up and made some tests...
member
Activity: 194
Merit: 14
Is anyone else concerned about digaran? Do you think he gave up Bitcointalk forum or just still active from different accounts?

He was last active on 20 January, 2024.

He was most active on this particular thread.
member
Activity: 165
Merit: 26
For all those who develop their own bots here are the main mistakes to avoid.

- Don't start your first transactions from a fixed fee.
- Don't increment a fixed amount.

To solve previous points you need to read what is the current fee in sat/vB and increment from that point, network only will accept transactions if those are +1 Sat/vB from previous know transactions.

Learn how to calculate your transaction size and set your fee multiplier this must done to try to maximize your possibilities to be accepted in mempool, without the need of burn all the fee.

What if the transactions have less or more inputs/outputs?
Let's say first TX has 900 bytes and some fee.
Would another transaction of 300 bytes, with less inputs, but a larger fee/byte, and so a smaller total fee, be accepted and replace the first TX?...

What if the first TX has input X among several inputs, and another TX only has X as input? What would the miners choose? It doesn't sound like an easy to solve problem.
member
Activity: 43
Merit: 10
Damn, guys. I had taken my bot offline a few hours before it all went down.

There was a mistake in my code pertaining the tx creation.

I've spotted the flaw while running a simulation with test-coins and was hoping to fix it in time. Oh well.

I have a hunch that mine would have been capable of detecting the tx correctly, but it wouldn't be able to submit any valid ones of it's own.

I'll spend the next few days rectifying everything and running more simulations.
jr. member
Activity: 85
Merit: 2
I want 24 hour live support   Grin    /s



and why not import it into bl.ckch..n.com so it's directly spendable, sendable, tradeable. guess should ask my percentage for this one,
or am i seeing this wrong, did many times,.

 guess the fork war also has bots for their blockchains,, a little one but has to be right.

Forget the old bot script. I'm making a new one that will work directly on node.
No API - no external domains. BTC network only.


So, full-node OS and tweaking directly on it? This is getting more and more complex to keep track of. Undecided
Are you going to make a tutorial for n00bs?   Grin

 Sure. And a telegram channel for support.   Grin  Grin
hero member
Activity: 862
Merit: 662
Do those who have Bots consider sharing?

Learn python or any other language to develop your own tools, Stop being a Beggar.

For all those who develop their own bots here are the main mistakes to avoid.

- Don't start your first transactions from a fixed fee.
- Don't increment a fixed amount.

To solve previous points you need to read what is the current fee in sat/vB and increment from that point, network only will accept transactions if those are +1 Sat/vB from previous know transactions.

Learn how to calculate your transaction size and set your fee multiplier this must done to try to maximize your possibilities to be accepted in mempool, without the need of burn all the fee.

tx bc16e7ce388d9.. was added to the block at 2024-07-28 09:42:12 (GMT +8) you only had one attempt at 2024-07-28 09:42:08 (GMT +8)

this is not all correct, that is the same Timestamp for the block mining:
Block  854265 - 2024-07-27 19:42:12 (GMT -6)

But since all the bots have enough time to get the publickey, calculate the private key and broadcast transactions, then we can assume that the original transactions was broadcasted somewhere after the previous Block  854264 2024-07-27 19:37:48 (GMT -6).
member
Activity: 499
Merit: 38

and why not import it into bl.ckch..n.com so it's directly spendable, sendable, tradeable. guess should ask my percentage for this one,
or am i seeing this wrong, did many times,.

 guess the fork war also has bots for their blockchains,, a little one but has to be right.

Forget the old bot script. I'm making a new one that will work directly on node.
No API - no external domains. BTC network only.


So, full-node OS and tweaking directly on it? This is getting more and more complex to keep track of. Undecided
Are you going to make a tutorial for n00bs?   Grin

 Sure. And a telegram channel for support.   Grin  Grin
full member
Activity: 431
Merit: 105
gotta ask again, hi nomachine you have the latest freeware to use bot for this war<

? :-) with bumpfee options enabled,, guess its important,

and why not import it into bl.ckch..n.com so it's directly spendable, sendable, tradeable. guess should ask my percentage for this one,
or am i seeing this wrong, did many times,.

 guess the fork war also has bots for their blockchains,, a little one but has to be right.
member
Activity: 499
Merit: 38
how many IPs to use to not get blocked

 I'm currently running my node on Clearnet and Tor and I2P  &  Cloudflare Tunnels .... No worries.
member
Activity: 165
Merit: 26
You can have your own mempool on your home machine. No one can block you in localhost. You can only DDoS ​​Clearnet and Tor network.

I've already tweaked the number of connections a node can make.  Grin

So you've setup your own Bitcoin node, have 5 computers, are worried about how many seconds of advantage you have and how many IPs to use to not get blocked, use your own mempool, and after all of this struggle you still invoke some 3rd party process to create and send your faith-based bumped-up TX consisting of a few hundred bytes? Jesus.

At least my excuse was that I was out of electricity last night. Bot was running for days. Bad luck.

No one needs some gigantic setup to run a bot. 400 lines of Python and a working kangaroo binary is enough.
jr. member
Activity: 67
Merit: 1
so whatever your plan is, you're not going to leave those bitcoins to the robots
in the worst case, you can burn all the bitcoins or actually spend for transaction fees, at least you will have a good feeling, if you don't have it, no one will have it xd
you can create a suicide transaction as a last resort
newbie
Activity: 8
Merit: 0
some bots threw errors during this test, why? there will probably be a catch
here's how you should do it, by some miracle you solve the 66 address puzzle, then you create a transaction, then a second later you start your own bot that starts creating new transactions for the 66 addresses you have access to, the goal is to flood the blockchain with transactions
then after a minute when foreign bots start creating transactions to steal your bitcoins mempol throws errors for those addresses

this means that mempool can block incoming transactions that try to send puzzle 66 to new addresses because it will be evaluated as a crypto attack and cryptographic protection will be turned on

the goal should be for mempool to start throwing other transactions from other bots overboard xd

I don't know, I haven't tried it, it just occurred to me, you have to test it yourself
This is not an attack on cryptography, no matter how it looks. In the blockchain, the owner of the address is the one who has the private key to the address. And the possibility of RBF is correct. Imagine that you accidentally (by mistake) sent 5 bts with a very low commission, and no one takes it into the block. And what should you do, well, of course RBF, otherwise you will wait a long time until someone mines it.
member
Activity: 499
Merit: 38
You can have your own mempool on your home machine. No one can block you in localhost. You can only DDoS ​​Clearnet and Tor network.

I've already tweaked the number of connections a node can make.  Grin
jr. member
Activity: 67
Merit: 1
some bots threw errors during this test, why? there will probably be a catch
here's how you should do it, by some miracle you solve the 66 address puzzle, then you create a transaction, then a second later you start your own bot that starts creating new transactions for the 66 addresses you have access to, the goal is to flood the blockchain with transactions
then after a minute when foreign bots start creating transactions to steal your bitcoins mempol throws errors for those addresses

this means that mempool can block incoming transactions that try to send puzzle 66 to new addresses because it will be evaluated as a crypto attack and cryptographic protection will be turned on

the goal should be for mempool to start throwing other transactions from other bots overboard xd

I don't know, I haven't tried it, it just occurred to me, you have to test it yourself
newbie
Activity: 8
Merit: 0

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"}

tx bc16e7ce388d9.. was added to the block at 2024-07-28 09:42:12 (GMT +8) you only had one attempt at 2024-07-28 09:42:08 (GMT +8)
jr. member
Activity: 82
Merit: 8
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 don't use electrum at this time ~~

my BOT is writed by python and bitcoinlib

about  6~7 second  POST RawTX  to  https://mempool.space/api/tx

I think I gave away (POST RawTX) too often and didn’t calculate  BTC/kvB  properly.

 Grin Grin

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"}

2024-07-28 09:42:31 (UTC+8)
Send_BTC    : 432818
Send_BTC_Fee: 86800
unspent_total_value = 519618
●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 :
429 Too Many Requests

429 Too Many Requests


Sign Up for Mempool Enterprise to get increased API limits





....
....
....


then~~~All response is "429 Too Many Requests"
Pages:
Jump to: