Blockchain · Development
Smart contracts and tokenisation, carefully built and tested
We develop smart contracts and token contracts for EVM-compatible networks – from specification and tests to deployment. We keep a clear line between what is implemented technically and the legal and commercial questions you resolve with your advisers.
Starting points
Typical situations
- Your project needs its own token with clearly defined rules.
- Existing logic – approvals, payouts or registers – should be represented on-chain in a traceable way.
- A company wants to represent shares, entitlements or certificates technically as tokens and needs an implementation.
- Existing contracts need to be extended, tested or documented.
- After deployment you need help with verification, explorer integration and operation.
Scope
What we do
-
Specification
Agreeing in writing what the contract must do, who holds which rights and what must explicitly be impossible.
-
Solidity development
Implementation based on established libraries and standards such as ERC-20 or ERC-721 where they fit.
-
Testing
Automated tests for intended flows and edge cases; deployment to a testnet first.
-
Roles & permissions
Traceable permissions; pause or upgrade mechanisms only where they are deliberately wanted.
-
Deployment & verification
Deployment to the target network, source verification in the explorer and handover of addresses.
-
Documentation
Functions, roles, parameters and operating steps described for your team.
Process
How a project runs
-
Initial call
Goal, network, stakeholders and the legal framework from your perspective; we clarify what makes sense technically.
-
Specification & quote
A written specification and a quote for development, testing and deployment.
-
Development & testing
Iterative implementation with automated tests and interim testnet releases.
-
Sign-off
You review the testnet version; where appropriate we recommend an independent external review before launch.
-
Deployment & handover
Deployment, verification, documentation and transfer of administrative rights.
Tokenisation
Tokenisation as a technical development service
Technically, tokenisation means that a right, a share, an entitlement or a certificate is represented by a token on a blockchain. We develop the contracts and processes for this. What a token means legally is not decided by code.
What we implement
- Token contracts based on suitable standards, e.g. ERC-20 for fungible or ERC-721 for individual units
- Rules for issuance, transfer, freezing and redemption – exactly as specified
- Roles for issuance and administration, optionally with multi-signature approval
- Register and certificate functions that reference external documents
- Integration with explorers, wallets and your own applications
- Tests, testnet deployment and documentation
What tokenisation does not do
- It does not make a project legally permissible. Whether regulatory requirements apply is for your legal and tax advisers to assess.
- It does not automatically transfer legal ownership of goods, real estate or company shares. The applicable legal formalities continue to apply.
- It does not promise appreciation or returns. We make no statements about the commercial success of a token.
- It does not replace an independent review of the contract where significant value is involved.
Our role is clearly defined: we deliver specification, code, tests, deployment and documentation. Legal, tax and commercial assessments remain with you and your advisers. We are happy to align the technical implementation with their requirements.
Deliverables
What you receive
- Written specification
- Source code with automated tests
- Testnet and mainnet deployment
- Verified source code in the explorer
- Technical documentation and handover record
- List of known limitations and recommendations
Ongoing support
After deployment we can help connect contracts to applications, explorers or your own infrastructure, and with later extensions. Deployed contracts can only be changed if this was deliberately designed in.
Questions
Frequently asked questions
Do you perform smart contract audits?
We test our contracts thoroughly and review them internally. That is not an independent audit. For contracts that manage significant value, we recommend an external review before launch.
Which networks can the contracts run on?
EVM-compatible networks. Which one makes sense depends on cost, audience and requirements; we discuss this upfront.
Who owns the source code?
Usage and ownership rights to the code are set out explicitly in the quote or contract.
Is tokenisation legally permissible?
That depends on the specific project and is a legal question. We provide the technical implementation, not legal advice. Please clarify the legal and tax framework with your advisers.
Can a contract be changed after deployment?
Only if an upgrade mechanism was deliberately built in. This has advantages and drawbacks that we discuss openly during specification.
Next step
Let’s talk about your project
Describe your starting point briefly. We will get back to you, clarify open questions and propose a sensible next step.