An important update from us: paragraph.com/@apeworx/intro…

Pashov open-sourced Solidity Auditor v4, and I’ve ported its workflow for Vyper codebases The @vyperlang ecosystem deserves security tools that fit how Vyper projects are actually written and tested. So I’ve been working on two tools: vyper-auditor v4 and fyzz - vyper-auditor v4 brings the Solidity Auditor v4 approach to Vyper: 12 specialized sub-agents, loop mode for revisiting findings, persistent memory across runs, and a consolidated report. The workflow is adapted for Vyper codebases, with Vyper-specific syntax and security concerns in mind - fyzz is a port of Fizz for Vyper. It helps you write Hypothesis-based fuzz tests and invariants for your contracts, using the Vyper testing tools your project already relies on Link below 👇

evm party trick: expand memory, then run the cheapest possible loop. a full-memory opcode trace copies the same bytes millions of times. the 11-byte construction projects to ~10 tb of uncompressed trace at 16.78m gas. PUSH0 PUSH3 <32*w - 32> MSTORE ; expand memory to w words PUSH1 <loop> loop: JUMPDEST ; 1 gas DUP1 ; 3 gas: duplicate retained loop address JUMP ; 8 gas this gets us 3 trace frames per 12 gas. a worse construction uses k consecutive JUMPDEST, followed by DUP1; JUMP. it trades larger contract size for approaching one frame per gas. on paper this variant gets you toward 39 tb. i deployed and tested the 11-byte variant on mainnet. gas burn confirmed; trace size calculated: etherscan.io/tx/0xf207863778… for the adventurous: replay with debug_traceTransaction and enableMemory: true on your own node. start with limit: 100, removing that limit is the adventure. inspired by my earlier dive into evm trace blowups, and marking the new evm-trace release: banteg.xyz/posts/evm-trace/ github.com/ApeWorX/evm-trace…

Working on the keeper network for Pasanaku, this feature is going to be essential to making Pasanaku more of a set-it-and-forget-it type of protocol, rather than something that you have to constantly manage I'm using Silverback for this one. Silverback lets you create your own Python bots that respond in real-time to onchain events, and it's developed and maintained by the team at @ApeFramework Had to say, the documentation is really good, and I'm already testing the first workflows, I'll be sharing more on that soon

I've spent the last week learning a lot about staking algorithms, how they work, and most importantly, how they are implemented. In this article, I will guide you through creating your own Staking pool smart contract using Vyper

As of these updates, we've made it easier than ever for you (or your agents) to contribute to our packages! Please lend a hand where you can

As a reminder, ApeWorX maintains all of it's changelogs in release notes attached to the github repository for our repos Documentation updates to reflect this update in the changelogs will be made later

added contract verification inspired by @banteg's @ApeFramework sourcify plugin

Rate limits? API keys? tf are those? Just use ape-sourcify to automatically verify any contract you want automatically. 🦍 ❤️🐰

ape-sourcify is out 🦍 automatically verify solidity + vyper contracts, fetch verified sources and abis without needing an api key and install verified contracts as ape dependencies by chain and address. $ ape plugins install sourcify github.com/ApeWorX/ape-sourc…

love ape! thanks to @fubuloubu for introducing me to it

Oh hey we just noticed @JxyHelper gave us a 4th of July gift! 🎉 🇺🇸 Thank you so much you absolute chad ❤️ 🦍

🆙 @ApeFramework website & docs revamped nitter.net/ApeFramework/status/20… (1/2)

Oh did we mention we also updated our docs site too? docs.apeworx.io