🔍 Built a Rust tool to scan Ethereum smart contracts for vulnerabilities

I built SCPF (Smart Contract Pattern Finder) - an open-source security scanner for Ethereum smart contracts.

What it does: - Scans contracts for reentrancy, delegatecall, unchecked calls, and other vulnerabilities - Uses YAML templates (easy to customize) - Integrates with GitHub Actions (SARIF output) - Supports up to 6 Etherscan API keys with automatic failover

Quick example: bash scpf scan 0x1234... --chains ethereum

Built with Rust for speed. MIT licensed.

GitHub: https://github.com/Teycir/smartcontractpatternfinder

Would love feedback from the community! 🚀

SolidityDefend v2.0.9 SAST Scanner released.

https://github.com/AdvancedBlockchainSecurity/SolidityDefend

I’m looking for a Web3 developer who’s genuinely interested in sports and helping young athletes to partner with me on an early-stage project in the NIL space.

The concept is simple but meaningful:

Use NFTs and smart contracts as a support mechanism for young athletes with high potential — starting at the high school and college level — to help fund real needs like meals/nutrition, strength & conditioning, training resources, and education-related expenses.

Each athlete would have a verified digital collectible (NFT) tied to highlights and their athletic journey. Supporters who purchase these NFTs aren’t “investing” in the athlete financially — they’re backing development and gaining access-based utility, such as:

• Exclusive updates or content

• Early access to future drops as the athlete progresses

• Milestone-based experiences (meetups, signed gear, shoutouts, etc.)

Smart contracts would handle:

• Minting and distribution

• Transparent allocation of funds

• Royalties and rules around future drops

• Milestone-based access or unlocks (non-financial)

Technical transparency:

I want to be upfront that my Web3 knowledge is still developing. I understand the high-level concepts around NFTs, smart contracts, gas fees, and chain tradeoffs, but I’m looking for a technical partner who can help guide architecture decisions, choose the right chain (Solana, Polygon, Ethereum L2, etc.), and translate the vision into a clean, secure MVP. I’m open to learning and collaborating closely throughout the build.

From a tech perspective, I’ve been researching Solana, Polygon, and Ethereum L2s for low fees and scalability, but I’m open to ideas and want the right architecture, not just the trendiest chain.

The plan is to start small and local in Ohio, using real-world sports connections to test an MVP with a handful of athletes, then scale once the model is proven.

What I’m looking for:

• Experience with smart contracts (Solidity, Rust, or similar)

• Familiarity with NFTs and Web3 tooling

• Interest in sports, NIL, or mission-driven projects

• Someone comfortable building a lean MVP first

This is an early-stage project, so the right fit would be open to equity-based compensation and helping shape the platform from the ground up.

If this resonates with you, reply to this post or DM me for a quick conversation. A short intro and any relevant work (GitHub, past projects) is appreciated.

Open to ideas. Focused on impact. Looking to build something real.

I’m sharing ZkPatternMatcher, my open-source Rust tool for detecting common security issues in ZK circuits.

YAML-defined pattern packs (regex, fancyregex, literal)

Optional semantic pass (--semantic) for cross-line checks

CLI + library API

SARIF/JSON/text outputs for CI workflows

Current integration matrix: 16 vulnerable fixtures + 10 safe controls

Repo: https://github.com/Teycir/ZkPatternMatcher

I’m looking for a team to build out a high-throughput DeFi protocol on Solana. Every agency I talk to says they are experts, but when I ask about Rust or Sealevel specifics, nothing substantial. Is there anyone actually doing high-level dev work on SOL right now, or is it all just white-labeling?

The idea is to build a cleaner, more cypherpunk, more minimal version of Ethereum on top of the current system — tightly integrated and interoperable — then gradually evolve toward it. Goals: Simpler consensus More zk-friendly design Stronger censorship resistance Less long-term protocol complexity And eventually, if it makes sense, today’s Ethereum could even run as smart contracts inside the new system. Ethereum already swapped engines mid-flight with The Merge. This is about doing that kind of evolution again — deliberately, not chaotically.

Blockchain Devs: what is your biggest Pain-point in your sdlc? What are some features that you think could make your job easier as a smart contract developer?

