Electrum uses base43 encoding for their QR codes. It helps to save the limited space for QR codes and Electrum will decode it when you're using the desktop client to scan the QR code.

If you want to get it in hex format, you can just use this: https://github.com/jacoblyles/base43js. It's the only converter that I'm aware of.

If it still doesn't work, PM me the raw TX and I'll take a look.

item shipped....congrats krog!

b-krogoth----winner

As a general rule... wallets can only report on the data contained within:

- The blockchain
- Their current "mempool"

If the transaction you create is not included in a block that has been added to the blockchain, nor broadcast into the network... then it is highly likely that your wallet will not reflect the "spending" of those coins in it's balance.

However, electrum has the concept of "local" transactions, which are transactions that you have finalised and signed but are not as yet broadcast to the network:



But it will display in your "transaction history" as a "local" transaction:



And show next to the balance as "unconfirmed":



(in other news, I wish I had as much real BTC as test BTC  )

I think you're using your Bitcoin address instead of your ECDSA public key. Go to your Address, Right click and Press Details there should be a public key. If you're unsure of the redemption process, I recommend you to test it out first with a smaller amount to get a better understanding.

1BTC. Remove the seed/wallet associated with the seed in the wallet.
No.

If someone has access to your seeds, they can construct a transaction and spend your funds anytime they want. Your timelocked transaction cannot be in the mempool until it's expiry. This also means that your timelock funds won't be truly bounded to the time unless you:
1) Destroy all traces of private key/seed after creating and saving the transaction.
2) Ensure that no one else can have access to your keys or seeds.


In gist, the only way for you to spend the funds within is only with that nLockTime transaction. The nLocktime only sticks with your specific transaction and not to the funds in your address.

For that reason, I prefer the P2SH method. It ensures that the funds within that address are only spendable at that specific date or block.

That will do but the "execution" is manual (I mean the broadcast after the nLocktime) and saving it locally to your Electrum wallet is a good option if you're using the wallet frequently,
saving it as a local transaction will prevent that wallet from using the specific UTXO used by that transaction; though, not in other instances of your wallet if you have any.

Ah okay, fair enough. nLocktime could suit you as long as you can take care to not lose your receiving address then I guess you can just use Electrum's UI and export your own raw transaction.

If you'd like, you can try exploring OP_CheckLockTimeVerify P2SH addresses. You'll be able to create a scripthash address which will lock your outputs till the block/time. Afterwhich, you can just create and sign your transactions as per usual. Benefit of that is that you can send to whichever address you want in the future and won't be restricted to that address specified in the nLockTime transaction.

See: https://coinb.in/#newTimeLocked for a nice UI to create your nLocktime address. You'll just need to keep the redeem script safe but to be fair, you can generate the redeem script anytime you want, just use the same public key and the same nLockTime date/block.

---

I won't large amount of my funds into any nLockTime transactions. I prefer having some form of control over when to spend most of my coins. Perhaps just a bit locked in there as a fun experiment.

Non-final transactions are not accepted by mempool as it'll allow for cheap mempool flooding. What's your use case for timelocked transactions? Would OP_CLTV work better for you? It's a P2SH address with inputs that is only spendable at certain height/time.

Electrum allows you to set a custom nLocktime but you cannot broadcast the transaction as nodes will not allow it. However, you can save it and send it to whoever you link.

I guess you better read this thread: [Tutorial] Making your crypto inheritible
It covers exactly nLocktime in Electrum for locking funds until certain block.

But you'll have to read the thread further, since somebody talked about mempool not accepting tx too far in future (if I understood correctly).

You mean the nLocktime in the "advanced preview"?
That can only make the transaction unable to be broadcast before the set height or date, not some sort of bitcoin locking function.

Alternatively, you can save the transaction locally using "save" after signing it and broadcast the transaction when the nLocktime passed.