Once published, it cannot be recalled. So we test first.

Typical scope

• Yield & staking platform

  Time-locked deposits, scheduled distributions, and brakes that stop the value being dumped all at once.

  • ·Brakes simulated before launch
  • ·Yield calculations anyone can verify
  • ·An emergency pause switch

  Typical duration: 6–10 weeks

• Automated exchange & lending

  Intermediary-free asset swapping and collateralised lending, with monitoring and a collateral-recovery mechanism.

  • ·Price references resistant to manipulation
  • ·Risk limits and isolation between assets
  • ·Adverse market conditions simulated before launch

  Typical duration: 8–14 weeks

• Decentralised exchange build

  Liquidity pools, swap routing, fee logic, and an interface an ordinary person can use — plus an admin panel to change fees without touching code.

  • ·Liquidity pools and swap routing
  • ·Fees configurable from a panel
  • ·An interface that demands no technical knowledge

  Typical duration: 8–14 weeks

• Lending protocol build

  Isolated per-asset markets, collateral thresholds, a liquidation engine, and interest curves — with risk separated so one collapsing asset cannot drag the whole protocol down.

  • ·Isolated markets: one asset failing does not spread
  • ·A liquidation engine with stress testing
  • ·Interest curves adjustable without redeployment

  Typical duration: 10–16 weeks

Typical scope

• Discovery & token design

  Two weeks to lock the token structure, holder rights, jurisdiction map, and technical specification — before code is written.

  • ·A chosen structure out of four options, with the reasoning
  • ·Holder rights and the distribution scheme spelled out
  • ·A jurisdiction map with its list of legal requirements

  Typical duration: 2 weeks

• Real-world asset tokenisation platform

  A four-layer platform — asset, verification, token, and application — built compliance-ready from the start, with an investor portal and issuer console.

  • ·Rules on who may buy enforced country by country
  • ·Proof the asset exists, open for anyone to check
  • ·Ownership register and distributions calculated automatically

  Typical duration: 4–12 weeks

• Compliance layer

  Identity checks, rules on who may hold and transfer, screening, and periodic reporting — per jurisdiction.

  • ·Adding a country is configuration, not a rebuild
  • ·Transfer rules enforced by the system itself
  • ·Periodic reports assembled automatically

  Typical duration: 4–8 weeks

• Platform operations

  Maintenance, infrastructure, data providers, and compliance updates for a platform already running.

  • ·Maintenance with a written response time
  • ·Infrastructure, data providers, and network nodes
  • ·Compliance updates when the rules change

  Typical duration: Annual

• Real-world asset tokenisation

  Issuing fractional ownership of a physical asset or receivable: issuance contracts, evidence storage, distribution rails, and transfer restrictions where required.

  • ·Issuance contracts and fractional ownership
  • ·Asset evidence storage anyone can verify
  • ·Automated distribution to holders

  Typical duration: 10–16 weeks

Typical scope

• Contract audit — up to 500 lines

  A layered security review with reproducible attack paths, plus one retest after fixes.

  • ·Findings ranked by real danger, not by count
  • ·Every finding carries a reproducible attack path
  • ·One retest after fixes is included

  Typical duration: 2 weeks

• Contract audit — 500 to 1,500 lines

  A larger scope with per-dimension review: arithmetic, access control, external calls, price feeds, and economic resilience.

  • ·Review dimension by dimension, not a single sweep
  • ·Resilience tested with randomised input, not just the happy path
  • ·Core properties proven to hold, not assumed

  Typical duration: 3–4 weeks

• Contract monitoring

  Watching a live contract: alerts on unusual behaviour, and an emergency pause switch ready to use.

  • ·Alerts when behaviour falls outside the norm
  • ·An emergency pause switch that has been tested, not merely present
  • ·A monthly report on what happened and what did not

  Typical duration: Monthly

• Contract recovery & upgrade

  Handling the aftermath of an exploit or a needed upgrade: recovering remaining funds, patching, and migration.

  • ·Recovering remaining funds comes first
  • ·The cause is traced, not merely patched over
  • ·Migration of holders to a new contract

  Typical duration: Diagnosis first

• Smart contract audit

  Line-by-line review by several auditors working from different angles, plus invariant and fuzz testing — not a scanner run pasted into a report template.

  • ·Several auditors working from different angles, not one person
  • ·Invariant and fuzz testing, not just the happy path
  • ·Every finding carries a concrete exploit path

  Typical duration: 2–5 weeks

• Token economics audit

  Testing whether the economic design holds under pressure: where the yield is actually paid from, what happens if the price halves, and who benefits most if everyone exits at once.

  • ·The true source of every promised yield
  • ·Stress simulation: price drop, thin liquidity, simultaneous exit
  • ·Unlock schedule and its effect on price

  Typical duration: 2–3 weeks

Typical scope

• Tamper-proof certificates

  Diplomas, quality certificates, and export documents whose authenticity anyone can verify in seconds.

  • ·Verifiable by anyone without contacting the issuer
  • ·Document contents are not published — only the proof
  • ·Revocable if the document is cancelled

  Typical duration: 3 weeks

• Cross-border payments & settlement

  On- and off-ramps plus cross-border settlement that completes in minutes rather than days.

  • ·Settlement in minutes
  • ·Identity checks and screening as required
  • ·Automatic reconciliation with your existing bookkeeping

  Typical duration: 8–12 weeks

• Protocol operational security audit

  Reviewing the layer a contract audit does not touch: who holds the keys, who can change parameters, how deployments happen, where prices come from, and whether abuse would be visible before the money is gone.

  • ·Who holds the keys, and what they can do alone
  • ·Real multisig authority and signing thresholds
  • ·Deployment path: who can swap a contract unobserved

  Typical duration: 3–4 weeks

• Milestone escrow

  Funds locked in a contract and released per milestone when both sides agree, with a dispute route for when they do not.

  • ·Milestone-based release
  • ·A dispute route with an arbiter
  • ·A trail both sides can inspect

  Typical duration: 6–10 weeks

• Token launch & vesting portal

  Allocation design, vesting contracts, a claim portal for holders, and an issuer panel — so the promised schedule is enforced by code rather than promised in a document.

  • ·Vesting enforced by contract
  • ·A claim portal ordinary people can use
  • ·An issuer panel to monitor distribution

  Typical duration: 6–10 weeks

• Protocol monitoring & early alerts

  Continuous watch over protocol invariants: solvency, unusual movement, privileged calls, and parameter changes — alerting the person who can act, not a dashboard nobody watches.

  • ·Solvency invariants checked continuously
  • ·An alert on every privileged call
  • ·Detection of out-of-hours parameter changes

  Typical duration: Ongoing

• Key management & multisig authority design

  Setting who holds what, how many signatures each class of action needs, how keys rotate when someone leaves, and what happens if one holder is lost.

  • ·A map of who can do what alone, today
  • ·Signing thresholds per class of action
  • ·Key rotation when someone leaves

  Typical duration: 2–3 weeks

• Price oracle integration & hardening

  Wiring price sources with fallbacks, time-weighted averaging, and movement bounds — so one briefly manipulated price cannot drain the protocol.

  • ·Redundant price sources, not a single point
  • ·Time-weighted averaging against brief manipulation
  • ·Movement bounds and circuit breakers

  Typical duration: 2–4 weeks

• Post-exploit protocol rescue

  Stopping the bleeding, establishing what happened, securing what remains, and building a recovery path that can be explained to holders.

  • ·Stop the bleeding first, investigate second
  • ·Fund tracing and securing what remains
  • ·Establishing the attacker’s entry path

  Typical duration: Immediate, then 2–6 weeks