LOCAL transaction not LOCAL

[darxiaomi]

Hi guys i dont post regular here but a few guys can know me from the gambling board or from my local board.

Well the "problem" im facing is the next one.



Why this transaction show as Local when they are not... i mean i receive that ones, they are from the signature campaign so its impossible to be "local".

Is some kind of bug? Or im missing something?

[mcdouglasx]

Maybe you're running a local node and therefore the transactions you receive are being labeled as local, or it's a tagging error on your part or the software's part when you assigned the BTCTalk tag.
Another reason could be that you and the person sending you the payments happen to be using the same node in Electrum, and they somehow identify them as local.

Try switching to another node to see if the tag changes.

[Zaguru12]

Just as said above the “local” means that the transaction is not in the mempool of the Node you’re current connected to but on your wallet file. Connect to a different server and the transaction status might change.

This things most usually happens to unconfirm transactions where the fees are too low and some servers drop them from there mempool.

To switch sever click on the green circle 🟢 at the bottom right corner select choose server automatically and the select a new server, here is a proper guide

[nc50lc]

Why this transaction show as Local when they are not... i mean i receive that ones, they are from the signature campaign so its impossible to be "local".

There's no doubt, it just an issue with the server you're connected to.
I'm certain because I managed to sync a watch-only copy of that wallet and those transactions are showing as confirmed using the public server "electrum.blockstream.info:50002"


