Changes

The Nintendo 3DS utilizes a similar title-based organization as seen in the Wii and DSi platforms. The same [http://nus.cdn.c.shop.nintendowifi.net/ccs/download/ update server] is being used as was with the DSi, however a new common key has been introduced. The update/shop servers must be accessed via SSLv3.(For curl, the --sslv3 option must be used otherwise connecting will fail)

The Nintendo 3DS utilizes a similar title-based organization as seen in the Wii and DSi platforms. The same [http://nus.cdn.c.shop.nintendowifi.net/ccs/download/ update server] is being used as was with the DSi, however a new common key has been introduced. When using SSL, the update/shop servers must be accessed via SSLv3.

The organization of Title IDs has not been documented fully yet. It's unknown how regions are determined in titleids if at all though there does appear to be evidence that the regions are sequential, similar to how Wii System Menu Updates are ordered: JPN USA EUR KOR and CHN (introduced with the DSi). 3DS has one additional region: TWN.

The organization of Title IDs has not been documented fully yet. Region info isn't stored in titleids however there does appear to be evidence that the regions are sequential, similar to how Wii System Menu Updates are ordered: JPN USA EUR KOR and CHN (introduced with the DSi). 3DS has one additional region: TWN.

The 3DS retrieves system tickets with SOAP request GetSystemCommonETicket, instead of directly downloading the cetk with HTTPS. The cetk is still accessible via HTTP, though 3DS doesn't use direct HTTP for this.

The 3DS retrieves system tickets with SOAP request GetSystemCommonETicket, instead of directly downloading the cetk with HTTPS. The cetk is still accessible via HTTP, though 3DS doesn't use direct HTTP for this.