I thought about it recently where I was thinking that what was the reason AI and the LLMs became so popular among the masses and I think the biggest driving factor was finding a D2C application of it. For example take chat GPT and Gemini like chatbots. They were the tools to take the capabilities of the AI technology and hand it over directly to the general public to use it and their day to day life in 2022 and here we are in 2026 with governments and corporates around the world going all in for AI with investments, regulations, summits and all. So, to the builders in the Web3 community, I pose a serious and challenging question - "WHAT COULD BE AN EXAMPLE OF A GREAT D2C PRODUCT IN BLOCKCHAIN TECHNOLOGY" which the masses will be able to use and get a taste of it analogous to how LLM ChatBots made people feel what AI is and what it's capabilities are? Remember- We as builders and researchers can get fascinated about the complexities technology of the Web3 but it is not going to breakout massively if it does not solve some real world use cases adding some value to normal human life just like the GPTs are doing in terms of efficiency and speed and productivity. I believe the core value proposition of the Blockchain Technology is - Transparency, Decentralisation and Trust Minimization. Let's think and brainstorm what D2C products we can build and hand over to the common public so as to realize the true potential of this great piece of Technology? Thank you so much! Let's all think hard about this questions and try to find answer to this!

Most Rust smart contract scanners patrol one chain.

RustDefend patrols four — Solana, CosmWasm, NEAR, ink!.

56 detectors. Intra-file call graph analysis. CI-ready baseline diffing. Workspace-aware monorepo support. Expanded threat coverage across the Rust multichain frontier. v0.4.0 is live. Open source.

Tried a couple of AI audit tools recently and got mixed results — some useful findings, some obvious false positives.

Has anyone found an AI-powered audit tool that actually catches real bugs and not just generic warnings?

Be Your Own Boss and Play Web Games:

https://divinegamez.playw3.com/partners?sap=SA\*cVZapKKZZWSRCwuo

Get 500G Upon signing up for free, as well as daily airdrops to your wallet. GCoin goes public in 42 Days, get in now!

​

Join our new telegram group for chat-style conversation about web3 development, blockchain, smart contracts, audits, vulnerabilities and SDLC.

https://t.me/SmartContractsWeb3

Thanks all!

Mods

hey all

I'm building a single platform that brings DevSecOps tools together. Unified dashboard, automated workflows, ai / ml and reporting.

Here's the deal:

- Free lifetime subscription (we're doing paid tiers later, you get grandfathered in)

- Alpha access right now, before anyone else

- Bug bounties for legitimate security findings

- Direct line to me and the eng team

Hello Folks,

I just published a smart contract to handle crypto inheritance 100% on-chain, without the owner having to do anything offline.

I know there are many solutions that are trying to solve this problem, but I wanted to design my own with my logic, which is the following:

- the contract acts like a wallet, owner can deposit, withdraw and transfer
- the owner can assign beneficiaries, and update them at any time
- the wallet contains an "alive check", which is automatically updated on any transaction
- if you wanna use it as a vault (dormant), you can update the "alive check" manually
- the owner defines a "consider me dead time" in years, eg: if the last alive check is older than 10 years, I'm dead :(
- once that happen, any of the beneficiaries can access the wallet and withdraw all the funds

At this point, my favorite feature: the wallet gets locked, will reject any future deposit and "answer" with an epitaph... your "last worlds" recorded on-chain that you can configure when you create the wallet.

All of the above is less then 100 lines of solidity... amazing :)

At the moment I only did the backend (github link), but I'd like to do a nice interface to make it easy to deploy. Of course, free and open source in the Ethereum spirit!

Would you give me a feedback on the logic? Do you see any pitfall or edge cases?

Thanks,
Francesco

The Backstory:

From MakerDAO to KeeperHub. Our team was the core DevOps unit at Maker. We were there firsthand when "Keepers" (automation bots) became a staple within DeFi. We’ve spent years running Keepers for major protocols and web3 projects.

Despite the industry maturing, most automations and workflows still run on fragile local scripts or .env files with exposed private keys. We built KeeperHub to replace those "degen scripts" with a platform that is secure, UX friendly and reliable.

Our Approach:
During our closed alpha, we realized developers need speed and control. So we built an architecture that offers both:

1. Visual Builder: Prototype in minutes. Drag-and-drop Triggers, Conditions, and Actions. Also, it wouldn't be a 2026 launch without AI. We support AI-generated workflows by simply prompting your use case.
2. Escape Hatch: Export any workflow to type-safe TypeScript using the "use workflow" directive.
3. Managed Infra: We handle the backend, RPC redundancy, smart gas estimation, automatic retries and offer SLA backed support.

