Debug Log

[LFC_Bitcoin]

Everything seems to be working fine on my node but I noticed this -


2019-06-25T19:39:26Z GUI:   OpenType support missing for "MS Shell Dlg 2", script 11
2019-06-25T19:39:26Z GUI:   OpenType support missing for "Arial", script 11​
2019-06-25T19:39:26Z GUI:   OpenType support missing for "MS UI Gothic", script 11​
2019-06-25T19:39:26Z GUI:   OpenType support missing for "SimSun", script 11​
2019-06-25T19:39:26Z GUI:   OpenType support missing for "MS Shell Dlg 2", script 16​
2019-06-25T19:39:26Z GUI:   OpenType support missing for "Arial", script 16​
2019-06-25T19:39:26Z GUI:   OpenType support missing for "MS UI Gothic", script 16​
2019-06-25T19:39:26Z GUI:   OpenType support missing for "SimSun", script 16​
2019-06-25T19:40:17Z GUI: Data set on unsupported clipboard mode. QMimeData object will be deleted.​
2019-06-25T19:40:36Z New outbound peer connected: version: 70015, blocks=582413, peer=8​
2019-06-25T19:41:24Z GUI: Data set on unsupported clipboard mode. QMimeData object will be deleted.​
2019-06-25T19:41:48Z GUI: Data set on unsupported clipboard mode. QMimeData object will be deleted.​
2019-06-25T19:42:09Z GUI: Data set on unsupported clipboard mode. QMimeData object will be deleted.​
2019-06-25T19:42:35Z GUI: Data set on unsupported clipboard mode. QMimeData object will be deleted.​
2019-06-25T19:43:02Z GUI: Data set on unsupported clipboard mode. QMimeData object will be deleted.​
2019-06-25T19:43:16Z GUI: Data set on unsupported clipboard mode. QMimeData object will be deleted.​
2019-06-25T19:43:33Z GUI: Data set on unsupported clipboard mode. QMimeData object will be deleted.​
2019-06-25T19:43:56Z GUI: Data set on unsupported clipboard mode. QMimeData object will be deleted.​
2019-06-25T19:44:16Z GUI: Data set on unsupported clipboard mode. QMimeData object will be deleted.​
2019-06-25T19:44:39Z GUI: Data set on unsupported clipboard mode. QMimeData object will be deleted.​
2019-06-25T19:45:08Z GUI: Data set on unsupported clipboard mode. QMimeData object will be deleted.​
2019-06-25T19:45:25Z GUI: Data set on unsupported clipboard mode. QMimeData object will be deleted.



Anybody know what this means?

[1714037560]

1714037560

[1714037560]

1714037560

[jnano]

Looks like random noise from the GUI library (Qt), don't know why it's shown.

These are Windows fonts. Are you not on Windows?

And I don't know why it would care about the contents of the clipboard.

[LFC_Bitcoin]

Looks like random noise from the GUI library (Qt), don't know why it's shown.

These are Windows fonts. Are you not on Windows?

And I don't know why it would care about the contents of the clipboard.

I am on Windows yes.
All new blocks are processing as usual, just never seen that before.

[jnano]

FWIW, in my log the only strange GUI message I see is this, just before quitting:

Code:

GUI: QItemSelectionModel: Selecting when no model has been set will result in a no-op.

Maybe you copied something special into your clipboard, and for some reason Core is trying to interpret it.

[LFC_Bitcoin]

FWIW, in my log the only strange GUI message I see is this, just before quitting:

Code:

GUI: QItemSelectionModel: Selecting when no model has been set will result in a no-op.

Maybe you copied something special into your clipboard, and for some reason Core is trying to interpret it.

Is it anything to be concerned about, in your opinion?

[jnano]

I'm not an authority on Bitcoin Core, but I'd say no reason for concern.
GUI, fonts, and clipboard contents, have nothing to do with the important stuff.

[jackg]

Is this while it's running or when you're shutting it down?

Have you managed to delete fonts or something? These are probably just a hangup with a gcc-cpp compiler thst doesn't know what to do with the error so it just dumps it in the log...

You could try hard drive diagnostics or check your fonts are intact.

[achow101]

These are just messages that come from the Qt library itself and should be harmless.

Do these appear when you do something (e.g. copy something from Bitcoin Core)?

[LFC_Bitcoin]

These are just messages that come from the Qt library itself and should be harmless.

Do these appear when you do something (e.g. copy something from Bitcoin Core)?

OK, I turned my computer off & restarted, it seems to have stopped doing it now but it was sporadically before that. I don’t think I copied anything.

Now I have this -



UpdateTip:.......snip........warning=‘45 of last 100 blocks have unexpected version.’

UpdateTip:.......snip........warning=‘44 of last 100 blocks have unexpected version.’
UpdateTip:.......snip........warning=‘44 of last 100 blocks have unexpected version.’

