Blockchain & Web3 Development Company in Edinburgh

Edinburgh blockchain work is sized by verification depth, because the local client base expects London-grade assurance. A scoped smart-contract MVP is a six to ten week engagement covering one to three core contracts on Foundry, full invariant and fuzz tests, Slither and Mythril static analysis, and a deployment to Sepolia or Arbitrum testnet. A production tokenisation platform adds custody integration, oracle wiring, an FCA registration support pack, Fireblocks or Copper integration, formal verification on critical invariants with Certora or Halmos, and an external audit budget from Trail of Bits, OpenZeppelin, Consensys Diligence, or Spearbit. Bank-scale settlement or custody systems add PRA SS1/21 operational-resilience documentation and Metaco Harmonize integration. Edinburgh carries a financial-services premium over Glasgow or Newcastle because the local clients (RBS, NatWest Group, Baillie Gifford, abrdn, Scottish Widows) expect the same audit and documentation depth as London Wall. We quote fixed fee, with the external audit itemised separately so the client owns audit-firm selection.

Almost certainly, if your project touches custody, exchange, or transfers of cryptoassets under the MLRs 2017 as amended. The FCA cryptoasset register has had a notably high refusal and withdrawal rate, and the regulator has been explicit that most applicants fail to meet financial-crime standards on first submission. Edinburgh financial-services clients tend to apply through their group entity rather than a Scottish-only vehicle, but registration is still required. Our engagement opens with an FCA Perimeter Guidance Manual review, a token classification memo (security token, electronic money token under PSD2 alignment, or unregulated cryptoasset), a Section 21 financial-promotions check under FSMA 2023, and an MLRs scoping note covering Travel Rule obligations under FATF Recommendation 16. We do not file the FCA application. We hand the documentation to your law firm (Burness Paull, Pinsent Masons, CMS in Edinburgh, or your group's London firm) who runs the actual submission. We have shipped the technical evidence packs that supported successful registration for Edinburgh-adjacent firms.

Yes. Fireblocks integration uses their REST and WebSocket APIs for transaction creation, policy enforcement, and tokenisation via their Tokenization Engine. Copper integration covers Copper ClearLoop for off-exchange settlement and the Copper Trade and Custody APIs with MPC key management. BitGo integration uses BitGo Express for self-custody and BitGo Trust APIs for qualified custody when an Edinburgh fund or pension trustee requires it. Metaco Harmonize integration covers institutional key management, policy engines, and integration into core banking systems where Edinburgh banks (RBS, Lloyds Scotland, Bank of Scotland) need a deployment pattern compatible with their existing T24, Avaloq, or Finacle cores. Every integration ships with a custody-model memo documenting who holds keys, what the recovery path is, who can authorise a transaction, and how the multisig or MPC quorum maps to the client's corporate signatory matrix. We pair custody integrations with Chainalysis KYT or Elliptic Navigator for sanctions screening and Travel Rule compliance under FATF Recommendation 16, because Edinburgh institutional clients require those controls before mainnet.

Banks regulated by the PRA expect a documented model lifecycle on anything that scores, prices, or routes a financial decision, and SS1/21 sets that expectation on model risk management. Edinburgh banks (RBS, NatWest Group, Lloyds Scotland) apply that lens to blockchain-adjacent components (oracle feeds, on-chain pricing logic, automated liquidation engines) when those components meet the SS1/21 model definition. Our pattern is to scope the SS1/21 perimeter early, document the model inventory inside the broader system, produce a model card for each scored component, run a challenger-model exercise where applicable, and align monitoring on Tenderly and Forta with the client's existing model-risk monitoring dashboards. Operational resilience under PRA SS1/21 (operational resilience supervisory statement) adds an impact-tolerance assessment, important business service mapping, and severe-but-plausible scenario tests. We have shipped these documentation packs alongside the technical build for Edinburgh-adjacent clients.

Four layers, with no shortcuts because Edinburgh banks and asset managers will refuse a deployment that skips any of them. First, Foundry test suites with invariant, fuzz, and stateful tests covering reentrancy, integer overflow, access-control bypass, signature-replay, and oracle-manipulation paths. Second, Slither, Mythril, and Aderyn in CI for static analysis. Third, formal verification on critical functions using Certora Prover, Halmos, or Kontrol, with verified properties documented in the deployment readme. Fourth, external audit from a firm Edinburgh institutional clients accept (Trail of Bits, OpenZeppelin, Consensys Diligence, Spearbit, or Sigma Prime). Post-deployment we run Forta and OpenZeppelin Defender on suspicious activity, with Tenderly real-time alerts on critical functions and a Chainalysis KYT layer on transaction screening. Multisig ownership is mandatory using Safe, with a time-lock on upgrades and an emergency-pause path tested under PRA Operational Resilience scenarios before mainnet. We do not deploy without all four layers.

A standard Edinburgh production blockchain build (tokenisation platform, settlement system, or custody integration for an asset manager or bank) takes eighteen to twenty-eight weeks. Weeks one to four are regulatory scoping under the FCA Perimeter Guidance Manual, PRA SS1/21 model-risk classification, custody-model design, and threat modelling. Weeks five to twelve are contract development on Foundry, oracle wiring with Chainlink, and custody integration with Fireblocks, Copper, BitGo, or Metaco Harmonize. Weeks thirteen to sixteen run formal verification with Certora or Halmos plus internal red-team review. Weeks seventeen to twenty are the external audit window with Trail of Bits, OpenZeppelin, or Consensys Diligence and remediation. Weeks twenty-one to twenty-six deploy to mainnet behind a Safe multisig with monitoring on Forta, Tenderly, and Chainalysis KYT. Bank-scale projects with Avaloq or T24 integration, FCA registration support, and PRA operational-resilience documentation extend by eight to fourteen weeks. We never compress the audit phase, and Edinburgh general counsel will not let us.

When a project requires genuinely novel cryptography or consensus work (custom zero-knowledge circuits, novel MEV-resistance schemes, post-quantum signature work) we scope collaborations with the University of Edinburgh Blockchain Technology Lab in the School of Informatics or affiliated researchers at the Bayes Centre, rather than overstating in-house capability. Most Edinburgh financial-services blockchain projects do not need this. Standard Solidity work, tokenisation, custody integration, and off-the-shelf zkSync or StarkNet deployment uses well-trodden primitives. We will tell you up front which bucket your problem falls into. For genuinely novel work we draft a research collaboration agreement that respects University of Edinburgh IP policy (managed through Edinburgh Innovations), produce a peer-reviewable paper alongside the production code, and contribute the primitive back to open-source ecosystems (Circom, Halo2, Noir) where the client's commercial position allows. We have closed engagements where the right answer was to use existing primitives with a documented trust assumption and saved Edinburgh clients a quarter.

Often yes, but the merged RDEC scheme from April 2024 narrowed eligibility on cryptoasset work, and HMRC has been notably sceptical of cryptoasset claims since 2023. The 20 percent above-the-line credit applies to qualifying R&D, with an enhanced rate for R&D-intensive SMEs (ERIS) at 14.5 percent payable. Eligible activity for Edinburgh blockchain projects generally includes novel consensus design, formal-verification methodology development, zero-knowledge circuit work, oracle reliability research, and cryptographic protocol engineering with documented algorithmic uncertainty. Routine Solidity development, off-the-shelf token deployment, and standard frontend integration are not eligible. We deliver time-tracked logs, technical narratives mapped to HMRC's CIRD81900 software guidance, and a failed-hypothesis log defensible against HMRC enquiry. Scottish R&D claimants sometimes also qualify for Scottish Enterprise grants on the commercialisation side. We hand the documentation to your R&D tax advisor (Ayming, ForrestBrown, or a Glasgow or Edinburgh boutique) for the actual HMRC filing.