Smart Contract
Describe one ledger-qualified smart contract deployment, its executable identity, observed behavior, control and evidence.
Bundle → Layer → Finding → Questions Filled
3 bundles · 3 layers · 5 findings · 10 questions
Deployment and code What is deployed where.
Deployed instance
The address, network and code of the contract.
Deployment
Where the contract lives and who deployed it.
- On which ledger network and at which address is the contract deployed?
- Who deployed it, and when?
Code and verification
The code behind the deployment and whether it was verified.
- Is the source code published and verified against the deployed bytecode?
- Has the code been audited, by whom and for which version?
Control and upgrade Who can change or stop it.
Administrative powers
Owner keys, upgrade paths and pause functions.
Admin rights
Privileged roles and how they are controlled.
- Which addresses hold administrative or upgrade rights?
- Can the contract be paused, upgraded or destroyed, and by whom?
Legal and economic link What it means outside the ledger.
Agreement mapping
The legal agreement and assets the code relates to.
Legal wrapper
The agreement and jurisdiction around the code.
- Is there a legal agreement the contract implements, and which terms prevail in a conflict?
- Which assets or rights does the contract control?
External inputs
Oracles and other dependencies.
- Which oracles or external contracts does it depend on?
- What happens if an input is wrong or unavailable?
Classifiers Filled
- Family
- World Models
- Category
- Information and virtual systems
- Entry kind
- entity
- Navigation path
- NAV.INF.VRT.SC
- Domain
- INF.VRT.SC
- Industry
- Cross-industry
- Tags
- smartcontractinf.vrt.sc
What it is Filled
A smart contract is program code deployed on a distributed ledger that executes automatically when called, changing ledger state according to its logic. It may implement all or part of an agreement, a token or an application; whether it is a legally binding contract depends on the agreement around it, and the ledger network itself is a separate subject.
In scope
- Deployment identity, referenced code and interface versions, state observations and execution evidence
- Contract-specific dependencies, privileged capabilities, change history and assurance assertions
- Agreement and asset references, local evidence stewardship and explicit profile gaps
Out of scope
- Ledger consensus, network operation, wallet custody and transaction signing or submission
- Software package development and distribution lifecycle, legal agreement validity and dispute adjudication
- Token economics, asset title, oracle operation, cross-chain bridge execution and generic audit-system semantics
Why it exists Filled
Describe one ledger-qualified smart contract deployment, its executable identity, observed behavior, control and evidence.
Distinguishing features Filled
- It executes automatically on a ledger once called, without a party performing the obligation.
- Deployed code is usually immutable; changes need a designed upgrade path.
- It is code, and is a legal contract only when an agreement makes it so.
- Distinct from a software package, which is distributed for installation rather than deployed to a shared ledger.
What robots and AI may and may not do Filled
Must not
- Sign or submit transactions that move assets without the holder's explicit approval.
- Handle or store private keys or seed phrases.
- Give investment advice about tokens or contracts.
- Describe unaudited code as safe.
- Help exploit vulnerabilities in deployed contracts.
Only with a human decision
- Deploying, upgrading or pausing a contract.
- Any transaction that transfers value.
- Deciding which terms prevail between code and legal agreement.
May
- Read contract state and events from the ledger.
- Explain what a verified contract's functions do.
- Check whether code is verified and audited.
- Flag administrative powers and upgrade paths to users.
Moral aspects Filled
- Bugs or exploits can cause irreversible losses for many users.
- Hidden administrative powers undermine the trust users place in automated rules.
- Users may not understand what they agree to when calling a contract.
Who is affected
- Users and token holders
- Developers and deployers
- Counterparties to linked agreements
Owners Filled
Steward
The deployer or governing body holding administrative rights, or no one when the contract is fully immutable.
Roles
- Record custodian
- Maintain local identity, namespace and retention decisions
- Technical observer
- Record qualified evidence without controlling the deployment
- Security reviewer
- Assess scoped assurance and unresolved hazards
- Governance authority
- Provide evidence for technical control and approved change decisions
- Legal and access reviewer
- Assess agreement applicability and permitted disclosure
Master systems
- Distributed ledger
- Source code repository
- Block explorer verification records
Links to other meta-models Filled
aligned
- WM-SFT-007 - Registry parent candidate only. Reference the software package/version without equating its lifecycle or identity to one deployment; binding requires review.
- ERC-1967 - Conditional alignment for compatible proxies only; no universal detection or conformance claim.
- PROV-O - Conceptual provenance alignment; a mapping and conformance implementation remain pending.
- Runtime interface and observation profiles - Conditional ABI and JSON-RPC or named-contract mappings; versions must be pinned.
references
- Ledger network and transaction master - Network-qualified ledger and transaction references; consensus and execution remain external.
- Legal agreement and asset masters - Optional mappings; legal validity, title and economics remain external.
- Oracle and dependency masters - Reference supplied inputs and trust assumptions without owning service operation.
neighbor
- WM-SFT-007 Software Component / Package - Registry parent candidate is conceptual alignment. A package may have many deployments; this model references exact package/build evidence without inheriting package identity or owning distribution.
- Ledger network and transaction - Network masters own consensus and transaction history. This deployment record stores qualified references and observations, not a replacement ledger or execution engine.
- Legal agreement and represented asset - Executable code need not constitute a legally enforceable agreement. Title, parties, terms and legal remedies remain separately mastered and require applicable legal assessment.
- Proxy and implementation - The proxy deployment and implementation deployment retain distinct identifiers; the selected implementation is an observed time-qualified relation, not a permanent identity equivalence.
parent
- WM-SFT-007
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- A smart contract is identified by its address on a named ledger network and chain identifier.
- Its code version is identified by a hash of the deployed bytecode.
Direct properties not applicable Not applicable
Not applicable
A smart contract is an information or software construct; its measurable attributes are configuration and operational data, not physical properties.
Recognition optional Filled
- A contract is recognised by its address, deployed code and emitted events on the ledger.
- Often confused with the token it implements, the user interface that calls it or the legal agreement around it.
Capabilities and actions required Filled
- A contract can hold and transfer assets, emit events and call other contracts.
- Some contracts can be paused, upgraded or self-destructed by privileged roles.
Hazards and failure modes required Filled
- Irreversible loss of assets through bugs or exploits.
- Abuse of administrative keys.
- Manipulated oracle inputs triggering wrong execution.
Standards and interfaces required Filled
- Application binary interfaces published with verified source code.
- ISO 22739 vocabulary for blockchain and distributed ledger technologies.
Context of use required Filled
- Used for tokens, decentralized finance, supply chain, registries and data sharing.
- The EU Data Act sets essential requirements for smart contracts used in data sharing agreements.
Sources Filled
- Introduction to smart contracts - Ethereum documentation community
- Contract ABI Specification - Solidity project
- EIP-6780: SELFDESTRUCT only in same transaction - Ethereum Improvement Proposals community
- Smart Contracts and Chaincode - Hyperledger Fabric project
- ERC-1967: Proxy Storage Slots - Ethereum Improvement Proposals community
- Security Considerations - Solidity project
- PROV-O: The PROV Ontology - World Wide Web Consortium
- Regulation (EU) 2023/2854, Article 36 - European Parliament and Council
- JSON-RPC API - Ethereum documentation community
- Contract Metadata - Solidity project
- Blockchain Technology Overview, NISTIR 8202 - National Institute of Standards and Technology
- ISO 22739 Blockchain and distributed ledger technologies - Vocabulary (ISO)
- Regulation (EU) 2023/2854 Data Act, Article 36 on smart contracts (European Union)
Open questions
- Restore independent external review before canonical or publishable-draft promotion.
- Run direct source checks outside the sandbox, pin documentation and protocol versions, and verify current legal applicability and licensing.
- Develop nested schemas and profile fixtures for ambiguous identity, forks, proxy changes, invalid commitment, stale or conflicting observations, disposal and lossy projections.
- Extend coverage through separate profiles for alternative VMs, UTXO scripts, account delegation, confidential execution and cross-network dependencies.
- Independent second-provider review is absent.
- Direct HTTP statuses and current source versions remain unverified; latest documentation URLs are not release pins.
- Current consolidated legal text, jurisdictional applicability, licensing and conformity procedures require review.
- UTXO scripts, account delegation, alternative VMs, confidential execution and cross-chain protocols need separate profiles.
- Nested schemas, implemented operations, live instance testing and pinned neighbor mappings are incomplete.
Machine files
Provenance
world-models research · reviewable-draft
Built from: models/wm-vrt-011-smart-contract/spec.yaml, ver-cy/world-models/card-supplements/wm-vrt-011-smart-contract.json