KtorZ Profile picture
17 Nov, 13 tweets, 5 min read
It seems like many people in the #Cardano community, builders or not, still don't know about the #CIP!

So let me explain a bit, and quickly dive into some of them👇👇

CIP stands for 'Cardano Improvement Proposal' and refers to both a process and a collection of technical solutions to common problems of the Cardano ecosystem.

Proposals take the form of written specification files, hosted in a public code repository:

The CIP is geared towards the community and everyone is welcome to participate in the discussions.

There are different types of CIP for different purpose, some are informational (i.e. explaining how something work) and some are standards to facilitate interoperability.
A group of "editors" ensure that the proposed solutions are sound, organize the conversation with the community and enforce the correct following of the process.

Current editors include myself, @SebastienGllmt, Duncan, @ACryptoMuppet and @COSDpool.
The initiative started almost two years ago and there are now over 30+ accepted proposals.

For a while now, we conduct bi-weekly meetings open to all in crowdcast to go over the latest proposals and discuss them with their authors.

One particularly popular CIP over the past weeks has been the CIP-0030


which lays down the foundation for DApps <-> light wallets interactions.

This is what will make DApps seamlessly work with any of the wallets (provided they follow this standard!)
CIP-1852 has been around for a while as well, and is used by a lot of wallets (e.g. Daedalus, Yoroi, Adalite, Ledger, Trezor...) as a way to organize secret credentials...


Pretty essential! It also has several extensions nowadays, also CIPs.
Some are not necessarily complicated but are really about agreeing on details that makes interoperability easier between applications.

Like CIP-0005 which standardizes prefixes on encoded bytestring like "addr_" or "pool_"

Some are more specific to a particular use-case like CIP-0022 from @amw7 which details a protocol for securely authenticating an SPO to some other service like adapools, adascan or pooltool

CIP-0013 is another interesting one which defines a URI scheme for Cardano, like sharing a payment request or a delegation choice across two different applications.

It opens the door to many use-cases!

I am pretty excited to see wallets implementing something such as CIP-0018 to enable multi-delegation from a single wallet and allow users to maintain portfolios of stake pools!

All-in-all, if your are building on Cardano, there's a good chance that some CIP is relevant to what you do.

If you're doing something completely new, there's probably room for standardizing some parts it to make sure others may re-use or integrate with you!
In the long run, we hope to move more and more core decisions as CIPs like protocol changes or improvements proposals on the ledger, the mempool and whatnot.

It's a space for discussion and sharing. Fully open and in constant seek for improvements.

• • •

Missing some Tweet in this thread? You can try to force a refresh

Keep Current with KtorZ

KtorZ Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!


Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @_KtorZ_

6 Nov
Another hot and quite captivating topic these days is whether or not #Cardano needs a *fee market*.

I don't have myself a definitive answer for I think a large part of the answer is not software-related, but about economics.

Here's my two lovelace nonetheless... 👇👇 1/n
Firstly, why do we need fee at all on blockchains? For two reasons mainly.

(a) as a security mechanism to prevent spamming attacks against the network.

(b) as an incentive to pay those powering the network -- typically nodes, but in PoS, this also includes delegators!
On Cardano, fees can be mapped to physical quantities (e.g. bytes in storage, bytes in RAM, seconds of CPU time...) so that they make certain classes of attacks infeasible (too expensive). This is the case for tx fee, but also stake key deposits or Plutus execution costs.
Read 18 tweets
3 Nov
Does #Cardano need rollups (optimistic or zk)?

Probably not.

Rollups are a technical solution to a particular problem: cost of on-chain computation.

Rollups move on-chain computation off-chain, while keeping most of the traffic on chain.

This is crucial for Ethereum for which on-chain contracts have turned into large and complex programs that are very resource demanding.

Blockchains are *not* general-purpose programming platforms. They do poorly if one tries to execute its entire app logic on it.

Cardano addressed that from the start by taking a very opinionated, albeit unusual, road when designing the EUTXO model.

The on-chain logic is only about validation and is a lot less ressource demanding. Most of the DApp logic *already* happens off-chain, by design.

Read 6 tweets
18 Sep
Perhaps an unpopular opinion but, I truly dislike the wording "smart contracts".

I used to find it confusing when I first got into crypto years ago, but now I dislike it even more in the context of Cardano.

Compared to most existing smart-contract platforms, Cardano takes a much different road. Recently, we've seen a lot of discussions going on about "concurrency issues" and "EUTXO vs accounts". While equally expressive, Cardano programmability is different and atypical.
Cardano introduces the concept of programmable validators. Validators are fully deterministic: their result entirely depends on the transaction that carries them (= predictable fees).

In a sense, they are similar to the notion of "pure functions" in functional programming.
Read 10 tweets
2 Sep
Ethereum Arbitrum vs #Cardano #Hydra, a thread about Layer 2 solutions.

With the recent release of Arbitrum on Ethereum, and the upcoming Alonzo hard-fork on Cardano, there has been many discussions and comparisons about layer 2 solutions. As some knows, I've been working on Hydra with a few others for some months now and I want to shed some lights.
Firstly, what's Arbitrum and what problem does it solve for Ethereum?
Arbitrum is a mechanism that allows to move smart-contract execution out of the layer 1, in such a way that participants can put their trust in some chosen validators (a.k.a managers).
Read 26 tweets

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Thank you for your support!

Follow Us on Twitter!