Topic: What is the correct P2SH coinbase flag? (Read 1678 times)
Our blocks now have the /P2SH/ in the coinbase. The problem was the custom coinbasing in PoolServerJ to embed messages [we tag our blocks with "BTC Guild"].
Just looked into it on the BTC Guild side. I've upgraded the bitcoind, but it looks like PoolServerJ's internal workmaker is the problem (Bitlc also uses PoolServerJ). It's making its own work and not including /P2SH/. I'll have to get in touch with shadders to find out how to make it carry forward (I'm not the best with Java).
getmemorypool now returns a field
"coinbaseflags" : "062f503253482f",
which is data that can just be stuck on the end of the coinbase. P2Pool uses it, poolserverj should too.
In the meantime, people who want to vote for P2SH could mine with p2pool! 
The wiki seems to be down at the moment but I thought that in order to show support for P2SH the string "/P2SH/" should be included in a blocks coinbase. However BTC Guild, Bitlc.net and a few other pools are voting for P2SH but their blocks do not contain this string.
Hex encoding of "/P2SH/" is "2f503253482f".
Block 166309 by bitcoin.cz contains it.
Block 166315 by BTC Guild and 166282 by Bitlc do not.
Has this changed, what is the correct byte sequence?
Hex encoding of "/P2SH/" is "2f503253482f".
Block 166309 by bitcoin.cz contains it.
Block 166315 by BTC Guild and 166282 by Bitlc do not.
Has this changed, what is the correct byte sequence?
Just looked into it on the BTC Guild side. I've upgraded the bitcoind, but it looks like PoolServerJ's internal workmaker is the problem (Bitlc also uses PoolServerJ). It's making its own work and not including /P2SH/. I'll have to get in touch with shadders to find out how to make it carry forward (I'm not the best with Java).
The wiki seems to be down at the moment but I thought that in order to show support for P2SH the string "/P2SH/" should be included in a blocks coinbase. However BTC Guild, Bitlc.net and a few other pools are voting for P2SH but their blocks do not contain this string.
Hex encoding of "/P2SH/" is "2f503253482f".
Block 166309 by bitcoin.cz contains it.
Block 166315 by BTC Guild and 166282 by Bitlc do not.
Has this changed, what is the correct byte sequence?
Hex encoding of "/P2SH/" is "2f503253482f".
Block 166309 by bitcoin.cz contains it.
Block 166315 by BTC Guild and 166282 by Bitlc do not.
Has this changed, what is the correct byte sequence?
Jump to: