OpShin | Python SCs

Cardano Smart Contracts in Python.

You want it. You buidl it.

$opshin

[OpShin | Python SCs @OpShinDev]

Did you know? OpShin solves one of the biggest challenges on #Cardano - onboarding new developers.

Traditional Cardano SCs are written in Haskell, known to 0.67% of developers. OpShin lets you write them in Python, known to a whopping 25% of developers!

More? 👇

[OpShin | Python SCs @OpShinDev]

Its *just* a patch release 🐍😓

[OpShin | Python SCs @OpShinDev]

OpShin 0.27.2 is out, with a variety of important bug fixes and convenience features:

- Mutual recursion and forward references now work
- A rewrite of the Union-handling and optimization framework
- Various smaller bug fixes

Enjoy!
https://t.co/39WqZhqpsX

[Cardano Foundation @Cardano_CF]

Cardano just got programmable tokens at scale.

With CIP-0113, token issuers now have a standard to enforce compliance logic directly to native Cardano assets.

The framework is modular, open source, and live on the Preview testnet.

Learn more:
https://t.co/KYSq3yOXGx

[OpShin | Python SCs @OpShinDev]

OpShin 0.27.2 is out, with a variety of important bug fixes and convenience features:

- Mutual recursion and forward references now work
- A rewrite of the Union-handling and optimization framework
- Various smaller bug fixes

Enjoy!
https://t.co/39WqZhqpsX

[OpShin | Python SCs @OpShinDev]

@cschmitz398 new smart contract language for midnight needed?

[OpShin | Python SCs @OpShinDev]

@phil_uplc Front-running attack on MinSwap exploited lexicographic ordering, which can be mined by just changing some random metadata to change the hash.

https://t.co/ndtAAHqsbM

[OpShin | Python SCs @OpShinDev]

@rvcas cross reference to recent AGI claim by LeCun etc al., not meant as a shot towards your Plutus VM implementations (which are great!)

[OpShin | Python SCs @OpShinDev]

@JaromirTesar Great

[OpShin | Python SCs @OpShinDev]

Is there interest in a ZK Cardano SC framework accessible from Python? Aiken? We played around and built a POC a few years ago, and might pick it up again if there is interest in the community.

[Giovanni - EASY1, Midnight & World Mobile Operator @CryptoJoe101]

I am usually very critical when I present something and often unhappy with the result of the presentation, but today, beside a couple of minutes of mixing up tabs and not finding a script hash, I think the presentation was a banger.

Thanks to all the people that attended and asked questions. Thanks even more to the people like @OpShinDev and @_KtorZ_ that gave me feedback and suggestions.

Tonite I found some time and vibe coded all the improvements recommended today during the session, in particular:

1. split the verification page into it's own page and route
2. enhanced the verification page to allow for "deep links" ie a special link that pre-load the verification page with all the onchain details required to verify a contract. it also immediately runs the verification, apply parameters and give you the results of the verification.
3. added deep-link sharing button in the result page. for easy access and share
4. added the value of the params applied in the script in the result page.

As part of this redesign, a new landing page has been implemented with a summary of the features, a quick search, and catchy stats to check the progress of how many contracts/hashes/repos have been verified.

The new Landing

Script Parameters

Deep Links

https://t.co/L0zeQr5fZk

Let's go!

[OpShin | Python SCs @OpShinDev]

@CryptoJoe101 @Cardano feature request: can you show the parameters for scripts in the registry? the final missing link for complete transparency (and not private anyways to anyone who can read UPLC)

[OpShin | Python SCs @OpShinDev]

@CryptoJoe101 @aiken_eng We can always write up a postfactual CIP if needed. but I don't necessarily see why standardization is needed at all and writing a CIP *will* cause philosophical discussions about your approach that distract you from buidling.

[OpShin | Python SCs @OpShinDev]

@CryptoJoe101 @aiken_eng Recommendation: don't wait until a CIP is accepted. Just buidl it and then ping the chain explorers to use/refer to your database.

Similar thing happened with https://t.co/xfgJYticV2

[OpShin | Python SCs @OpShinDev]

@CryptoJoe101 Thats very cool! OpShin currently does not define a standard yet on how to build the contract (other than aiken) but it could be as simple as a makefile.

[OpShin | Python SCs @OpShinDev]

Interesting proposal! Make smart contract matching to source code simple :)

[Giovanni - EASY1, Midnight & World Mobile Operator @CryptoJoe101]

🚀 First step of my first CIP 🎯

https://t.co/aSccOQ7Sic

@aiken_eng @helios_lang @Scalus3 @hlabs_tech for plu-ts @OpShinDev

[OpShin | Python SCs @OpShinDev]

@CryptoJoe101 @aiken_eng looks great

[OpShin | Python SCs @OpShinDev]

@FrankDeVriend @midnightexplr @IOHK_Charles @MidnightNtwrk @Bybit_Official check https://t.co/I4Hc4q80hz (thaws any random day between 10th Dec and in 90 days)

[Intersect @IntersectMBO]

Milestone Confirmed
OpShin – Smart Contract Tooling for Cardano (M1)

@opshindev, the Python-based smart contract language for Cardano, continues strengthening its foundation for dApp developers.

This milestone focused on fixing critical bugs and improving reliability across the codebase, ensuring developers can build and deploy smart contracts with greater stability and confidence.

A more dependable OpShin means faster, safer dApp development, supporting a stronger Cardano ecosystem.

🔗 https://t.co/0xTs1yK4Y2

Follow the full Delivery Assurance dashboard: https://t.co/qs4bVp2yNH

[OpShin | Python SCs @OpShinDev]

Check out and support these great proposals for OpShin SCs - now with Plutus V3!

[while0x1 @while0x1]

@krissbaird @Catalyst_onX @MidnightNtwrk 🫡

[Ales @berry_ales]

No matter how much we strive for perfect code, humans always make mistakes. What really matters is how a network responds when things go wrong, and how easily it can recover. And I think that's where Cardano shines.