Skip to content

TxShield #2544

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 13 commits into
base: master
Choose a base branch
from
Open

TxShield #2544

wants to merge 13 commits into from

Conversation

HoodClock
Copy link

Grant Application: TxShield - Transaction Safety Simulator
Project Name: TxShield
MVP Official Docs: github.com/HoodClock/OfficialDocs
MVP Demo: safe-tx-simulator.vercel.app

Overview
TxShield is a transaction simulator and a detection tool for the contracts as well that prevents failed transactions, gas waste, and honeypot scams by previewing risks before execution. Built with Ethers.js and Next.js, it targets 21M+ wallets users and plans to expand to Polkadot’s EVM

@github-actions github-actions bot added the admin-review This application requires a review from an admin. label Apr 24, 2025
@HoodClock HoodClock mentioned this pull request Apr 24, 2025
@keeganquigley
Copy link
Contributor

See #2541 for reference.

@keeganquigley
Copy link
Contributor

Thanks for the updated application @HoodClock. Can you explain more about how the honeypot contract works in practice?

@HoodClock
Copy link
Author

Hi @keeganquigley, Thanks for the follow up, The honeypot Contract looks like a normal smart contract on the outer shell but deep in this its a trick to block the user funds. It lets user send amount and promises a reward or sometime return with extra based on the scammer hook but when a user try to withdraw their funds the internal logic of smart contract wont let user do that instead it traps the funds.
I have made the custom honeypot contract just for testing using solidity here is the link [https://github.com/HoodClock/OfficialDocs.git]

@HoodClock
Copy link
Author

So to demonstrate the honeypot contract i have made the simple smart contract that pretends to allow withdrawals. But in reality, a fallback function force-ably revert.
Since this is one of the most common honeypot tricks, I’m also exploring ways to detect more advanced types as I continue building the Beta version.

Copy link
Contributor

@keeganquigley keeganquigley left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the explanation @HoodClock this sounds very similar to Token Sniffer for Solana. Let me clarify though that the W3F grants program is focused solely on the Polkadot ecosystem. Therefore there are many deliverables we wouldn't be able to fund, such as:

  • 1.3 "Extend Ethers.js support to Polygon & Optimism (Sepolia tested)"
  • 2.0b "Tutorial update for Polygon support".

For further consideration, I would recommend re-purposing the application to focus on Polkadot, with a possible Asset Hub (PVM) deployment in addition to Moonbeam (which are planned to launch in September).

@keeganquigley keeganquigley added the changes requested The team needs to clarify a few things first. label Apr 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
admin-review This application requires a review from an admin. changes requested The team needs to clarify a few things first.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants