A long time ago, I mentioned a tool called Cquisitor cardananium.github.io/cquisi… here. It has now been updated with a more convenient UI and some new, cool features. It can now:

New in CQuisitor: CDDL Tool • Edit a CDDL schema next to CBOR, validate live • Parse & mismatch errors mapped onto both schema and bytes • Hover/pin links schema ↔ hex ↔ decoded JSON ↔ tree • All Cardano era schemas one pick away, Conway bundled • Auto-detects the root rule • Shareable links cardananium.github.io/cquisi…

Cool! 🙌

This is a really impressive tool. Cardano DevEx is rapidly ramping up.

Anyone who used taptools heavily, please reach out! This is still very early, but I'd love to hear how you used taptools, and what would bring you to Float every day. float.sundae.fi/SUNDAE

Some things we do just for fun. Some people collect pokemon cards, others build cars piece by piece. As for me, sometimes I write random tools just out of curiosity—to see how realistic it is to build something. So, meet a UPLC → Aiken-like pseudocode decompiler, available directly in Cquisitor. The decompilation quality can be a bit rough around the edges, sure - but where else have you seen something like this before?

Updates to DE-UPLC: You can now profile your favourite UPLC code directly in DE-UPLC. As always, you can share your debugging session via a link. Don’t forget to star: DE-UPLC: cardananium.github.io/de-upl… CQuisitor: cardananium.github.io/cquisi…

Big day for de-uplc: it has now migrated to the web, so you no longer need to install an vs code extension to debug your UPLC code. Everything can be done in the web app: cardananium.github.io/de-upl… In addition to the previous functions of de-uplc, it can now debug random UPLC code without needing any transaction context. But it wouldn’t be a big day without integration with CQuisitor: there is now a button that navigates to de-uplc to debug a specific redeemer in its transaction context.

Additionally, CQuisitor can now detect usage and decode datums from the following projects: SundaeSwap Minswap WingRiders Splash MuesliSwap Genius Yield VyFinance SaturnSwap CSWAP Chakra ChadSwap SnekFun Danogo Liqwid Finance Lenfi FluidTokens Levvy Indigo Protocol Butane Djed Optim Finance Strike Finance Charli3 Orcfax JPG Store The list of projects is a bit eclectic — I was just experimenting and having fun. Except for SundaeSwap support — for that, you already know who to thank (Just check previous tweets). Detection and decoding may be limited for some projects, but you can always open a PR to CQuisitor or DM me.

More features for CQuisitor: 1. You can now inspect the script context for each script. 2. Load on-chain transaction CBOR directly in the CQuisitor interface. 3. View script trace logs in the Plutus scripts tab. 4. See asset details for each asset in a transaction. 5. See formatted asset amounts in decimals. 6. See how much of the total execution unit limits are used in the transaction. 7. Paste a missing signature and submit the transaction directly in the CQuisitor UI. 8. See the divergence of the validity interval from the local time. Big kudos to @Quantumplation for: Script context inspection Script trace logs Execution unit limits usage Missing signature paste and transaction submission Validity interval divergence from local time

Bro tool reference in CQuisitor. If you’re tired of CQuisitor or want to check an alternative view, you can now go directly to Tx Studio by @Ryun1_ and check your transaction there. Both tools are great.

A week of great updates for CQuisitor: it now supports Blockfrost. Blockfrost has some limitations from a data-providing perspective, but it’s still a solid alternative. Extra huge thanks to @Quantumplation for adding it!

More cool features on CQuisitor: it can now decode and display SundaeSwap-relevant data.Huge thanks to @Quantumplation for implementing this.

🤝

Transaction Studio 🤝 Cquisitor new share button to open transactions in Cquisitor from transaction.studio/

Small but gorgeous updates to CQuisitor: 1. If a CBOR payload is invalid, CQuisitor can now show the partially decoded payload with error highlighting. No more guessing where it was encoded incorrectly. 2. The tool now shows warnings when a CBOR payload uses non-canonical encoding.

Now in CQuisitor, you can share your CBOR with a link. Sometimes you come across a funny transaction or CBOR and want to share it with your friends, colleagues, or family—like it’s the latest meme. But honestly, if CBOR makes you laugh, you might need to see a doctor… and definitely take a vacation.

I have one more tool to mention that could be very useful for developers who want to debug UPLC code in the context of a transaction. It is called DE-UPLC. github.com/cardananium/de-up… DE-UPLC is a VS Code extension that provides a convenient UI for working with UPLC’s otherwise rather inconvenient CEK-machine-based execution model. The extension uses a modified UPLC representation that preserves more information than the usual textual UPLC view. It also provides convenient debugging features such as breakpoints, step-by-step execution, and other familiar UI tools. In addition, it can display the machine state, machine frames, transaction context, and CEK-machine environments. The workflow is straightforward: you simply open a transaction hex file in the extension and choose the redeemer whose script you want to debug. The latest .vsix file can be downloaded from the GitHub Releases page: github.com/cardananium/de-up… This project is quite experimental but if DE-UPLC looks useful to you, please give it a star on GitHub — it really helps the project.