(about how I managed create this watch-only wallet, it's in your post history)

[darbitmobilerecovery]

Maybe you're running a local node and therefore the transactions you receive are being labeled as local, or it's a tagging error on your part or the software's part when you assigned the BTCTalk tag.
Another reason could be that you and the person sending you the payments happen to be using the same node in Electrum, and they somehow identify them as local.

Try switching to another node to see if the tag changes.

Just as said above the “local” means that the transaction is not in the mempool of the Node you’re current connected to but on your wallet file. Connect to a different server and the transaction status might change.

This things most usually happens to unconfirm transactions where the fees are too low and some servers drop them from there mempool.

To switch sever click on the green circle 🟢 at the bottom right corner select choose server automatically and the select a new server, here is a proper guide

Why this transaction show as Local when they are not... i mean i receive that ones, they are from the signature campaign so its impossible to be "local".

There's no doubt, it just an issue with the server you're connected to.
I'm certain because I managed to sync a watch-only copy of that wallet and those transactions are showing as confirmed using the public server "electrum.blockstream.info:50002"


(about how I managed create this watch-only wallet, it's in your post history)

Thank you all guys! For the answers and fastest responses.

Im gonna try it when i have time.

Aside of that dont you think Electrum needs to improve that? I mean when i read the "local" i suposes is a real local transaction like for example one we can do for consolidate outputs, so dont you think they have to label it in a diferent way?.

Because is not "local" is "in the same node". Or im wrong?

[hosemary]

Aside of that dont you think Electrum needs to improve that? I mean when i read the "local" i suposes is a real local transaction like for example one we can do for consolidate outputs, so dont you think they have to label it in a diferent way?.

In my opinion, everything is fine.
The term "Local" means that the transaction exists in your wallet file, but the node you have connected to doesn't have it in its mempool or in its copy of the blockchain.

Because is not "local" is "in the same node". Or im wrong?

What do you mean by "in the same node"? Can you please elaborate more?

[darxiaomi]

Aside of that dont you think Electrum needs to improve that? I mean when i read the "local" i suposes is a real local transaction like for example one we can do for consolidate outputs, so dont you think they have to label it in a diferent way?.

In my opinion, everything is fine.
The term "Local" means that the transaction exists in your wallet file, but the node you have connected to doesn't have it in its mempool or in its copy of the blockchain.

Thats the whole point. I cant understand how the transaction can be only in my wallet file when im the receiver of that transaction.

I mean Royse send the payment, that payment pass trought the whole mempool/node etc so how it can be only in my local.

I understand what you said about my node is not seeing it because they dont have it in its mempool, but i always thinked they have to know anyways.

Now the transactions are all confirmed and i dont need to do anything.

Sorry for my bad english i cant point out my real point.

[hosemary]

Thats the whole point. I cant understand how the transaction can be only in my wallet file when im the receiver of that transaction.

You opened your wallet and connected to a server that had that transaction in its mempool. The transaction was saved in the wallet file. You closed your wallet and opened it again. This time you connected to a different server. The new server didn't have that transaction in its mempool and electrum displayed it as local.

[khaled0111]

This time you connected to a different server. The new server didn't have that transaction in its mempool and electrum displayed it as local.

The first transaction that appears in his wallet as "local" was sent about two weeks ago (or even before that).
So how is that possible?
I would understand it if only the most recent transactions (from the last few blocks) shows as local, but not a transaction that has been sent two weeks (or even more) ago! Am I missing something here?

[hosemary]

The first transaction that appears in his wallet as "local" was sent about two weeks ago (or even before that).

You are right. I didn't notice that those transaction had already been confirmed when they were shown as local.
So, I think the issue was that the server didn't have an updated version of the blockchain.

[BitMaxz]

The first transaction that appears in his wallet as "local" was sent about two weeks ago (or even before that).
So how is that possible?
I would understand it if only the most recent transactions (from the last few blocks) shows as local, but not a transaction that has been sent two weeks (or even more) ago! Am I missing something here?

Maybe I think the OP did open the Electrum in a short period of time or just a few seconds and then close it. Electrum is automatically connecting randomly to any server. On the 2nd attempt of opening Electrum, it shows these 3 local transactions because the current server doesn't have this latest block data that contains these transactions. So changing server or reopening Electrum should solve this case. So the 3rd attempt, I guess Electrum should be synced properly unless it connects again to the same server with delayed data.

I think on the 2nd attempt that the owner of that server might be using a Raspberry Pi node; that is why it is delayed a few blocks.

[darxiaomi]

The first transaction that appears in his wallet as "local" was sent about two weeks ago (or even before that).
So how is that possible?
I would understand it if only the most recent transactions (from the last few blocks) shows as local, but not a transaction that has been sent two weeks (or even more) ago! Am I missing something here?

Maybe I think the OP did open the Electrum in a short period of time or just a few seconds and then close it. Electrum is automatically connecting randomly to any server. On the 2nd attempt of opening Electrum, it shows these 3 local transactions because the current server doesn't have this latest block data that contains these transactions. So changing server or reopening Electrum should solve this case. So the 3rd attempt, I guess Electrum should be synced properly unless it connects again to the same server with delayed data.

I think on the 2nd attempt that the owner of that server might be using a Raspberry Pi node; that is why it is delayed a few blocks.

That was my doubt, the transaction was weeks old, and that brings my attention.

Mmmm i left it open a minute for sure, plus i open it several times and plus i do a transaction to see if when the wallet makes a move sending maybe it make it refresh, but nothing happens.

Just after Nc50lc make his post and i enter to see and change the server i see it was all solved. So i didnt did anything.

[pooya87]

When you were seeing the local transactions, if you had clicked on the little circle on bottom right corner of the Electrum window to open the Network window, you should have seen the server you were connected to was out of sync and at least two weeks (4000 blocks) behind.

For example it should have shown something like 800,000 as its block height instead of the same number as other nodes.

You can also find the current block count on any block explorer.

When the server (full node) is out of sync, it obviously doesn't have the block that contains your transaction and is unlikely to have it in its mempool either (possibly just came online after a long period of being offline) to show it as either confirmed or waiting for confirmation (aka unconfirmed in its mempool) respectively; therefore your wallet sets its status as local.

[LoyceV]

You opened your wallet and connected to a server that had that transaction in its mempool. The transaction was saved in the wallet file. You closed your wallet and opened it again. This time you connected to a different server. The new server didn't have that transaction in its mempool and electrum displayed it as local.

It gets weirder: I had a local transaction right after opening my wallet. That transaction didn't exist yet the last time I opened this wallet, and the server I connected to was up to date with it's block height. Manually changing servers didn't change the "local" transaction, but closing and opening my wallet solved it.