1. Home
  2. /
  3. Clarity Typing Test
  4. /
  5. Allowlist Example

Allowlist Example - Clarity Typing CST Test

Skip to main content
CodeSpeedTest
Languages
Start TypingJump into a test — pick any languageAdaptive TrainingUnlock chars as you master themPractice DrillsFocused sessions targeting weak spotsDaily ChallengesNew coding challenges every dayRace ModeCompete against others in real timeAI OpponentRace against an AI at your WPM levelTournamentsLive coding speed tournamentsArcade GamesZType, Overkill Survival, Glyphica & moreGamificationXP, coins, badges & quests
LeaderboardGlobal rankings for every languageCertificatesEarn verifiable Bronze / Silver / Gold certsActivityDaily streaks & historical analyticsProfileYour stats, badges & achievements
Browse Languages500+ languages with real code examplesBlogTips, guides & deep divesFree ToolsWPM calculator, typing speed report & moreFAQCommon questions answeredGetting StartedNew to CodeSpeedTest?AboutOur story & missionSupportGet help — Pro users get priorityContactGet in touch with the team
Pricing
Mode:
Duration:
1
2
3
4
5
6
7
8
9
10
11
(define-map allowed principal bool)

(define-public (add user)
	(begin
		(map-set allowed user true)
		(ok true)))

(define-public (remove user)
	(begin
		(map-set allowed user false)
		(ok true)))
Coding works best on desktop or with an external keyboard.
CodeSpeedTest

Improve your coding speed, code accuracy, and programming syntax WPM with practice sessions across 500+ programming languages.

Quick Links

HomeAboutFeaturesGetting StartedLanguages

Legal & Support

Pro ⚡ PricingContactPrivacy PolicyTerms of Service

Connect

CodeSpeedTest on GitHubCodeSpeedTest on TwitterEmail CodeSpeedTest

© 2026 CodeSpeedTest. All rights reserved.

Allowlist Example — Clarity Code

Stores allowed addresses with add/remove operations.

(define-map allowed principal bool)

(define-public (add user)
	(begin
		(map-set allowed user true)
		(ok true)))

(define-public (remove user)
	(begin
		(map-set allowed user false)
		(ok true)))

Clarity Language Guide

Clarity is a decidable smart contract language used on the Stacks blockchain. It enables predictable and secure smart contracts without gas estimation or unpredictable behavior.

Primary Use Cases

  • ▸Building secure DeFi protocols on Stacks
  • ▸NFT minting and trading
  • ▸On-chain governance contracts
  • ▸Bitcoin-integrated smart contracts
  • ▸Deterministic financial applications

Notable Features

  • ▸Decidable language - predictable execution
  • ▸No gas estimation needed
  • ▸Strong static typing
  • ▸Direct Bitcoin integration
  • ▸Lisp-like syntax with functional constructs

Origin & Creator

Clarity was created by Blockstack PBC (now Hiro Systems) around 2018 to provide secure, predictable smart contracts that integrate with Bitcoin.

Industrial Note

Clarity is used in projects where security and predictability are paramount, such as DeFi protocols on Bitcoin, NFT platforms, and on-chain governance solutions.

Quick Explain

  • ▸Clarity is a Lisp-like language that is interpreted, not compiled to bytecode, ensuring contracts behave deterministically.
  • ▸It is decidable, meaning all outcomes of contract execution can be known before running.
  • ▸Contracts can interact with the Bitcoin blockchain via Stacks.
  • ▸It prevents runtime errors common in other languages by enforcing strict typing and bounds checking.
  • ▸Used in DeFi, NFTs, and decentralized applications on Stacks.

Core Features

  • ▸define-public -> exposes functions externally
  • ▸define-constant -> immutable constants
  • ▸map, list, tuple types for structured data
  • ▸Contract-to-contract calls
  • ▸Error handling via (ok ...) and (err ...)

Learning Path

  • ▸Learn Lisp-like syntax
  • ▸Understand Clarity data types and functions
  • ▸Practice public/private function writing
  • ▸Deploy on Stacks testnet
  • ▸Integrate with Bitcoin and frontend apps

Practical Examples

  • ▸STX token transfer contract
  • ▸NFT minting and listing
  • ▸Voting governance contract
  • ▸Escrow with Bitcoin integration
  • ▸Predictable DeFi interest protocol

