Second release today @pebble_lang v0.4.3 is out with better support for generic and recursive struct definitions github.com/HarmonicLabs/pebb…

I can definitely recommend!

As part of the @pebble_lang milestone, I have to write a few contracts of various complexity to demonstrate Pebble working. While doing so, I thought it would be fun to deploy one of them on mainnet such that everyone could try it out. So let me present to you: TheCardanoMasterpiece.com This is a 1008x1008 collaborative art project, where the full image is stored onchain (yes, the full megabyte) and replicated on ipfs, with the smart contract validating the ipfs link matches, fully onchain, fully trustless. The way it works is simple: - mint an ownership NFT - draw on it (load an image) - submit the transactions onchain, and watch the collaborative art take shape. The initial price is 2.5 ADA per pixel; however, the price to claim will likely increase as the supply of unclaimed pixels decreases. Once all pixels are claimed, you can list and buy ownership NFTs on the marketplace if someone else has listed them. Have fun.

v0.4.0 was deprecated in favor of @pebble_lang v0.4.1 with some important bug fixes

v0.3.7 turned out to be v0.4.0 @pebble_lang 0.4 now fixes many miscompilation bugs reducing execution costs (matching or slighthly outperforming aiken on average) Introduced `redeemerof` keyword to help with composability between contracts github.com/HarmonicLabs/pebb…

Impressive that current models can one-shot a contract in pebble Not the most optimised contract, but not too bad either, it even prevents double satisfaction (which early models definitely always ignored). This used to be hard a few years back, and at the core of major businesses like jpg store.

.@pebble_lang v0.3.6 is out, with several bug fixes, reducing compiled script size github.com/HarmonicLabs/pebb…

published @pebble_lang v0.3.2 with some bug fixes check the changelog: github.com/HarmonicLabs/pebb…

Pebble 0.3.1 is out! Introduces optimisations targeting the *new PlutusV3* (upcoming hardfork) With cost reduction up to -40% in CPU and -50% in memory pebble.harmoniclabs.tech/Ins…

Would you go to token2049 if there was a Hackathon with a prize for building with @pebble_lang ?

How it feels to wait for pebble to reach 67%

Some even juicier optimizations coming up with @pebble_lang targeting plutus v4 Pebble is not only easy to write and read, but it's probably the best choice if you care about efficiency Make sure you vote YES for it

Upgrading @pebble_lang to target PlutusV4 Make sure your DRep votes YES to get pebble ready to be used in production.

We appreciate @Cardano_CF voting yes on the Pebble & Tooling maintenance proposal We hope the other DReps who showed support previously will still choose to support us once again so that we can get started working on it 🙏

Planning to release pebble 0.2.0 tomorrow Will introduce: - initial support for unit tests + property based tests - namespaces - better support for generic functions - better support for interfaces If you would like to test it out check out the installation process

Starting to implement some low-hanging fruit that is specified in the first milestone of the pebble proposal In the next version of @pebble_lang you will be able to define contract states (datums) and spending methods only for that state (state transitions) With pebble, you don't need to worry about matching datums and redeemers You can just focus on your contract logic

Both proposals have been submitted In an effort to contain treasury spending we have reduced our base ask by 125k USD *per proposal* 250k USD less in total We also reduced the contingency from 25% down to 15% We need all the community support we can get, don't wait to vote, we can't wait to start working 🫡