Onchain Registries
DevStation keeps the records that matter onchain. Two registry contracts back the app, so your deployment history and contract labels are auditable and portable rather than locked in a private database.
ProjectRegistry
Records every contract deployed through DevStation against the deploying wallet, and keeps a global counter of total deployments. The Projects page reads your deployments back from it, scoped to your connected wallet. The Overview reads the global counter for the total contracts and total users stats.
function recordDeployment( address contractAddress, string calldata templateId, string calldata projectName, string calldata network, string calldata txHash) external; function getDeployments(address deployer) external view returns (Deployment[] memory); uint256 public totalDeployments;ContractLabelRegistry
Stores human-readable labels for contracts, with a source (auto, community, or verified) and the submitter. Routebook and the Label Registry page read from it.
Registry writes use an explicit gas limit. QIE's gas estimator can under-report the gas a storage-writing call needs, so DevStation pins a safe limit to keep these transactions from running out of gas. At QIE's gas price this costs a negligible fraction of a QIE.