Bitcoin Forum

......

This is mostly referred to as customization of fee and there are many bitcoin wallets that support such feature. Wallet like electrum, BlueWallet, sparrow and even some closed source wallets allow you to customize your fee. Although some wallet settings or let’s say nodes or servers you’re connected to might outrightly fail to broadcast your transaction because of low transaction fee and you could end up getting error messages

Wallets like Bitcoin Core can let you set below 1 sat/vbyte as the fee rate. You can even use 0 sat as the fee on Bitcoin Core. But the SPV wallets that I have used before that makes you to customize fee will not allow you to use below 1 sat/vbyte.

0 sat vB fee rate won't be propagated. You need at least 1 sat vB to get into mempool of other nodes.

A miner can insert a 0 sat vB transaction in a Block, but you can't, even using bitcoin core 

More info here

I've never tried to send 0 sat/B on Bitcoin core, but I don't think it's allowed, as I vaguely remember trying that.

Why would you want to send at 0 sat/b even though you know your transaction will never be accepted? 1 sat/B has a chance of being accepted, although it may take many days, due to the current state of the mempool.

How nice it was to send transactions paying 1 sat/B fee... anyway, you can still use Bitcoin Core even if your storage disk is smaller than the current blockchain size when opening Bitcoin Core for the first time, in the configuration, you will be asked if you want to prune the blockchain to X size... Ex: 2gb, 4 gb, then it is downloaded to 4gb (or whatever size you define) and the old blocks are deleted... You lose some resources, but they are not absolutely important.

Do not mind me for this correction. It supposed to be sat/vB and not sat vB.

I know that unless someone is a miner (that is able to mine a block like mining pool) or knows a miner (that is able to mine a block like mining pool) that can help him include the transaction into a block, the node runner has no other option because most miners set it at 1 sat/vbyte. I suppose to include that.

No even having any chance for now. Many nodes can also purge the transaction out of mempool. The purging right now is above 5 sat/vbyte, which means most nodes are not accepting 1 sat/vbyte transaction right now.

There is nothing better than to download the full blockchain for easy wallet recovery. Prune node has it disadvantages.

This is the minimum now. 6 sat v/B

Op you are actually referring to fee customization most wallets now have that function since most users are aware that it's possible to choose the fees you wish to use. Customizing Bitcoin fees is something that should be done with fine understanding of how the block chain works. Meaning you should be able to check the Mempool with necessary tools to know the level of conjestion at the time you intend on broadcasting your transaction.

As usual, the higher the fees you make use of the faster your transaction is confirmed and added to the next block. However when trying to pick the best fee for your transaction you should take note of the minimal fee at the time of broadcast. This is because if your fees fall below the minimal fee , nodes will simply drop your transaction.

You must understands basics about Bitcoin transactions and transaction fee.

Transaction fee depends on two main factors: transaction size, and fee rate.

Transaction size depends on your inputs, transaction address, transaction type, ...
Fee rate is what you set when broadcasting your transaction. Fee rate is in satoshi/ byte or satoshi/ vbyte.

If you understand, you will see there will be nothing to be set during broadcasting a transaction process, relates to $. It means there is no wallet that can allow you to set your transaction fee in $.

Most people will never do that. If you have one wallet, it will always be synced on your pruned node.

What are you trying to do? You jump from wanting to create a transaction that can only exist locally in your wallet to importing private keys. What's the goal here?

Hmm, that error... could it be "Only legacy wallets are supported by this command"? Because, there's nothing else exactly like that.

If so; Bitcoin Core's new "descriptor wallet" doesn't allow importprivkey command, use importdescriptor instead.
Instead, create a "pkh" descriptor with that uncompressed WIF private key, get its "checksum", then import it.

Example:
Create a descriptor:

Get its checksum:
Result: "checksum": "pcxrjydy",

Import it, append the checksum:

You can also import "pk()" descripto if you think you own P2PK outputs.

Use your signature space to include this to your posts instead of posting it at the bottom of each of your topics.
To get there, click "PROFILE->Forum Profile Information".

Newbies don't have signature space if I am not wrong, it is only available from Jr. Members or above.

Sorry for the off-topic. ;)