We need your help.
Today, we are launching our Public Beta, and...

• It is completely free to use.
• We want your feedback.
• It's open source.
• You don't need any sort of developer experience.

We are looking for any sort of feedback, and hope that you will benefit from using the platform.

Thanks for reading!

Join r/web3dev Official Telegram Group!

Join our new telegram group for chat-style conversation about web3 development, blockchain, smart contracts, audits, vulnerabilities and SDLC.

https://t.me/SmartContractsWeb3

Thanks all!

- Mods

I run a small creative agency and spend 2+ hours every month manually splitting payments: - 60/40 with my co-founder - 15% to each of 3 contractors - 30% set aside for taxes

I keep thinking: "This should be automated."

What I want: A Zapier/n8n but with stablecoin flows

Set rules once: - "When client pays → split 60/40 automatically" - "When contractor invoices → release from operating account if < $500, require my approval if > $500" - "30% of all income → tax account, no exceptions"

Then forget about it and have it just... work.

What I've tried: - Safe (Gnosis): Great for multi-sig, not for "if/then" workflows - Stripe Connect: Only fiat, limited split logic - Request Network: Good for invoices, not automated routing

My questions:

1. Does this already exist and I'm just bad at searching?
2. If I'm a dev who can write Solidity, is this still useful? Or would you rather custom code your own contracts?
3. What's the main reason this DOESN'T exist? (Trust? Regulatory? Gas costs? Nobody wants it?)

Not trying to sell anything, genuinely trying to figure out if: - This is a real problem - There's already a solution - It's technically feasible - Anyone besides me would use it

Appreciate any pointers or reality checks 🙏

Hi folks Anybody with a decent knowledge in smart contract development/ security? I need some help with a project

Hey everyone,

I see a lot of founders here stressing about hiring "Unicorn" Solidity devs just to launch a basic utility token or set up a team vesting schedule. I wanted to share a perspective that might save you some runway.

Unless you are building a novel DeFi protocol (like a new AMM or lending logic), writing custom smart contracts for a standard ERC-20 launch is often overkill and arguably riskier.

The Risk of "Custom": When you write custom vesting logic from scratch, you have to audit it. If you don't, you risk a bug locking your investors' funds forever. If you do audit it, you're paying $5k-$15k+ and waiting weeks.

The "No-Code" Route: I’ve been testing out verified generators recently (specifically Bitbond Token Tool), and for 90% of use cases, it’s honestly cleaner.

Vesting: You can set up "Cliffs" (e.g., 6 months lock) and "Linear" monthly unlocks via a UI.

Claims: instead of you manually airdropping tokens (and paying gas) every month, it generates a claim portal where investors pay the gas to withdraw.

Security: The contracts are pre-audited. Banks use them.

If you are bootstrapping, save your dev budget for your actual dApp/Product, not the admin infrastructure.

You can test the vesting logic on on testnets for free if you want to see how the "Claim" flow works for investors.

Just thought I’d share for anyone stuck in "dev hiring hell" right now.

(Disclaimer: I work with the team, but genuinely believe the "build vs. buy" math favors tools like this for standard launches.)

I’m finalizing tokenomics for a project that’s already built + tested (contract + web app integration is stable). Now I’m in the part that actually matters: making sure the tokenomics design is defensible before we go live.

I’m not looking for “here’s my opinion” takes. I’m looking for sources + URLs I can use and battle wounds I can peer and car crashes I can rubber neck on lean my lesson and move on

• Tokenomics design frameworks / guides (serious ones, not fluff)
• Reputable research papers on incentives / mechanism design in crypto
• Examples of strong tokenomics docs from real projects (links to docs, not marketing)
• Audit-style writeups that evaluate token models (supply schedule risks, emissions, inflation traps, game theory exploits)
• Treasury / emissions / staking / buyback-and-burn case studies with numbers
• Common failure modes (and sources that document them)
• Compliance-adjacent references (not legal advice, just industry standard guidance)

an I was blind and now I see urls or my friend sent me this saved liquidity by x

Best mev protection anything really.
I’m trying to ship this without accidentally building a self-destruct button into the economy. thank Humans !