Bitcoin Forum
June 26, 2024, 08:02:19 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 [4]  All
  Print  
Author Topic: New transaction accelerator on the market - mempool.space  (Read 916 times)
xixou
Member
**
Offline Offline

Activity: 152
Merit: 11


View Profile
June 14, 2024, 04:24:50 PM
 #61

-snip-
Thanks for your help but this is too complicated for me.
I use bitcoin core QT.
You can also (temporarily) set mempoolfullrbf=1 option to let your node accept replacement to transactions without opt-in rbf flag.
Sign the transaction LoyceV provided you (output checks out), then broadcast it to your node's mempool.

Follow these simple steps:
  • Go to "Settings->Options...", click "Open Configuration File" and your 'bitcoin.conf' file should open with your text editor.
  • In your config file, type: mempoolfullrbf=1 in a new line and save the changes, then close the text editor.
  • Close Bitcoin Core, wait for it to properly close, then launch it again.
  • Once running, Open Core's console in "Window->Console", make sure that the correct wallet is selected in the console's drop-down menu;
    In that console window, type the command: signrawtransactionwithwallet "unsigned_raw_transaction" to sign the (unsigned_raw_transaction) LoyceV's transaction above.
  • Copy the resulting signed raw transaction hex and use the command: sendrawtransaction "signed_raw_transaction" to broadcast it to your node and relay it to your peers.

Once done, you may disable the 'fullrbf' setting if you do not want to use it.

Ok I used
# Accept transaction replace-by-fee without requiring replaceability
# signaling (default: 0)
mempoolfullrbf=1

close the tool and opened again, wen't in console, but got this error:

signrawtransactionwithwallet "42888c7b1540f8d5b9e074d15c2d86d7b03878adf6f173c7316f09910c2dabd9"

TX decode failed. Make sure the tx has at least one input. (code -22)

I selected the good wallet
LoyceV
Legendary
*
Offline Offline

Activity: 3360
Merit: 16915


Thick-Skinned Gang Leader and Golden Feather 2021


View Profile WWW
June 14, 2024, 04:49:03 PM
 #62

signrawtransactionwithwallet "42888c7b1540f8d5b9e074d15c2d86d7b03878adf6f173c7316f09910c2dabd9"
That's the txid (transaction ID). You should use the raw transaction:
Code:
 signrawtransactionwithwallet "01000000010481a776ff31478b8b967e15a9e68f78f4cd06b156a5d12910f72d8885147e95020000001976a914367ca154148ceabbcfc3b6c6167f512bb4f9c23388acfdffffff01b88800000000000017a914e09aa133479cff513578a460c606ba504fd761a68700000000"

xixou
Member
**
Offline Offline

Activity: 152
Merit: 11


View Profile
June 14, 2024, 06:14:32 PM
 #63

signrawtransactionwithwallet "42888c7b1540f8d5b9e074d15c2d86d7b03878adf6f173c7316f09910c2dabd9"
That's the txid (transaction ID). You should use the raw transaction:
Code:
 signrawtransactionwithwallet "01000000010481a776ff31478b8b967e15a9e68f78f4cd06b156a5d12910f72d8885147e95020000001976a914367ca154148ceabbcfc3b6c6167f512bb4f9c23388acfdffffff01b88800000000000017a914e09aa133479cff513578a460c606ba504fd761a68700000000"

Error: Please enter the wallet passphrase with walletpassphrase first.

ok I had to use walletpassphrase and the timeout value, it still ask it though.
It does not seems to pick both command in one line, what to do now?

LoyceV
Legendary
*
Offline Offline

Activity: 3360
Merit: 16915


Thick-Skinned Gang Leader and Golden Feather 2021


View Profile WWW
June 14, 2024, 06:55:27 PM
 #64

It does not seems to pick both command in one line, what to do now?
First use the wallet passphrase with a timeout (say 600 seconds), then sign the transaction (on the next line).

xixou
Member
**
Offline Offline

Activity: 152
Merit: 11


View Profile
June 15, 2024, 05:09:59 AM
 #65

It does not seems to pick both command in one line, what to do now?
First use the wallet passphrase with a timeout (say 600 seconds), then sign the transaction (on the next line).

ok, completed:
b30c00",
  "complete": true
}


ok so next step:
Copy the resulting signed raw transaction hex and use the command: sendrawtransaction "signed_raw_transaction" to broadcast it to your node and relay it to your peers.

ok done, what's next?
LoyceV
Legendary
*
Offline Offline

Activity: 3360
Merit: 16915


Thick-Skinned Gang Leader and Golden Feather 2021


