Post by nodemaster » Fri Aug 12, 2011 8:56 pm

Luke-Jr wrote: 1) It takes up extra space in the coinbase -- we only have 100 bytes, each merkle takes up 33; that gives us room for 3 aux chains at most. Adding 4 more bytes for a header kills any hope of ever doing 3 aux chains. (in fact, it would be nice if the space requirements were reduced...)

Luke-Jr wrote: 2) Since the code only allows the header once, you can't have two aux chains.

Luke-Jr wrote: 3) The header can occur accidentally in other coinbase data.

Luke-Jr wrote: Why is it so hard to simply disallow a master-chain block from "vouching for" more than one block in each aux chain? :/

Thank you four your feedback. it is much appreciated!Yeah, that sounds reasonable. In fact I guess it would be desirable to even support more AUX chainsI would really like to see more than one blockchain supported. There are a couple of blockchains in the make and IMHO it won't make sense to only support BTC and NMC.I'm not a C programmer, but I understand that this could lead to unwanted problems. Any idea on how to find a "coinbase proof header"?Mhmm, If I understand it correctly this might be undesirable because it might be (and is common) that you solve several AUX chain blocks and have one master-block vouching for them, right? This problem would only be solved if the difficulty of both blockchains draw levels.