Comparisons

  • ▸Clarity vs Solidity: Clarity is decidable and predictable, Solidity runs on EVM.
  • ▸Clarity vs Vyper: Both are safer than Solidity, but Clarity is interpreted and deterministic.
  • ▸Clarity vs Ink!: Clarity targets Stacks/Bitcoin, Ink! targets Substrate/Wasm.
  • ▸Clarity vs Ocean SDK: Clarity is smart contract language; Ocean SDK is a data marketplace SDK.
  • ▸Clarity vs Move: Move is resource-oriented for Diem/Aptos; Clarity is functional and decidable.

Strengths

  • ▸Predictable smart contract execution
  • ▸High security with decidability
  • ▸Strong type system prevents many bugs
  • ▸Integrates with Bitcoin safely
  • ▸Simplifies auditing and formal verification

Limitations

  • ▸Limited to Stacks blockchain
  • ▸Lisp-like syntax may have learning curve
  • ▸Fewer libraries compared to Solidity/EVM
  • ▸Not general-purpose outside Stacks
  • ▸Smaller community and tooling ecosystem

When NOT to Use

  • ▸EVM-based projects
  • ▸Non-Stacks blockchain deployments
  • ▸Projects needing extensive third-party libraries
  • ▸Developers unfamiliar with Lisp-like syntax
  • ▸High-complexity contracts requiring dynamic execution

Cheat Sheet

  • ▸define-public -> external function
  • ▸define-private -> internal function
  • ▸define-constant -> immutable value
  • ▸ok(...) -> success result
  • ▸err(...) -> error result

FAQ

  • ▸Is Clarity Turing-complete?
  • ▸No - it is decidable for predictable outcomes.
  • ▸Can Clarity interact with Bitcoin?
  • ▸Yes - through Stacks blockchain integration.
  • ▸Which languages are similar to Clarity?
  • ▸Lisp/Scheme-like syntax.
  • ▸Can Clarity be used for NFTs?
  • ▸Yes - supports minting and trading on Stacks.
  • ▸Is Clarity safe for DeFi?
  • ▸Yes - predictable and auditable contract execution.

30-Day Skill Plan

  • ▸Week 1: Clarity syntax basics
  • ▸Week 2: Public/private functions and constants
  • ▸Week 3: Maps, lists, tuples, and storage
  • ▸Week 4: Deploy testnet contracts
  • ▸Week 5: Integrate with frontend and Bitcoin

Final Summary

  • ▸Clarity is a decidable, predictable smart contract language.
  • ▸Used on Stacks blockchain with Bitcoin integration.
  • ▸Ideal for secure DeFi, NFTs, and governance applications.
  • ▸Functional, Lisp-like syntax with strong type safety.
  • ▸Ensures auditable and deterministic contract execution.

Project Structure

  • ▸contracts/ - Clarity source files
  • ▸tests/ - unit and integration tests
  • ▸scripts/ - deployment scripts
  • ▸package.json - project configuration
  • ▸README.md - documentation and usage notes

Monetization

  • ▸Deploy DeFi contracts
  • ▸NFT marketplaces
  • ▸Governance solutions
  • ▸Subscription-based apps on Stacks
  • ▸Offer secure Bitcoin-integrated apps

Productivity Tips

  • ▸Leverage Clarity REPL for quick tests
  • ▸Use constants for repeated values
  • ▸Modularize functions
  • ▸Monitor deterministic outputs
  • ▸Document code and storage clearly

Basic Concepts

  • ▸define-public functions for external calls
  • ▸define-private for internal contract logic
  • ▸define-constant for immutable values
  • ▸use maps, lists, tuples for structured storage
  • ▸ok/err pattern for safe return values

Official Docs

  • ▸https://docs.stacks.co/docs/clarity/overview
  • ▸https://github.com/hirosystems/clarity

More Clarity Typing Exercises

Clarity Simple Counter ContractClarity Token Balance StoreClarity Ownership ModuleClarity Simple Voting SystemClarity Boolean ToggleClarity Fixed Supply TokenClarity Timelock ContractClarity Simple Message StorageClarity Key-Value Store

Practice Other Languages

CReactPythonC++RustTypeScriptKotlinPHPJavaC#RubyMqlCqlN1qlCypher