SC-01 · Protocol engineering · Priority
Senior Smart Contract Engineer - Protocol
Own the contract boundary for model registries, compute receipts, storage proofs, access policy and governed protocol change.
- Location
- Remote · Singapore overlap
- Engagement
- Full-time or contract-to-hire
- Path
- Core opening
Mandate
Turn the Ztakora Grid protocol direction into a compact contract suite whose permissions, invariants and compute-certification paths can withstand independent review.
The Grid anchors model provenance, dataset references, compute receipts and access policy. This role keeps the on-chain surface narrow, testable and aligned with the AI runtime and the permanent storage layer.
First 90 days
Four reviewable outcomes for the contract boundary.
- 01
Produce a reviewed contract map covering roles, subnet boundaries and upgrade paths.
- 02
Implement model-registry, compute-receipt, storage-proof and access modules with invariant tests.
- 03
Define deployment, verification and privileged-action runbooks with the security owner.
- 04
Prepare an assurance package covering limitations, test evidence and remediation status.
You will own
- Design Solidity modules with established OpenZeppelin patterns.
- Model subnet membership, role separation, multisig authority and timelocked change.
- Write unit, integration, fuzz and invariant tests before release decisions.
- Review external contract contributions and document consequential tradeoffs.
- Partner with the AI runtime and storage owners on receipt and recovery state.
Strong fit
- Deep Solidity 0.8.x and EVM execution knowledge.
- Strong Foundry experience, including fuzz and invariant testing.
- Evidence of secure access-control, registry or token-system delivery.
- Comfort rejecting unnecessary on-chain complexity.
- Clear technical writing and asynchronous review habits.
Stack
Application
Show how you reason about authority, invariants and failure.
Share public or sanitized material only. Do not send confidential source code, private keys or client-restricted documents.
- One contract system you personally owned
- A test or invariant you consider unusually strong
- A security tradeoff you documented and defended