UpdateTip:.......snip........warning=‘44 of last 100 blocks have unexpected version.’
UpdateTip:.......snip........warning=‘44 of last 100 blocks have unexpected version.’
UpdateTip:.......snip........warning=‘44 of last 100 blocks have unexpected version.’
UpdateTip:.......snip........warning=‘44 of last 100 blocks have unexpected version.’

(Didn’t want to copy anything to clipboard so had to type out.
I trust this is normal? I’ve seen similar before, miners messing about?

Looking for somebody to put my mind at ease so I can stop being paranoid. achow, a reply would be awesome

[bob123]

This just means some miner have mined blocks with a version number which is unknown to core.

Most miner simply change the version number if they have tried out all possible nonce's when searching for a block.
Since this is still accepted by the network and changing this field is faster than building a new block (merkle tree, etc.), that's their favored way to change the resulting hash and to not lose time when mining.

You can ignore this, without worrying  

[LFC_Bitcoin]

This just means some miner have mined blocks with a version number which is unknown to core.

Most miner simply change the version number if they have tried out all possible nonce's when searching for a block.
Since this is still accepted by the network and changing this field is faster than building a new block (merkle tree, etc.), that's their favored way to change the resulting hash and to not lose time when mining.

You can ignore this, without worrying  

I’ve had that on a lot of blocks since around 11pm last night (GMT).
Definitely OK, Bob?

[bob123]

It is definitely fine.

Unknown block versions are either voting for / signaling a soft-/hardfork - which is probably not the case because i am not aware of any proposed fork - or miner use this field to generate a different hash for their block.

Well.. it might be possible that they are also just messing around with it for fun.. but i doubt that.


But since this basically only says that core does not recognize the block version (still valid blocks), there is nothing to worry about.

[jackg]

See what pool it comes from? My guess would be viabtc since they like the bitcoin unlimited blocks so are voting for it...

[achow101]

OK, I turned my computer off & restarted, it seems to have stopped doing it now but it was sporadically before that. I don’t think I copied anything.

Now I have this -



UpdateTip:.......snip........warning=‘45 of last 100 blocks have unexpected version.’

UpdateTip:.......snip........warning=‘44 of last 100 blocks have unexpected version.’
UpdateTip:.......snip........warning=‘44 of last 100 blocks have unexpected version.’

UpdateTip:.......snip........warning=‘44 of last 100 blocks have unexpected version.’
UpdateTip:.......snip........warning=‘44 of last 100 blocks have unexpected version.’
UpdateTip:.......snip........warning=‘44 of last 100 blocks have unexpected version.’
UpdateTip:.......snip........warning=‘44 of last 100 blocks have unexpected version.’

(Didn’t want to copy anything to clipboard so had to type out.
I trust this is normal? I’ve seen similar before, miners messing about?

Looking for somebody to put my mind at ease so I can stop being paranoid. achow, a reply would be awesome

This is a completely benign warning that is being triggered by Asicboost. Asicboost uses the block version field as a nonce which causes a false positive in Bitcoin Core's soft fork detection logic. For Bitcoin Core 0.18, this warning has been disabled because it is triggered too often and is just noise.

[jnano]

"warning='## of last 100 blocks have unexpected version'" is still shown in v0.18.0.
I'm seeing it since height=582383.

[achow101]

"warning='## of last 100 blocks have unexpected version'" is still shown in v0.18.0.
I'm seeing it since height=582383.

Oh, the warning that was removed was the Warning: Unknown block versions being mined! It's possible unknown rules are in effect warning, not the unexpected version one. Whoops.

[LFC_Bitcoin]

"warning='## of last 100 blocks have unexpected version'" is still shown in v0.18.0.
I'm seeing it since height=582383.

Oh, the warning that was removed was the Warning: Unknown block versions being mined! It's possible unknown rules are in effect warning, not the unexpected version one. Whoops.

So the ‘unexpected version’ one is still harmless, yes?

[bob123]

So the ‘unexpected version’ one is still harmless, yes?

Yes, those 2 different messages have the same source.
Just one has been removed and the other not (don't know why though).

[DeathAngel]

So the ‘unexpected version’ one is still harmless, yes?

Yes, those 2 different messages have the same source.
Just one has been removed and the other not (don't know why though).

I’m keen to know if this is safe too. I’m also seeing since 25/6/19 - -

warning= ## of last 100 blocks have unexpected version

Core & blockchain tech expert achow101, do you have a comment on this?

[jackg]

I’m keen to know if this is safe too. I’m also seeing since 25/6/19 - -

warning= ## of last 100 blocks have unexpected version

Core & blockchain tech expert achow101, do you have a comment on this?

He's already said it's safe and caused by asicboost where the nonce is used in generating the hash using the version (as it's less hashing afaik) instead of using the coinbase.

I assume the warning message will be removed at some point but it can be ignored, while it isn't.

It's not much of a concern anyway as nodes should be following the longest chain...