What I actually do

Most small-business IT is sold as a package that was designed for somebody else. I specify to what you actually do — how many people, what software, what you cannot afford to lose, and what budget exists.

• Network design and rebuild, wired and wireless
• File servers, NAS and in-house storage
• Backup strategy that survives losing the building, not just the drive
• Hardware and software selection, with the reasoning written down
• Migration planning for new machines or a new office

Diagnosis first. A machine that has been slow for six months and a machine that died on Tuesday are different problems, and the fix for one is a waste of money on the other.

• No-boot, no-display and intermittent-shutdown diagnosis
• Thermal faults — throttling, failed pads and paste, dead fans
• Storage upgrades and data migration, including laptop SSD and NVMe work
• Operating system repair, clean rebuilds and performance recovery
• Custom builds specified for the work they will actually do

The hardware is the easy part. What sinks most mining projects is power, heat, noise and the arithmetic — and those need answering before anything is bought.

• Deployment planning: circuits, power budget, airflow and heat rejection
• ASIC and GPU hardware selection for the target coin and site
• Firmware, tuning and pool configuration
• Monitoring, alerting and uptime — the number that decides earnings
• Honest profitability modelling, including the case for not building
• Diagnosis and rescue of deployments that are already underperforming

On the maths: mining returns depend on power cost, network difficulty and market price, none of which I control and none of which are predictable. I will show you the model and its assumptions. I will not promise you a return, and you should be wary of anyone who does.

Auditing is reading code for what it actually permits, not what the documentation claims. Most of what goes wrong on-chain is not exotic cryptography — it is access control, arithmetic and assumptions that held right up until someone tested them.

• Solidity smart contract review
• Solana program development
• Access control, permissions and privileged-function review
• Written findings ranked by severity, with the reasoning shown
• Re-review after fixes, so the report closes out

Scope honestly: an audit reduces risk, it does not eliminate it, and no auditor can certify code as safe. Anyone who tells you otherwise is selling something. You will get findings, severity, and my reasoning — not a guarantee.

Investigation of how networks and protocols behave under stress or attack, and the published measurement that makes it possible to tell the difference. When a chain misbehaves, the first question is always whether the problem is the network or your own rig — and you cannot answer that without a trustworthy baseline.

• Network behaviour and hashrate anomaly investigation
• Protocol and mining-security review
• Published per-GPU hashrate baselines from measured hardware
• Written findings your team can act on