1) if an outdated client receives a transaction with an unknown version, it invalidates this transaction?
2) what happens if 99.99% of the network already uses the new version and mine is outdated?
3) there is a website where I can see the percentage of version 3 blocks on the network?

interesting...
has now launched the rc3 that corrects this error ...

Bitcoin-qt 0.10.1 rc2
I found 1 bug in fee calculation and in help text...

I was using the client when I came across texts not translated in the part of custom rate.
When I put the mouse on "per kilobyte", a popup appears with a text: (...) while "at least" pays (...)
And in "total at leat": (...) while "total at least" pays (...)
I think both should be the same text ...

And the bug...
The explanatory text says that the rate for 1000 satoshis by kb and the transaction has 250 bytes, will pay 250 satoshis.
But that's not what I see

  maybe

site still off??

just duplicate the part:

01                < Number of inputs
5d475fab463fee15d6d32b33151748cbc4eb7c8f06166f50ad77224ddc07bbc8  < Input transaction id
00000000          < Vout
00                < scriptSig length*
ffffffff          < Sequence number

why more op_return?

i got it
but would be nice a message saying "all good" ^^

ok
i give up
I downloaded the python and ran the script
it shows the data about my transactions ...
and show "compare" (ln 51)
and stops ...

i dont want to download the python

there how to run this script online?

i made a mistake
the pubkey count is in hex
so is 21, not 33

52 21 035b641b667aded965c2f7c2be17c736e6d960e3316a5c2d46ccacf6ff9fa87edd 21 02b94370211403cac9378dfbc414df44842523e120e5301d3d593a370cf6b9fb38 21 0260b26aa4d0e921f322bcad0f04c1bcd475a70e4553f3bda007eb1534081ead46 53 ae

in the command listaddressgroupings, no
in gui, yes

the unknown address is an obscured address...
but why the program ignored the address specified for change?
i think its because he does not recognize multisig in the field change...

the first byte, 52, is the M (52-50=2) and the second last byte, 53, is tne N (53-50=3)

i have all the Keys of the multisig used...

the redeem script format:

the byte 50 + required Keys
pubkey1 count
pubkey1
(...)
byte 50 + pubkey count
byte ae

example (2 of 3)
52 21 035b641b667aded965c2f7c2be17c736e6d960e3316a5c2d46ccacf6ff9fa87edd 21 02b94370211403cac9378dfbc414df44842523e120e5301d3d593a370cf6b9fb38 21 0260b26aa4d0e921f322bcad0f04c1bcd475a70e4553f3bda007eb1534081ead46 53 ae

I'm using bitcoin-qt 0:10
I made a purchase of a game on a website ...
When I made the transaction, I specified my change  address ...
for the record, the address is multisig

1) the program said that the address is unknown (the address is on my list of receiving address)
2) he sent the change to an address that is not on my list but the program says it's my

only with a redeem script...

when i send coins with advanced interface in qt 0.10, he says the mining fee is +/- 2.116 satoshis per input
i pay 2044 satoshis by 966 bytes..
the fee are reduced??
it was 100 micro??

please implement the block version 3