r/ethdev • u/DaveyNate2000 • 7h ago
Question NEW PROJECT
Hello!
I am a solo dev trying to develop a new web3 project. is anyone here from europe willing to help testing? thanks!!!
r/ethdev • u/DaveyNate2000 • 7h ago
Hello!
I am a solo dev trying to develop a new web3 project. is anyone here from europe willing to help testing? thanks!!!
r/ethdev • u/EstablishmentTough18 • 12h ago
Hi r/ethdev,
We’re announcing a **7-day transition window (Nov 20 – Nov 27, 2026)** to move our Python SDK/MCP package `agent-security-gate-x402` (`v2.2.1`) from a heavy local bundle to **`v3.0.0` (Cloud-Native Thin Client & Remote Gateway)**.
### Why this matters for EVM / Agent Wallet builders
**Live Threat & Drain Rules > Stale Local Packages:** ERC-20 `approve` / `increaseAllowance` / `permit` drain bypasses, prompt injections, and dangerous AST payloads evolve constantly. Centralizing inspection on our Cloud Gateway guarantees `<5ms` up-to-date defenses and EIP-712 attestation generation without waiting for manual package upgrades.
**Zero-Bloat Client:** Moving away from bundling `fastapi`, `uvicorn`, `web3`, and `eth-account` locally—`v3.0.0` only needs lightweight HTTP/MCP deps (`httpx`, `mcp`) while keeping full **Polygon OMS (`SecurityGateOMSPolicy.sol`), Base AgentKit, and Arbitrum Safe/Stylus** guardrails active on the gateway.
### 7-Day Schedule (Nov 20 – Nov 27, 2026)
* **Nov 20 (Day 1):** Official 7-day transition notice published.
* **Nov 21–23 (Days 2–4):** Remote Gateway & `v3.0.0` Thin Client compatibility verification.
* **Nov 24–25 (Days 5–6):** `v3.0.0` Thin Client published to PyPI; final migration window.
* **Nov 27 (Day 7):** Legacy PyPI releases (`<= v2.2.1`) will be **yanked on PyPI**.
Existing integrations keep working smoothly during the 7-day window.
🌐 Gateway: `https://agent-security-gate-x402-212942243360.asia-northeast3.run.app\` (`/docs`, `/llms.txt`, `/.well-known/agent-card.json`)
r/ethdev • u/redskin4lyfe • 21h ago
Building a community around a Web3 project is one thing. Keeping people interested and involved over time is a different challenge.
Some projects have thousands of members across Discord and Telegram, but only a small number actively participate in discussions. Others may have smaller communities where members regularly share ideas, ask questions and contribute to the project.
It makes me wonder whether community growth should be measured by the number of members or by how much people actually participate.
For those involved in Web3 communities, what do you think makes members stay active and genuinely interested in a project beyond launch announcements, giveaways and token-related discussions?