---
title: "Discussion on \"A questionable design choice in Stacks/Clarity\" | Hashnode"
description: "Discussion on \"A questionable design choice in Stacks/Clarity\". Fri 14 March 2025\nby 100proof\nTL;DR\n\nMost Clarity contracts use a form of authentication similar to Solidity's tx.origin for sensitive/\"owner only\" functions. This is a known \"bad thing\" in the Ethereum community.\n\nThis authentication method interact..."
url: "https://hashnode.com/posts/a-questionable-design-choice-in-stacksclarity/67d9205f05a6d8ec02679eeb"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [A questionable design choice in Stacks/Clarity](https://neumo.hashnode.dev/a-questionable-design-choice-in-stacksclarity?utm_source=hashnode&utm_medium=feed)

Fri 14 March 2025 by 100proof TL;DR Most Clarity contracts use a form of authentication similar to Solidity's tx.origin for sensitive/"owner only" functions. This is a known "bad thing" in the Ethereum community. This authentication method interact...

Mar 18, 2025 · 17 min read · neumo.hashnode.dev  
Read the article

-   [#blockchain](https://hashnode.com/tag/blockchain)
-   [#clarity-lang](https://hashnode.com/tag/clarity-lang)
-   [#stacks](https://hashnode.com/tag/stacks)
-   [#bountyhunter](https://hashnode.com/tag/bountyhunter)
-   [#phishing](https://hashnode.com/tag/phishing)
-   [#phishingattacks](https://hashnode.com/tag/phishingattacks)
-   [#nft](https://hashnode.com/tag/nft)

## Written by

[neumo](https://hashnode.com/@neumo)

@neumo

  
[View profile](https://hashnode.com/@neumo)

Mo Bugs Mo Problems

## Responses

Markdown supported · ⌘↵ to post

No responses yet.