Baskentliia
Jr. Member
 Offline
Activity: 60
Merit: 1
34Sf4DnMt3z6XKKoWmZRw2nGyfGkDgNJZZ
|
 |
Today at 11:32:57 AM |
|
Do those who have Bots consider sharing?
Additionally, 100s of bots have been installed for Puzzle 66.
Share it so we can build it and join the fight.
If our bot wins, we give some reward to those who share it.
What do bot owners think about this?
|
34Sf4DnMt3z6XKKoWmZRw2nGyfGkDgNJZZ
|
|
|
OxSD
Newbie
Offline
Activity: 7
Merit: 0
|
|
Today at 12:36:50 PM |
|
Well, I successfully beat any bots that were still in the game.
Thanks for creating the competition, but to be honest I expected more from it. Expectation: battle of bots, background techniques, unknown technique for starting the first outgoing transaction... Reality: starting fee 26% of balance, 1-2 bots It was already clear that if you give a quarter of your balance as fee, then the probability that bots will beat the transaction is quite low. And if the bot is really greedy, then it can turn 100% of balance into fee and then definitely win. LoL new feerate 0.00205562 BTC/kvB <= old feerate 0.00669492 BTC/kvB 669sat per byte - guys, are you serious? |
|
|
|
|
jacky19790729
Jr. Member
Offline
Activity: 80
Merit: 8
|
|
Today at 01:07:39 PM |
|
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/txI think I gave away (POST RawTX) too often and didn’t calculate BTC/kvB properly.  ====== 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 : <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" |
|
|
|
|
OxSD
Newbie
Offline
Activity: 7
Merit: 0
|
|
Today at 01:29:47 PM |
|
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) |
|
|
|
|
Feron
Jr. Member
 Online
Activity: 55
Merit: 1
|
|
Today at 01:35:22 PM |
|
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
|
|
|
|
|
nomachine
Member
Offline
Activity: 383
Merit: 21
|
|
Today at 01:49:58 PM |
|
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. |
|
|
|
|
OxSD
Newbie
Offline
Activity: 7
Merit: 0
|
|
Today at 01:55:54 PM |
|
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. |
|
|
|
|
Feron
Jr. Member
Online
Activity: 55
Merit: 1
|
|
Today at 02:01:49 PM |
|
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
|
|
|
|
|
kTimesG
Member
Offline
Activity: 108
Merit: 24
|
|
Today at 02:13:09 PM |
|
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. 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. |
|
|
|
|
nomachine
Member
Offline
Activity: 383
Merit: 21
|
|
Today at 03:04:03 PM |
|
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. |
|
|
|
|
|
dextronomous
|
|
Today at 03:23:31 PM |
|
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.
|
|
|
|
|
nomachine
Member
Offline
Activity: 383
Merit: 21
|
|
Today at 03:39:56 PM |
|
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.  Are you going to make a tutorial for n00bs? Sure. And a telegram channel for support. |
|
|
|
|
|
albert0bsd
|
|
Today at 04:41:31 PM |
|
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). |
|
|
|
|
Woz2000
Jr. Member
Offline
Activity: 76
Merit: 2
|
|
Today at 04:56:23 PM |
|
I want 24 hour live support /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. Are you going to make a tutorial for n00bs? Sure. And a telegram channel for support. |
|
|
|
|
CY4NiDE
Jr. Member
Offline
Activity: 44
Merit: 10
|
|
Today at 07:37:05 PM |
|
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.
|
1CY4NiDEaNXfhZ3ndgC2M2sPnrkRhAZhmS
|
|
|
|