View Profile WWW
June 15, 2024, 05:44:00 AM
 #66

Copy the resulting signed raw transaction hex and use the command: sendrawtransaction "signed_raw_transaction" to broadcast it to your node and relay it to your peers.

ok done, what's next?
It's not showing up on mempool.space yet, so the broadcast didn't work. Try to broadcast the signed transaction through coinb.in.

xixou
Member
**
Offline Offline

Activity: 152
Merit: 11


View Profile
June 15, 2024, 06:32:53 AM
 #67

Copy the resulting signed raw transaction hex and use the command: sendrawtransaction "signed_raw_transaction" to broadcast it to your node and relay it to your peers.

ok done, what's next?
It's not showing up on mempool.space yet, so the broadcast didn't work. Try to broadcast the signed transaction through coinb.in.

Could you help me as well how to enter the data on coinb.in?

Thank you for your help so far.
nc50lc
Legendary
*
Offline Offline

Activity: 2450
Merit: 5735


Self-proclaimed Genius


View Profile
June 15, 2024, 06:54:39 AM
 #68

ok done, what's next?
What's the result when you used sendrawtransaction command?
If it's success (txid) but not propagating, your peers may still have your old transaction and don't support "fullrbf" so they're rejecting it.
One solution is to use addnode command to connect to peers that is known to support fullrbf
like the ones listed here: petertodd.org/2023/why-you-should-run-mempoolfullrbf#full-rbf-peering

Another simple solution is to broadcast it to nodes that support it.
AFAIK, Blockstream supports fullrbf so try to broadcast the signed raw transaction there: blockstream.info/tx/push

You may also share the signed raw transaction so others can try to broadcast it to their node. (there's no difference in privacy since your original transaction is already known)
Use [code][/code] tags to preserve its formatting.

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
xixou
Member
**
Offline Offline

Activity: 152
Merit: 11


View Profile
June 15, 2024, 12:39:36 PM
 #69

ok done, what's next?
What's the result when you used sendrawtransaction command?
If it's success (txid) but not propagating, your peers may still have your old transaction and don't support "fullrbf" so they're rejecting it.
One solution is to use addnode command to connect to peers that is known to support fullrbf
like the ones listed here: petertodd.org/2023/why-you-should-run-mempoolfullrbf#full-rbf-peering

Another simple solution is to broadcast it to nodes that support it.
AFAIK, Blockstream supports fullrbf so try to broadcast the signed raw transaction there: blockstream.info/tx/push

You may also share the signed raw transaction so others can try to broadcast it to their node. (there's no difference in privacy since your original transaction is already known)
Use [code][/code] tags to preserve its formatting.

ok I got this after putting the signed:

https://blockstream.info/tx/42888c7b1540f8d5b9e074d15c2d86d7b03878adf6f173c7316f09910c2dabd9
LoyceV
Legendary
*
Offline Offline

Activity: 3360
Merit: 16915


Thick-Skinned Gang Leader and Golden Feather 2021


View Profile WWW
June 15, 2024, 05:26:46 PM
 #70

ok I got this after putting the signed:
That's the same transaction you posted in March. You didn't sign and broadcast a new one.

nc50lc
Legendary
*
Offline Offline

Activity: 2450
Merit: 5735


Self-proclaimed Genius


View Profile
June 16, 2024, 06:42:14 AM
 #71

-snip-
ok I got this after putting the signed:
It should be the new signed raw transaction, the result of the signrawtransactionwithwallet command in your previous "ok, completed" reply.

If you haven't kept a copy of it: within 2 minutes after using; walletpassphrase "your_passphrase" 120
Use:
That's the txid (transaction ID). You should use the raw transaction:
Code:
 signrawtransactionwithwallet "01000000010481a776ff31478b8b967e15a9e68f78f4cd06b156a5d12910f72d8885147e95020000001976a914367ca154148ceabbcfc3b6c6167f512bb4f9c23388acfdffffff01b88800000000000017a914e09aa133479cff513578a460c606ba504fd761a68700000000"

Take note that LoyceV put the same output in that smaller transaction that could "replace" your old unconfirmed 1sat/vB transaction
Use that exact command in the code if you're still willing to send a smaller amount of 35,000sat to 3NAcXNafRsDDNqfzxMmd7qARswfob1e1xL.
If everything's fine, broadcast the result.

BTW, we've been derailing this topic about mempool.space's accelerator.
It's best to start a new topic in 'Bitcoin Technical Support' board where this fits and for better visibility.

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
Pages: « 1 2 3 [4]  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!