skills.rest
Tekholms-LW
Tekholms-LWCOMMUNITY
Explore all skills by this author →
GitHub

concepts

Identify incorrect assumptions in smart contract execution and decentralized incentives.

Updated Aug 27, 2026
Search Tags:#blockchain#smart contracts#state machines#evm#incentive design#apertum
One-click install
npx skills add https://github.com/Tekholms-LW/apertum-skills --skill concepts-tekholms-lw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: concepts
Source: https://github.com/Tekholms-LW/apertum-skills/tree/main/concepts
Command: npx skills add https://github.com/Tekholms-LW/apertum-skills --skill concepts-tekholms-lw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers avoid flawed blockchain designs by providing core mental models for smart contract behavior, incentives, state transitions, and decentralized system architecture.

Core Features & Use Cases

  • State Machine Design Guidance: Explains why smart contracts require external callers and how to design reliable state transitions with clear incentives.
  • Blockchain Architecture Principles: Helps evaluate what belongs onchain, gas economics, decentralization requirements, and Apertum-specific characteristics.
  • Use Case: A developer designing a DeFi protocol can use this Skill to identify missing actors, incentives, or automation assumptions before deploying contracts.

Quick Start

Use the concepts skill to review my blockchain protocol design and identify missing incentives or flawed assumptions.

Frequently Asked Questions about concepts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify missing incentives in a smart contract protocol design?▼

Missing incentives in a smart contract protocol design can be identified by evaluating trust boundaries and external caller requirements to ensure all decentralized actors have clear economic motivations for reliable state transitions.

Why do smart contracts require external callers for state transitions?▼

Smart contracts require external callers for state transitions because they are passive onchain programs that cannot execute autonomously, meaning an external actor or keeper must trigger and incentivize every state change.

What should go onchain when designing EVM-compatible applications?▼

When designing EVM-compatible applications, what goes onchain should be determined by evaluating gas economics, decentralization requirements, and trust boundaries to ensure only necessary protocol architecture and state transitions are stored onchain.

Does this blockchain design guidance work with Apertum development scenarios?▼

Yes, this blockchain design guidance applies to Apertum development scenarios by providing conceptual requirements specifically tailored for evaluating protocol architecture, state machines, and gas economics within Apertum environments.

What are common flawed assumptions about decentralized incentive mechanisms?▼

Common flawed assumptions about decentralized incentive mechanisms include expecting smart contracts to execute autonomously without external callers, misjudging trust boundaries, and underestimating gas economics required for reliable onchain decision making.

Related Skills

Explore More Software Engineering Skills→
ZodomoZodomo
7

concepts

Correct Ethereum onchain design misconceptions about deterministic execution and randomness.

Community
Basic
briannadoubtbriannadoubt

getting-started

Guide developers through installing, configuring, and starting a Trebuchet project.

Community
Basic
Canhada-LabsCanhada-Labs
2

solidity-smart-contracts

Audit Solidity smart contracts for security vulnerabilities and best practices.

Official
Advanced
jc180105jc180105

Blockchain Security Auditor

Identify and remediate smart-contract vulnerabilities in DeFi protocols.

Community
Advanced