Solidity on Kortana

There is no Kortana Solidity dialect

Kortana runs an EVM-compatible engine, the KEVM, with 0x addresses and standard Ethereum semantics. Solidity written for Ethereum compiles and behaves the same way here. Studio does not invent a dialect and does not add nonstandard pragmas.

The compiler

Studio runs the official solc-js build in a Web Worker on your machine. The compiler binary is fetched from the official Solidity CDN and pinned to an exact version per project, recorded in the project file so a later default change cannot silently alter your output.

Your source never leaves the browser to be compiled.

Imports

There is no package manager behind the browser, so imports resolve only against files in your project. The bundled templates are deliberately self-contained for that reason. To use a library, add its source to your project.

Interoperating with Quorlin

Both engines settle on the same chain and can call each other in either direction. Quorlin adopted Ethereum conventions rather than inventing its own: function selectors are keccak256("name(type,type)")[0..4], event topics are keccak256("Event(type,type)"), and map storage is keccak256(key ‖ slot). A Quorlin contract is an ordinary ABI target from Solidity, and vice versa.