10677
Paul Berg
@prberg #10677
Co-Founder at sablier.com, and open-source developer. I have a broad range of interests, including longevity, epistemology, physics, and psychology.
261021 Follower 154 Following
The Ghibli version of this meme is hilarious
Interesting findings about creatine
AI is wild.
I built the ByteGaze website in a few hours this weekend with Claude’s help.
Clean and responsive design powered by Tailwind CSS, dark/light mode, smooth animations, proper error handling—stuff that used to take me days, done in no time.
I built the ByteGaze website in a few hours this weekend with Claude’s help.
Clean and responsive design powered by Tailwind CSS, dark/light mode, smooth animations, proper error handling—stuff that used to take me days, done in no time.
I built a dev tool called ByteGaze — try it at bytegaze.vercel.app
You can use it for visualizing Ethereum ABI-encoded data in a human-readable format.
It detects 4-byte selectors and splits the rest into 32-byte chunks for easier analysis.
You can use it for visualizing Ethereum ABI-encoded data in a human-readable format.
It detects 4-byte selectors and splits the rest into 32-byte chunks for easier analysis.
Unsurprising — social media is great
Bad: Not using LLMs
Worse: Using LLMs and trusting everything they say
Best: Use LLMs critically—assume they're as fallible as any person
Worse: Using LLMs and trusting everything they say
Best: Use LLMs critically—assume they're as fallible as any person
Caffeine and alcohol dominate the drug landscape in Western societies at the moment.
But the design space of possible cultures is far broader.
A society shaped by psychedelics, for example, would likely be much more creative, peaceful, and tolerant.
But the design space of possible cultures is far broader.
A society shaped by psychedelics, for example, would likely be much more creative, peaceful, and tolerant.
.@safe should allow developers to build custom transaction interpreters, called Safe Lenses.
Like Safe Apps, but for decoding the ABI-encoded data on the transaction confirmation page.
There would be official Lenses, with the option to load custom ones as well.
Like Safe Apps, but for decoding the ABI-encoded data on the transaction confirmation page.
There would be official Lenses, with the option to load custom ones as well.
A table with the most common derivation paths for HD wallets:
Who's coming to ETHBucharest? 🇷🇴
Let's do a roll call 🙋♀️🙋♂️
Let's do a roll call 🙋♀️🙋♂️
Random Solidity tip:
Be careful when using immutables in the declaration of other constants or immutables.
The order of immutable variable declarations MATTERS.
Be careful when using immutables in the declaration of other constants or immutables.
The order of immutable variable declarations MATTERS.
It is a collective failure of our community that we kept using ERC-20 and its silly allowance mechanism.
The Pioneer's Dilemma
The impossibility of distinguishing true novelty from failed repetition.
As an entrepreneur, you can't know whether something failed because it’s fundamentally flawed—or because no one has done it properly, or at all, before.
The impossibility of distinguishing true novelty from failed repetition.
As an entrepreneur, you can't know whether something failed because it’s fundamentally flawed—or because no one has done it properly, or at all, before.
Are there any EVM chains that do NOT use the standard ETH denominations (wei, gwei, szabo, etc.)?
It'd be pretty cool if Chainlink offered a user-defined value type for their 8-decimal price feeds.
Similar to how PRBMath offers UD60x18 and SD59x18.
Similar to how PRBMath offers UD60x18 and SD59x18.
I wrote this little Git helper called `git done`:
1. You're on the feature branch `feat/foo`
2. The PR for `feat/foo` has been merged into `main`
3. With the alias below, running `git done` will:
Switch back to main.
Pull the latest changes.
Delete `feat/foo` locally.
1. You're on the feature branch `feat/foo`
2. The PR for `feat/foo` has been merged into `main`
3. With the alias below, running `git done` will:
Switch back to main.
Pull the latest changes.
Delete `feat/foo` locally.
If a web3 product deploys smart contracts for users, but those contracts are not open-source, there's zero accountability.
Neither customers nor the broader public can verify whether there have been any bugs in those contracts.
Neither customers nor the broader public can verify whether there have been any bugs in those contracts.
If your product doesn’t make it easy for users to request features or suggest improvements, you’re leaving a goldmine of feedback on the table.
I just found out about Biome — a dev tool that is both a formatter and a linter.
Bye, bye ESLint + Prettier setup 👋😊
Bye, bye ESLint + Prettier setup 👋😊
Some chains (e.g., Polygon) created a 'dual' ERC-20 representation of their native token (e.g., POL) to avoid a separate wrapper contract (e.g., WPOL).
Bad idea.
It's an unsafe design and it will 100% lead to exploits.
Bad idea.
It's an unsafe design and it will 100% lead to exploits.
Sablier has a Bug Bounty Program that pays up to $100k for discovering critical bugs in our smart contracts.
Link in the replies.
Link in the replies.
