A community badge, a voting token and a treasury have different powers.
A fictional community called Open Studio uses a website to issue attendance badges and decide how to fund a public workshop. Calling the project Web3 does not tell you who controls every part. Follow the badge and the budget to distinguish a dapp, its smart contracts, an NFT, a DAO and a governance token.
Separate the screen from the enforceable rule
Web3 is a broad label for applications that use blockchain-based ownership, payments or coordination. In our example, the dapp combines a web interface with smart-contract logic. The interface might be hosted by one company even though the contract is accessible through other clients. The chain cannot guarantee that the website stays online or explains a request accurately.
A smart contract enforces the operations its code permits when invoked. If an administrator can upgrade it, pause it or change eligibility, those permissions are part of the system too. 'Onchain' describes where a record or rule lives; it does not establish that nobody has privileged control.
One badge is not every kind of ownership
Open Studio gives each workshop attendee a non-fungible token. In an ERC-721-style design, a particular badge is identified by its contract and token ID on a specific network. The picture and displayed title help people recognize it, but another contract can reuse those labels.
The badge could qualify its holder for a later event if the application explicitly implements that rule. It does not automatically grant copyright in the artwork, ownership of the venue or voting power over the treasury. Those are separate rights and mechanisms. A metadata link may also point to a file stored outside the blockchain, so token ownership and continued image availability are separate questions.
Read how a decision becomes an action
A DAO coordinates people and resources through a defined decision process. Its governance token may assign voting weight, but a successful poll is not necessarily an executable transaction. One design lets a governance contract queue and execute approved actions after a delay. Another records a preference that a multisignature treasury's signers must carry out.
For Open Studio, ask who may propose, which balances count at the voting snapshot, what quorum means and who can actually move funds. Also ask whether administrators can veto or change the process. Token-weighted voting does not imply one person, one vote: one holder may control many units and one person may use several addresses.
A proposal passes, but the money has not moved
Suppose Open Studio defines 1,000 eligible voting units, a quorum of 200 votes cast and passage by a simple majority of cast votes. There are no abstentions. A workshop proposal receives 140 yes and 90 no: 230 votes meet quorum, and 140 exceeds half of 230. It passes this fictional rule.
If the treasury is controlled by separate multisignature signers, the result alone has not paid the workshop organizer. The next evidence is the authorized treasury transaction. If a contract instead enforces execution, inspect the queued action and its completion. The attendance NFT does not change either outcome unless the published governance rules give it that role.
Check your understanding
Does owning a community NFT mean you can vote or spend its treasury?
Only if the actual governance and contract rules grant those powers. A token's artwork, membership label or association with a DAO cannot establish that authority by itself.
Check the primary sources
These references explain the rules behind the lesson. The examples above are fictional teaching scenarios written for this dictionary.