Extraordinary claims require...
No, no one is asking for extraordinary evidence here. You've developed something most people with a Sky3DS would want, with help from the community (although considering someone as knowledgeable and capable as yourself, I have no idea what knowledge you gained from making this thread), so why wouldn't you share that exploit?
All I see is attention seeking. You've made a thread you didn't need, and now you won't share something in the thread because no one believed you. Now it's our fault of course. Bravo, really. This thread would have had 4 replies tops if you had a green or blue avatar, but I'm sure you know that
I asked in the first place as I thought I would get some good knowledge about where to find the code for the SIG's and cartridge encryption, I thought it would save me time...
It clearly didn't as I only got two people giving me anything usable.
I decided to take it to the next level myself and look at the 3DBrew site... here I found good info about where the SIG's would be (it tells you exactly what to look for).
I found once I had patched the SIG function (using one single line of code to change a 16bit thumb instruction from MOV R0,0 to MOV r0,1) that the rest of the e-shop content was exactly the same as cartridge data.
The only thing to do next was get the Sky3DS card to work.
I did this by waiting for the MAGIC missing 16 bytes nobody knows about in the template file to show up in memory when I used OOT. I then knew exactly where to stop the code and let the 3DS generate the 16 bytes needed for e-shop game and add them to the template file.
I then used one extra patch (a 16bit NOP instruction) to make the the kernel go in the right direction when it decided it was an e-shop game or a cartridge.
All sounds pretty easy, that's because it was!