Hiring a Solidity Developer: The Brief to Write First
Before you ask for a quote, can you say who may move the assets, pause the contracts or upgrade them?
IN 30 SECONDS
A Solidity brief is a short document, written before the quote, that says what your smart contracts hold and who controls them. Without it, code that compiles can still leave the risky questions open.
KEY TAKEAWAYS
· 3
- Write down the assets, the people and systems that act on them, and who can upgrade the contracts before you ask for a quote.
- ERC-3643 gives technical building blocks, not a legal approval: a legal or compliance owner sets the real rules.
- Name the responsibility you are missing before you compare proposals.
On this page
The problem: hiring for the contract, not the system
IN SHORT Code that compiles says little about safety. The harder question is who can move the assets.
WORDS TO KNOW
- Smart contract
- A program on a blockchain that can hold or move assets by fixed rules. Its code can’t change after launch unless it was built to be upgraded.
- Permission model
- The written list of who may do what, such as pause, upgrade or move assets, and who can grant or remove those powers.
- Upgrade authority
- The account or group allowed to switch a contract to new code after launch, on a contract built to allow it.
At Tokeny, I worked on permissioned tokens. Only approved holders can receive them. Then I led blockchain engineering at Biconomy, including modular smart accounts.
I’m also a named author of ERC-3643. That range shapes my first question to a candidate. Before we talk gas fees (the cost of a transaction), I’d want to know who can move an asset, who can change that power, and how the team will catch a mistake.
ADAM says: A brief is a building’s key plan: who gets which key, who may change the locks. Where it breaks: a deployed contract’s code can’t change unless built to be upgraded, and anyone on the chain can try to call it.
IN PLAIN WORDS
Coming up next: So what goes in the brief?
Describe the asset flows and authority
IN SHORT Write the Permission model The written list of who may do what, such as pause, upgrade or move assets, and who can grant or remove those powers. See the glossary before the feature list: it says who can move, pause or change things.
“Build a token” leaves most of the work open. Pause, recovery, moves by an operator: what is allowed, and who holds the Upgrade authority The account or group allowed to switch a contract to new code after launch, on a contract built to allow it. See the glossary? Which of those powers does the product need?
STEP BY STEP
Step 1. Assets. What enters, who holds it and what must happen before it leaves, outside tokens and dependencies included.
- Assets What enters, who holds it and what must happen before it leaves, outside tokens and dependencies included.
- Actors Users, operators, admins, upgrade authorities, outside systems: who may do what, and how that power is revoked.
- Lifecycle Creation, normal use, pause conditions, recovery and retirement. Say which transitions should be impossible.
- Environment Target chain, existing contracts, wallet integrations, and any oracle or off-chain service the design relies on.
In a Solidity brief, the actors part deserves the most care: it shows who could do damage.
OpenZeppelin publishes reusable Solidity contracts. Its access-control docs cover owners and roles. But which roles you need, and who runs them, is still a choice: product and engineering make it together.
An upgradeable contract needs extra care. OpenZeppelin’s upgrade guide covers the limits on initializers and the traps in storage layout. Ask to see both on your own contracts, migrations and on-chain state included.
Coming up next: Then who do you hire to build it?
Choose the engagement by the missing ownership
IN SHORT Name the responsibility you are missing before you compare proposals.
For smart accounts, spell out the module permissions you need. ERC-7579, still a Draft (not yet final), defines interfaces for modular accounts. It doesn’t tell you what a given module can do once installed: you still have to check that.
ITEM GET
Missing role first
I work on Solidity, smart accounts and tokenization systems. Hiring for a mission or a permanent role? Send me the repo context, target chain and scope.
Questions about the brief and the quote
The contracts in scope, target networks, integrations, permission model, tests, docs, deployment tasks, an allowance for audit fixes and the exclusions. Price and timing depend on those inputs. Ask who pays for the independent review and who owns changes once scope is set.
No. ERC-3643 gives technical tools (identity and compliance checks), not a legal approval. It doesn’t decide if a given token issue meets the law that applies to it. Your product and legal owners must set the rules, and engineers build and test them.
PART COMPLETE
What you now know
- Why a brief first says who can move, pause or upgrade, and its four parts: assets, actors, lifecycle, environment.
- How a freelance build, a senior hire and an independent audit differ.
Check yourself
Tap or click a question to see the answer.
You have a written spec and an in-house team that will maintain the contracts. Do you hire an auditor to build them?
No. That is a bounded build, a fit for a freelance developer. You still book an independent review on top, by someone who didn’t write the code.
Web3 x AI engineer, former CTO of Integra. Named author (1 of 5) of ERC-3643, first author of ERC-6960, co-author of ERC-7410, and co-author of ERC-8203, which is still a draft.
Have a project to ship or a role to fill?
Discuss your project or roleMy work at the web3 x AI intersectionOpen-source tools I build
Follow the engineering notes
Get new articles on production AI and smart contracts by email.

