|
Interesting, after 5 months, I received an email from mempool telling I have access to their accelererator.
I was able to pay (google pay) their accelerator and finally got my transaction validated within 30 minutes.
Big lesson learned on this one.
|
|
|
|
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-peeringAnother 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/pushYou 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 |
|
|
|
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. |
|
|
|
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? |
|
|
|
signrawtransactionwithwallet "42888c7b1540f8d5b9e074d15c2d86d7b03878adf6f173c7316f09910c2dabd9" That's the txid (transaction ID). You should use the raw transaction: 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? |
|
|
|
-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 |
|
|
|
Thanks for your help but this is too complicated for me. Export private key, import it into Electrum, click "Tools > Load transaction", sign it, broadcast it. Or just convince Bitcoin Core to drop your transaction. Maybe upgrade to the latest version first, I don't know if that would help. Broadcasting won't help as the fee is too low. I just tried latest Bitcoin Core 27.0, option to cancel the transaction is still grayed out (wallet is synced). https://zupimages.net/up/24/24/t852.png |
|
|
|
My transaction is still in mempool for 3 months now ... I assume you're talking about this transaction: 42888c7b1540f8d5b9e074d15c2d86d7b03878adf6f173c7316f09910c2dabd9. Why is it not getting out of the mempool? There is no "one mempool". Anyone can keep that transaction as long as it's valid. Easy fix: move one of the inputs. For example, (check and if you like it) sign this transaction: 01000000010481a776ff31478b8b967e15a9e68f78f4cd06b156a5d12910f72d8885147e95020000001976a914367ca154148ceabbcfc3b6c6167f512bb4f9c23388acfdffffff01b88800000000000017a914e09aa133479cff513578a460c606ba504fd761a68700000000 This takes your smallest input, adds a higher fee, and sends it to your destination address. I used coinb.in to create this unsigned transaction. Once this is confirmed, your months-old transaction is no longer valid. Thanks for your help but this is too complicated for me. |
|
|
|
|
My transaction is still in mempool for 3 months now ...
Why is it not getting out of the mempool?
|
|
|
|
|
I made the payment to empty my wallet, this is why it is at 0 At the moment.
It was not the case before of course.
|
|
|
|
|
Could it be that the delete transaction can only be done if you still have BTC in you wallet?
I get 0 for now.
|
|
|
|
I still see
You are currently on the waitlist. You will get notified once you are granted access.
Do you know how much time it takes to get access to the accelerator?
I have set a way to low fee and turned off RBF ... What a mess, there is no confirmation after 1 month ...
If 1 month already passed, most node already drop your transaction from it's node. Depending on which wallet software you use, you can "delete" that unconfirmed transaction and create new ones with better fee rate. I use bitcoin core QT. I do not see delete transaction when right clicking on it. (abandon transaction and increase fee (RBF was off) are grayed out) Transaction is here: https://mempool.space/tx/42888c7b1540f8d5b9e074d15c2d86d7b03878adf6f173c7316f09910c2dabd9If I delete, will my sat be back in the wallet? |
|
|
|
|
I still see
You are currently on the waitlist. You will get notified once you are granted access.
Do you know how much time it takes to get access to the accelerator?
I have set a way to low fee and turned off RBF ... What a mess, there is no confirmation after 1 month ...
|
|
|
|
|
weird, the miner for the kawpow says:
kawpowminer - GPU ProgPOW(0.9.3) miner for Zing
Well, ...
C:\mining\miners\kapow>kawpowminer.exe --help
kawpowminer 1.1.3+commit.d8f61789
Build: windows/release/msvc
kawpowminer - GPU ProgPOW(0.9.3) miner for Zing
minimal usage : kawpowminer [DEVICES_TYPE] [OPTIONS] -P... [-P...]
Devices type options :
By default kawpowminer will try to use all devices types
it can detect. Optionally you can limit this behavior
setting either of the following options
-G,--opencl Mine/Benchmark using OpenCL only
-U,--cuda Mine/Benchmark using CUDA only
Connection options :
-P,--pool Stratum pool or http (getWork) connection as URL
scheme://[user[.workername][:password]@]hostname:port[/...]
For an explication and some samples about
how to fill in this value please use
kawpowminer --help-ext con
Common Options :
-h,--help Displays this help text and exits
-H,--help-ext TEXT {'con','test',cl,cu,api,'misc','env'}
Display help text about one of these contexts:
'con' Connections and their definitions
'test' Benchmark/Simulation options
'cl' Extended OpenCL options
'cu' Extended CUDA options
'api' API and Http monitoring interface
'misc' Other miscellaneous options
'env' Using environment variables
-V,--version Show program version and exits
|
|
|
|
no, i told you i instantly received the sin. BTW, is there a cpu miner for the x25x? |
|
|
|
|
Cool, I could easily send my SUQA from my full node wallet to the new Sinovate full node wallet ^^
Instant transfert.
|
|
|
|
I can confirm that this version is even better than CryptoDredge. The only thing that one instance of the program is working with only one GPU. It is not so convenient to use it on multi GPU configurations. It perfectly runs fine with one instance for 3 Pascal GPU under Win10. |
|
|
|
|
Works great with Pascal version.
|
|
|
|
|
Sad, only 1 vites coin per block found .. (solo mining)
|
|
|
|
Where can we get info on what MTP is,aisde the fact that it will take more GB on the HDD?
Is it 10 Gb of system ram or GPU ram?
Will that works with 3 GBytes (gtx 1060)?
https://github.com/zcoinofficial/ccminer says: "mtp requires 4Gb of vram, hence cards with less than 4.5Gb of vram won't work. while running, ccminer will also use around 5.5Gb of ram." I've tested the miner on a GTX 960 4GB, and it didn't work, as expected. GTX 1060 6GB and GTX 1070 8GB were fine, though slower than expected, both around 100 kh/s. ok, not for me then, too bad. |
|
|
|
|
Show Posts
