cardano-serialization-lib VS CIPs

You will need cardano-serialization-lib for that. Check out their github repo: https://github.com/Emurgo/cardano-serialization-lib

Please allow me to introduce you PyCardano, a Cardano library written in Python. It allows users to create and sign transactions without depending on third-party Cardano serialization tools, such as cardano-cli and cardano-serialization-lib, making it a lightweight library, which is simple and fast to set up in all types of environments.

The Flint backend is open source (https://github.com/dcSpark/cardano-backend), the SDK we manage is open source (https://github.com/Emurgo/cardano-serialization-lib/) and the way the wallet works is documented via multiple CIPs (ex: https://github.com/cardano-foundation/CIPs/tree/master/CIP-0030)

Yes, that's dcSparks the team behind Milkomeda ( https://github.com/Emurgo/cardano-serialization-lib ), all thanks to them! Catalyst is great but I wonder why isn't IOHK financing this directly, because compensation for this kind of work through Catalyst is not great, considering how much a Rust dev can get in the market and work elsewhere.

Be aware of this issue if you try it.

But anyways, even none of the code examples they list on docs(https://docs.cardano.org/cardano-components/cardano-serialization-lib) or in their github repos(https://github.com/Emurgo/cardano-serialization-lib/blob/master/doc/getting-started/generating-transactions.md) work at this point. You can give it a try if you are interested. So I'll pause this project for a while, and report back as soon as it at least functions.

I think CHEFF is referring to https://github.com/Emurgo/cardano-serialization-lib

There are a few different Github repositories that server different things -- I'm not sure if there is a list of all of them. The job posting would mostly be related to https://github.com/Emurgo/cardano-serialization-lib and the network lib https://github.com/2nd-Layer/rust-cardano-ouroboros-network

> There are more downsides than that. The eUTxO model is not equivalent to accounts when it comes to its capabilities for building dApps.

> I explained it in more detail recently in a problem statement document for Cardano: https://github.com/cardano-foundation/CIPs/pull/874

I think I'm siding with Michele in this situation that what you describe as a problem is rather just a UX painpoint of UTXO and not a flaw or issue that needs to be fundamentally changed.

If you want to be able to coordinate to construct transactions you need to do it off-chain. The network can have standard systems for doing that or for verifying content (ex: DA-ed data that doesn't commit to L1) but any transactions that are settling on chain need to be 100% deterministic.

CPS-???? | Governance Security [New Problem]: This problem statement describes security issues to be considered by protocol governance CIPs.

The Lace team is already working with the community on how to find the best way to develop the CIP-72 - DApp Registration & Discovery. If you’re interested in taking part, contribute here

All mobile wallets have some kind of dApp browser, but there are no hard specs for how they should be run that is implemented at the moment. You might be interested in CIP72 if you're interested in standards for this topic more generally: https://github.com/cardano-foundation/CIPs/pull/355

CIP-???? | Extend token metadata for translations [New Proposal]: This proposal defines an addition to CIP-25 | Media NFT Metadata Standard to support more languages than English.

If you wish to add your perspectives to CIP 1694, make sure to share them here. Add your voice as the era of Voltaire rolls out!

Last week, a community-led roundtable took place on the topic of CIP-1694. You can catch the recap and outcome in last week’s newsletter or this Cardano Forum recap here. Worth a read.

Conditions inside a native script (but there is a CIP for changing this here)