Solution: We propose a series of videos to be uploaded on youtube explaining the technical concept of it assuming no background experience in blockchain (though targets are developers)

Solution: This proposal assumes the approval of the ledger and network proposals, the goal is to build a successful and testable consensus module that can be reused across multiple purpose-specific nodes.

Solution: cardano-ledger-ts is already solving this problem, this proposal covers some more work to integrate past cardano ledgers and future new ones keeping compatibility with other projects (such as plu-ts).

Solution: The goal is to have a module reusable on any js runtime for node-to-node and node-to-client direct comunications, ultimately allowing for Cardano light clients in future.

Solution: plu-ts is an eDSL for Typescript and Javascript developers. It targets respectively the 5th and the first most used languages between professional developers according to stackoverflow.

Solution: CIP-113 is the closest to a standard we can adopt at the moment.

We propose to review and complete the latest version to allow better dev experience and implement a library for creating these assets.

Solution: A centralized server and client implementation, that connects to a cardano-node and keeps track of utxos that are "about to be spent" (via a virtual mutex on a utxo: mutexo)

Solution: We propose to prototype a radically different approach to allow for AMM swaps in a single, deterministic Cardano transaction.

Solution: We will "un-embed" plu-ts from typescript for it to be a proper compiled language. The goal still to be to use a syntax as similar as possible to typescript.