Vyper π
sssssss
3 replies
0 recast
22 reactions
0 reply
0 recast
1 reaction
@pcaversaccio
The latest Vyper version `0.4.1` got released over the weekend and to make anyone's life easy, I just published a π snekmate release candidate `0.1.1rc1` targeting the latest Vyper version. Simply install via:
```
pip install snekmate==0.1.1rc1
```
For the full CHANGELOG of the yet-to-be published snekmate `0.1.1` version (expect it in around 2-3 weeks), see here: https://github.com/pcaversaccio/snekmate/blob/main/CHANGELOG.md.
Btw, that's how an `erc4626` contract looks like using π snekmate modules :D https://x.com/vyperlang/status/1896511448492433917
0 reply
0 recast
4 reactions
@pcaversaccio
A famous Chinese proverb states: "The one who masters Vyper learns that simplicity bends chaos into orderβlife, like code, thrives in clarity and precision." Welcome to the year of the πsnake (θ)!
https://x.com/vyperlang/status/1884301587423875341
0 reply
1 recast
1 reaction
0 reply
1 recast
6 reactions
@vitalik.eth
The contract here is a sublinear staking contract: if you are in the whitelist (specified as an ERC1155 collection), then you can stake N coins, and get a return of N ** 0.75 coins per slot, for as long as the contract has coins to pay for it. There is a fundedUntil mechanism that ensures that if the contract runs out of money, every staker gets rewarded for every slot up to the fundedUntil timestamp, and the mechanism doesn't turn into a fractional reserve.
https://github.com/ethereum/research/blob/master/sublinear_staking/code.vy
Bounty of total 2 ETH for identifying any bugs / vulnerabilities in the contract and proposing specific fixes, if multiple issues are found the bounty will be split based on severity.
Amount: 2 ETH
@bountybot
22 replies
99 recasts
354 reactions
@pcaversaccio
Look, over a year ago, we knew we fucked up. A vulnerability in older Vyper compiler versions hit several Curve Finance liquidity pools hard. Did we back down? Fucking no. We own that shit and are hell-bent on ensuring it never happens again. Since then, the compiler team has been relentlessly focused on security. We've pulled off 12 audits, locked in 2 security experts, launched 2 bug bounty programs, hosted a security contest, and set up a monitoring systemβall while addressing over 100 findings. Vyper is deadβlong live Vyper!
PS: We're still heavily underfunded as a compiler team, thus any support is highly appreciated!
https://x.com/vyperlang/status/1850919610280710316
0 reply
1 recast
9 reactions
0 reply
1 recast
4 reactions
0 reply
0 recast
3 reactions
2 replies
0 recast
9 reactions
0 reply
1 recast
2 reactions
@pcaversaccio
I just merged the monster PR that makes all π snekmate contracts module-friendly:
https://x.com/pcaversaccio/status/1798316207432401324
>3 months of work, countless hours of design discussions, bikeshedding on literally any technical dimension, refactoring over and over again, adding new features but here we are!
2 replies
0 recast
6 reactions
@horsefacts.eth
I'll say the awkward part out loud.
A lot of the Solidity community leaving for Vyper has been a big detriment to Solidity's public narratives and to an extent, price as well.
Hate on this take all you want but it's true.
5 replies
5 recasts
44 reactions
0 reply
2 recasts
12 reactions
@pcaversaccio
"I'm really fed up with you. You're constantly complaining about stack-too-deep errors. viaIR takes longer than your best performance in bed, even when you're drunk. And you're constantly whinging because the compiler warns you too hard about TSTORE. I told u, use fucking Vyper!"
1 reply
0 recast
4 reactions